Redline
Two versions. A reviewable account of what changed.
Load both versions and the engine produces the numbered revision list — the current passage, the proposed passage, and the reason, grounded in the exemplars' practice or the governing rules.
- Material-change detection with the explanation an associate would owe you.
- Exemplar-grounded litigation redlines cite the convention the change follows.
- Every revision is adjudicable — nothing merges without your ruling.
Work happens in the workspace — matter-bound, governed, and on the record. Sign in inside if you haven’t already.
Fictional litigation example
Compare the relief before and after counsel’s ruling
- Start with
- The original motion and the proposed revision, identified as separate versions.
- Inspect the result
- A comparison showing the narrower demand and removed intent allegation alongside the factual account that remains unchanged.
A comparison explains changes; it does not adopt them or establish that a cited rule applies.
Explore this stage in the fictional motion story →What the desk does
A grounded comparison of two versions, measured against the exemplar set's practice as well as against each other.
- Deterministic text diff for the mechanics of the change
- The exemplar spine for the practice comparison
- The same integrity guards as the draft and review desks
What the desk refuses
- Two readable documents are required; a scanned image without text is refused
- The desk reports effects; it does not choose a position
- Running a paid desk without an active session, a trial allotment or a covering purchase. Sign in, use the trial allotment, or purchase the matter.
- Drafting, reviewing or redlining a document for which no lawful exemplar lane is live. Choose a document type with a lane, or wait on the named owner item (a keyed connector or a reviewed pack).
- Output that lifts verbatim runs, or too much scattered overlap, from the exemplar filings. The run is refused and reported; the engine drafts afresh on the same pinned exemplars.
- Output that carries the exemplar filings' party names into the matter. The run is refused and reported; the attorney never sees a foreign party in the draft.
- A dual-engine consensus that swallows a material disagreement between the engines, or names it without binding a disposition to its issue id (a missing, duplicated or unknown id, a bare marker, or a conflict marked decided). The divergence is carried as a decision card bound to its issue id; the attorney adjudicates it.
- Delivering single-engine output when a dual run was purchased and one engine failed. Retry, or run the standard lane knowingly.
Inputs
- Two versions as files or pasted text
- The document type and governing state
- The purchased matter, carried in the link and the browser context from the last desk
Outputs
- The comparison report
- The marked redline export
- The adjudication trail
Every output is for review until a recorded decision puts it in the record.
The three states every desk speaks
- In the record
- Decided, approved or verified, and written to the decision trail; it can be exported as the approved version.
- For review
- Produced by an engine or a person and not yet decided; generated is never approved, received is never reviewed.
- Not cleared
- Refused, blocked, unverified or unreadable, with the reason stated; unknown is never zero.
Capabilities and limits of the redline desk — the generated reference, dated by release.