Give a version of your City Key a recognisable face. Derive its fingerprint, see that fingerprint as a constellation, then compare it with another record. The portrait carries the key as well as its appearance.
The fingerprint, κ, identifies the key’s contents. The VTA connection establishes who controls the agent identity. How the key and sign-in fit together →
The page hashes the key’s canonical contents and compares the result with its recorded κ. Teal means they match; coral means they differ. A key without a fingerprint receives one here.
Colour comes from the palette; shape comes from the key’s geometry and recorded fields; light comes from its fingerprint. Select a vertex to read it. Exporting a portrait also includes the key.
Load a second key to see shared touched vertices, the two portraits and the fields that differ. Identical contents produce the same fingerprint, whoever holds the file. This comparison reads both records in full; overlap alone does not establish trust.
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 fingerprint — 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 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 carried content — they move the κ. Rendering them does not independently verify their source or measurement.
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 V6 · V5.4 lineage) · substrate: holospaces · instrument sources: Labs.