TAMV Protocols Governance
Relevant source files
The following files were used as context for generating this wiki page:
TAMV Protocols Governance represents the operational and ethical framework governing the digital infrastructure of Real del Monte. It is a multi-layered system designed to prioritize life and territorial sovereignty through algorithmic rules, immutable ledgers, and federated oversight. The governance model ensures that every technical execution adheres to the project's ontological and constitutional mandates.
Sources: README.md, src/components/rdm/tomos.tsx:115-117
Protocol Execution Engine
The ProtocolEngine is the core orchestrator responsible for processing commands within the TAMV ecosystem. It integrates ethical evaluation, event logging, and narrative publishing into a single execution flow.
Core Execution Flow
When a command is issued, the engine follows a strict sequence:
- Ethical Evaluation: The
EoctServiceevaluates the command against pre-defined rules. - Event Creation: The
MsrEnginegenerates a Multi-State Record (MSR) event capturing the decision and risk level. - Immutable Logging: The
BookPiServicepublishes a signed entry summarizing the protocol outcome.
The execution lifecycle results in a status of either accepted or rejected based on the ethical evaluation.
Sources: src/lib/tamv/protocol.engine.ts:8-33
Ethical Oversight (EOCT Service)
The EOCT (Edwin Oswaldo Castillo Trejo) Service acts as the primary gatekeeper for protocol safety. It applies a set of heuristic rules to determine if a command is ethically viable or poses a risk to system integrity.
Governance Rules
The service currently enforces specific checks to prevent destructive actions and ensure data utility:
| Rule ID | Description | Logic |
|---|---|---|
payload-non-empty | Ensures commands include useful data. | Checks if payload keys > 0 |
safe-command-name | Prevents harmful or destructive actions. | RegEx block: destroy, delete-all, wipe |
Sources: src/lib/tamv/eoct.service.ts:8-21
Kernel MD-X4 Decision Matrix
The Kernel TAMV MD-X4 implements four primary protocols in a cascaded architecture to handle system integrity and external threats.
Cascade Protocols
- PROTO-01: Autopoiesis: Monitors "Integrity Temperature" (CPU, latency, PQC error rates) and regenerates components if thresholds are breached.
- PROTO-02: Modo Isla (Island Mode): Ensures local P2P connectivity and essential services continue during total internet isolation using store-and-forward synchronization.
- PROTO-03: Defensa Extrema: Deploys defensive radars (Quetzalcóatl/Ojo de Ra) and containment layers during systemic attacks to block exfiltration.
- PROTO-04: Fénix: Handles global integrity compromises through strong encryption of keys and snapshot restoration.
Sources: src/components/rdm/kernel.tsx:4-63
Data Schema and Persistence
Governance state is persisted through a specialized SQL schema in Supabase, ensuring auditability and role-based access control.
Key Governance Tables
protocol_executions: Stores the history of every protocol action, decision, and the resulting SHA-256 hash.bookpi_entries: An immutable ledger of narrative entries, including digital signatures.audit_signatures: Maintains the cryptographic link between data resources and their verified signatures.federations: Defines the seven governance domains (Educativa, Cultural, Económica, Tecnológica, Salud, Comunicación, Gubernamental).
Sources: supabase/migrations/202605080001_lovable_federated_kernel.sql:56-85, scripts/001_rdm_schema.sql:35-46
Network Layer Governance
TAMV governance extends to the physical and logical network layers, organized into a 7-layer (L0-L7) model.
Layer Coverage
| Layer | Domain | Example Node |
|---|---|---|
| L0 | Identity/Nexus | Nexus-RDM (Nodo Cero) |
| L4 | P2P Swarm | Phoenix Swarm (libp2p) |
| L6 | Vault/IPFS | BookPI Vault |
| L7 | Blockchain Bridge | MSR Blockchain Bridge |
The system maintains "Network Health" by calculating the ratio of active nodes, average latency, and security gap coverage (Quantum Encryption, MSR Bridge, and BookPI Anchor).
Sources: src/stores/network.ts:10-74
Summary of Technical Specifications
The governance framework is "PQC ready" (Post-Quantum Cryptography), utilizing ML-KEM and ML-DSA standards (NIST FIPS 203/204). It employs "Bulkheading" to isolate failures between federations and requires a 95% threshold for Human-In-The-Loop (HITL) supervision in critical decisions.
Sources: src/components/rdm/kernel.tsx:95-108