Register:Blog/Tag3 recordsSHA3-256 chainedhead
sha3:7bb505aeedbef1c2a08363724cf09e952dd6bf6077abfea53ef7d396687f0569IntactREC 0000HEADsha3-256
918fc90d3d9ae65cad6c40f29ec5e6721f55dd720fde3d17318be3602ebfbe45prev:67274705d3beRegisterBlogTag: defense contractor compliance tools
Blog entries tagged defense contractor compliance tools
Every blog entry tagged defense contractor compliance tools, newest first. Tags group the register by subject so a reader working one requirement can follow it across entries as the rules change. Each entry is sealed on the date shown and amended in place when it is updated; the full register is at the blog index.
1 entry
REC 0001ENTRIESsha3-256
3c38f8f2d8c2498657f896ab085f7ff987deccf8e11a495c75701e0916ab31e1prev:918fc90d3d9aREC 0002RELATED RECORDSsha3-256
7bb505aeedbef1c2a08363724cf09e952dd6bf6077abfea53ef7d396687f0569prev:3c38f8f2d8c2Related records
Guides and articles describe the work. The evidence that work produces is described in three proof pages and one architecture page.
- proof.state
- Proof of State. What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
- proof.change
- Proof of Change. Who or what altered the environment, under what authority, with before and after state hashes.
- proof.agency
- Proof of Agency. What a machine was permitted to do before it acted, what it did, and what would have stopped it.
- architecture
- Architecture. How the chain is built and where it lives: inside your tenant, with no egress of evidence.
Read the entries. Then verify the record they describe.