Semantic Glyph Interpretation, Teleodynamics AI, and Unicode Governance for Protocol5 IOTA-1

Full report

On this page

Executive summary

I conclude that Semantic Glyph Interpretation and Teleodynamics AI can be made mutually reinforcing for Protocol5’s IOTA-1 converter, but only if I keep the layers separate: Unicode and ISO 10646 remain the public interchange and governance layer, while teleodynamic reasoning operates as an internal semantic stability layer that never overrides public-symbol rules. Protocol5’s current public boundary is already compatible with that architecture: the hosted converter is explicitly approximate, evidence-first, and limited to assigned public Unicode characters and public standard sequences, while rejecting private-use authority and hidden codebooks. Its current live status also matters operationally: the public endpoint reports publicSeedConcepts: 36, vectorDimensions: 1998, and an unreachable SQL corpus on the hosted surface, which makes a governance-safe internal semantic layer more valuable, not less.

On the teleodynamics side, the conceptual foundation is strong but still early. Deacon’s teleodynamics treats living organization as intrinsically end-directed because coupled self-organizing processes generate and preserve each other’s boundary conditions; Varela, Maturana, and Uribe’s autopoiesis provides the classic self-producing systems frame; and closure-of-constraints work by Montévil, Mossio, and Bich gives a precise account of mutual dependence and self-determination. In AI specifically, the most concrete current paper is the 2026 preprint Teleodynamic Learning, which models learning as the co-evolution of structure, parameters, and endogenous resources under constraint, while a 2026 PhilArchive manuscript extends the idea toward operator-level semantic drift, regime transitions, and attractor-like dynamics. I therefore treat Teleodynamics AI as an emerging research program, not a settled engineering canon.

On the Unicode side, the governance picture is much firmer. Unicode and ISO/IEC 10646 have synchronized character codes and encoding forms since 1991, but Unicode adds the normative algorithms, character properties, and conformance machinery that real implementations rely on. Unicode also enforces a crucial principle for this report: it encodes characters, not glyphs. Characters are abstract entities; glyphs are visual renderings; the standard does not define glyph images. That distinction is exactly why Protocol5 should not treat visual glyph semantics as identical to code points. Instead, I should attach a teleodynamic semantic layer to public Unicode surfaces through normalization, segmentation, decomposition, ontology constraints, and repeated-validation scoring.

My central recommendation is therefore a layered design. I would keep IOTA-1 visible outputs restricted to assigned Unicode characters and valid public sequences, but I would store a richer internal glyph record containing Unicode conformance metadata, decomposition, embeddings, ontology tags, human validation traces, and a proposed phase-lock score. That phase-lock score should not be treated as a metaphysical claim; it should be an operational measure of whether a glyph repeatedly converges on the same ontology-validated canonical meaning across contexts, model versions, and human tests. This fits both Unicode governance and Protocol5’s evidence-first philosophy.

Concepts and assumptions

In this report, I use Semantic Glyph Interpretation in an operational engineering sense: the task of taking a visible glyph or glyph sequence, decomposing its form and context, and mapping it into a stable, ontology-constrained semantic object. That is consistent with Protocol5’s public goal of approximate semantic conversion and also with Unicode’s distinction between abstract characters and rendered glyphs. Your uploaded design notes already push in this direction by treating glyphs as semantic carriers rather than mere drawable marks, and by proposing telemetry such as attention metadata and phase-lock-aware records. I treat those uploaded materials as project hypotheses and design context, not as normative standards.

For Teleodynamics AI, I use a conservative definition. The philosophical core comes from autopoiesis and organizational closure: Varela, Maturana, and Uribe characterize living systems by autopoietic organization; Montévil and Mossio formalize biological organization as closure of mutually dependent constraints; Mossio and Bich argue that such closure naturalizes teleology because the organization collectively self-constrains and self-determines. Deacon’s teleodynamics adds the crucial distinction that living systems are not merely self-organizing dissipative structures: they are structured to preserve the boundary conditions on which their own persistence depends. The most relevant AI extensions are recent and early-stage: Teleodynamic Learning proposes two interacting learning timescales plus an endogenous resource variable, while Rudolph’s manuscript proposes attractor-induced semantic drift and operator-level orientation as requirements for goal-directed semantics beyond sequence prediction.

