Projects & Enterprise Overview
Mapping the Applied Ecosystem: Institutions, Platforms, Protocols, Workstations & Sovereign Fabrics
Spine Position
Corpus Sector: 05 — Applied Systems & Fabrica
Node ID: NAV-PROJECTS-OVERVIEW
Primary Function: Portfolio classification, systems taxonomy & epistemic status mapping
Upstream Anchor: Applied Systems Architecture
Public Status Boundary. This overview maps the project, platform, and institutional portfolio of the Fabrica ecosystem. It distinguishes between formal institutions, software architectures, cryptographic protocols, applied fabrics, and strategic roadmaps. It does not assert accepted external certification, commercial investment offerings, legal treaty status, or global network deployment unless supported by explicit empirical receipts.
1. Architectural Taxonomy & Ecosystem Mapping
The applied ecosystem translates foundational principles from the Science of Fabric Reality (SFR) and Digital Fabrica Theory (DFT) into discrete operational layers:
graph TD
A["Applied Systems Portfolio"] --> B["Institutional & Archival Layer"]
A --> C["Sovereign Platforms & Node Runtimes"]
A --> D["Consensus & Verification Protocols"]
A --> E["Domain-Specific Applied Fabrics"]
B --> B1["GILC Charter & Governance"]
B --> B2["Universum Knowledge Corpus (UKC)"]
C --> C1["Digital Fabrica Platform"]
C --> C2["CodexStation Governed Runtimes"]
C --> C3["Kernel-Based Intelligence (KBI)"]
D --> D1["Yellow Chain Invariant Ledger"]
D --> D2["ScrollDNA Provenance Schema"]
E --> E1["CySys Cybernetic Systems"]
E --> E2["Citizen Solar Energy Fabric"]
E --> E3["New Millennium Frontier (NMF)"]
2. Portfolio Classification Matrix
| Program / System | Classification | Operational Role | Implementation Status | Canonical Route |
|---|---|---|---|---|
| GILC | Institution / Charter | Sovereign research governance & corpus stewardship | Public Record | GILC Charter → |
| UKC / KBI | Archival & Kernel Substrate | Structured knowledge repository & reasoning tuples | Operational Model | KBI Architecture → |
| Digital Fabrica | Applied Platform | Invariant-preserving digital substrate & node engine | Architecture Specification | Digital Fabrica → |
| CodexStation | Governed Workstation | Controlled local-first execution runtime & build gates | Partially Implemented | CodexStation → |
| Yellow Chain | Verification Protocol | RFC 8785 Merkle epoch ledger & consensus state | Ledger Specification | Yellow Chain → |
| ScrollDNA | Identity Schema | Cryptographic provenance & validator lineage tuples | Operational Schema | ScrollDNA Schema → |
| CySys | Enterprise Engineering | Cybernetic invariant controllers & systems design | Architecture Specification | CySys Systems → |
| Citizen Solar | Decentralized Energy | Storage-first microgrid routing & telemetry ledger | Applied Architecture | Citizen Solar → |
| NMF | Frontier Coordination | Challenge framing, proof registries & referee intake | Planned Roadmap | NMF Initiative → |
| MLCO | Living Document Substrate | Cybernetic Markdown architecture for dynamic books | Architecture Roadmap | MLCO Architecture → |
3. Epistemic Demarcation & Verification Gates
Every serious reader, peer reviewer, or institutional evaluator may inspect and audit each portfolio component through five formal gates:
- Definition Gate: Terms, symbols, invariants, and scope boundaries must be formally defined.
- Boundary Gate: Claims must be explicitly tagged (Operational Code, Architecture Specification, Formalization Target, Public Record, or Strategic Roadmap).
- Source Gate: All code repositories, Lean 4 proofs, manuscripts, and cryptographic hashes must be traceable to primary artifacts.
- Formalization Gate: Mathematical claims must reduce to explicit definitions, lemmas, theorems, and machine-checkable proof obligations.
- Implementation Gate: Software claims require verifiable repositories, build scripts, reproducible logs, and deterministic verification receipts.
4. Evidence Classification Table
| Layer | Evidence Classes | Boundary Language |
|---|---|---|
| Public Identity | Domain registries, site manifests, published manuscripts | Public research route, not external certification |
| Architecture | Formal specifications, DAG schemas, whitepaper editions | Systems architecture and operational design |
| Implementation | Git repositories, reproducible builds, automated test receipts | Implemented strictly within declared subsystem scope |
| Governance | Institutional charters, status boundaries, audit logs | Internal governance ruleset unless legally certified |
| Research Grounding | SFR, DFT, Invariant Engineering, Lean 4 theorems | Authorial theoretical framework and formalization |
| Roadmap | Milestone tracks, dependency matrices, proof backlogs | Planned developmental milestones |
5. Canonical Continuation Pathways
| Direction | Target Node | Route | Focus / Purpose |
|---|---|---|---|
| Upstream | Applied Systems Root | /05-fabrica/ | Sector 05 master systems gateway |
| Current Node | Projects Overview | /05-fabrica/projects-overview | Applied portfolio classification & taxonomy |
| Project Spine | Enterprise / Project Spine | /05-fabrica/project-spine | Visual project grid and domain cartography |
| Platform Spec | Digital Fabrica Platform | /05-fabrica/digital-fabrica | Invariant digital substrate architecture |
| Workstation | CodexStation Runtime | /05-fabrica/codexstation | Governed local execution station |
| Review Gateway | SFR Review Portal | /03-research/sfr-review-portal/ | Five-gate critique protocol & referee inquiry |