Federation UI Components
Relevant source files
The following files were used as context for generating this wiki page:
The Federation UI Components form the visual and interactive layer of the TAMV MD-X4 kernel's heptafederated architecture. These components are designed to represent seven distinct functional domains (federations) that operate within isolated security boundaries while maintaining coordinated orchestration. The purpose of these components is to provide visibility into the "Sovereign Urban Operating System" of Real del Monte, enabling monitoring of node health, resource distribution, and geopolitical alignment.
This system serves as a digital twin and operational dashboard, transitioning from traditional cloud-centric models toward "Edge Supremacy" and territorial sovereignty. It utilizes React-based interfaces to communicate complex telemetry data from the underlying Supabase backend and Edge Functions.
Sources: README.md:1-15, src/components/rdm/federations.tsx:112-120, src/components/rdm/geopolitics.tsx:1-10
The Heptafederated Kernel
The core of the UI is the representation of the seven functional federations. Each federation is defined by a unique ID, icon, role, and a set of specific capabilities. The UI components display these as an "Anatomy of the Kernel," emphasizing cellular orchestration where failure in one domain does not compromise the others.
Federation Definitions and Capabilities
The following table outlines the seven federations as defined in the system's static configuration and database schema.
| ID | Name | Role | Core Capabilities |
|---|---|---|---|
| F1 | Contenido y Artes | Inmutabilidad de activos | Merkle/MSR signatures, BookPI™, Anti-scraping |
| F2 | Mentoría Profesional | Optimización neurocognitiva | IRT Adaptive Engine, Cognitive monitoring |
| F3 | Economía Multimodal | Autonomía financiera | Edge ledger (Isla Mode), 20/30/50 Protocol |
| F4 | Gestión Territorial | Gemelo Digital RDM | Finite element simulation, Geotechnical radar |
| F5 | Seguridad Criptográfica | PQC / Agilidad | FIPS 203 (ML-KEM), FIPS 204 (ML-DSA) |
| F6 | Gobernanza Ética | Protocolo Isabella | XAI Algorithmic bias radar, Shapley traces |
| F7 | Soberanía Regional | Firewall geopolítico | Digital border radar, Data residency, Isla Mode |
Sources: src/components/rdm/federations.tsx:13-83, supabase/migrations/202605080001_lovable_federated_kernel.sql:130-137
Visual Topology: The Heptagon
The Heptagon component provides a mathematical visualization of the federation structure. It uses an SVG-based 7-vertex polygon to represent the interconnected yet modular nature of the MD-X4 kernel.
The diagram shows the cellular orchestration where each federation maintains its own pipeline of integrity while being part of a unified grid.
Sources: src/components/rdm/federations.tsx:142-184
Operational Monitoring: Federation Ring
The FederationRing component is a high-level monitoring tool that visualizes the state of the "EOCT Federation Ring." It fetches real-time telemetry from the tamv_federation_ring table and renders up to 195 nodes in a circular layout.
Node State Logic
Nodes are categorized by their "ECG Rhythm" and status, which dictates their visual representation in the UI:
- OK (Cyan): Standard operational state.
- SATURATING (Rose): Triggered when
ecg_rhythmexceeds 85. - BOOTSTRAP (Amber): Initializing state.
- OFFLINE (Slate): Node is unreachable.
Data Flow for Telemetry
The component utilizes a custom hook useSupabaseQuery to maintain a continuous stream of state updates.
The UI provides a filter to isolate nodes by their specific federation_id (1-7), allowing for granular debugging of specific domains.
Sources: src/components/tamv/federation-ring.tsx:10-85
Database Integration and Schema
The UI components are backed by a structured Supabase schema that defines the relationships between federations, repositories, and territory points of interest (POIs).
Federation Data Model
The federations table acts as the source of truth for all UI labels, colors, and active modules.
| Field | Type | Description |
|---|---|---|
id | text (PK) | Unique identifier (e.g., "educativa", "cultural") |
name | text | Display name for the federation |
color_hex | text | Primary color for UI accents |
modules | jsonb | List of active executable modules (e.g., ["Kernel", "Isabella"]) |
active | boolean | Global status toggle |
Sources: src/lib/types.ts:1-11, supabase/migrations/202605080001_lovable_federated_kernel.sql:24-34
Repository Classification
The Repositorio page extends the federation UI by classifying GitHub repositories into federation domains. It uses the federation_id foreign key to link codebases to their respective functional areas, enabling an "Evolutionary Repository" view.
Sources: src/pages/Repositorio.tsx:45-75, src/integrations/supabase/types.ts:285-300
Geopolitical and Infrastructure Positioning
A critical component of the Federation UI is the communication of the project's "Edge Supremacy" philosophy. The Geopolitics component uses a split-view comparison to contrast traditional cloud-centric models with the TAMV federated proposal.
Comparison Matrix: Dependency vs. Sovereignty
| Feature | Cloud-Centric Model | TAMV Federated Kernel |
|---|---|---|
| Data Locality | Global Data Centers | Territorial Nodes (Local Jurisdiction) |
| Governance | Opacity / Vendor Lock-in | Social Audit / Algorithmic Accountancy |
| Connectivity | Permanent Dependency | Isla Mode (Controlled Disconnection) |
| Logic | Data as Commodity | Data as Sovereign Infrastructure |
Sources: src/components/rdm/geopolitics.tsx:15-60
Summary of Operational Status
The Federation UI components are currently estimated at 72% production readiness. While the visual representations of the Heptafederated Kernel and the Federation Ring are functional, the full implementation requires completing the "Hardening" phase, which includes systematic rate limiting, E2E testing, and formal SLO/SLI instrumentation across all federation domains.
Sources: README.md:125-145