A 13-stage pipeline. Deterministic first.
Manifesto extracts, normalizes, and verifies every row before a reviewer sees it. AI is a fallback for ambiguous cases — never the engine.
Watch the 13-stage pipeline process a real contract
Coming soon — request a live walkthrough
13 stages, end to end.
Each stage is deterministic, versioned, and auditable. Failures cluster on document family — not random samples.
Metadata
The pipeline opens the PDF and reads the cover page to extract the contract identifier, carrier name, shipper, effective and expiration dates, and minimum quantity commitment. This data anchors every downstream row to the correct contract version.
AI is a fallback. Not the engine.
Auditability
Every row links back to the page, line, and tokens it came from.
Reproducibility
Pipeline runs are versioned. Reprocess and the diff is exact.
Explainability
Failures cluster on document family, not random samples.
Three states, made visible.
Every extracted row is scored against the PDF text that supports it. The result is one of three evidence states — surfaced directly on the row, not hidden behind a single confidence number.
This is evidence verification (does the PDF support the row?), distinct from benchmark verification (does the row match a template?) which is optional.
- verifiedStrong PDF text support.
- needs-reviewPartial or ambiguous support.
- weakMinimal or no text match found.
Built on infrastructure your security team will accept.
Cloudflare R2 for encrypted object storage. EU residency available on request. Read the security overview →
Questions from engineering teams.
What's the LLM used for?
Can we bring our own templates?
How are amendments handled?
How fast is a typical run?
Can we run it on-prem?
See the pipeline on your contract.
Bring a sample to the discovery call. We'll run it live and walk through every stage.