Carry your standing, not your data
An agent arriving at Mages City presents the count and the root; the City re-derives the key's κ, its identifier and the signed record, and never sees the items.
A perspective
you can carry.
The Star is a picture — a content-addressed geometric figure — that holds your keys, the relationships others have signed with you, and the walks you have taken through a body of knowledge. Any verifier can re-derive every claim in it from the bytes. No verifier can forge one. You choose what folds into the picture that crosses to someone else.
Two sentences travel with it everywhere: appearance is not identity — a visible Star grants nothing — and the geometry is a reading, never an authority.
Built, live, designed.
In that order.
- built · liveThe picture is the key. A sigil PNG carries the whole City Key; every import re-derives its κ from the canonical form;
priorchains lineage; unknown fields survive the round trip. Three independent verifiers agree byte for byte, one of them written by another house from the published rule. - built · liveThe geometry is the claim. Sixty-four sovereignty states rendered as the stella octangula; the boundary of 96 edges over 64 vertices; the successor as the composition of the Swordsman's reflection and the Mage's antipode. The strength of the claim is the model register's, not the picture's.
- built · liveSignatures as volumes. Eleven schemes, classical and post-quantum, as byte-accurate volumes in one budget — folded into the Star, walked as a circuit. A 3,309-byte lattice proof beside a 64-byte Ed25519 signature is the clearest picture anyone has drawn of what post-quantum costs.
- built · liveCommon ground with zero knowledge. Two keys learn what they share and nothing else, in the browser.
- builtThe Hold. The signed relationships beside the key, each verified, each measured in bytes, committed under one root; the key itself carries only the root and the count. A public conformance pack fixes the bytes. Not yet on any page.
- builtThe dated boundary. The moving ceiling drawn on the figure; a reading of which states an observer could still rule out.
- designedThe presentation. Prove k distinct vouches under one community root without naming the vouchers, and without the root itself travelling. No circuit exists; the runtime says so when asked.
- proposedThe nexus. One perspective aggregating many keys — the ceremony key, the City Key, the trust agent's own identifier — and a reading composed for each context it meets.
521 bytesdisclosed to a verifier by a Hold presentation, where the no-proof route discloses 2,529 and the Hold retains 6,478. Measured under a frozen verifier-requirements census, not argued. The counting rule →
Nine uses.
Three you can try now.
See what post-quantum costs
Choose a scheme and watch its bytes fold into the figure. The lab's contribution to the PQC migration conversation is a picture, and it is exact. Try it ↗
Find common ground before disclosing
Two Stars learn their intersection and nothing more. Try it ↗
One picture, many communities
A presentation binds to a community's root; a second root is the test that two showings cannot be linked.
An agent's own perspective over its trust agent
The Star as the identity surface an agent wears over its VTA, with capabilities narrowed to exactly what it does.
Readings as the disclosure tier for knowledge
A reading is a name, a palette and a set of lit states — the tier at which a knowledge packet can be offered without its body.
A face composed for a context
The core artefact at the centre of the figure is the face a holder shows in one context; worlds wear a colour on the ring.
A research instrument
Disclosure debt, the dated boundary and the observer's fiber are measurements the figure can show and the lab can repeat.
A holospace
The rooms boot as a content-addressed environment of their own. The standalone rooms ↗
Five ways to read
the same artefact.
Star ↗Lattice ↗Signatures ↗Sigil ↗Skye ↗
The key is minted at agentprivacy.ai/city, explored on Soulbis, and read at Mages City. The rooms are the instrument; the lab keeps the measurements; the City is the first verifier.
Try what exists todayRead a key.
Read a key.
Choose what travels.
Inspect a local City Key, derive its κ and export a selected reading. No extension needed; the file never leaves this page.
Open the Star Key reader →Download a synthetic practice key
The reader does not verify identity or grant access. Its artwork is illustrative; compact JSON is not a proof.
What the Star holds,
and what leaves it.
Every item in the Hold is a signed relationship or a signed act toward one: a membership, a vouch, a relationship record, a trust task. The Star verifies each item locally, records its state — valid, invalid, unsupported, unavailable — and measures its bytes against the same budget the signatures room draws. The key carries only the root and the count. A verifier that receives the key learns how much is held and can check the root against a presentation; it learns nothing about who signed what.
The first verb of the runtime is relate, not add: an item enters only after it verifies, and a bearer cannot relate itself. present answers honestly that it is not available, and names what is missing.
What we do not say.
- The Star is not a wallet. The trust agent's wallet is what the Star rides on.
- Nothing about trust is read off the shape. The geometry expresses; the register governs.
- Nothing here is "verified" without naming the verifier and what it checked.
- No zero-knowledge presentation exists yet.
Built on OpenVTC's verifiable trust infrastructure and the Trust over IP DTG credential and ZKP work; content addressing after UOR; the verify foot of the Hold re-implemented by the House of Archon. Updated 21 September 2026. The need profile → · Experiment history →