@evolith/core-domain 1.0.1 → 1.0.3

package/rulesets/definition-of-done/definition-of-done.rules.json

@@ -1,135 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/definition-of-done/definition-of-done.rules.json",
-  "title": "Definition of Done Rules",
-  "description": "Machine-readable encoding of the Evolith Definition of Done. Mandatory checklist for every Technical Story before it can be marked Done.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-01-01",
-  "rules": [
-    {
-      "id": "DOD-01",
-      "severity": "MUST",
-      "category": "code",
-      "title": "Code implemented and reviewed",
-      "description": "All implementation code is written and at least one peer review approval exists. Self-review does not count.",
-      "validationQuery": "PR has minimum 1 approved review. No direct push to main/develop.",
-      "blocking": true,
-      "checklistItem": "code-implemented"
-    },
-    {
-      "id": "DOD-02",
-      "severity": "MUST",
-      "category": "testing",
-      "title": "Unit tests meet coverage threshold",
-      "description": "Unit test coverage for business logic >= 80%. Layer-specific thresholds apply: Domain >= 95%, Application >= 85%, Infrastructure >= 60%.",
-      "validationQuery": "Coverage report from CI shows >= 80% for business logic. Per-layer thresholds validated.",
-      "blocking": true,
-      "checklistItem": "tests-passing"
-    },
-    {
-      "id": "DOD-03",
-      "severity": "MUST",
-      "category": "testing",
-      "title": "All acceptance criteria verified",
-      "description": "All acceptance criteria from the Functional Story are verified and pass. Manual or automated verification documented.",
-      "validationQuery": "All acceptance criteria marked as verified in story tracker. E2E or integration tests confirm criteria.",
-      "blocking": true,
-      "checklistItem": "acceptance-criteria-verified"
-    },
-    {
-      "id": "DOD-04",
-      "severity": "MUST",
-      "category": "documentation",
-      "title": "Documentation updated",
-      "description": "Documentation delta is produced alongside code changes. This includes: updated ADRs if decisions were made, inline code documentation for complex logic, README updates if public interfaces changed.",
-      "validationQuery": "PR includes documentation changes. Reviewer validates documentation completeness.",
-      "blocking": true,
-      "checklistItem": "documentation-updated"
-    },
-    {
-      "id": "DOD-05",
-      "severity": "MUST",
-      "category": "observability",
-      "title": "Observability instrumentation added",
-      "description": "Production paths have observable telemetry: traces with CorrelationId, structured logs with SessionTrackingId, metrics for key operations.",
-      "validationQuery": "OTel spans present for production API paths. Logs include required context fields.",
-      "blocking": true,
-      "checklistItem": "observability-added"
-    },
-    {
-      "id": "DOD-06",
-      "severity": "MUST",
-      "category": "security",
-      "title": "Security gates passed",
-      "description": "CodeQL scan passed with zero High/Critical findings. No new CVEs introduced. Secret scanning passed.",
-      "validationQuery": "CI security gates all green. CodeQL, dependency scan, secret scan passed.",
-      "blocking": true,
-      "checklistItem": "security-gates-passed"
-    },
-    {
-      "id": "DOD-07",
-      "severity": "MUST",
-      "category": "architecture",
-      "title": "ADR created if architectural decision made",
-      "description": "If the implementation required a new architectural decision (boundary change, technology selection, security model change), an ADR is created and linked to the story.",
-      "validationQuery": "Architectural decisions documented in ADR. Story links to relevant ADR IDs.",
-      "blocking": false,
-      "checklistItem": "adr-created-if-needed"
-    },
-    {
-      "id": "DOD-08",
-      "severity": "MUST",
-      "category": "integration",
-      "title": "Integration tests pass",
-      "description": "Integration tests (adapter tests with testcontainers) pass. Tests cover persistence adapters, gateway adapters, and inter-service contracts.",
-      "validationQuery": "Integration test suite passes. Contract tests for inter-service calls pass.",
-      "blocking": true,
-      "checklistItem": "integration-tests-passing"
-    },
-    {
-      "id": "DOD-09",
-      "severity": "MUST",
-      "category": "lint",
-      "title": "Linting and formatting passed",
-      "description": "All linting rules pass (ESLint, Prettier formatting). No lint errors, no formatting violations.",
-      "validationQuery": "CI lint step green. No ESLint errors, Prettier formatted.",
-      "blocking": true,
-      "checklistItem": "lint-passing"
-    },
-    {
-      "id": "DOD-10",
-      "severity": "MUST",
-      "category": "ci",
-      "title": "CI pipeline green on target branch",
-      "description": "CI pipeline runs successfully on the feature branch with all quality gates passing before merge.",
-      "validationQuery": "All CI checks green. Pipeline completed successfully on feature branch.",
-      "blocking": true,
-      "checklistItem": "ci-green"
-    }
-  ],
-  "summaryChecklist": [
-    "code-implemented",
-    "tests-passing",
-    "acceptance-criteria-verified",
-    "documentation-updated",
-    "observability-added",
-    "security-gates-passed",
-    "adr-created-if-needed",
-    "integration-tests-passing",
-    "lint-passing",
-    "ci-green"
-  ],
-  "references": [
-    "reference/governance/sdlc/02-engineering/construction-focused-sdlc-framework.md",
-    "reference/governance/sdlc/quality-gates.md"
-  ],
-  "exitCriteria": {
-    "description": "All MUST items checked. Story cannot be marked Done without all blocking items satisfied.",
-    "validationTools": [
-      "CI pipeline",
-      "coverage reports",
-      "PR review",
-      "story tracker"
-    ]
-  }
-}

