Register:Blog/Tag3 recordsSHA3-256 chainedhead
sha3:05943c5a8ecebba1ffffab95149d96d9b4c1379d805b5717e6744d75749a817fIntactREC 0000HEADsha3-256
e8719f91976679151c34152848d1ecd6078a7a886596b97adbc391b898c14a1bprev:df644f4a02a2RegisterBlogTag: compliance automation
Blog entries tagged compliance automation
Every blog entry tagged compliance automation, 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
d27675dc6f94cb7d6c78786724103e8528e5210daffcde79d1d3f51f6e3f4e41prev:e8719f919766REC 0002RELATED RECORDSsha3-256
05943c5a8ecebba1ffffab95149d96d9b4c1379d805b5717e6744d75749a817fprev:d27675dc6f94Related 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.