Table evidence and origin

Read retained source support and recognize when edits invalidate the basis.

A table accepted from a captured-document draft can retain a source basis that connects saved row identities and columns to the draft's captured documents and evidence. This allows a cell to open the exact retained source used for the accepted value.

Inspect a cell

Select the cell's evidence action. Read the quote, source name, available location, and captured-document details. Open or download the retained source to verify context, units, dates, and ownership of the statement.

The captured bytes are checked against the saved content hash and size. A missing or altered capture is not replaced with the latest source file. Treat a verification failure as unavailable evidence.

Revisions matter

Evidence is bound to the saved table's schema and data revisions, row identity, column definition, and value. Manual changes can invalidate that relationship. A previous citation must not be presented as proof of a newly typed value or redefined field.

A legacy table or manually created table can have no captured basis. Strive does not infer one from filenames currently present in the App. A value displayed beside a document is not automatically an evidence-backed extraction.

Origin is broader than a quote

A schema proposal can describe where a table definition came from, while the saved source basis establishes the captured documents used for particular accepted values. A workflow result's provenance identifies its producing run. Each answers a different question.

Source validation establishes support in parsed text under the extraction rules. It does not prove perfect OCR, correct domain interpretation, or that every relevant field was found. Review consequential values against the original layout and wider context.

See citations and captured evidence, review and acceptance, and manual editing.