Implementation plan

Protocol5 IOTA-1 semantic roadmap

A phased path from English-first approximate conversion toward a governed, glyph-aware semantic interpreter.

Current design pressure.

The converter already has a coherent public-symbol boundary and evidence-first posture. The next weakness is meaning that depends too much on registry rows, lexical descriptors, and sparse fallback concepts.

A glyph semantics layer can deepen interpretation without relaxing public governance.

Upgrade principle

Do not replace the public-symbol rule. Add an internal kernel that reasons over geometry, composition, embeddings, ontology constraints, and validation traces before rendering public output.

Failure-mode map.

Failure mode	Mechanism	Upgrade response
Token registry sparsity	Meanings depend on available rows or seed concepts.	Add visual, structural, and semantic retrieval lanes with fallback provenance.
Rendering coupling	Public symbol selection dominates internal interpretation.	Keep public output separate from internal SVG and ontology evidence.
Lexical bias	Pipeline starts from English segments before glyph-first reasoning.	Support glyph-in, meaning-out parsing with primitive decomposition.
Vector compression	One embedding cannot carry all visual, structural, and semantic signals.	Use multiple vector spaces and late fusion.
Observability gap	Scores explain nearest neighbors, not structural reasoning.	Expose primitive ablations, ontology checks, and drift metrics.

Phased build plan.

Phase 0

Audit the boundary

Confirm normalization, grapheme handling, private-use rejection, evidence traces, and public sequence validity.

Phase 1

Static grammar registry

Define public-token operators, roles, arity, precedence, glosses, and warnings for compact shorthand.

Phase 2

Glyph object registry

Add records for surface, SVG hash, render profile, primitives, ontology tags, and provenance.

Phase 3

Multi-vector retrieval

Store separate visual, structure, semantic, and ontology vectors. Fuse late under constraints.

Phase 4

Stability loop

Track phase-lock, drift, human comprehension, regression tests, and review budget.

Suggested interpretation contract.

Keep the existing converter facade stable, then add one internal interpretation service and one diagnostics object.

{
  "input": "?=汝⟡→=",
  "mode": "glyph-first",
  "returnEvidence": true
}

Evidence payload.

{
  "canonical": "Question(Becomes(Modified(YOU), UNKNOWN))",
  "bestGloss": "What are you becoming?",
  "confidence": 0.68,
  "warnings": [
    "right-side target omitted",
    "state modifier ambiguous"
  ]
}