I also need to be explicit about what I am not claiming. I am not claiming that Protocol5’s converter becomes biologically autopoietic, or that Unicode characters have fixed universal meanings independent of culture, font, and context. Instead, I am translating teleodynamic ideas into software observables: stability, closure, constraint satisfaction, attractor-like reuse, and drift detection. I am also respecting Unicode’s own limits: the standard gives me character identities, properties, sequences, and conformance rules, but it does not define the semantic ontology IOTA-1 wants to infer.

The assumptions below are the working assumptions I use where the request leaves specifics open.

Teleodynamic mapping to semantic glyphs

The deepest relation between semantic glyphs and teleodynamics is that both involve constraint-rich compression. A glyph can function as a compressed semantic field because it does not merely name a referent; it bundles orientation, emphasis, relationships, and cultural convention into a compact visible form. Unicode itself warns me not to confuse character identity with glyph appearance, because the same abstract character may have very different glyph shapes and glyphs do not map one-to-one to characters. At the same time, glyph-aware modeling work such as Glyce and vector-native structure learning such as SVGformer show that shape and internal geometry can carry practically useful semantic information that pure token identity misses.

That creates a productive division of labor. Unicode gives me the stable public anchor; teleodynamic reasoning gives me the dynamic semantic stability layer. In that arrangement, a glyph’s visible public form can stay unchanged while its internal semantic confidence, neighborhood consensus, and attractor stability are continuously measured. This fits Protocol5 unusually well, because Protocol5 already emphasizes approximate meaning, ranked candidates, scores, provenance, and inspection rather than hidden authority.

I map the main teleodynamic concepts to glyph systems as follows.

The most useful engineering translation is phase-lock. I do not use phase-lock here as a physics claim about literal oscillators. I use it as a rigorous converter metric for recurrent semantic convergence: does a glyph keep collapsing to the same ontology-validated canonical meaning across contexts, model revisions, fonts, and human testing? That is directly aligned with Deacon’s concern for maintaining supportive conditions, with closure theories’ focus on mutual dependence, and with recent teleodynamic AI proposals about attractor-induced drift and phase-structured learning.

The key practical point is that a teleodynamic glyph layer should behave like a stability monitor, not a replacement authority. If the teleodynamic layer starts inventing hidden meanings that cannot be rendered, validated, normalized, or publicly inspected, it violates both Unicode governance and Protocol5’s public-symbol boundary. If instead it acts as a calibrated internal measure of semantic settling, reuse, and drift, it strengthens the converter without altering its public trust model.

Unicode governance and the boundary of compatibility

The Unicode–ISO governance layer is the hard boundary for any semantic glyph system intended for open interchange. Unicode and ISO/IEC 10646 have synchronized character codes and encoding forms since 1991, but Unicode adds important implementation constraints, algorithms, and character property data beyond ISO/IEC 10646 alone. That means any Protocol5-compatible semantic glyph system should treat the Unicode Standard, its annexes, and the Unicode Character Database as the effective implementation authority for normalization, segmentation, conformance, and public sequence validity.

Unicode’s most important conceptual rule for this project is the separation of character identity from glyph appearance. The standard directly addresses only the encoding and semantics of text; it does not define glyph images. Characters are abstract entities, glyphs are renderings, and glyphs do not correspond one-to-one with characters. Some sequences render as one glyph, some characters are split across multiple glyphs, and rendering order can differ from storage order. This rule is not a minor detail. It means I cannot lawfully or conceptually treat font-specific shape variation as a new public semantic encoding unless Unicode itself encodes that distinction, or unless I keep the distinction entirely inside an internal analysis layer.

