Plain English
Tools turn the messaging model into something you can inspect and test.
Technical summary
The current browser tools are local prototypes for source review, registry candidate extraction, JSON envelope validation, Unicode warnings, and demo compact export.
Deep spec
They are not a hosted UAI-1 validator, certification service, or protocol authority. They are JustAnIota implementation surfaces for building on top of UAI.
Tool map
- Concept Bridge Console: source text, locale, normalization, registry candidates, warnings.
- JustAnIota Converter: English source, visible tokens, PUA scalar preview, canonical envelope, and reverse gloss.
- Validator / Encoder: candidate JSON, required-field checks, Unicode safety warnings, demo compact form.
- HTML Keyless Extractor: HTML source parsing, visible-text cleanup, and positional keyless array output.
- Registry Explorer: lookup surface for ID definitions, code points, modes, examples, and reversibility notes.
- Export Pack: planned evidence bundle for release review.
JustAnIota Converter
Bidirectional semantic conversion for English and IOTA-1
This workbench follows the public-MVP direction from the source docs: deterministic registry matches first, visible IOTA-1 tokens for copy/paste, PUA scalar preview for the later compressed profile, and a canonical envelope that keeps meaning outside Unicode itself. When the converter plugin is active, the browser calls the REST service and keeps the local path as fallback.
Concept Bridge Console
Inspect source text before compact output exists
This local prototype shows the review stages from natural language to registry-backed candidate tokens. It does not claim final semantic compression or UAI-1 authority.
HTML Keyless Extractor
Turn HTML into a reviewable keyless candidate
This browser-only prototype follows the intake reports: parse HTML as source evidence, clean visible text, normalize it, then emit a compact positional array that still depends on declared registry meaning.
Validator / Encoder
Check the envelope before exporting compact tokens
The browser workbench validates required fields, Unicode safety warnings, registry-dependent payloads, and a deterministic demo encoding. Server-side validation remains a future implementation surface.
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 and PUA do not assign these meanings. The registry does, and a production registry must be versioned, signed, immutable after assignment, and validator-tested.