Documentation
Docs & audits
These are the documents that ship with the package, rendered verbatim rather than rewritten. The limitations file is the one to read first.
Product documentation
- README
What the product is, the three disciplines it enforces, and how to run it.
- Known limitations
Read this before relying on anything. A limitation documented here is worth more than one discovered by opposing counsel.
- Data protection
What is processed, whose it is, the erasure argument, and the DPIA input pack. Read it before your first seal.
- Operations runbook
For whoever gets paged. This system fails quietly; every procedure here turns one of those silences into a signal.
The audits
Four independent adversarial audits were commissioned against this codebase: cryptographic, application security, enterprise readiness, and data protection. Between them they produced 86 findings, including three that invalidated the product’s core promise — report content read from an unsigned channel, Merkle inclusion proofs accepted without checking the path, and a PROVEN grade that was unreachable while a fabricated timestamp satisfied quorum.
They are published here in full, opening verdicts included. Every one of them begins by saying no. Publishing the criticism alongside the fix is the only version of this that is consistent with what the product claims to be.
- Remediation status
The disposition of all 86 audit findings, stating what was implemented versus documented.
- Audit — cryptographic
Adversarial review of canonicalisation, Merkle proofs, anchoring and what the signatures actually protect. 24 findings.
- Audit — application security
Hostile-input review across every parser, the rules directory as a trust boundary, and the agent surface. 23 findings.
- Audit — enterprise readiness
Would an enterprise know if this silently stopped producing evidence? Durability, observability, scale. 17 findings.
- Audit — data protection & compliance
The audit that produced DATA-PROTECTION.md, and the over-claims register that removed three claims. 19 findings.
Machine-readable
/llms.txt — product description written for a model that will answer questions about this product without reading anything else, with the limitations section as its longest part.