Normalization and segmentation are equally central. UAX #15 defines Unicode normalization forms and guarantees that equivalent strings can have a unique binary representation; normalization stability policies exist precisely so normalized strings remain valid across later versions. UAX #29 recommends extended grapheme clusters over legacy grapheme clusters for implementation. Together, those rules mean I should segment glyph inputs at grapheme-cluster level, not raw code-unit level, and I should pin a normalization policy—normally NFC for general text-oriented interchange—before building teleodynamic metrics. Otherwise, drift scores may measure encoding noise rather than semantic change.

The table below is the governance core I would implement.

These constraints do not block teleodynamic semantic layers. In fact, they help. Unicode stability gives me a fixed surface on which to measure semantic settling. The UCD gives me normative properties and test data. Variation sequences, ideographic variants, and emoji sequences offer limited public composition mechanisms so long as I do not misuse them as private semantic escape hatches. Protocol5’s own rule set—public symbols only, no secret map, evidence-first—already points in the same direction.

The conflicts are just as important. A teleodynamic layer wants to model emergent, context-sensitive, possibly drifting semantics. Unicode does not encode that kind of semantic drift. Unicode also resists meaning-bearing use of glyph variation where the underlying character identity would no longer be the same. So the right architecture is layered: Unicode governs public form; teleodynamics governs internal semantic confidence and adaptation. If those layers are collapsed together, either interoperability breaks or the semantic model becomes an invisible private codebook.

There is also a real legal and licensing layer. Unicode data files and software are generally covered by the Unicode License v3, which is permissive, but code charts and the fonts used in them have additional usage constraints. Unicode explicitly says I may not extract glyphs from the PDF code charts for product use, and that chart fonts are licensed for chart publication only. So if Protocol5 builds visual training data, previews, or SVG seeds, it should source them from appropriately licensed fonts or internally created assets, not by scraping chart glyphs.

Teleodynamic-aware design patterns for Protocol5 IOTA-1

Protocol5’s current converter is a strong substrate for this work because it already exposes the right public contract. The public page states that the converter breaks English text into paragraphs, sentences, longer stored category segments, and then word fallback before ranking public Unicode glyph candidates. The logic layer already owns NFC normalization, scalar handling, grapheme grouping, candidate ranking, evidence summaries, provenance, and private-use rejection; the repository already uses ADO.NET over SQL Server vectors; and the package already uses public metadata and provenance for its symbol atlas. That means I can add a teleodynamic semantic layer behind the existing IOTA-1 public boundary instead of rewriting the whole converter.

The pipeline I recommend is below.

flowchart LR
    A[Input text or public glyph sequence] --> B[Unicode validation and NFC normalization]
    B --> C[Extended grapheme cluster segmentation]
    C --> D[Unicode conformance classifier<br/>single char / variation seq / ZWJ / invalid]
    D --> E[Visual and structural decomposition<br/>font-normalized renders, SVG or primitive graph]
    E --> F[Multimodal retrieval<br/>visual / structural / semantic / ontology]
    F --> G[Ontology and public-rule filter]
    G --> H[Canonical IOTA expression]
    H --> I[Public Unicode rendering]
    H --> J[Explanation payload<br/>scores, provenance, candidates]
    J --> K[Teleodynamic monitor<br/>reuse, drift, consensus, context stability]
    K --> L[Human validation and curation queue]
    L --> M[Ontology and weight updates]
    M --> F
    K --> N[Model/version drift alarms]
    N --> F

This design is “teleodynamic” in a disciplined software sense because the semantic organization is maintained by coupled constraints. Unicode validity constrains what can be emitted publicly. Ontology rules constrain what meanings are admissible. Retrieval neighborhoods constrain interpretation by empirical similarity. Human validation constrains semantic drift. Drift and phase-lock scores constrain whether a glyph is treated as mature, emerging, or unstable. Each layer both depends on and maintains the others, which is exactly the kind of closure-inspired control structure that makes the teleodynamic analogy useful without becoming mystical.

