Chirograph — document processing that proves its work

Chirograph — document processing that proves its work.

Chirograph — an intelligent document processing platform by Locus Consulting.

One governed pipeline. Two front doors — for people and for agents.

Not yet available Chirograph is a working title, pending trademark counsel. The evidence panel below shows Indenture #0000, real evidence from the Chirograph product repository, not a live system.

Extracted. Validated. Recorded. Proven.

See it work

Recorded evidence Indenture #0000 — bootstrap — real Software Bill of Materials (SBOM), license, and extraction-pipeline evidence from the Chirograph product repository, not a simulation.

Indenture #0000 — bootstrap

Cut manually at repository bootstrap, deliberately before a dependency tree existed, so the first indenture Chirograph ever produced already carried a license verdict. Every build since has cut its own indenture automatically as part of the pipeline.

Extraction
Not yet recorded

Recorded — the extraction pipeline processed 3 sample documents (an invoice, a purchase order, and a receipt) and correctly extracted all 12 tracked fields.

Validation
Not yet recorded

Recorded — every extracted field was checked against a verified answer key; all 12 checks passed. A second extraction backend is defined but not yet connected, so only one pipeline configuration has validated results so far.

License / SBOM verdict
Recorded — Advisory (warn-only)
Scan tool
syft 1.50.0, SPDX (Software Package Data Exchange) JSON

Clean — zero dependencies, zero findings

Governing policy
License-admissibility policy v0.1.0 — Advisory (warn-only)

This scan ran in advisory (warn-only) mode. Once our internal policy review is complete, this same scan becomes a blocking gate that must pass before a release can go out.

What this panel shows, and why
Indenture #0000 — bootstrap carries a real license and SBOM verdict, cut against an empty source tree at repository bootstrap. The extraction and validation figures above come from Chirograph's most recent pipeline evaluation run, scored against a fixed set of sample documents — real, recorded results, not simulated ones.

About the name

A chirograph was a legal instrument written in duplicate on a single sheet, then cut apart along an indented line. One part — a counterpart — went to each party, and the document proved authentic when the two halves matched, answering to one another along the cut: the historical root of verification-by-correspondence, the same principle behind engraved check stubs and stock-certificate borders. Chirograph the product applies that same principle to document processing: every extraction is verifiable, every decision is on the record, and its two front doors are counterparts of one governed instrument (per the Chirograph product repository's naming documentation, docs/naming.md).

The mark echoes the same idea at the level of construction, not just meaning: two identical squares, overlaid 45 degrees apart into an eight-pointed rosette, are literally built by laying one shape over its own duplicate (per this kit's own mark rationale, wwwroot/brand/chirograph/README.md).

Glossary

Counterpart
One of a chirograph's two matching halves; in the product, one of Chirograph's two front doors — the human web application or the agent Model Context Protocol (MCP) endpoint.
Indenture
In the chirograph metaphor, the indented cut line itself; in the product, the evidence bundle assembled and signed at a promotion gate — see the demo panel above.
An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.