sub-modules
Audit Evidence
Answer the auditor's hardest question in one query — 'prove it.'
'Prove it' ends more audit meetings than any other phrase — and most companies answer with a project: weeks of collection, interviews, and reconstructed timelines. Audit Evidence makes the answer a query instead. Every mutation seals actor, policy decision, and source digests at commit time, so the trail exists before anyone asks for it.
Evidence lifecycle
Each stage below seals accountability at commit time — nothing reconstructs after the fact from memory or scattered logs.
data Viz
data View
section: stages
Seal
Mutations bind actor, policy decision, source digests, and state transition into envelopes at commit. The seal is the proof, created when facts are fresh.
Trace
Lineage links envelopes into causal chains across domains. Any outcome traces back through every decision and event that produced it.
Disclose
Audits, investigations, and records requests run as structured queries with redaction applied. Responses carry their own provenance for challenge.
Evidence guarantees
- Actor binding
- ARGUS identity and policy-decision reference on every mutation
- Source linkage
- Input digests and source events cited inside the sealed envelope
- Causal lineage
- Timeline-X references enabling replay and downstream impact tracing
- section
- capabilities
Evidence by industry
Audit proof bends per industry — same sealed envelopes, different examiner expectations.
data Viz
data View
section: industries
Manufacturing
Device history with work-order lineage, inspection results, and operator identity per unit. Customer and regulator audits assemble from sealed events.
Government
Appropriation-to-outcome chains with authorization evidence per step. Sunshine and FOIA responses generate as redacted queries instead of document hunts.
Financial Services
Transaction lineage with policy versions and approval chains intact. Examiner requests resolve to envelope queries with lineage they can follow.
Audit Evidence questions
Section 1
What does an evidence envelope contain?
Actor identity, policy decision reference, source event identifiers, input digests, and the resulting state transition — sealed at commit time.
Section 2
How do public-records requests work?
As structured queries over sealed envelopes with redaction policy applied, instead of weeks of manual collection and review.
Section 3
Our auditors bill by the hour. Won't this transparency cost us more?
The opposite: auditors bill discovery hours hunting documents. Pre-assembled evidence collapses fieldwork to confirmations — ask any client who has lived both.
data View
section: faqs
content section
value: When an auditor asks who approved what and on which evidence, the answer is one query away. FOIA requests, sunshine-law reporting, and public-records obligations resolve through structured evidence retrieval — not manual document collection across departments.
Section 6
Evidence envelopes on mutating operations
Section 7
ARGUS actor and policy-decision binding
Section 8
Timeline-X causal lineage for replay and review
Section 9
FOIA and sunshine-law retrieval as structured queries