Your City Key 🗝️, read three ways. ① Derive — its name, the κ = sha256:H(canonical form), recomputed from its bytes and checked, in the open. ② Constellate — the name drawn: 64 hash glyphs, one per vertex. ③ Compare — two keys side by side. Identity is content, not location. Full grounding in the 📖 legend below.
The key's exact bytes, then their SHA-256 typed out against the stamped κ. Teal = it is what it says · coral = it isn't · no κ yet = the key learns its name here.
Colour = your palette (chosen) · shape = your stance + earned relief (carried) · light = the hash (derived — one edit moves ~60 of 64 glyphs). Click a vertex to read it. 📸 exports a PNG that carries the key.
Between two bearers the κs will always differ — that's identity working, not news. The discovery is the common ground: the ∩ lattice leads — vertices both keys have walked (lit · described · poured · proven). Drop a second key (JSON or sigil PNG) into B. Below the ∩: each sigil in its own palette (the pulse = identity divergence), then the exact diverging fields. Today, compare reads both keys in full; the designed next rung discovers the ∩ with zero knowledge — learn what's shared, reveal nothing else.
sha256:H(canonical form) — a UOR-ADDR content address; the sha256 axis is canon upstream. Never trusted, always re-derived: movement ① is the law performed.
the sigilglyph intensity 0→f lights each vertex; colour follows the key's own palette by stratum. The sigil is always drawn from the re-derived κ — the content's true name — never from the stamped claim. Change one description and the whole constellation reshapes — the key is its content.
the carrierthe exported PNG holds the full City Key (base64 JSON in a PNG tEXt chunk, keyword cityKey) with its κ stamped. Import the image on /star, /lattice, or here — the key unfolds back out, and movement ① re-derives its κ from what the image carried.
the shapethe second chosen layer: the key's geometry field carries the manifold parameters from /star's Lattice Console (ε · m · n · det(Σ) · ⚔️:🧙 — reserved in the 2026-05-27 interop, filled 2026-06-10). The ring here wears the ε·cos(nθ) envelope of r(θ,φ) — at n = 6, six petals, one per dimension. Shape is content: change it and the κ — and the whole sigil — relight.
the engraving · SHAPE-1.5the petals are the stance you chose; the relief on them is the work you did. Each vertex's radius is raised by its compression weight — w(x) = 0.50·focus + 0.25·lit + 0.15·witness-proven + 0.10·described — a pure function of the key's content, so the same key (JSON, or carried in anyone's sigil PNG) makes the same shape everywhere. The evolution path (measured figures: agent overlap → det(Σ), visibility ratios → petal amplitudes, zkp → the ⚡ petal) is the plan doc PLAN_KEY_EVOLUTION_MEASURED_GEOMETRY_2026-06-10.md.
the figures · FIG-2.0when a key carries a measured figures block (agent-data overlap · ⚔️:🧙 ratio · per-dimension visibility · zkp counts), shape stops being chosen: /star derives the manifold from it (ε = 0.6·(1−overlap) · det(Σ) = overlap), each dimension's petal here scales by its visibility ratio, and proof activity floors the ⚡ petal. Figures are content — they move the κ.
the lineage · prioran evolved export stamps prior = the κ of the key it grew from — keys form a hash chain (C87: the key accumulates). An unchanged re-export keeps its prior and its κ unchanged: lineage marks evolution, not circulation.
vocabularyglyph — one hex character at one vertex · rune-row — the 64 in succ order · sigil — the whole lighting, the key's face. (The City's runes keep their own register; the sigil is the Swordsman's seal.)
Model: agentprivacy.ai/model (PVM V5.4 / V6) · substrate: holospaces · this repo's seam: HOLOSPACE.md.