Plain English
IOTA-1 (ɩ≃1) is the JustAnIota authority profile for compact, structured AI-message candidates. It targets UAI-1 without replacing or controlling it.
Technical summary
IOTA-1 messages keep source text, locale, direction, normalization, registry version, segment trace, payload fields, validation evidence, and compact previews together so a short output can be inspected and compared.
Deep spec
IOTA-1 is an application-layer profile. Unicode is the encoding layer; PUA is private-use only; UAI-1 protocol authority remains with UAIX.org; semantic meaning comes from registry records, schemas, canonicalization, examples, segment evidence, result modes, and validator behavior.
Authority scope
- JustAnIota.com is the current source for IOTA-1 naming, profile drafts, reference page language, public examples, registry drafts, tool expectations, and result-evidence vocabulary.
- Protocol5 contributes experiment evidence for .NET, SQL Server, public-symbol retrieval, segmentation, ranking lanes, and database-only fallback behavior.
- UAIX.org remains the source for UAI-1 protocol authority, conformance language, validator authority, governance, and roadmap truth.
Profile layers
- Source layer: raw input, source locale, direction, and normalization rule.
- Segmentation layer: sentence, phrase, token, lookup key, match level, fallback, and unknown-rate evidence.
- Mapping layer: registry snapshot, stable IDs, localized labels, ambiguity notes, provenance, score, and reversibility mode.
- Envelope layer: JSON/I-JSON shape, payload fields, provenance, and canonicalization metadata.
- Validation layer: Unicode safety warnings, schema checks, registry hits, negative cases, and export readiness.
- Compact layer: public Unicode symbol or ASCII-safe candidate output that is incomplete without the envelope.
{
"spec_version": "iota-1-draft",
"authority_scope": "JustAnIota IOTA-1 draft profile",
"uai_target": "UAI-1",
"source_language": "en-US",
"source_direction": "ltr",
"normalization": "NFC",
"registry_digest": "demo:not-signed",
"result_mode": "DatabaseOnly",
"segment_trace": [
{ "text": "request review", "match_level": "registry_phrase" },
{ "text": "validator result", "match_level": "registry_phrase" }
],
"units": [
{ "id": "request_review", "code_point": "U+2753" },
{ "id": "validator_result", "code_point": "U+2705" }
]
}[
"iota-1-draft",
"JustAnIota IOTA-1 draft profile",
"UAI-1",
"en-US",
"ltr",
"NFC",
"demo:not-signed",
"DatabaseOnly",
[
[
"request review",
"registry_phrase"
],
[
"validator result",
"registry_phrase"
]
],
[
[
"request_review",
"U+2753"
],
[
"validator_result",
"U+2705"
]
]
]Field order follows the keyed JSON example, the published schema order, and the public field registry.
Non-goals
- IOTA-1 does not claim Unicode is a semantic language.
- IOTA-1 does not turn PUA code points into public Unicode assignments.
- IOTA-1 does not certify UAI-1 conformance or speak for UAIX.org.
- IOTA-1 does not treat embeddings, hashes, screenshots, model token IDs, or glyph appearance as semantic authority.
- IOTA-1 does not promise exact translation; approximate paths must show scores, alternatives, evidence, and drift.
JustAnIota Converter
Bidirectional semantic conversion for English and IOTA-1
This workbench follows the public-symbol direction from the source docs: deterministic registry matches first, visible IOTA-1 tokens for copy/paste, assigned Unicode symbol previews, and a canonical envelope that keeps approximation, provenance, and exact-recovery limits visible. When the converter plugin is active, the browser calls the REST service and keeps the local path as fallback.