package/rulesets/engineering-manifesto/README.es.md

@@ -1,26 +0,0 @@
-# Ruleset del Manifiesto de Ingeniería
-
-> **Navegación Bilingüe:** [English Version](./README.md)
-
-Punto de entrada ejecutable WS1 para el ruleset del Manifiesto de Ingeniería de Evolith.
-
-## Propósito
-
-Este directorio expone `rulesets/engineering-manifesto` como la ruta ejecutable canónica que verifica la auditoría de fortaleza como data inteligente. El ruleset codifica restricciones SOLID, DRY, KISS, YAGNI y anti-patrones consumidas por el validador nativo de rulesets y los flujos de evidencia CI.
-
-## Artefactos
-
-| Artefacto | Propósito |
-|---|---|
-| [engineering-manifesto.rules.json](./engineering-manifesto.rules.json) | Ruleset nativo machine-readable para validación del Manifiesto de Ingeniería |
-| [../opa/engineering-manifesto.rego](../opa/engineering-manifesto.rego) | Artefacto de paridad OPA para validación del Manifiesto de Ingeniería |
-| [../opa/engineering-manifesto.test.rego](../opa/engineering-manifesto.test.rego) | Cobertura de pruebas OPA para la política del Manifiesto de Ingeniería |
-
-## Validación
-
-Ejecuta estos checks después de cambiar el ruleset:
-
-```bash
-npx jest --config packages/core-domain/jest.config.js --rootDir packages/core-domain --testPathPatterns='ruleset-validation.mode' --no-coverage
-.harness/bin/opa test rulesets/opa/engineering-manifesto.rego rulesets/opa/engineering-manifesto.test.rego -v
-```

package/rulesets/engineering-manifesto/README.md

