Compliance Document Substrate
The complete system record. Choose the proof lens that fits your role.
Choose The Proof Lens
One system record, three reader paths.
The Document System Behind a Multi-Entity Company
Replaced scattered legal-document work with one API and CLI across 14 document types, while blocking dormant Nigerian Ltd from invoices.
Architectural Brief: Compliance Document Substrate
Fourteen document families share one renderer, while invoices, credit notes, pro-forma invoices, and resolutions keep separate service paths.
Reachable Is Not the Same as Correct
The docs CLI proved that a document type can be reachable while still bypassing the service that owns its legal behavior.
Legal Identity Is Not a Template String
Entity snapshots turned legal identity from template text into durable document state, including the dormant Nigerian Ltd constraint.
A Compliance Pipeline Should Not Be Polite
The invoice send path refuses to invent a valid-looking document when XML, PDF/A, or signing checks fail.
The Audit Trail Has to Be Recomputable
Each finalized document enters a per-entity chain so later verification can prove order, content, and tamper evidence.
The Hard Part of Numbering Is Failure
Document numbers are reserved before finalization, reclaimed after failure, and isolated by entity, type, and year.
Related Systems
More proof in the same problem space.
Financial Compliance Ledger
Append-only finance history
The append-only audit design essay shows how row ordering and locking protect historical truth.
Vendor Performance Intelligence Engine
Frozen supplier alert snapshots
The frozen tenant snapshot essay is the cleanest example of preventing later edits from rewriting old alerts.
SLA Penalty Settlement Engine
Replayable penalty evidence
Shows settlement records built around replayable math, paired rows, and disabled external clients by default.