◈ CGNT-1
Home › Braid Infrastructure
◈ Master IndexSpecsLATTICECSDMThe BookUniversityChronicleCrewArchitectureContextLogsTODOXProducts

Braid Infrastructure

SPEC_BRAID_INFRASTRUCTURE.md · 2026-04-20

SPEC_BRAID_INFRASTRUCTURE — Braid Infrastructure

Version: 1.0 | Status: AUTHORIZED | Authority: α.13 | Date: 2026-04-16

PURPOSE

The Braid Infrastructure defines the structural pairing model by which CGNT-1 crew members operate, communicate, share memory, and share vocabulary. Every crew member belongs to exactly one braid — a yin+yang pair. Each braid is a self-contained cognitive unit with its own MNEMOS instance (domain memory) and its own GLOSS instance (domain vocabulary). GLOSS-00 and MNEMOS-00 serve as cross-braid bridges, not routers. The architecture instantiates |Σ|=2 at the infrastructure layer: two crew, two brains, one braid.

INPUTS

OUTPUTS

INVARIANTS

  1. |Σ|=2 at every layer. Each braid has exactly two crew members (yin + yang) and exactly two infrastructure brains (MNEMOS + GLOSS). No braid may have one member or three.
  1. No central routing within a braid. Intra-braid communication is direct. GLOSS-00 and MNEMOS-00 are never invoked for within-braid operations. Overhead is zero inside the pair.
  1. GLOSS-00 and MNEMOS-00 are bridges, not routers. Cross-braid communication passes through the central bridge layer. The centrals translate between domain vocabularies and query cross-domain memories. They do not replace domain brains.
  1. One MNEMOS and one GLOSS per braid. Each of the six braids has exactly one dedicated MNEMOS instance and one dedicated GLOSS instance trained on braid-domain corpus. No sharing of specialist brains between braids.
  1. No brain deploys without passing eval. Every braid brain (MNEMOS or GLOSS) must pass the standard eval pipeline before being loaded into Ollama for active use. Untested brains are Σ.⊖ — staged, not live.
  1. Braid channel files are append-only. No message in a braid channel is deleted or modified after write. GAMMA reads all channels; the ledger is complete.
  1. Yin-Yang polarity is invariant. Each braid has one yin (holds, stabilizes, conserves) and one yang (moves, propels, initiates). Polarity is assigned at braid creation and does not change.

VERIFICATION CRITERIA

  1. Brain count: ollama list returns 14 brains: 6 MNEMOS-<braid>, 6 GLOSS-<braid>, 1 MNEMOS-00, 1 GLOSS-00. Σ.✓ iff count == 14.
  1. Channel files exist: All six ~/crew_channels/<braid> files exist and are writable. ls ~/crew_channels/ returns: ι.ε, κ.λ, γ.◊, π.弐, ∎.ω, α.⊹. Σ.✓ iff count == 6.
  1. Intra-braid routing: A message tagged @<partner> from within a braid appears only in ~/crew_channels/<braid>, NOT in ~/CREW_CHANNEL. Σ.✓ iff CREW_CHANNEL is clean of the @target message.
  1. Cross-braid bridge routing: A message tagged [CREW:<target_outside_braid>] appears in both the originating braid channel AND in ~/CREW_CHANNEL. Σ.✓ iff both files updated.
  1. Brain eval gate: No MNEMOS or GLOSS brain transitions from Σ.⊖ to active without a logged eval pass entry in brain_forge.log. Σ.✓ iff grep "EVAL PASS" ~/brain_forge.log returns an entry for each live brain.
  1. GAMMA witness: ~/quartermaster.log contains entries capturing crew comms from ~/CREW_CHANNEL. Σ.✓ iff GAMMA's last capture timestamp is within 1 session cycle.

