Deployment Guide
Relevant source files
The following files were used as context for generating this wiki page:
The TAMV MD-X4™ ecosystem is a digital civilizatory infrastructure utilizing a modern stack composed of React, TypeScript, Vite, and Supabase. This guide outlines the mandatory procedures for deploying the frontend, backend services (Edge Functions), and database migrations to production environments, ensuring architectural integrity and quality through constitutional checks.
Sources: README_TAMV_COMPLETO.md:1-6, DEPLOYMENT_GUIDE.md:1-5
Pre-Deployment Requirements
Before initiating a deployment, the environment must meet specific software and cloud service prerequisites. The ecosystem primarily relies on Lovable Cloud, which provides integrated PostgreSQL, Supabase Auth, Edge Functions, and an AI Gateway.
Sources: DEPLOYMENT_GUIDE.md:7-19
Technical Prerequisites
| Category | Requirement | Source |
|---|---|---|
| Node.js | Version >= 18.0.0 | DEPLOYMENT_GUIDE.md:10 |
| npm | Version >= 9.0.0 | DEPLOYMENT_GUIDE.md:11 |
| CI/CD | GitHub Actions (Optional: Lovable) | DEPLOYMENT_GUIDE.md:13 |
| Database | PostgreSQL via Supabase | README_TAMV_COMPLETO.md:11 |
Quality Gate: The Deca-V Protocol
Every deployment MUST pass the MD-X5 Operational Protocol, known as Deca-V. This protocol acts as a quality shield by executing a series of validation checks in repeated cycles (defaulting to 10) to prevent regressions in UI, 3D/XR, or Edge Functions.
The Deca-V flow ensures that the software is technically valid before release.
Sources: MDX5_OPERATIONAL_PROTOCOL.md:13-18, PLAN-TAMV-MODULAR.md:188-197
Architectural Validation
The scripts/check-architecture.ts script is invoked during the CI/CD pipeline to enforce QC-TAMV-01 v1.1 invariants. It builds a dependency graph and fails the build if violations are detected, such as:
- Page-to-page imports.
- Routing logic inside modular components.
- Direct Supabase imports within view layers (should be in integrations).
Sources: scripts/check-architecture.ts:16-30, PLAN-TAMV-MODULAR.md:18-24
Deployment Strategies
Option 1: Lovable Cloud (Automatic)
The default deployment path involves pushing code to the Lovable editor. Changes are automatically deployed to the managed infrastructure. Custom domains require CNAME records pointing to cname.lovable.app.
Sources: DEPLOYMENT_GUIDE.md:24-38
Option 2: Manual Vercel/Netlify Deploy
For manual deployments, a production build must be generated and environment variables configured.
# Production Build
npm run build
# Vercel Deployment
vercel --prod
Sources: DEPLOYMENT_GUIDE.md:43-58, README_TAMV_COMPLETO.md:104
Database & Backend Configuration
Core Tables
Deploying the database requires executing migrations for critical tables. The system utilizes Row Level Security (RLS) as a mandatory security layer for all entities.
| Table | Purpose | Security |
|---|---|---|
profiles | User identity and roles | RLS Enabled |
analytics_events | Behavioral tracking | User-filtered |
user_metrics | Quantum coherence data | System-updated |
security_scans | Threat level monitoring | Admin/System |
Sources: DEPLOYMENT_GUIDE.md:86-146
Edge Functions Deployment
The ecosystem utilizes specialized Edge Functions for AI and Security. These are located in supabase/functions/ and must be deployed via the Supabase CLI or Lovable dashboard.
isabella-chat: AI assistant logic.tamv-content-sync: Documentation indexing.tamv-fusion-core: System health and MSR registry.
Sources: README_TAMV_COMPLETO.md:13-18, supabase/functions/tamv-fusion-core/index.ts:1-10
Automated CI/CD Pipeline
The following sequence diagram illustrates the GitHub Actions workflow triggered by a push to the main branch.
Sources: DEPLOYMENT_GUIDE.md:182-212, README.md:118-120
Post-Deployment Checklist
- Verification: Confirm
login/signupflows and Isabella AI responsiveness. - Architecture: Review
architecture-report.jsongenerated by the checker. - Security: Ensure RLS is active on all new tables via
ALTER TABLE ... ENABLE ROW LEVEL SECURITY. - Monitoring: Check Edge Function logs for 404 or CORS errors.
Sources: DEPLOYMENT_GUIDE.md:215-228, scripts/check-architecture.ts:285-288
The successful deployment of the TAMV Digital Nexus ensures the convergence of 177 federated repositories into a single, unified, and secure operational core. Through the Deca-V protocol and constitutional QA checks, the system maintains high standards of architectural integrity and reliability.
Sources: README.md:3-6, PLAN-TAMV-MODULAR.md:1-6