Register:Blog/Tag3 recordsSHA3-256 chainedhead
sha3:cc81ab662147c4cfc4bc168a4e4f3ef35fdf442cb3c1235e60bdd3107e6dc929IntactREC 0000HEADsha3-256
07b9ca31e5c2624f7519c1a64142b2c735cc8faa63aebcb0ddca353e050c3518prev:fa74ce319ee3RegisterBlogTag: infrastructure as code
Blog entries tagged infrastructure as code
Every blog entry tagged infrastructure as code, 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
dd78aed283141905a82290bfcc12f5e89e2cab67c292cdd0b5be5ba576cc36f6prev:07b9ca31e5c2REC 0002RELATED RECORDSsha3-256
cc81ab662147c4cfc4bc168a4e4f3ef35fdf442cb3c1235e60bdd3107e6dc929prev:dd78aed28314Related 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.