Redline

Redline shows the model’s edits to a document as tracked changes, word by word. Its insertions are pigment; the words it would remove are struck through in ink, because a person wrote them. Each change carries its reason, and is accepted or rejected in place.

Live specimen

The model proposed five changes to a break clause. Tap one to see why it made it. Accept the six-month notice and reject the plain-English rewording: accepted words stay in still pigment, rejected ones disappear.

Anatomy

When to use

  • When the model edits something a person wrote: clauses, policies, reports, emails.
  • When each change needs its own decision, because some are right and some aren’t.
  • For a figure or value, use Shift. For whole alternatives, use Fork.

Behaviour

StateInserted wordsRemoved words
OpenFlowing pigment, underlinedStruck through in ink
AcceptedStill pigmentGone
RejectedGoneBack to plain ink

Accepted words never turn to ink. Months later, the clause still shows which words the model wrote.

Best practices

  • Keep each change small: a word or a phrase, not a rewritten paragraph.
  • Give every change a reason with a source: “Matches the six-month notice in clause 4.2.”
  • Let people step through open changes in order, with next and previous.
  • Offer accept all, but never accept anything on the person’s behalf.
DoShow each change in place, with its reason.
Don’tDon’t replace a person’s clause wholesale. Nobody can see what changed or why.

Accessibility

  • Each change is a button named for what it does: “Change 3: replace ‘three’ with ‘six’”.
  • Inserted and removed words differ by strike-through and order, not only by colour.
  • Deciding a change announces the result and how many are left.

Specifications

Insertion
Pigment, 650 weight
Removal
Ink 2, 1.5 pt strike
Selected
1.5 pt tyrian outline
Reason card
Surface 2, below the text