Plain English
The Registry Explorer shows the mapping records behind compact output.
Technical summary
A compact token is usable only when its registry entry, profile, version, examples, negative cases, and validator behavior are visible.
Deep spec
Registry entries should prefer assigned public symbols for public output. Private-use characters remain private-use, and the registry plus envelope carry meaning.
Explorer jobs
- Find a stable ID from a label, definition, code point, or example.
- Separate lossless lexical mappings from lossy concept candidates.
- Show whether a unit is public, vendor/session, or local debug scope.
- Keep registry policy visible before encoder output is reused.
Registry Explorer
Inspect the mappings that give compact output meaning
This local registry is a demo snapshot. It shows the fields a real signed registry record needs: ID, definition, code point, mode, reversibility, examples, and policy notes.
Unicode supplies assigned public symbols and metadata. The registry supplies the demo mapping, and a production registry must be versioned, signed, immutable after assignment, provenance-backed, and validator-tested.