@@ -1,26 +0,0 @@
-# Engineering Manifesto Ruleset
-
-> **Bilingual Navigation:** [Versión en Español](./README.es.md)
-
-Executable WS1 entrypoint for the Evolith Engineering Manifesto ruleset.
-
-## Purpose
-
-This directory exposes `rulesets/engineering-manifesto` as the canonical executable path checked by the intelligent data strength audit. The ruleset encodes SOLID, DRY, KISS, YAGNI, and anti-pattern constraints consumed by the native ruleset validator and CI evidence flows.
-
-## Artifacts
-
-| Artifact | Purpose |
-|---|---|
-| [engineering-manifesto.rules.json](./engineering-manifesto.rules.json) | Native machine-readable ruleset for Engineering Manifesto validation |
-| [../opa/engineering-manifesto.rego](../opa/engineering-manifesto.rego) | OPA policy parity artifact for Engineering Manifesto validation |
-| [../opa/engineering-manifesto.test.rego](../opa/engineering-manifesto.test.rego) | OPA test coverage for the Engineering Manifesto policy |
-
-## Validation
-
-Run these checks after changing the ruleset:
-
-```bash
-npx jest --config packages/core-domain/jest.config.js --rootDir packages/core-domain --testPathPatterns='ruleset-validation.mode' --no-coverage
-.harness/bin/opa test rulesets/opa/engineering-manifesto.rego rulesets/opa/engineering-manifesto.test.rego -v
-```

package/rulesets/engineering-manifesto/engineering-manifesto.rules.json

