Register:Blog/Tag3 recordsSHA3-256 chainedhead
sha3:397e502ae29478017e0703d75be5546529af343fe60d1d85899b41988010b90bIntactREC 0000HEADsha3-256
9ed3b00519a637212076b8e443d8b118cd33d519f211b300b6e9942ef08dffcfprev:9db16fc88752RegisterBlogTag: compliance monitoring
Blog entries tagged compliance monitoring
Every blog entry tagged compliance monitoring, 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
f2a785c7af66087e71f8578825b21aba9e5a6c9ba3083bfca64c673b7d637489prev:9ed3b00519a6REC 0002RELATED RECORDSsha3-256
397e502ae29478017e0703d75be5546529af343fe60d1d85899b41988010b90bprev:f2a785c7af66Related 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.