Skip to main content
Foundry’s Output · Clause lineage sink compares each processed document’s clauses against the previous version and proposes a revision history: which clauses carried over, which were amended, which are new, which were removed. Proposals land unreviewed until a person confirms them. nora clause-lineage is the terminal surface for that review. Non-destructive throughout: the document text is never touched. Only the lineage labels (the relations between clause versions) are what you approve, correct, or drop.

Command groups

  • Browse: pending, by-block, by-document, pending-documents
  • Decide: review, reject, bulk-approve

Browsing pending proposals

pending

Every unreviewed proposal across every pipeline and document in the workspace. --limit caps rows (default 500).

by-block

Everything one out_clause_lineage block has proposed. --include-reviewed flips the default (pending-only) to include already-decided rows too.

by-document

One document’s revision history: every proposed relation between this version and its predecessor, plus pending items.

pending-documents

Roll-up view: one row per document that still has pending proposals, with a count. Handy for prioritising which document to review next.

Deciding

review

Confirms (or overrides) one proposal. --relation values: carried_over · amended · new · removed.

reject

Drops the lineage row entirely. The proposal isn’t accepted and isn’t recorded as reviewed either. Use this when the model paired clauses that shouldn’t have been paired at all.

bulk-approve

Accepts every listed row as proposed, with no relation override. Right for high-confidence batches where the model got everything right and you just want to stamp them all as reviewed.

Recipes

Triage: pick the document with the most pending items

Auto-accept everything a specific block proposed

Only run this if the block’s proposals have historically been correct. Bulk-approve is unrecoverable without re-running the pipeline.

Export pending queue to a spreadsheet

See also