Register:Blog/Tag3 recordsSHA3-256 chainedhead
sha3:c33dda6576bc38dd61f3222aaa2034c532ab38296867b8f58b3bc8c8f99332eeIntactREC 0000HEADsha3-256
a5cf21e5eb55ee81914de4044c2a4609a34db6111e84fa1a2c9be599794e35e1prev:0ddccd7f3406RegisterBlogTag: GCP
Blog entries tagged GCP
Every blog entry tagged GCP, 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
97d22f9198a854c2de1ceebf29b46e0e299769e4ddf18c2a49937af4d25f874aprev:a5cf21e5eb55REC 0002RELATED RECORDSsha3-256
c33dda6576bc38dd61f3222aaa2034c532ab38296867b8f58b3bc8c8f99332eeprev:97d22f9198a8Related 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.