InkTrail — the traceability layer

The record that
writes itself.

InkTrail is the receipt for how a piece was actually written. Every meaningful move — sealed as you work, verifiable by anyone. When somebody asks how you wrote it, you show them instead of explaining.

What it is

An authorship record. Not an audit trail.

Audit trails record everything. InkTrail records what mattered. The saves you kept. The AI you consulted. The suggestions you accepted or declined. The drafts you finalized. Autosaves, cursor movement, and routine formatting stay noise — because a record of everything is a record of nothing.

Every entry is cryptographically linked to the one before it. Change any past event and the chain breaks — visibly, to anyone verifying. There is no silent rewrite. Anyone with the link can check the record at a public endpoint; no RedInkAI account required, no trust in us required.

Because “trust me” is not a governance answer.

What InkTrail records

Six kinds of move. Every one on the record.

Meaningful moves only. The decisions that shaped the piece. Not the keystrokes.

You saved a draft

Every draft you keep is on the record with its content hash, timestamp, and author. Autosaves and cursor movement stay noise.

You asked the AI something

The prompt you sent, the guidance it returned, and which model answered. Not for surveillance — so a reader can see the questions that shaped the work.

You accepted or declined a suggestion

Adopt, dismiss, or edit-before-adopt on any Redline note. The choice is on the record with the exact suggestion it acted on.

You imported an external edit

When another editor or collaborator returns your draft, the round trip is recorded — who touched what, when, and what changed.

You finalized a draft

The moment you mark a version as final, the whole chain up to that point becomes independently verifiable. Anyone with the link can check it.

A rule you set was breached

If a suggestion violated a constraint you established — no new characters in the final act, no profanity, no touching Chapter 12 — the breach is on the record alongside the rule.

What InkTrail does not record: autosaves, cursor movement, panel opens, routine formatting, ordinary spellcheck acceptance, or time-on-screen. A record of everything is a record of nothing.

Why the two together

Redline makes the draft stronger. InkTrail proves you made it.

An audit trail on a weak draft is a receipt for a piece that didn’t deserve the ink. A stronger draft nobody believes you wrote is a defense you can’t give. You need both.

Redline is the reason a writer stays. InkTrail is the reason a reviewer trusts. Together, they are the moat.

The contract

Four rules InkTrail follows.

01

Meaningful moves only.

Autosaves, cursor movement, routine formatting, and panel opens are noise. InkTrail is a record of the decisions that shaped the work, not a keystroke log.

02

AI proposed vs. you authorized — never collapsed.

When you accept a suggestion, the AI stays credited as the origin of the words. Your authorization is the accountable event. The two are structurally distinct.

03

Tamper-evident by design.

Every entry is cryptographically linked to the one before it. Alter any past event and the chain breaks — visibly, to anyone verifying. There is no silent rewrite.

04

Independent verification.

Anyone with the link can verify the record at a public endpoint. No RedInkAI account required. No trust in us required. The math checks itself.

For the technical reader: how the hash-chain is constructed, how deterministic classification decides what qualifies as an accountable event, and how independent verification works end-to-end.

Read the architecture deep-dive

Start writing with a record that keeps itself.

Free to start. 25 guidance credits. No card. When someone asks how you wrote it, you show them instead of explaining.