@@ -1,145 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/engineering-manifesto/engineering-manifesto.rules.json",
-  "title": "Engineering Manifesto Rules",
-  "description": "Machine-readable encoding of the Evolith Engineering Manifesto principles. SOLID, DRY, KISS, YAGNI, and anti-pattern rules enforced via linting and review.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-01-01",
-  "antiPatterns": [
-    {
-      "id": "AP-01",
-      "name": "God Class / Object",
-      "description": "Class with too many responsibilities (> 500 lines, > 20 methods). Violates SRP.",
-      "detection": "ESLint max-lines-per-file, max-classes-per-file"
-    },
-    {
-      "id": "AP-02",
-      "name": "Circular Dependency",
-      "description": "Module A imports Module B which imports Module A directly or indirectly.",
-      "detection": "dependency-cruiser no-circular"
-    },
-    {
-      "id": "AP-03",
-      "name": "Shotgun Surgery",
-      "description": "One change requires modifying many different classes across the codebase.",
-      "detection": "Code review; refactoring debt"
-    },
-    {
-      "id": "AP-04",
-      "name": "Spaghetti Code",
-      "description": "Code with complex nested control structures, no clear structure, tangled logic.",
-      "detection": "High cyclomatic complexity + low cohesion metrics"
-    },
-    {
-      "id": "AP-05",
-      "name": "Magic Numbers/Strings",
-      "description": "Unnamed constants scattered throughout code instead of named constants.",
-      "detection": "ESLint no-magic-numbers"
-    }
-  ],
-  "references": [
-    "reference/governance/standards/engineering/engineering-manifesto.md",
-    "reference/architecture/adrs/core/0049-naming-semantics-clean-code-policy.md"
-  ],
-  "exitCriteria": {
-    "description": "All SOLID violations blocked in CI. DRY violations detected and fixed. Anti-patterns flagged in code review.",
-    "validationTools": [
-      "ESLint",
-      "SonarQube",
-      "dependency-cruiser",
-      "code review"
-    ]
-  },
-  "rules": [
-    {
-      "id": "EM-S-01",
-      "severity": "MUST",
-      "category": "SOLID",
-      "title": "Single Responsibility: one reason to change",
-      "description": "Every class and module has one, and only one, reason to change. No God classes or multipurpose utilities.",
-      "validationQuery": "ESLint rule max-classes-per-file or equivalent. Class length < 200 lines.",
-      "blocking": false
-    },
-    {
-      "id": "EM-S-02",
-      "severity": "MUST",
-      "category": "SOLID",
-      "title": "Open/Closed: open for extension, closed for modification",
-      "description": "Software entities (classes, modules, functions) are open for extension but closed for modification. New behavior added via inheritance/composition, not by editing existing code.",
-      "validationQuery": "Code review verifies no modification of tested/approved classes for new features. Extension via polymorphism preferred.",
-      "blocking": false
-    },
-    {
-      "id": "EM-S-03",
-      "severity": "MUST",
-      "category": "SOLID",
-      "title": "Liskov Substitution: subtype substitutable for base",
-      "description": "Objects of a superclass shall be replaceable with objects of a subclass without affecting correctness. No Liskov violation anywhere.",
-      "validationQuery": "TypeScript: no unsafe casting. Liskov violations detected via type checking and test coverage.",
-      "blocking": true
-    },
-    {
-      "id": "EM-S-04",
-      "severity": "MUST",
-      "category": "SOLID",
-      "title": "Interface Segregation: fine-grained interfaces",
-      "description": "Clients should not be forced to depend on interfaces they do not use. Prefer many small interfaces over one large interface.",
-      "validationQuery": "Interface size checked. No interface with > 10 methods without documented justification.",
-      "blocking": false
-    },
-    {
-      "id": "EM-S-05",
-      "severity": "MUST",
-      "category": "SOLID",
-      "title": "Dependency Inversion: depend on abstractions",
-      "description": "High-level modules must not depend on low-level modules. Both must depend on abstractions. Abstractions must not depend on details.",
-      "validationQuery": "Dependency direction validated via eslint-plugin-boundaries. Core has no Infrastructure imports.",
-      "blocking": true
-    },
-    {
-      "id": "EM-D-01",
-      "severity": "MUST",
-      "category": "DRY",
-      "title": "Don't Repeat Yourself",
-      "description": "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system. Duplicated logic must be extracted to a single source.",
-      "validationQuery": "AST analysis detects duplicated code blocks > 5 lines. ESLint no-duplicate-imports or equivalent.",
-      "blocking": false
-    },
-    {
-      "id": "EM-D-02",
-      "severity": "MUST",
-      "category": "DRY",
-      "title": "Configuration not duplicated",
-      "description": "Configuration values (strings, numbers, URLs) must not be hardcoded in multiple places. Centralized config or constants.",
-      "validationQuery": "Magic numbers/strings detected. Configuration centralized in config files or env vars.",
-      "blocking": false
-    },
-    {
-      "id": "EM-K-01",
-      "severity": "MUST",
-      "category": "KISS",
-      "title": "Keep It Simple, Stupid",
-      "description": "Simplicity is the ultimate sophistication. Prefer simple solutions over complex ones. Complexity is the enemy of reliability.",
-      "validationQuery": "Cyclomatic complexity < 15 per method/function. Nested ternaries and complex conditions flagged.",
-      "blocking": true
-    },
-    {
-      "id": "EM-K-02",
-      "severity": "SHOULD NOT",
-      "category": "KISS",
-      "title": "Avoid premature abstraction",
-      "description": "Do not abstract for hypothetical future reuse. Abstract when duplication appears, not before.",
-      "validationQuery": "Unused interfaces or abstract classes flagged. Abstraction must have concrete use.",
-      "blocking": false
-    },
-    {
-      "id": "EM-Y-01",
-      "severity": "MUST NOT",
-      "category": "YAGNI",
-      "title": "You Aren't Gonna Need It",
-      "description": "Do not implement features or abstractions until they are actually needed. Building for hypothetical futures creates complexity debt.",
-      "validationQuery": "Code review checks for unused code paths or interfaces with no implementing classes.",
-      "blocking": false
-    }
-  ]
-}

package/rulesets/evidence/README.es.md

@@ -1,12 +0,0 @@
-# Rulesets de Evidencia
-
-> **Navegación bilingüe:** [English version](./README.md)
-
-Reglas para evidencia trazable usada por gates SDLC, auditorías, revisiones de release y reportes ejecutivos.
-
-## Rulesets
-
-| Ruleset | Propósito |
-|---|---|
-| [Manifest de Evidencia](./evidence-manifest.rules.json) | Define los metadatos mínimos de evidencia necesarios para probar cumplimiento de gates, reglas o waivers. |
-

package/rulesets/evidence/README.md

