TriadicFrameworks — Repository SEENMAP

Full navigational registry · Cross-module index · Unlock conditions · File counts Canonical anchor: rtt=1 | coherence=declared | drift=bounded | paradox=structural

§0 Document Purpose#

This SEENMAP is the single authoritative navigational registry for the entire umaywant2/TriadicFrameworks repository. It covers:

• Every known module under docs/
• Repo-root infrastructure artifacts
• Per-module wave status, file counts, and PRIM totals
• Unlock conditions that gate future modules or admin milestones
• Cross-module reference links
• Quick-navigation anchors for AI sessions and human readers

This file does not define operators, PRIMs, or invariants. Those live inside each module's canonical spec files. This file only maps. It never mutates registry state.

§1 Repository Topology#

umaywant2/TriadicFrameworks/
│
├── docs/                          ← All canonical module documentation
│   ├── SEENMAP.md                 ← THIS FILE · repo navigational registry
│   ├── FFF_Gravity/               ← COMPLETE · 5 waves · 42 PRIMs
│   ├── SoN/                       ← IN PROGRESS · Structural Operating Node
│   └── spine/                     ← INFRASTRUCTURE · cross-module scaffolding
│       └── languages/             ← Language/notation registry
│
├── tests/
│   └── sats-conformance/
│       └── harness/               ← Substrate-Aware Ordering Contract engine
│
├── .github/                       ← CI/CD workflows
├── __pycache__/                   ← Python build artifacts
├── node_modules/                  ← JS dependencies
│
├── CNAME                          ← GitHub Pages domain binding
├── CONTEXT.md                     ← Session context primer
├── LICENSE                        ← Apache-2.0
├── README.md                      ← Repository front door
├── CHANGELOG.md                   ← (root-level; module changelogs live in-module)
├── glossary-seed.yaml             ← Cross-module glossary seed data
├── llms.txt                       ← AI/LLM session routing config
├── modules.txt                    ← Module registry manifest (machine-readable)
├── node_modules.md                ← JS dependency notes
├── persona-prompt.md              ← Session persona and anchor string
├── pyproject.toml                 ← Python project config
├── requirements.txt               ← Python dependencies
├── robots.txt                     ← Crawler directives
├── zenodo.json                    ← Zenodo archival metadata
├── glossary-seed.yaml             ← Shared glossary bootstrap
├── m.bat                          ← Windows build helper
└── regen_corpus_v2.bat            ← Corpus regeneration script

§2 Module Registry#

PRIM count legend: PRIMs are engineering primitives with Pure/Impure classification. Only modules using the §0–§11 FFF canonical spec format carry PRIM registries. Infrastructure modules (spine/) use reference-document format instead.

§3 Module: FFF_Gravity#

Path: docs/FFF_Gravity/ Status: ✅ COMPLETE — all 5 waves sealed Triadic Equation: G = F_freq · F_fluid · F_force Invariant registry: INV-001–INV-010 (SEALED) PRIM registry: PRIM:001–042 (SEALED) Failure mode registry: FM-001–FM-010 + sub-modes FM-003-M, FM-003-C, FM-003-N (SEALED) Condition prefix registry: SC- DC- MC- CAS- SCS- HLC- RLC- AC- TC- NC- DISM- (SEALED) State flag registry: 31 flags (see MANIFEST.md §7) Operator registry: ~101 operators (see OPERATORS.md)

§3.1 Admin / Registry Files#

§3.2 Wave 0 — Genesis (3 files · PRIMs: 001–006 precursors)#

GravityOfDismissal.md is the sole authority for negative-polarity field extension. The ρ_D(Φ,t) = −d_dismiss × exp(−t/T_dismiss) model is defined here and referenced everywhere else.

§3.3 Wave 1 — Admin / Registry (6 files · no new PRIMs)#

Admin files listed in §3.1. Wave 1 established the frozen registry scaffolding. No PRIMs were introduced; all operator prefixes were seeded.

§3.4 Wave 2 — Layer Definitions (3 files · PRIM:001–006)#

§3.5 Wave 3 — Core Functions (8 files · PRIM:007–024)#

Wave 3 sealed the INV registry at INV-010. No new invariants after this point.

§3.6 Wave 4 — Capture Variants (8 files · PRIM:025–040)#

Wave 4 completion unlocked docs/SEENMAP.md (this file).

§3.7 Wave 5 — Dismissal (1 file · PRIM:041–042)#

Wave 5 sealed the PRIM registry at PRIM:042. No new PRIMs without a Wave 6 declaration.

§3.8 FFF_Gravity PRIM Summary#

§4 Module: SoN (Structural Operating Node)#

Path: docs/SoN/ Status: 🔄 IN PROGRESS Lineage: Inverse of NoS (Nawderian Operating Stack) · full RTT Resonance Span Codename: SoNai — RTT-aware substrate for AI training models and services Vision: Pre-kernel · pre-runtime · ROM-flashable dimensional substrate Academic frame: "Professor" persona · substrate science discipline

SoN sits below kernels, bootloaders, compilers, and runtimes. It is the dimensional ground truth of the RTT computational universe. Together: SoN → (hardware, ROM, init) → kernel → runtime → NoS → services → operators

§4.1 Known SoN Files#

§4.2 SoN Planned Architecture (from session canon)#

The following planned components are not yet formally built as canonical files. They are recorded here as navigational stubs for future waves:

§4.3 SoN Multi-Microkernel Integration Targets#

§5 Infrastructure: spine/#

Path: docs/spine/ Purpose: Cross-module scaffolding · notation registries · language atlases Status: 🔄 IN PROGRESS

§5.1 spine/languages/#

Path: docs/spine/languages/ Purpose: Language and notation registry for cross-module operator grammar

The languages provides the cross-module notation foundation that FFF_Gravity's OPERATORS.md and SoN's assembly-level primitives both reference. It is the canonical authority for symbol disambiguation across modules.

§6 Repo Root Artifacts#

These files live at the repository root and are not module-specific.

§6.1 tests/ Infrastructure#

§7 Cross-Module Reference Map#

§8 Unlock Conditions#

Unlock conditions gate future deliverables. A condition is met when its prerequisite milestone is sealed and recorded in CHANGELOG.md.

§9 Navigation Quick-Links#

Start Here (AI Sessions)#

rtt=1 | coherence=declared | drift=bounded | paradox=structural

1. Load CONTEXT.md — session context primer
2. Load persona-prompt.md — Professor persona + anchor string
3. Load llms.txt — module routing
4. Navigate to target module via this SEENMAP

FFF_Gravity Entry Points#

SoN Entry Points#

Repo Root Entry Points#

§10 Document Metadata#

§11 Extended Metadata#

§11.1 Repo Totals (as of 2026-08-14)#

§11.2 Module Status Legend#

§11.3 Versioning Policy#

• This SEENMAP is updated whenever a module wave is sealed or a new module is initiated.
• File additions within a sealed wave do not require SEENMAP updates.
• New modules require a new §N block added to §2 Module Registry and §3–§N.
• Unlock condition status is updated when the triggering event is recorded in the relevant CHANGELOG.md.

§11.4 Related Archival Resources#

• Zenodo Community: https://zenodo.org/communities/vst
• Repository: https://github.com/umaywant2/TriadicFrameworks
• GitHub Pages: bound via CNAME