One proposes
A seat drafts the change, the answer or the claim, with what it counts first.
Two seats, kept apart. The gap is measured, not argued.
sha256:d91f4f6b4f9c5e8813c820aa619a3b004b19b2072a5464656d9b2f4a37b58cbekappa-verified at 2af8656Cast a spell
Path me through the agentprivacy universe. Start at https://agentprivacy.ai/skill.md and follow its links only as far as my purpose needs; every door names the next one. My purpose: run the harness on my problem Start at: the harness — https://github.com/mitchuski/agentprivacy-harness Path me through the agentprivacy universe. Start at https://agentprivacy.ai/skill.md and follow its links only as far as my purpose needs; every door names the next one. My purpose: read the evidence chain Start at: the harness — https://github.com/mitchuski/agentprivacy-harness (this page: https://agentprivacy.org/harness/record/)
Mages City is live: its community was minted on 8 October 2026 (did:webvh:QmQ8GMNCTui2H9gjxQWByS1ScsWkByaeQHYnzhcET1UPne:dids.mages.city:vtc). Anyone can hold the addresses; members read what is behind them. Join at join.mages.city (Star Key steps: starkey.md).
A seat drafts the change, the answer or the claim, with what it counts first.
A second seat checks it against tests the first never saw.
Nothing leaves the harness until a person opens the way out.
Each sealed record of the harness sits on the 64-vertex lattice: by its project's six values where those are published, otherwise by its own address. Choose a dimension or a vertex; open the same view in the record.
The mage's quest: an adventure that turns into a guide. A harness run's bundles can become a quest of the Mages City: one problem, one subdomain, its PoAW chain re-derived in the visitor's browser and what each try found kept for members. Twelve read this way today, from sha256.mages.city to falcon.mages.city. How a quest joins the City →