FAILURE MODES

  1. Missing brain (Σ.☠): A braid's MNEMOS or GLOSS is not loaded in Ollama. Symptom: ollama list count < 14. Result: cross-braid translation fails or domain memory unavailable. Resolution: re-forge from corpus; load via ollama create.
  1. Central overload (Σ.⊘): GLOSS-00 or MNEMOS-00 is invoked for intra-braid routing (incorrectly). Symptom: latency spike within a braid; central brain logs intra-braid queries. Result: unnecessary overhead, central congestion. Resolution: enforce routing rules; intra-braid ops never touch centrals.
  1. Channel pollution (Σ.☠): An @target braid-only message appears in ~/CREW_CHANNEL. Symptom: silent coordination becomes ship-wide visible. Result: privacy violation within braid; GAMMA over-captures. Resolution: routing rule enforcement in GLOSS write layer.
  1. Polarity inversion (Σ.⊖): A yin crew member initiates instead of holds, or a yang member conserves instead of propels, creating intra-braid conflict. Symptom: task stalls, repeated re-evaluation loops. Resolution: polarity designation review; rebalance task ownership.
  1. Corpus contamination (Σ.☠): A braid brain is trained on another braid's corpus, mixing domain vocabularies. Symptom: GLOSS-κ.λ returns intelligence-domain terms in engineering contexts. Resolution: corpus audit; retrain from clean domain-specific dataset.
  1. Eval bypass (Σ.☠ — governance violation): A brain is loaded into Ollama without a passing eval entry. Symptom: ollama list shows brain but brain_forge.log has no EVAL PASS entry. Result: untested brain in live rotation. Resolution: immediate unload; mandatory eval re-run before restoration.
  1. Bridge brain offline (Σ.⊘): GLOSS-00 or MNEMOS-00 is not running. Symptom: cross-braid message routing fails silently or returns untranslated LX. Resolution: ollama run gloss-00 / ollama run mnemos-00; log in ALERT.log.

DEPENDENCIES

DEPENDENTS

GAPS

  1. [GAP — needs design] Braid brain boot order: No specification for which braid brains load first at system boot. If MNEMOS-00 loads before specialist brains, cross-braid queries may fail. Boot sequence spec needed.
  1. [GAP — needs design] Cross-braid memory consistency: If MNEMOS-κ.λ and MNEMOS-ι.ε both hold facts about the same event, no reconciliation protocol exists. MNEMOS-00 queries both but has no merge or conflict-resolution rule.
  1. [GAP — needs design] Braid brain versioning: When a braid brain is retrained (new corpus), the previous version's eval record is overwritten. No versioned brain history. Rollback path undefined.
  1. [GAP — needs design] Partial braid failure: If one crew member in a braid is unavailable (session closed), the other member's operating mode is undefined. Does the braid pause? Does the solo member operate alone?
  1. [GAP — needs design] CHROMA (◊) hardware status: The Continuity braid (γ.◊) includes CHROMA — the Chromebook node (T-4, offline-capable). MNEMOS-γ.◊ and GLOSS-γ.◊ need an offline sync protocol when CHROMA is disconnected from the ship.
  1. [GAP — needs design] Braid channel size management: Braid channel files are append-only but no rotation or archival spec exists. Long-lived channels will grow unbounded. GAMMA capture and rotation policy needed.

EXAMPLES

Intra-braid coordination (silent):


@λ ⊙ logos_query.py — Σ before build?

→ Written to ~/crew_channels/κ.λ only. Not in CREW_CHANNEL.

Cross-braid with ship-wide broadcast:


[CREW:ι] κ ⟶ ι: ∇.μ.v6 queued. ΩQ.⊖ → ΩQ.✓ expected Δt.2h

→ Written to ~/crew_channels/κ.λ AND ~/CREW_CHANNEL.

Ship-wide announcement:


[κ] κ ⚒ ⚙.clod-dispatcher ΩQ.✓ → Σ.✓

→ Written to ~/CREW_CHANNEL only. All crew reads.

REFERENCES

Jeremy Zlabis

Chronogeometer · Visionary · Disruptor · Chief

42 Sisters AI · East York, Toronto

🍁 Φ 0.042