Core Orchestration Engine
Relevant source files
The following files were used as context for generating this wiki page:
The Core Orchestration Engine, identified as the Kernel TAMV MD-X4, serves as the central operational hub for the RDM Digital platform. It is designed as a "Sovereign Urban Operating System" (SO Urbano) that manages territorial identity, telemetry, and civic governance through a heptafederated architecture. Its primary purpose is to provide a resilient, auditable, and self-governing infrastructure for the "Real del Monte" territory, operating independently of global cloud provider dependencies.
Sources: README.md:9-15, src/components/rdm/kernel.tsx:37-43, src/components/rdm/hero.tsx:39-44
Heptafederated Architecture
The system is organized into seven distinct federations, each acting as a sovereign domain with its own modules, data schemas, and governance rules. This structure ensures fault isolation (bulkheading) and specialized management of territorial services.
Federation Domains
The orchestration engine synchronizes state across these seven entities:
| Federation | ID | Core Focus | Modules |
|---|---|---|---|
| Educativa | educativa | Decolonized knowledge | utamv, masterclass, biblioteca |
| Cultural | cultural | Living memory/Heritage | manuscrito, museos, rituales |
| Económica | economica | Sovereign commerce | mercado, msr, bookpi, stripe |
| Tecnológica | tecnologica | Cognitive infrastructure | isabella, kernel, nexus, quantum |
| Salud | salud | Federated wellbeing | telesalud, clinicas |
| Comunicación | comunicacion | Territory voice | radio, prensa, blog |
| Gubernamental | gubernamental | Digital sovereignty | protocolos, eoct, citemesh, nodos |
Sources: supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:19-25, scripts/002_rdm_seed.sql:10-40
Relationship Diagram
The following diagram illustrates how the core engine links federations to physical infrastructure (POIs) and digital assets (Repositories).
The orchestration engine uses these relationships to enforce domain-specific protocols and routing.
Sources: supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:10-150
Protocol Execution Logic
The Kernel executes four primary protocols in a cascading sequence to manage system integrity and security.
Operational Protocols
- PROTO-01: Autopoiesis: Monitors "Integrity Temperature" (CPU, PQC error rates, inter-federation latency). Triggers component regeneration if thresholds are breached.
- PROTO-02: Modo Isla (Island Mode): Enables operational continuity during connectivity loss via a P2P local mesh and store-and-forward synchronization.
- PROTO-03: Defensa Extrema: Deploys defensive assets (Tenochtitlan, Horus, Quetzalcóatl) to contain attacks and prevent data exfiltration.
- PROTO-04: Fénix: A recovery protocol that performs strong key encryption and service restoration from clean snapshots during global compromise.
Sources: src/components/rdm/kernel.tsx:4-31
Decision Tree Orchestration
The engine categorizes events into risk-based pathways, prioritizing human life over technical efficiency.
The decision tree ensures that vital risks trigger immediate isolation and human-in-the-loop (HITL) intervention.
Sources: src/components/rdm/kernel.tsx:50-84
Edge Function Integration
The engine leverages Supabase Edge Functions (Deno) for real-time orchestration, telemetry ingestion, and federation state management.
Key Functional Endpoints
federation-state: Aggregates counts for active federations, core repositories, and protocol executions.dashboard-summary: Provides a high-level operational overview including active businesses and kernel version (TAMV/MD-X4).github-sync: Normalizes and synchronizes evolutionary repositories from GitHub, classifying them into federations and core status.telemetry-ingest: Processes system signals and logs them into theanalyticstable for forensic analysis.
Sources: supabase/functions/protocols-execute/index.ts:30-45, supabase/functions/github-sync/index.ts:25-50, README.md:43-47
Repository Classification
The engine classifies repositories to maintain architectural coherence within the federated ecosystem.
| Classification | Description | Source Policy |
|---|---|---|
| Canónico | Core system modules (e.g., rdm-digital-nodo-cero) | EOCT Protocol |
| Protocolo | Governance and logic layers (e.g., civilizational-core) | EOCT Protocol |
| Comercio | Economic federation tools (e.g., trueque-mexa) | MSR/BookPI |
| Infra-Cognitiva | AI and Twin models (e.g., real-del-monte-twin) | Isabella Sentinel |
Sources: src/pages/Repositorio.tsx:43-55, supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:128-140
Security and Integrity
The core engine implements several advanced security measures to ensure "Sovereign Resilience."
Forensic and Cryptographic Layers
- Audit Signatures: Every critical resource is hashed (SHA256) and signed, stored in the
audit_signaturestable for immutable chain of custody. - Post-Quantum Cryptography (PQC): Ready for ML-KEM and ML-DSA (NIST FIPS 203/204) to protect against future computational threats.
- BookPI™ Ledger: Uses Merkle trees and robust timestamps for MSR (Multi-State Record) tracking, acting as a "Third Technical Witness."
Sources: src/components/rdm/kernel.tsx:102-110, supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:107-118, src/components/rdm/territory.tsx:88-93
Citations: supabase/functions/protocols-execute/index.ts:60-65, supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:107-115
Governance Standards
- Bulkheading: Total failure isolation between federations.
- Zero-Trust: Mandatory validation between microservices.
- HITL (Human-in-the-loop): A 95% threshold requirement for human intervention in critical decision-making.
Sources: src/components/rdm/kernel.tsx:102-112
Summary
The Core Orchestration Engine (Kernel TAMV MD-X4) provides a structured, multi-layered approach to territorial management. By combining cascading operational protocols, a heptafederated domain model, and immutable audit logs, it establishes a technical framework where digital sovereignty is treated as an ongoing forensic audit. Its significance lies in its ability to maintain local autonomy through "Island Mode" while providing a sophisticated defense and recovery mechanism against global systemic risks.