Algorithms I would use

The literature gives me conceptual guidance for stability, attractor dynamics, and closure, but it does not give me a standard glyph phase-lock formula. I therefore propose the following operational metrics for Protocol5. They are design recommendations, grounded conceptually in teleodynamic stability and in Protocol5’s evidence-first architecture, rather than standardized external formulas.

Let \(g\) be a glyph record, \(W\) a rolling observation window, \(p_t\) the posterior over canonical expressions at time \(t\), \(e_t\) the fused embedding at time \(t\), and \(B\) a set of context buckets.

\[ \textbf{reuse\_stability}(g) = \frac{1}{|W|-1}\sum_{t=2}^{|W|}\left(1-\mathrm{JSD}(p_t,p_{t-1})\right) \]

This measures whether the glyph keeps resolving to the same canonical meaning distribution over repeated uses. It stays soft rather than binary, which is important for approximate conversion.

\[ \textbf{embedding\_drift}(g) = \frac{1}{|W|}\sum_{t=1}^{|W|}\left(1-\cos(e_t,\bar e_W)\right) \]

where \(\bar e_W\) is the centroid or exponentially weighted moving average. Lower is better. This catches semantic movement even when the top candidate has not yet flipped.

\[ \textbf{neighbor\_consensus}(g) = \frac{1}{M}\sum_{m=1}^{M} \frac{|N_k^{(m)}(g)\cap N_k^\star(g)|}{|N_k^{(m)}(g)\cup N_k^\star(g)|} \]

where \(N_k^{(m)}(g)\) is the top-\(k\) ontology-concept neighborhood for modality \(m\) and \(N_k^\star(g)\) is the fused top-\(k\) neighborhood. This measures whether the modalities agree on what “semantic neighborhood” the glyph belongs to.

\[ \textbf{context\_stability}(g)=\sum_{b \in B} P(b\mid g)\max_y P(y\mid g,b) \]

This is intentionally context-sensitive rather than context-blind. A glyph may legitimately mean one thing in one context and another in another; I want high scores for within-context consistency, not for context-insensitive flattening.

\[ \textbf{attention\_agreement}(g)=1-\frac{1}{H}\sum_{h=1}^{H}\mathrm{JSD}(a_h,\bar a) \]

where \(a_h\) is the primitive-level attention map for head \(h\), and \(\bar a\) is the mean attention map. If heads disagree wildly about which primitives matter, semantic confidence should drop.

\[ \textbf{phase\_lock}(g)=\mathrm{clip}_{[0,1]}\Big( 0.25R + 0.20N + 0.20C + 0.15H + 0.10A + 0.10(1-D) \Big) \]

where \(R\) is reuse stability, \(N\) neighbor consensus, \(C\) context stability, \(H\) human agreement, \(A\) attention agreement, and \(D\) embedding drift.

I also recommend two additional diagnostics:

\[ \textbf{candidate\_entropy}(g) = -\frac{\sum_{i=1}^{K} p_i\log p_i}{\log K} \]

and

\[ \textbf{rarity\_score}(g)= -\log\frac{f(g)+\alpha}{N+\alpha |V|} \]

Candidate entropy tells me whether the model is broadly uncertain. Rarity tells me whether the glyph is long-tail or culturally uncommon in the observed corpus.

Retrieval and composition rules under Unicode constraints

The most important implementation discipline is to separate Unicode-level composition from semantic-level composition. Unicode-level composition asks whether a code-point sequence is valid and canonicalizable. Semantic-level composition asks what the validated unit means in IOTA ontology. Those are not the same problem.

I would implement the following sequence:

The subtle but crucial implication is that containment is usually a property of a glyph’s internal structure, not of a plain Unicode text stream. Order is naturally represented in text. Proximity can be inferred only when layout survives round-tripping. So for Protocol5’s ordinary text converter, the safest semantic relations are sequence and modifier roles across grapheme clusters, while containment should mainly come from SVG or primitive analysis inside a glyph record. That respects Unicode plain text while still enabling richer glyph semantics for curated records.

