CI/CD Pipelines & Validation

Relevant source files

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

• src/pages/wiki/implementacion/CicdPipelines.tsx
• federation/tamv-digital-nexus/scripts/check-architecture.ts
• federation/tamv-digital-nexus/supabase/functions/tamv-fusion-core/index.ts
• src/pages/wiki/modulo-omega/WikiViva.tsx
• src/pages/wiki/metaverso-xr/RoadmapCivilizatorio.tsx
• federation/tamv-digital-nexus/AGENTS.md

The CI/CD (Continuous Integration/Continuous Deployment) and Validation system in TAMV is governed by the QC-TAMV-01 Constitutional Quality Framework. This framework translates architectural principles into executable mechanisms to ensure technical non-negotiables are met by humans, AI agents, and automated pipelines. It serves as the "prefrontal cortex" of the ecosystem, linking technical compliance with operational validity.

Sources: src/pages/wiki/implementacion/CicdPipelines.tsx:12-16, src/pages/wiki/modulo-omega/ManifiestoTamv.tsx:23-25

QC-TAMV-01 Constitutional Invariants

The core of the validation logic is the L1–L9 Constitutional Laws, which define strict architectural boundaries. These laws ensure structural determinism and total traceability within the civilizatory client.

Summary of Constitutional Laws (L1–L9)

Law	Name	Technical Invariant
L1	Unique Root	createRoot must only exist in src/main.tsx
L2	Unique Router	BrowserRouter restricted to src/App.tsx
L3	Unique Layout	Layout.tsx mounted exactly once in App.tsx
L4	Route-Page Mapping	Files in src/pages/* must correspond to a single route
L5	Page Responsibility	Pages compose modules/domains; they do not initialize services
L6	Independent Modules	src/modules/* cannot import navigation or pages
L7	Visual Isolation	Root path / cannot show components specific to /login
L8	Separation of Concerns	No layer may assume the responsibilities of another
L9	Audited Exceptions	Violations require formal registration in DigyTAMV

Sources: src/pages/wiki/implementacion/CicdPipelines.tsx:21-34, federation/tamv-digital-nexus/scripts/check-architecture.ts:133-146

MD-X5 (Deca-V) Pipeline

The MD-X5 Deca-V pipeline is the mandatory execution sequence for any Pull Request targeting main or release/* branches. It consists of 10 distinct cycles that validate everything from static syntax to post-deployment health.

Automated Architecture Validation

The system employs a specialized script, check-architecture.ts, to detect violations of the constitutional laws by analyzing the dependency graph.

Architectural Invariant Checker

The checker validates the following constraints using regex and file-system analysis:

• Module Agnosticism: Modules are checked to ensure they do not import react-router-dom or files from the pages/ directory.
• Initialization Control: Pages are warned if they directly import Supabase clients, as services should be abstracted in integrations/.
• Domain Isolation: Ensures domain files do not import UI-layer components like pages.

function validateL6_ModulesAgnostic(files: string[], violations: Violation[]): void {
  // Logic to prevent modules from importing routing or pages
  for (const file of moduleFiles) {
    const imports = extractImports(content);
    for (const imp of imports) {
      if (imp.includes('react-router-dom')) {
        violations.push({ rule: 'L6', severity: 'error', message: 'Module imports navigation' });
      }
    }
  }
}

Sources: federation/tamv-digital-nexus/scripts/check-architecture.ts:182-205, federation/tamv-digital-nexus/scripts/check-architecture.ts:207-226

Fusion Core Orchestration

The TAMV Fusion Core acts as the MD-X4 Orchestrator, performing health checks, content synchronization, and registering validation evidence into the MSR (Immutable Narrative Ledger).

Orchestration Cycle Workflow

AI Agent Validation & Safety

AI agents operating within the TAMV ecosystem (such as Isabella AI) are subject to specific validation locks to prevent unauthorized modifications to the core logic.

• CANON_LOCK: Set to TRUE to prevent agents from redefining canonical modules.
• CODE_WRITE: Restricted to prevent direct changes to production logic without human authorization.
• Escalation Policy: Any instructions that conflict with the Master Canon or QC-TAMV-01 require a complete stop and human review.

Sources: federation/tamv-digital-nexus/AGENTS.md:6-15, src/pages/wiki/implementacion/CicdPipelines.tsx:112-118

Operational Metrics & Success Criteria

Validation success is measured through specific performance and compliance targets defined in the QC framework.

Area	Success Metric
QA Compliance	100% coverage of QC-TAMV-01 rules
E2E Stability	0 failures in critical routes (feed, login)
Observability	100% of Auth/Post events logged to MSR
P95 Latency	< 4s for AI services (Isabella)
Performance	≥ 45 FPS in XR environments

Sources: src/pages/wiki/implementacion/CicdPipelines.tsx:98-106, src/pages/wiki/metaverso-xr/RoadmapCivilizatorio.tsx:40-45

The CI/CD system in TAMV is not merely a deployment tool, but a Constitutional Guard that ensures every code change adheres to the civilizatory and ethical standards of the project, providing 100% traceability via the MSR/BookPI ledger.