Audit and trace
Every access is on the record.
Every operation this demo performs, every page processed, every search, every governed read, is recorded into a hash-chained, tamper-evident audit log. Each entry carries the hash of the entry before it, so an edit, a deletion, or a reordering breaks the chain and becomes detectable rather than merely prohibited. This page publishes the proof.
The chain proof runs server-side, inside Edgent's boundary. Nothing on this page names a person: the public readout is aggregate by design.
Chain proof
Is the record intact right now?
The proof walks the whole chain, recomputing every hash link, including the sealed monthly archive segments. It reports the first break if there is one. What renders below is the live answer, not a claim.
- Entries in the chain
- Head anchor
- Recorded in the last 24 hours
What was recorded, by kind (last 24 hours)
Live
The chain, advancing
When anything touches governed data, the recorder announces that an entry was appended, and what kind, never its content. This strip listens to that announcement stream. Leave the page open, run a search or a scan in another tab, and watch the record grow.
Where the line is
What is public, and what is not
What is public
That the chain is intact, how many entries it holds, its head anchor, and how many accesses occurred by kind. That is the part which proves the log has not been altered, and it identifies no one: actors never appear on this page, and any operation shown here is attributed at most to an operator role.
What is held back
The entries themselves. Each one names what was touched and when, and a record-by-record feed on a public page would publish the platform's access patterns. Reading them requires administrator authority, checked on every request. This public surface has no sign-in, so it deliberately holds no credential that could stand in for one.
For the administrator
The itemized ledger lives in the governance workspace. The A4A demo
corpus lands under object keys prefixed cedms.; filter
the ledger's object field to that prefix to see exactly this
pipeline's entries, hash links and all.
Open the governance ledger Requires administrator sign-in at vforce.edgentllc.com
Why it is built this way
This is the audit and accountability posture NIST SP 800-53 asks for: entries carry the content of AU-3 (who, what, when, where, outcome), and this page plus the governance ledger are the AU-6 review path. The same mechanism, unchanged, is what a federal deployment gets.
Coverage
Recorded at every choke point
The recorder is not sprinkled through the code; it sits at the choke points every operation must pass. Each stage of the pipeline records as it acts:
- 1 Upload an archive enters the pipeline; the run and its source are recorded
- 2 Rasterize each page becomes an image; page masters land in governed storage
- 3 OCR a vision model reads the page under the governed model router
- 4 Classify document type, disposition and confidence are scored and recorded
- 5 Gold the governed row is written; every later read of it is itself recorded
The time each page spends inside the pipeline is already visible: the Runs page renders a per-page timing waterfall for any run, from the same recorded timestamps, so the choke point that is actually choking shows up as shape, not as a claim.