Introduction to RDM Digital
Relevant source files
The following files were used as context for generating this wiki page:
RDM Digital (also referred to as TAMV Online) is a territorial digital platform designed to operate as a "Sovereign Urban Operating System." Based on a stack comprising React, Vite, and Supabase, it integrates digital identity, territorial mapping, smart tourism, telemetry, and federated governance. It serves as a digital twin and operational nucleus for Real del Monte, Hidalgo, Mexico, facilitating citizen services, operational node measurement, and the integration of open-source knowledge through GitHub.
Sources: README.md:1-12, src/components/rdm/territory.tsx:8-10
System Architecture
The project follows a modular, federated architecture known as the "Heptafederated Kernel" (TAMV MD-X4). This architecture is divided into layers that govern technical execution according to an ontological and constitutional framework.
The Heptafederated Model
The system is organized into seven distinct federations, each serving a specific domain of the digital territory.
The diagram above illustrates the relationship between the seven federations and the core infrastructure components.
Sources: supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:16-25, src/components/rdm/tomos.tsx:43-47
Technical Stack
The platform utilizes a modern web stack for its Single Page Application (SPA) and serverless backend.
| Component | Technology |
|---|---|
| Frontend | React 18 + Vite + TypeScript |
| Routing | React Router |
| Data Fetching | TanStack React Query |
| UI/Styling | Tailwind CSS + Radix UI |
| Mapping | Leaflet + React-Leaflet |
| Backend | Supabase Edge Functions (Deno) |
| Database | PostgreSQL (via Supabase) |
| Payments | Stripe |
Sources: README.md:38-47
Core Modules and Features
1. Digital Territory and Mapping
RDM Digital operates as a "1:1 Digital Twin" for Real del Monte. It includes a "Forensic Digital Twin" capability to model structural entities like roads and drainage for public work auditing.
- POIs (Points of Interest): Locations categorized by federation (e.g., Mina de Acosta under 'cultural').
- Geographical Constraints: The system is "GEO-LOCKED" to the coordinates of Real del Monte (approx. 19.9655° N, 98.6753° W).
- Mode Isla (Island Mode): Local P2P mesh support to maintain economic and emergency pulses if external connectivity fails.
Sources: src/components/rdm/territory.tsx:16-32, supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:43-52
2. Federated Governance and Repositories
The platform uses GitHub as a "Federated Database," classifying repositories into federations and typologies (e.g., canonical, commerce, protocol).
The sequence diagram shows the data flow for synchronizing GitHub repositories with the internal federation state.
Sources: src/pages/Repositorio.tsx:32-46, supabase/functions/federation-state/index.ts:31-36
3. Evolutionary Repository (Canon)
The project documentation and framework are organized into eleven "Tomos" (Volumes), which establish the legal, philosophical, and technical basis of the system.
| Tomo | Title | Focus |
|---|---|---|
| I | Fundamentos | TAMV definitions and axioma |
| II | Filosofía | IA as a legal instrument |
| V | Arquitectura Técnica | Federated layers (F1-F7) |
| XI | Apéndices Técnicos | BookPI™ schemes and PQC protocols |
Sources: src/components/rdm/tomos.tsx:5-96
Data Model
The database schema is designed to support multi-tenancy via federations and strict audit trails through signatures.
Key Database Tables
federations: Stores the configuration, domain, and active modules for each of the 7 branches.pois: Geolocation data for points of interest linked to specific federations.repositories: Metadata for GitHub repos used for ecosystem analysis.audit_signatures: Stores SHA256 hashes of resources to provide immutable chain of custody.businesses: Manages commerce entities, their payment status (via Stripe), and federation affiliation.
Sources: supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:10-120, src/integrations/supabase/types.ts:40-100
Security and Integrity
RDM Digital implements several layers of data integrity:
- Row Level Security (RLS): Policies in Supabase ensure only authorized users (admins) can write to sensitive tables like
federationsorrepositories. - Audit Signatures: Uses PQC (Post-Quantum Cryptography) schemes and Merkle trees to sign critical telemetry and events.
- BookPI™: A ledger system for Multi-State Records (MSR) used for tracking protocols and territorial operations.
Sources: src/components/rdm/territory.tsx:114-120, supabase/migrations/20260512080845_110fe96e-4027-403f-98c8-f6d495c1bf4c.sql:100-105
Summary
RDM Digital is an operational infrastructure that transitions from reactive city management to proactive technical sovereignty. It combines citizen services with a robust technical architecture capable of operating independently under "Island Mode" while providing a verifiable "Third Technical Witness" for territorial management through its digital twin and audit capabilities.
Sources: README.md:120-125, src/components/rdm/territory.tsx:135-145