Register:Blog/Tag3 recordsSHA3-256 chainedhead
sha3:d3f5f5d8798f39ac71684623c3e79f3740911a131ab20a9a0033f6255aeea0c0IntactREC 0000HEADsha3-256
703f0245a64de91fa6789d4cc9d1cce38c4af3ad44c31e0335e55acf10e96b89prev:27f81db0b1bdRegisterBlogTag: compliance cost
Blog entries tagged compliance cost
Every blog entry tagged compliance cost, 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
d22b796ce4f43d76a63df46ad843bca593b7ee4dc01ee3b5bf82276da192269bprev:703f0245a64dREC 0002RELATED RECORDSsha3-256
d3f5f5d8798f39ac71684623c3e79f3740911a131ab20a9a0033f6255aeea0c0prev:d22b796ce4f4Related 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.