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

Registry / Mapping System

Registry / Mapping System

Controlled mapping records for compact identifiers, localized descriptions, ambiguity handling, and reversibility notes.

  • Record JAI-REGI-0016
  • Path /registry/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-REGI-0016
Surface
Registry / Mapping System
Access
Public and linkable

How to use this page

Use this page for published profile IDs, schema links, example links, and compatibility notes.

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

The registry is where compact strings get meaning.

Technical summary

Registry records map identifiers to definitions, allowed profiles, localized labels, examples, negative cases, reversibility levels, and validator expectations.

Deep spec

Neither Unicode nor PUA assigns JustAnIota semantics. PUA is private-use only, and public meaning must be carried by the registry plus validation evidence.

Registry entry requirements

  • Stable ID and human-readable label.
  • Plain-English definition.
  • Allowed profiles and payload positions.
  • Locale notes and direction-sensitive warnings.
  • Positive examples, negative examples, and validator issue behavior.

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 

			

			

				Boundary note
				
Unicode and PUA do not assign these meanings. The registry does, and a production registry must be versioned, signed, immutable after assignment, and validator-tested.