Data model and schema

The entity structure below makes the teleodynamic layer explicit while preserving Unicode governance.

erDiagram
    GLYPH ||--o{ UNICODE_SURFACE : has
    GLYPH ||--o{ DECOMPOSITION : has
    GLYPH ||--o{ EMBEDDING : stores
    GLYPH ||--o{ ONTOLOGY_TAG : uses
    GLYPH ||--o{ TELEODYNAMIC_STATE : tracks
    GLYPH ||--o{ HUMAN_VALIDATION : receives
    GLYPH ||--o{ PROVENANCE_RECORD : cites
    GLYPH ||--o{ CONTEXT_OBSERVATION : appears_in
    GLYPH ||--|| CANONICAL_EXPRESSION : resolves_to

    GLYPH {
        string glyph_id PK
        string profile
        string status
        string unicode_version
        string normalization_form
        float candidate_entropy
        float rarity_score
    }

    UNICODE_SURFACE {
        string surface_id PK
        string sequence_class
        string normalized_sequence
        boolean public_output_allowed
        boolean pua_rejected
        boolean fully_qualified
    }

    DECOMPOSITION {
        string decomposition_id PK
        string primitive_type
        string relation_type
        string render_profile
    }

    EMBEDDING {
        string embedding_id PK
        string modality
        string model_name
        int dimensions
        string model_version
    }

    ONTOLOGY_TAG {
        string tag_id PK
        string concept_id
        string role
        string constraint_set
    }

    TELEODYNAMIC_STATE {
        string state_id PK
        float phase_lock
        float reuse_stability
        float embedding_drift
        float neighbor_consensus
        float context_stability
        float attention_agreement
        string maturity_state
    }

    HUMAN_VALIDATION {
        string validation_id PK
        string method
        float agreement
        string locale_group
        string notes
    }

    PROVENANCE_RECORD {
        string provenance_id PK
        string source_family
        string source_version
        string license
    }

    CONTEXT_OBSERVATION {
        string observation_id PK
        string context_bucket
        string model_version
        string timestamp
    }

    CANONICAL_EXPRESSION {
        string expression_id PK
        string expression_type
        string ontology_version
        float confidence
    }

A compact JSON Schema example follows.

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Protocol5TeleodynamicGlyphRecord",
  "type": "object",
  "required": [
    "glyphId",
    "surface",
    "ontology",
    "teleodynamics",
    "provenance"
  ],
  "properties": {
    "glyphId": { "type": "string" },
    "surface": {
      "type": "object",
      "required": ["unicodeSequence", "sequenceClass", "normalizedForm"],
      "properties": {
        "unicodeSequence": {
          "type": "array",
          "items": { "type": "string" }
        },
        "sequenceClass": {
          "type": "string",
          "enum": [
            "SingleCharacter",
            "StandardizedVariationSequence",
            "IdeographicVariationSequence",
            "EmojiSequence",
            "EmojiZWJSequence"
          ]
        },
        "normalizedForm": {
          "type": "string",
          "enum": ["NFC", "NFD", "NFKC", "NFKD"]
        },
        "publicOutputAllowed": { "type": "boolean" },
        "unicodeVersion": { "type": "string" }
      }
    },
    "ontology": {
      "type": "object",
      "required": ["canonicalExpression", "tags"],
      "properties": {
        "canonicalExpression": { "type": "object" },
        "tags": {
          "type": "array",
          "items": { "type": "string" }
        }
      }
    },
    "teleodynamics": {
      "type": "object",
      "required": [
        "phaseLock",
        "reuseStability",
        "embeddingDrift",
        "neighborConsensus",
        "contextStability"
      ],
      "properties": {
        "phaseLock": { "type": "number", "minimum": 0, "maximum": 1 },
        "reuseStability": { "type": "number", "minimum": 0, "maximum": 1 },
        "embeddingDrift": { "type": "number", "minimum": 0, "maximum": 1 },
        "neighborConsensus": { "type": "number", "minimum": 0, "maximum": 1 },
        "contextStability": { "type": "number", "minimum": 0, "maximum": 1 },
        "attentionAgreement": { "type": "number", "minimum": 0, "maximum": 1 },
        "maturityState": {
          "type": "string",
          "enum": ["emerging", "stabilized", "drifting", "deprecated"]
        }
      }
    },
    "provenance": {
      "type": "array",
      "items": {
        "type": "object",
        "required": ["source", "version"],
        "properties": {
          "source": { "type": "string" },
          "version": { "type": "string" },
          "license": { "type": "string" }
        }
      }
    }
  }
}

Worked examples

The first example uses a public multi-glyph sequence similar to Protocol5’s own examples.

Example A: stable warning glyph

Input: ⚠火 Interpretation path: assigned public characters → valid grapheme clusters → structural decomposition of warning sign and ideographic fire component → ontology-constrained mapping to WarningOf(Fire).

Illustrative metrics:

• reuse stability \(R = 0.92\)
• neighbor consensus \(N = 0.85\)
• context stability \(C = 0.80\)
• human agreement \(H = 0.78\)
• attention agreement \(A = 0.74\)
• embedding drift \(D = 0.08\)

So:

\[ PL = 0.25(0.92)+0.20(0.85)+0.20(0.80)+0.15(0.78)+0.10(0.74)+0.10(1-0.08)=0.743 \]

That yields a high but not perfect phase-lock score of 0.743, which is the right profile for a public sequence that is interpretable yet still approximate.

{
  "glyphId": "iota:warning-fire:v1",
  "surface": {
    "unicodeSequence": ["U+26A0", "U+706B"],
    "display": "⚠火",
    "sequenceClass": "SingleCharacter+SingleCharacter",
    "normalizedForm": "NFC",
    "publicOutputAllowed": true,
    "unicodeVersion": "17.0.0"
  },
  "ontology": {
    "canonicalExpression": {
      "type": "Relation",
      "name": "WarningOf",
      "arguments": [{"type": "Concept", "id": "Fire"}]
    },
    "tags": ["warning", "hazard", "fire"]
  },
  "teleodynamics": {
    "phaseLock": 0.743,
    "reuseStability": 0.92,
    "embeddingDrift": 0.08,
    "neighborConsensus": 0.85,
    "contextStability": 0.80,
    "attentionAgreement": 0.74,
    "maturityState": "stabilized"
  }
}

Example B: ambiguous centered glyph

Input: ◎ Candidate meanings: focus, target, core, sun, center Illustrative metrics:

• reuse stability \(R = 0.45\)
• neighbor consensus \(N = 0.41\)
• context stability \(C = 0.36\)
• human agreement \(H = 0.31\)
• attention agreement \(A = 0.52\)
• embedding drift \(D = 0.29\)

\[ PL = 0.25(0.45)+0.20(0.41)+0.20(0.36)+0.15(0.31)+0.10(0.52)+0.10(1-0.29)=0.336 \]

That gives a phase-lock score of 0.336, which I would classify as emerging or unstable. The system should continue to allow approximate gist output, but it should route this glyph into active review instead of treating it as semantically settled.

{
  "glyphId": "iota:centered-ring-dot:v1",
  "surface": {
    "unicodeSequence": ["U+25CE"],
    "display": "◎",
    "sequenceClass": "SingleCharacter",
    "normalizedForm": "NFC",
    "publicOutputAllowed": true,
    "unicodeVersion": "17.0.0"
  },
  "ontology": {
    "canonicalExpression": {
      "type": "Disjunction",
      "members": ["Focus", "Target", "Core"]
    },
    "tags": ["center", "focus", "target", "ambiguous"]
  },
  "teleodynamics": {
    "phaseLock": 0.336,
    "reuseStability": 0.45,
    "embeddingDrift": 0.29,
    "neighborConsensus": 0.41,
    "contextStability": 0.36,
    "attentionAgreement": 0.52,
    "maturityState": "emerging"
  }
}

Tech-stack options I would favor

For the modeling stack, I would use SigLIP 2 as the main vision-language tower because it improves multilingual semantic understanding, localization, and dense features over original SigLIP; SVGformer as the main vector-native structural encoder because it explicitly encodes continuous SVG geometry and long-range dependencies; DINOv2 as a robustness branch for rasterized or imperfect renders; and Glyce-like decomposition ideas as inspiration for primitive-centric modeling where pictographic form matters. For storage, I would start inside SQL Server because Protocol5 already uses ADO.NET and SQL vectors, SQL Server’s vector type supports up to 1998 dimensions, and Microsoft recommends exact search when filtering reduces candidate pools to roughly 50,000 or fewer; if filtered ANN becomes dominant, Qdrant’s filterable HNSW is the cleanest next step.

Evaluation, roadmap, and governance risks

I would evaluate this system on two axes at once: semantic quality and stability quality. For semantic quality, ISO 9186-1 is the right standard anchor because it defines a method for testing the comprehensibility of graphical symbols and measures how well a symbol communicates its intended message. For stability quality, I would track phase-lock, reuse stability, neighbor consensus, drift, entropy, and cross-version robustness. I would also explicitly test cultural variance, because icon studies show that semantic distance affects cognitive performance and that cultural background influences graphical-symbol interpretation.

The evaluation matrix I recommend is below.

I would structure human testing in three tiers. First, a comprehension tier modeled on ISO 9186-style testing. Second, a semantic-distance tier using close distractors rather than easy negatives, because semantic distance strongly affects performance and attention. Third, a cross-cultural tier with stratified participant groups, because the same symbol may appear stable in one community and unstable in another. A glyph should only move from “emerging” to “stabilized” when those three tiers tell a compatible story.

The roadmap below is the one I would recommend for Protocol5.

gantt
    title Teleodynamic-aware IOTA-1 roadmap
    dateFormat  YYYY-MM-DD
    section Phase 1
    Schema and Unicode conformance layer      :a1, 2026-05-12, 21d
    Teleodynamic state storage                :a2, 2026-05-19, 21d
    Provenance and version pinning            :a3, 2026-05-26, 14d

    section Phase 2
    Decomposition and retrieval fusion        :b1, 2026-06-09, 28d
    Ontology reranking and phase-lock engine  :b2, 2026-06-23, 28d
    Human review queue                        :b3, 2026-07-07, 21d

    section Phase 3
    ISO-style comprehension testing           :c1, 2026-07-28, 21d
    Cross-cultural and drift evaluation       :c2, 2026-08-04, 28d
    Governance hardening and release gate     :c3, 2026-08-25, 21d

The main risks and mitigations are governance-shaped.

My final judgment is that teleodynamic-aware semantic glyph interpretation is compatible with Unicode governance if—and only if—I treat teleodynamics as an internal stability and adaptation framework rather than a competing character standard. Protocol5 is already unusually well positioned for that move because its public contract is approximate, evidence-first, and anti-private-codebook. The design challenge is therefore not to invent a new writing standard under IOTA-1, but to build a better semantic control system behind the public Unicode boundary.

The strongest limitation in the current evidence is that Teleodynamics AI remains early-stage: the conceptual foundations in autopoiesis, closure, and teleodynamics are much stronger than the AI implementation literature, which is currently represented mainly by a recent preprint and a manuscript rather than a mature benchmark ecosystem. That is why I present the phase-lock family, drift metrics, and glyph records here as proposed operational designs rather than standards-backed formulas. On the Unicode side, by contrast, the governance boundary is mature and clear. The safest path is to innovate semantically inside that boundary, not outside it.