Introduction & Setup

Relevant source files

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

• README.md
• package.json
• README_TAMV_COMPLETO.md
• DEPLOYMENT_GUIDE.md
• 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md
• PLAN-TAMV-MODULAR.md

The TAMV MD-X4™ (Digital Nexus) is a unified civilizatory ecosystem designed to consolidate 177 federated repositories into a single, maintainable core. It integrates advanced modules for 3D/XR environments, AI assistance (Isabella Prime), digital economy (TAU/TCEP), and decentralized governance, all governed by a strict "Constitutional" Quality Assurance (QA) framework.

The setup process focuses on ensuring structural determinism through the MD-X5 (Deca-V) quality shield, which enforces architectural invariants before any deployment. This ensures that the system remains stable and traceable as it scales from a collection of federated modules to a unified sovereign digital infrastructure.

Sources: README.md:1-15, README_TAMV_COMPLETO.md:1-10, PLAN-TAMV-MODULAR.md:5-20

Technical Stack & Architecture

The project utilizes a modern web stack optimized for immersive experiences and secure backend operations.

Layer	Technologies
Frontend	React 18.3, TypeScript, Vite, Tailwind CSS, Framer Motion
3D/XR Engine	Three.js, @react-three/fiber, @react-three/drei
State Management	Zustand (with persistence)
Backend (BaaS)	Supabase (PostgreSQL, Auth, Edge Functions, Storage)
QA/Shield	ESLint (TAMV Plugin), Vitest, Playwright, Deca-V

Sources: README_TAMV_COMPLETO.md:13-30, package.json:35-85

Architectural Invariants (QC-TAMV-01)

The project follows strict "Constitutional Laws" to maintain structural integrity:

• L1 (Unique Root): createRoot must only exist in src/main.tsx.
• L2 (Unique Router): BrowserRouter is restricted to src/App.tsx.
• L3 (Unique Layout): Layout.tsx is mounted exactly once in App.tsx.
• L4 (Page Correspondence): Every file in src/pages/* maps to one route; pages never import other pages.
• L6 (Navigation Agnostic Modules): Modules in src/modules/* cannot import react-router-dom or pages.

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

Development Setup

Prerequisites

• Node.js: >= 18.0.0
• npm: >= 9.0.0
• Supabase Account: For database and edge functions.

Sources: README_TAMV_COMPLETO.md:105-110, DEPLOYMENT_GUIDE.md:6-15

Installation Steps

1. Clone the Repository: `git clone https://github.com/OsoPanda1/tamv-digital-nexus.git%60
2. Install Dependencies: npm install
3. Environment Configuration: Create a .env file with Supabase credentials:

   VITE_SUPABASE_URL=your_supabase_url
   VITE_SUPABASE_PUBLISHABLE_KEY=your_key
   

4. Launch Development Server: npm run dev (Available at http://localhost:8080)

Sources: README_TAMV_COMPLETO.md:112-135

Core Commands

The following scripts facilitate development and quality control:

Command	Description
npm run build	Generates the production build using Vite.
npm run lint	Runs ESLint with the custom eslint-plugin-tamv.
npm run typecheck	Executes TypeScript compiler check without emitting files.
npm run audit:deca-v	Runs the MD-X5 quality shield (10 cycles of lint, check, test, build).
npm run check:architecture	Executes the script to validate architectural invariants.

Sources: package.json:7-25, README.md:38-60

System Workflow & Deployment

The deployment process is gated by the Deca-V Audit, ensuring that no code with architectural violations reaches production.

Quality Shield Flow

This diagram illustrates the mandatory CI/CD pipeline before a PR can be merged into the main branch.

The Deca-V audit runs multiple cycles of validation to ensure consistency and prevent regressions.
Sources: README.md:52-65, PLAN-TAMV-MODULAR.md:185-195, 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md:175-190

Database Initialization

The system requires specific PostgreSQL tables and Row Level Security (RLS) policies to function.

Required Tables

• profiles: Stores user metadata and "ID-NVIDA" digital identity.
• analytics_events: Tracks system interactions and quantum coherence metrics.
• user_metrics: Stores real-time performance and coherence data.
• security_scans: Logs results from the Anubis/Dekateotl security systems.

Sources: DEPLOYMENT_GUIDE.md:58-120

Security Configuration

All tables must have RLS enabled to prevent unauthorized data access. The project uses Supabase Auth with JWT expiration set to 3600 seconds.

-- Example RLS Policy for Profiles
ALTER TABLE public.profiles ENABLE ROW LEVEL SECURITY;
CREATE POLICY "Users can update own profile" ON public.profiles
  FOR UPDATE USING (auth.uid() = user_id);

Sources: DEPLOYMENT_GUIDE.md:122-135

Conclusion

Setting up the TAMV Digital Nexus involves more than just installing dependencies; it requires adhering to the QC-TAMV-01 constitutional framework. By utilizing the Deca-V audit and architectural checkers, developers ensure that the modular components (AI, XR, Economy) remain interoperable and secure within the unified ecosystem. Correct setup of the Supabase backend and environment variables is critical for the multimodal capabilities of Isabella AI and the immersive environments of Dream Spaces.

Sources: README.md:75-90, PLAN-TAMV-MODULAR.md:230-245