@@ -1,12 +0,0 @@
-# Evidence Rulesets
-
-> **Bilingual navigation:** [Versión en Español](./README.es.md)
-
-Rules for traceable evidence used by SDLC gates, audits, release reviews, and executive reporting.
-
-## Rulesets
-
-| Ruleset | Purpose |
-|---|---|
-| [Evidence Manifest](./evidence-manifest.rules.json) | Defines the minimum evidence metadata needed to prove gate, rule, or waiver compliance. |
-

package/rulesets/evidence/evidence-manifest.rules.json

@@ -1,48 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/evidence/evidence-manifest.rules.json",
-  "title": "Evidence Manifest Rules",
-  "description": "Minimum metadata for auditable evidence generated by CLI, MCP, CI, or Tracker.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-06-08",
-  "scope": "satellite",
-  "category": "evidence",
-  "rules": [
-    {
-      "id": "EVD-01",
-      "severity": "MUST",
-      "category": "identity",
-      "title": "Evidence Has Stable Identity",
-      "description": "Every evidence item MUST include id, source, generatedAt, producer, and related rule or gate.",
-      "validationQuery": "Validate evidence manifests contain id, source, generatedAt, producer, and relatedRuleIds or relatedGateId.",
-      "blocking": true
-    },
-    {
-      "id": "EVD-02",
-      "severity": "MUST",
-      "category": "traceability",
-      "title": "Evidence Links to Source Artifact",
-      "description": "Every evidence item MUST link to the source artifact, command, CI run, or external system record that produced it.",
-      "validationQuery": "Verify sourceRef is present and resolvable.",
-      "blocking": true
-    },
-    {
-      "id": "EVD-03",
-      "severity": "MUST",
-      "category": "integrity",
-      "title": "Evidence Captures Validation Outcome",
-      "description": "Every evidence item MUST capture status, evaluated rules, blocking failures, and waiver reference when applicable.",
-      "validationQuery": "Verify status, evaluatedRules, blockingFailures, and waiverRef fields.",
-      "blocking": true
-    },
-    {
-      "id": "EVD-04",
-      "severity": "SHOULD",
-      "category": "retention",
-      "title": "Evidence Declares Retention Expectation",
-      "description": "Evidence SHOULD declare retention period and accountable owner for audit follow-up.",
-      "validationQuery": "Inspect retentionPeriod and owner fields.",
-      "blocking": false
-    }
-  ]
-}

package/rulesets/executive-scorecards/executive-scorecards.rules.es.json

