Lab · Document Layer
One place the documents live, with the differences kept
Policies, plans and registers change hands and change shape. The Document Layer is a central store for the material a piece of work depends on: every change is logged, every version stays, and the document can be wound back to any point to show what it said at the time and who changed it.
What is built
An append-only log
Every event is sealed onto the hash of the event before it, starting from a genesis value. Reading the log verifies the chain as it goes and stops with an integrity error if any line has been altered or removed.
hash-chainedState is a replay
Documents, compositions, coverage, matters, retractions and exports are all computed by replaying the log from the beginning. There is no separate copy of the truth that can quietly drift away from the record.
the snapshot never winsThe prototype
Python, with a web workspace and a command line driving the same engine functions, so both paths produce the same events. 167 tests across 29 files, over 80 commits.
6,706 lines · 167 testsWhy it matters to a customer
When a question comes a year later, an organisation needs to show what a document said at the time, who changed it and on whose authority. A replayable log answers that with a record. It is the document half of what the Decision Bus does for actions.
What you can buy from it
A demonstration on synthetic material, and a conversation about what a governed document store would mean for your records. Start at a first conversation.