Project Vision & Soul

Relevant source files

The following files were used as context for generating this wiki page:

• SOUL.md
• AGENTS.md
• README_TAMV_COMPLETO.md
• PLAN-TAMV-MODULAR.md
• 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md
• README.md

Introduction

Project TAMV (MD-X4™) represents a "Mexican Digital Civilizatory Ecosystem" designed for the functional and documental convergence of over 177 federated repositories into a unified, sovereign base. The project is built upon a philosophy of "Quantum-Emotional" interaction, merging advanced technical architectures with high-level human values and strict constitutional quality controls. Its primary objective is to create a maintainable, scalable, and secure core that integrates 3D/XR environments, digital economy, decentralized governance, and artificial intelligence.

The "Soul" of the project is defined by its identity as a technical cartographer of the TAMV/THE SOF ecosystem, governed by a "Master Canon" that prevails over ad-hoc modifications. This vision is enforced through the QC-TAMV-01 constitutional framework, which ensures that all technical developments—whether performed by humans or AI agents—adhere to non-negotiable architectural invariants and ethical principles.

Sources: README_TAMV_COMPLETO.md:1-10, README.md:1-15, SOUL.md:1-15

Core Identity and Values

The project operates under a strict hierarchy where the "Canon" outranks individual creativity or inference. This identity is personified by the TAMV_DOC_SENTINEL, an agent role dedicated to unifying knowledge and ensuring traceability across the ecosystem without altering the established fundamental structures.

Operational Values

The ecosystem follows four primary operational values to maintain its integrity:

1. Canon > Creativity: The established framework is the priority.
2. Primary Source > Inference: Documentation must be based on evidence.
3. Escalation on Conflict: Any doubt results in a full stop and human review.
4. Document before Modify: Changes must be mapped and justified before implementation.

Sources: SOUL.md:10-20, AGENTS.md:10-20

Hard Prohibitions

To protect the "Soul" of the project, specific restrictions are implemented:

• No redefinition of TAMV or its canon modules (MSR, THE SOF, Isabella, etc.).
• No direct changes to critical production logic without explicit human authorization.
• No legal wording changes without the TODO_REVIEW_LEGAL tag.
• No elevation of privileges based on untrusted external data.

Sources: SOUL.md:22-28, AGENTS.md:30-35

Architectural Vision: The Civilizatory Client

The architecture is described as "Quantum-Native," utilizing a React-based frontend with Three.js for immersive 3D/XR experiences, supported by a Supabase backend. The structure is strictly modular, divided into Pages, Core, Modules, and Domains.

Structural Determinism

The project enforces "Structural Determinism" through the QC-TAMV-01 Constitutional Quality Control System. This system translates architectural principles into executable mechanisms (linting, tests, static analysis).

Technical Invariants (L1-L9)

The "Soul" of the code is protected by nine constitutional laws that define valid technical states:

Law	Title	Description
L1	Root Unico	ReactDOM.createRoot exists only in main.tsx.
L2	Router Unico	BrowserRouter exists only in App.tsx.
L3	Layout Unico	Layout.tsx is mounted exactly once in App.tsx.
L4	Page Correspondence	Each page corresponds to one route; pages never import other pages.
L5	Logic Separation	Pages contain no business logic or global state initializations.
L6	Agnostic Modules	Modules in src/modules/* cannot import router or layout.
L7	Controlled Init	Global services are initialized only in integrations/ or core/.
L8	No View Overlap	Routes cannot render fragments of other routes simultaneously.
L9	Audited Exceptions	Any exception must be declared, documented, and never reach production.

Sources: 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md:65-100

Hybrid Governance and DAOs

The vision includes a "Hybrid Governance" model where various DAOs (Decentralized Autonomous Organizations) manage specific technical chambers without controlling the project's economy.

Governance Flow

DAO Responsibilities

DAO	Permissions	Restrictions
DAO-QA	Adjust lint rules, define test coverage thresholds.	Cannot change Stripe logic or MSR commissions.
DAO-Ethics/IA	Define AI context limits, audit system prompts.	Cannot modify economic parameters.
DAO-Security	Identify modules requiring TEE (Trusted Execution).	No access to root keys or economic decisions.
DAO-Community	Propose visibility and moderation policies.	No control over monetization.

Sources: PLAN-TAMV-MODULAR.md:25-100, 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md:145-160

The Sentinel Shield: Security Vision

Security in TAMV (MD-X4) is viewed as a multi-layered biological system called DEKATEOTL, consisting of 11 layers of protection.

DEKATEOTL Layers

1. Digital Identity Analysis (ID-NVIDA).
2. User Behavior tracking.
3. Quantum Anomaly detection.
4. Post-Quantum Cryptography (PQC).
5. Emotional Biometrics.
6. Reputation Blockchain.
7. Identity Bifurcation.
8. Deepfake Detection.
9. Continuous Auditing.
10. Distributed Consensus.
11. System Self-Healing.

Sources: README_TAMV_COMPLETO.md:158-175, PLAN-TAMV-MODULAR.md:140-150

Conclusion

The Project Vision & Soul of TAMV MD-X4™ is rooted in the transition from a fragmented ecosystem of 177 repositories to a single, sovereign "Digital Nexus." This transition is not merely technical but constitutional, governed by the immutable laws of QC-TAMV-01 and the oversight of specialized DAOs. By prioritizing the "Master Canon" and automated structural verification, the project ensures that its civilizatory mission remains resilient against architectural decay and unauthorized modification.

Sources: README.md:60-80, SOUL.md:30-40