@@ -1,213 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/executive-scorecards/executive-scorecards.rules.es.json",
-  "title": "Reglas de Scorecards Ejecutivos",
-  "description": "Reglas que codifican métricas DORA y SPACE para visibilidad ejecutiva. Estas reglas aseguran Predictibilidad, Adherencia (Architecture Drift Index), y Eficiencia en productos satélite.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-06-06",
-  "scope": "satellite",
-  "category": "executive-metrics",
-  "principles": [
-    {
-      "id": "DORA-01",
-      "principle": "Frecuencia de Despliegue",
-      "statement": "Los productos satélite DEBEN medir y reportar frecuencia de despliegue. Objetivo: al menos una vez por semana a producción.",
-      "rationale": "Evolith Product Vision §6: Frecuencia de Despliegue es una métrica DORA core. Alta frecuencia indica pipeline CD saludable.",
-      "severity": "MUST",
-      "validationQuery": "CI/CD pipeline exporta métrica de frecuencia de despliegue. Reporte muestra deployments/semana a producción.",
-      "blocking": false,
-      "metrics": {
-        "name": "Deployment Frequency",
-        "unit": "despliegues por semana",
-        "target": ">= 1",
-        "measurement": "Count de despliegues a producción en últimas 4 semanas / 4",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "DORA-02",
-      "principle": "Lead Time para Cambios",
-      "statement": "Los productos satélite DEBEN medir y reportar lead time desde commit a producción. Objetivo: menos de 7 días para cambios medianos.",
-      "rationale": "Evolith Product Vision §6: Lead Time mide qué tan rápido los cambios fluyen de commit a producción. Lead time corto indica pipeline eficiente.",
-      "severity": "MUST",
-      "validationQuery": "CI/CD pipeline exporta métrica de lead time. Reporte muestra días mediana desde primer commit a despliegue a producción.",
-      "blocking": false,
-      "metrics": {
-        "name": "Lead Time for Changes",
-        "unit": "días",
-        "target": "<= 7",
-        "measurement": "Tiempo mediana desde primer commit de un cambio a despliegue a producción",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "DORA-03",
-      "principle": "Tasa de Fallo en Cambios",
-      "statement": "Los productos satélite DEBEN medir y reportar tasa de fallo en cambios. Objetivo: menos de 15% de despliegues causan fallos.",
-      "rationale": "Evolith Product Vision §6: Change Failure Rate mide el porcentaje de despliegues que causan fallos en producción.",
-      "severity": "MUST",
-      "validationQuery": "CI/CD pipeline exporta tasa de fallo en cambios. Reporte muestra % de despliegues que requieren rollback o hotfix.",
-      "blocking": false,
-      "metrics": {
-        "name": "Change Failure Rate",
-        "unit": "porcentaje",
-        "target": "<= 15%",
-        "measurement": "(Despliegues fallidos / Total despliegues) * 100 en últimas 4 semanas",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "DORA-04",
-      "principle": "Tiempo para Restaurar",
-      "statement": "Los productos satélite DEBEN medir y reportar MTTR (Mean Time To Restore). Objetivo: menos de 1 hora para fallos críticos.",
-      "rationale": "Evolith Product Vision §6: Time to Restore mide qué tan rápido el equipo se recupera de fallos. MTTR bajo indica respuesta a incidentes efectiva.",
-      "severity": "MUST",
-      "validationQuery": "Sistema de gestión de incidentes exporta MTTR. Reporte muestra horas mediana desde detección de fallo a restauración de servicio.",
-      "blocking": false,
-      "metrics": {
-        "name": "Time to Restore",
-        "unit": "horas",
-        "target": "<= 1",
-        "measurement": "Tiempo mediana desde detección de fallo a restauración para incidentes P1/P2",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "SPACE-01",
-      "principle": "Confiabilidad (Observabilidad)",
-      "statement": "Los productos satélite DEBEN tener infraestructura de observabilidad (traces, logs, metrics) operativa en producción.",
-      "rationale": "Evolith Product Vision §6: Confiabilidad asegura que los sistemas de producción sean observables. ADR-0007 de Evolith mandates OpenTelemetry.",
-      "severity": "MUST",
-      "validationQuery": "Dashboard de observabilidad de producción accesible. Traces OpenTelemetry fluyendo. Tasa de error < 1%.",
-      "blocking": true,
-      "metrics": {
-        "name": "Error Rate",
-        "unit": "porcentaje",
-        "target": "<= 1%",
-        "measurement": "(Requests fallidos / Total requests) * 100 en últimas 24 horas",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards",
-        "reference/architecture/adrs/nodejs/0007-observability-telemetry-loki-opentelemetry.es.md"
-      ]
-    },
-    {
-      "id": "SPACE-02",
-      "principle": "Cultura (Salud del Equipo)",
-      "statement": "Los productos satélite DEBERÍAN medir salud del equipo trimestralmente. Objetivo: > 70% sentimiento positivo.",
-      "rationale": "Evolith Product Vision §6: Cultura mide satisfacción y salud del equipo. Equipos saludables envían mayor calidad.",
-      "severity": "SHOULD",
-      "validationQuery": "Encuesta de salud de equipo conducida trimestralmente. Resultados almacenados en documentación del producto. Tendencia rastreada.",
-      "blocking": false,
-      "metrics": {
-        "name": "Team Health Score",
-        "unit": "porcentaje",
-        "target": ">= 70%",
-        "measurement": "% respuestas positivas en encuesta trimestral de salud de equipo",
-        "dashboardRequired": false
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "SPACE-03",
-      "principle": "Ejecución (Throughput)",
-      "statement": "Los productos satélite DEBEN medir y reportar throughput de sprint. Objetivo: > 80% del trabajo comprometido entregado.",
-      "rationale": "Evolith Product Vision §6: Ejecución mide efectividad de entrega. Throughput consistente indica pipeline predecible.",
-      "severity": "SHOULD",
-      "validationQuery": "Métricas de sprint exportadas. Reporte muestra % de story points entregados vs comprometidos en últimos 4 sprints.",
-      "blocking": false,
-      "metrics": {
-        "name": "Sprint Throughput",
-        "unit": "porcentaje",
-        "target": ">= 80%",
-        "measurement": "(Story points entregados / Story points comprometidos) * 100 en últimos 4 sprints",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "SPACE-04",
-      "principle": "Comunicación (Visibilidad)",
-      "statement": "Los productos satélite DEBEN tener estado SDLC actual visible para todos los stakeholders. Objetivo: estado de phase gate actualizado dentro de 24h.",
-      "rationale": "Evolith Product Vision §6: Comunicación asegura que los stakeholders tengan visibilidad en tiempo real del estado de desarrollo.",
-      "severity": "SHOULD",
-      "validationQuery": "Tablero de estado de phase gates accesible. Actualizaciones hechas dentro de 24h de cambio de estado. Todos los stakeholders tienen acceso.",
-      "blocking": false,
-      "metrics": {
-        "name": "Gate Status Freshness",
-        "unit": "horas",
-        "target": "<= 24",
-        "measurement": "Tiempo máximo entre cambio de estado y actualización del tablero de estado",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "SPACE-05",
-      "principle": "Patrocinio (Alineación de Liderazgo)",
-      "statement": "Los productos satélite DEBEN tener sponsor ejecutivo asignado y activamente engajado. Sponsor debe revisar estado trimestralmente.",
-      "rationale": "Evolith Product Vision §6: Patrocinio asegura alineación de liderazgo. Patrocinio activo previene drift estratégico.",
-      "severity": "MUST",
-      "validationQuery": "evolith.yaml incluye campo governance.executiveSponsor. Reunión de revisión trimestral documentada.",
-      "blocking": false,
-      "metrics": {
-        "name": "Executive Engagement",
-        "unit": "revisiones por trimestre",
-        "target": ">= 1",
-        "measurement": "Count de revisiones de sponsor ejecutivo en trimestre pasado",
-        "dashboardRequired": false
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "DRIFT-01",
-      "principle": "Architecture Drift Index",
-      "statement": "Los productos satélite DEBEN medir y reportar Architecture Drift Index. Objetivo: < 10% drift de estándares Evolith Core.",
-      "rationale": "Evolith Product Vision §6: Adherencia medida via Architecture Drift Index. Drift > umbral indica erosión de gobernanza.",
-      "severity": "MUST",
-      "validationQuery": "Comando evolith validate ejecutado mensualmente. Reporte muestra % de reglas fallidas vs total aplicables.",
-      "blocking": false,
-      "metrics": {
-        "name": "Architecture Drift Index",
-        "unit": "porcentaje",
-        "target": "<= 10%",
-        "measurement": "(Reglas fallidas / Total reglas aplicables) * 100",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#6-executive-vision-scorecards"
-      ]
-    }
-  ],
-  "governance": {
-    "complianceVerification": "Métricas DORA+SPACE verificadas trimestralmente durante revisión de gobernanza. Comando evolith validate proporciona drift index.",
-    "exceptionProcess": "Revisión del Architecture Board requerida cuando cualquier métrica excede objetivo por 2+ trimestres consecutivos.",
-    "dashboardRequirements": "Métricas marcadas dashboardRequired: true DEBEN ser visibles en Evolith Tracker o dashboard ejecutivo equivalente.",
-    "reportingCadence": "Métricas DORA reportadas mensualmente. Métricas SPACE reportadas trimestralmente."
-  },
-  "bilingual": {
-    "en": "Executive Scorecards Rules",
-    "es": "Reglas de Scorecards Ejecutivos"
-  }
-}