Omnikernel & Atlas Gateway
Relevant source files
The following files were used as context for generating this wiki page:
The Omnikernel (referred to in implementation as MD-X4/MD-X5 or the Atlas Kernel) serves as the core technical infrastructure of the TAMV Online ecosystem. It functions as a heptafederated kernel and a "Digital Nexus" that provides a unified API for identity management, protocol execution, and civilizational observability. The Atlas Gateway acts as the primary entry point, orchestrating communication between the frontend interfaces and the underlying microservices.
Sources: README.md:4-15, src/pages/wiki/modulo-cero/Introduccion.tsx:10-15
The system is designed as an antifragile "Zero-Trust" architecture that unifies 177+ federated repositories into a single operational framework. It handles identity (DID/SSI), cryptographic signatures, XR events, and academic tracing through integrated persistent identifiers (PIDs).
Sources: README.md:17-25, src/pages/wiki/modulo-cero/Introduccion.tsx:85-90
System Architecture
The architecture is structured into functional layers and processing pipelines that separate critical operations from adaptive intelligence.
The MD-X Kernel Layers
The kernel operates across multiple levels to ensure high-level abstraction and specialized service delivery:
- Level 1 (MD-X4 / MD-X5): The infrastructure core responsible for observability, autopoiesis, and the "HOYO NEGRO" protocol.
- Atlas Kernel Runtime: Provides optional persistence through Supabase and manages real-time signals (SSE/WebRTC).
- Node API Server: A native HTTP backend using ESM that exposes core endpoints for signatures, identity, and the Isabella AI ledger.
Sources: src/pages/wiki/modulo-cero/Introduccion.tsx:75-84, README.md:48-60
Pipeline A/B/CCP Framework
The Atlas Gateway orchestrates three distinct pipelines defined in the system's OpenAPI specification:
| Pipeline | Designation | Key Services | Port Range |
|---|---|---|---|
| Pipeline A | Critical Operations | Auth, Security (QSL™), Transaction (Saga), Payment | 8001–8005 |
| Pipeline B | Adaptive Intelligence | AI Generation, Voice (TTS), Embedding (pgvector) | 8101–8105 |
| CCP | Control & Coordination | Orchestrator, Policy Engine (OPA-like), Governance | 8200–8202 |
Sources: federation/tamv-digital-nexus/packages/contracts/openapi/tamv.v1.yaml:6-22
Core Components and Data Flow
TAMV Fusion Core (Orchestrator)
The tamv-fusion-core is the functional implementation of the Orchestrator for MD-X4. It executes a "Fusion Cycle" that synchronizes content and monitors ecosystem health.
The Fusion Core checks critical routes (e.g., /isabella, /economy, /governance) and monitors database tables like profiles, msr_events, and tcep_wallets.
Sources: federation/tamv-digital-nexus/supabase/functions/tamv-fusion-core/index.ts:18-100
Security and Identity Gateway
The Gateway implements a Post-Quantum Cryptography (PQC) layer, using hybrid signatures (RSA + Dilithium/Kyber) to ensure long-term data integrity.
- Identity Endpoint:
/v1/identity/*manages organizational DIDs. - Signature Service:
/v1/signature/signand/v1/signature/verifyhandle payload verification. - Quantum Security Layer (QSL): Integrates hybrid keys and Dilithium3 algorithms for high-security transactions.
Sources: README.md:33-40, federation/tamv-digital-nexus/packages/contracts/openapi/tamv.v1.yaml:105-135
Operational Namespaces and Edge Functions
The kernel manages the ecosystem through specialized namespaces and distributed edge functions:
Namespace Allocation
tamv-core: Central kernel logic and routing.tamv-identity: SSI and DID management.tamv-events: Event-bus for webhooks and internal messaging.tamv-observability: Metrics (latency p95, trust-score drift).
Sources: src/pages/wiki/implementacion/CicdPipelines.tsx:78-85
Critical Edge Functions
The gateway routes requests to several high-performance edge functions:
tamv-fusion-core: The main orchestrator cycle.isabella-chat-enhanced: Advanced AI interaction layer.dekateotl-security: Security gates and policy enforcement.quantum-analytics: High-speed data processing.
Sources: src/pages/wiki/implementacion/CicdPipelines.tsx:88-100
API Domain Specifications
The gateway exposes several domains with varying degrees of implementation coverage:
| Domain | Base Path | Functionality |
|---|---|---|
| Auth | /api/v1/auth | JWT+PQC Registration, Login, Refresh |
| Identity | /api/v1/identity | Dignity Score + SSI verification |
| MSR | /api/v1/msr | Event ledger and actor timeline |
| Governance | /api/v1/governance | DAO proposals, voting, and powers |
| XR | /api/v1/xr | Stream signaling and metadata |
Sources: src/pages/wiki/metaverso-xr/RoadmapCivilizatorio.tsx:112-120, README.md:38-42
The diagram shows the standard flow of a secured request through the Atlas Gateway, highlighting the signature verification step before the Orchestrator delegates the task to the appropriate pipeline.
Sources: README.md:48-60, federation/tamv-digital-nexus/packages/contracts/openapi/tamv.v1.yaml:45-55
Summary
The Omnikernel and Atlas Gateway form the technical backbone of TAMV Online, transitioning from a conceptual framework to a "Digital Nexus" (MD-X4). By utilizing a heptafederated kernel and a multi-pipeline microservices architecture, the system provides a robust platform for identity, governance, and decentralized operations. Its integration of post-quantum security and automated health orchestration via the Fusion Core ensures the ecosystem remains antifragile and scalable for territorial deployment.