MD-X5 Operational Protocol

Relevant source files

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

• MDX5_OPERATIONAL_PROTOCOL.md
• README.md
• PLAN-TAMV-MODULAR.md
• 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md
• scripts/check-architecture.ts
• eslint-plugin-tamv/index.js

The MD-X5 Operational Protocol, also referred to as Deca-V, is the real-world execution framework designed to enforce the "Quality Shield" of the TAMV Digital Nexus project. Its primary purpose is to ensure that no changes are deployed to production without passing a rigorous, repeated cycle of validation checks that guarantee technical integrity, architectural consistency, and build reproducibility.

This protocol acts as a gatekeeper for all functional areas, including UI/3D/XR, domain logic, and Supabase Edge Functions. By executing these checks in repetitive cycles, the system mitigates the risk of regressions in frontend state, TypeScript typing, or structural violations that could otherwise reach production environments.

Sources: MDX5_OPERATIONAL_PROTOCOL.md:1-12, README.md:43-51

Deca-V Validation Engine

The core of the MD-X5 protocol is the Deca-V audit system. The name is derived from the requirement to run ten consecutive cycles of the project's verification suite to ensure that the build is not only successful but stable and consistent across multiple iterations.

Core Command and Configuration

The primary interface for this protocol is a single master command that orchestrates the underlying tools.

# Standard execution (10 cycles)
npm run audit:deca-v

# Fast mode (custom cycles for local iteration)
DECA_V_CYCLES=2 npm run audit:deca-v

Sources: MDX5_OPERATIONAL_PROTOCOL.md:14-25, README.md:53-61

Execution Sequence

During each cycle, the protocol executes four mandatory checks. If any command fails during any cycle, the process aborts immediately with an exit code of 1, blocking the deployment or integration.

Step	Command	Description
1	npm run lint	Runs the constitutional ESLint rules (QC-TAMV-01)
2	npm run typecheck	Validates TypeScript types across the entire codebase
3	npm run test	Executes unit and integration tests (Vitest)
4	npm run build	Verifies that a production build can be successfully generated

Sources: MDX5_OPERATIONAL_PROTOCOL.md:17-21, README.md:56-60

Architectural Integration

The MD-X5 protocol serves as the final gate in the CI/CD pipeline, specifically protecting the repository against "architectural regressions." It is deeply integrated with the QC-TAMV-01 Constitutional Quality Control system.

The Quality Shield Flow

The following diagram illustrates how the Deca-V protocol interacts with the development workflow and the constitutional ruleset.

This diagram shows the iterative nature of the Deca-V audit and its dependence on constitutional linting rules to enforce architectural laws.
Sources: MDX5_OPERATIONAL_PROTOCOL.md:27-32, PLAN-TAMV-MODULAR.md:225-235, eslint-plugin-tamv/index.js:10-50

Constitutional Verification (QC-TAMV-01)

A significant portion of the MD-X5 protocol relies on the eslint-plugin-tamv and the check-architecture.ts script. These tools enforce "Invariant Laws" that are non-negotiable for the project's structural integrity.

Invariant Laws Enforced

• L1 - Unique Root: Ensures ReactDOM.createRoot exists only in src/main.tsx.
• L2 - Unique Router: Restricts BrowserRouter to src/App.tsx.
• L4 - Page Isolation: Prevents pages from importing other pages to maintain strict route-page correspondence.
• L6 - Navigation Agnostic Modules: Prohibits modules in src/modules/* from importing react-router-dom.

Sources: 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md:65-100, eslint-plugin-tamv/index.js:15-180

Automated Analysis Logic

The scripts/check-architecture.ts tool, triggered during the audit, builds a dependency graph of the project to find violations that standard linting might miss.

The sequence shows the script's role in the automated validation of the MD-X5 protocol by scanning the file system and enforcing isolation rules.
Sources: scripts/check-architecture.ts:200-260, 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md:155-165

Operational Requirements for Deployment

For any Pull Request (PR) to be merged into protected branches (main, release/*), the MD-X5 protocol defines a mandatory pipeline.

1. Static Analysis: npm run lint must return zero errors using the tamv plugin configuration.
2. Type Integrity: npm run check (TypeScript without emit) must pass.
3. Unit Tests: All Vitest suites must pass.
4. E2E Validation: Playwright tests must confirm critical routes (/, /login, /isabella).
5. Structural Integrity: The check-architecture script must confirm no graph violations.

Sources: PLAN-TAMV-MODULAR.md:225-235, 02_MODULOS/M05_IA_TAMVAI/INTERNO/QC-TAMV-01-v1.1.md:188-198

Conclusion

The MD-X5 Operational Protocol (Deca-V) is the implementation of TAMV's constitutional quality standards. By mandating a 10-cycle verification process, it ensures that the "Civilizatory Client" remains deterministic, structurally sound, and free from architectural drift. It serves as the final technical barrier, ensuring that only "Canon-compliant" code reaches the production ecosystem.