We build compact AI messaging tools.
JustAnIota official shield mark JustAnIota UAI tooling ɩ.com Compact AI messaging tools Language-neutral AI messaging: registries, schemas, validation.
Draft IOTA-1 tools
  • Current surface JustAnIota tooling draft
  • Plain-English definition Compact, structured AI messaging tools
  • Current attribution Michael Joseph Kappel, MCP
  • Short-domain status ɩ.com redirects to JustAnIota.com

Specification

Registry

Nested specification entry for registry-backed meaning, source governance, evidence notes, and safety notes.

  • Record JAI-SPEC-18149
  • Path /en-us/specification/registry/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-SPEC-18149
Surface
Specification
Access
Public and linkable

How to use this page

Use this page as part of the current Specification public record, then follow its linked standards pages for the next step.

Proof path

Validator-backed proof path

Keep the public reading order tied to one evidence trail: profile, schema, example, validator result, and release record.

  1. 1Pick a message profile.Start with a published UAI-1 profile and the record family that matches the exchange you need to prove.
  2. 2Compare it with schemas and examples.Resolve the schema, registry entry, and one fixture before writing or mapping your candidate packet.
  3. 3Run validator evidence.Validate keyed, minified-keyed, or keyless JSON against the current public UAI-1 records.
  4. 4Attach the result to implementation or handoff records.Carry the exported result into implementation notes, changelog entries, or Project Handoff evidence.

Plain English

Registry records are where public demo meaning lives.

Technical summary

Each record names a stable ID, label, canonical phrase, compact candidate, normalization, locale, direction, status, version, source governance, evidence notes, safety notes, reverse gloss, and examples.

Deep spec

Visible glyphs and Unicode scalars are transport candidates. They are not semantic authority unless the profile, registry, schema, examples, and validator evidence say how to read them.

Registry checks

  • Use stable IDs, not hidden dictionaries.
  • Keep source governance visible.
  • Mark incomplete records as public-demo or draft.
  • Deprecate records without silently changing old meaning.

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.

Registry snapshot 

			

			

				Record cards
				

			

			

				Boundary note
				
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.