@evolith/core-domain 1.0.1 → 1.0.3

package/rulesets/repository-taxonomy/README.md

@@ -1,26 +0,0 @@
-# Repository Taxonomy Ruleset
-
-> **Bilingual Navigation:** [Versión en Español](./README.es.md)
-
-Executable WS1 entrypoint for the Evolith Repository Taxonomy ruleset.
-
-## Purpose
-
-This directory exposes `rulesets/repository-taxonomy` as the canonical executable path checked by the intelligent data strength audit. The ruleset encodes naming, directory structure, ADR naming, bilingual pairing, and artifact classification constraints consumed by the native ruleset validator and CI evidence flows.
-
-## Artifacts
-
-| Artifact | Purpose |
-|---|---|
-| [repository-taxonomy.rules.json](./repository-taxonomy.rules.json) | Native machine-readable ruleset for Repository Taxonomy validation |
-| [../opa/repository-taxonomy.rego](../opa/repository-taxonomy.rego) | OPA policy parity artifact for Repository Taxonomy validation |
-| [../opa/repository-taxonomy.test.rego](../opa/repository-taxonomy.test.rego) | OPA test coverage for the Repository Taxonomy 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/repository-taxonomy.rego rulesets/opa/repository-taxonomy.test.rego -v
-```

package/rulesets/repository-taxonomy/repository-taxonomy.rules.json

@@ -1,172 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/repository-taxonomy/repository-taxonomy.rules.json",
-  "title": "Repository Taxonomy Rules",
-  "description": "Machine-readable encoding of the Evolith Repository Taxonomy. Naming, structure, and artifact classification rules for all Evolith repositories.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-01-01",
-  "rules": [
-    {
-      "id": "TAX-01",
-      "severity": "MUST",
-      "category": "naming-conventions",
-      "title": "File names use kebab-case",
-      "description": "All file names use kebab-case (lowercase with hyphens). No spaces, no underscores in file names. Example: my-file-name.md, user-service.ts.",
-      "validationQuery": "File names validated via linting or CI script. Pattern: ^[a-z0-9-]+\\.[a-z]+$",
-      "blocking": true,
-      "examples": [
-        "my-file.md",
-        "user-service.ts",
-        "api-gateway.ts"
-      ]
-    },
-    {
-      "id": "TAX-02",
-      "severity": "MUST",
-      "category": "naming-conventions",
-      "title": "Class and type names use PascalCase",
-      "description": "Classes, interfaces, types, enums, and UI components use PascalCase.",
-      "rationale": "ADR-0056: Ubiquitous language enforcement. PascalCase for types/components.",
-      "validationQuery": "ESLint naming-convention for classes and interfaces.",
-      "blocking": true,
-      "examples": [
-        "UserService",
-        "HttpClient",
-        "ApiResponse"
-      ]
-    },
-    {
-      "id": "TAX-03",
-      "severity": "MUST",
-      "category": "naming-conventions",
-      "title": "Variable and function names use camelCase",
-      "description": "Variables, functions, methods use camelCase.",
-      "rationale": "ADR-0056: camelCase for variables and functions.",
-      "validationQuery": "ESLint naming-convention for variables and functions.",
-      "blocking": true,
-      "examples": [
-        "getUserById",
-        "userData",
-        "isValid"
-      ]
-    },
-    {
-      "id": "TAX-04",
-      "severity": "MUST",
-      "category": "naming-conventions",
-      "title": "Constants use UPPER_SNAKE_CASE",
-      "description": "Compile-time constants and configuration keys use UPPER_SNAKE_CASE.",
-      "validationQuery": "ESLint naming-convention for constants.",
-      "blocking": false,
-      "examples": [
-        "MAX_RETRY_COUNT",
-        "API_BASE_URL"
-      ]
-    },
-    {
-      "id": "TAX-05",
-      "severity": "MUST",
-      "category": "directory-structure",
-      "title": "Evolith Core structure: reference/, sdk/, rulesets/",
-      "description": "Evolith Core repository uses three primary directories: reference/ (human-authored standards), sdk/ (CLI, MCP, and executable access tooling), rulesets/ (machine-readable rules, including rulesets/topologies/ for executable topology rules). No other top-level content directories.",
-      "rationale": "Repository Taxonomy defines three entry points with clear ownership.",
-      "validationQuery": "Top-level directories match taxonomy. No arbitrary content directories added.",
-      "blocking": true,
-      "structure": [
-        "reference/",
-        "sdk/",
-        "rulesets/",
-        "rulesets/topologies/"
-      ]
-    },
-    {
-      "id": "TAX-06",
-      "severity": "MUST",
-      "category": "directory-structure",
-      "title": "Satellite structure: src/, tests/, docs/",
-      "description": "Satellite repositories follow standard structure: src/ (source code), tests/ (test code), docs/ (documentation). Infrastructure code lives under src/Infrastructure, domain code under src/Domain.",
-      "rationale": "Repository Taxonomy standard satellite structure.",
-      "validationQuery": "Satellite root has src/, tests/, docs/ directories. Hexagonal layers under src/.",
-      "blocking": true,
-      "structure": [
-        "src/Domain",
-        "src/Application",
-        "src/Infrastructure",
-        "src/Api"
-      ]
-    },
-    {
-      "id": "TAX-07",
-      "severity": "MUST",
-      "category": "adr-naming",
-      "title": "ADR files named with zero-padded ID",
-      "description": "ADR files use format: NNNN-descriptive-name.md where NNNN is zero-padded 4-digit number. Example: 0002-clean-architecture-nestjs.md, 0069-dotnet-grpc-service.md.",
-      "rationale": "core/ADR-0048: Canonical numbering enables sorting and referencing.",
-      "validationQuery": "ADR filenames match pattern: ^[0-9]{4}-[a-z-]+\\.md$",
-      "blocking": true,
-      "examples": [
-        "0002-clean-architecture-nestjs.md",
-        "0069-dotnet-grpc-service-setup-protobuf-contracts.md"
-      ]
-    },
-    {
-      "id": "TAX-08",
-      "severity": "MUST",
-      "category": "adr-naming",
-      "title": "Bilingual ADR files use .es.md suffix",
-      "description": "Spanish translations of ADRs use .es.md suffix in same directory. Example: 0002-clean-architecture-nestjs.es.md alongside 0002-clean-architecture-nestjs.md.",
-      "rationale": "Bilingual naming convention: Pattern A for individual files.",
-      "validationQuery": "Bilingual parity: every .md ADR has corresponding .es.md in same directory.",
-      "blocking": true
-    },
-    {
-      "id": "TAX-09",
-      "severity": "MUST",
-      "category": "artifact-classification",
-      "title": "Evolith reference artifacts in reference/",
-      "description": "Reusable policy, decision criteria, accepted trade-offs, and human-authored topology profiles go in reference/architecture/, reference/architecture/topologies/, reference/governance/, reference/knowledge/. These are normative or decisional depending on document status.",
-      "rationale": "Repository Taxonomy: Canonical Reference goes in reference/.",
-      "validationQuery": "Architecture decisions, standards, and patterns placed in correct reference/ subdirectory.",
-      "blocking": true
-    },
-    {
-      "id": "TAX-10",
-      "severity": "MUST",
-      "category": "artifact-classification",
-      "title": "Product-specific evidence not in reference/",
-      "description": "Product-specific routes, schemas, seeds, and branding do NOT go in reference/. They go in the satellite repository. Enterprise policy changes go through Evolith governance.",
-      "rationale": "Repository Taxonomy: Product evidence stays in product repo, not reference.",
-      "validationQuery": "No product-specific files in reference/. Product evidence in satellite repositories.",
-      "blocking": true
-    },
-    {
-      "id": "TAX-11",
-      "severity": "MUST",
-      "category": "directory-structure",
-      "title": "No root-level topologies directory",
-      "description": "Evolith Core MUST NOT create /topologies/ at repository root. Multi-topology documentation and executable rules must stay within taxonomy-approved corpus and ruleset locations, specifically reference/architecture/topologies/ and rulesets/topologies/, unless a future accepted ADR supersedes the root taxonomy.",
-      "rationale": "core/ADR-0079 rejects root-level /topologies/ to preserve ADR-0048 and ADR-0070 root taxonomy constraints.",
-      "validationQuery": "Repository root directory listing does not contain topologies/.",
-      "blocking": true,
-      "examples": [
-        "reference/architecture/topologies/",
-        "rulesets/topologies/"
-      ]
-    }
-  ],
-  "references": [
-    "reference/governance/standards/repository-taxonomy.md",
-    "reference/architecture/adrs/core/0048-enterprise-taxonomy-reference-layout.md",
-    "reference/architecture/adrs/core/0056-enterprise-naming-design-conventions.md",
-    "reference/architecture/adrs/core/0070-lean-root-repository-taxonomy.md",
-    "reference/architecture/adrs/core/0079-multi-topology-reference-corpus.md"
-  ],
-  "exitCriteria": {
-    "description": "All files follow naming conventions. Directory structure matches taxonomy. ADR files correctly numbered.",
-    "validationTools": [
-      "CI naming validation",
-      "directory structure check",
-      "ADR numbering validation"
-    ]
-  }
-}

package/rulesets/satellite-contracts/README.es.md

@@ -1,27 +0,0 @@
-# Ruleset de Contratos Satélite
-
-> **Navegación Bilingüe:** [English Version](./README.md)
-
-Punto de entrada ejecutable WS1 para el ruleset Satellite Contracts de Evolith.
-
-## Propósito
-
-Este directorio expone `rulesets/satellite-contracts` como la ruta ejecutable canónica que verifica la auditoría de fortaleza como data inteligente. El ruleset codifica las reglas de contrato evolith.yaml del satélite consumido por el validador nativo de rulesets y los flujos de evidencia CI.
-
-## Artefactos
-
-| Artefacto | Ruta | Propósito |
-|---|---|---|
-| Ruleset nativo | [satellite-contracts.rules.json](./satellite-contracts.rules.json) | Reglas machine-readable de validación de contratos satélite |
-| Política OPA | [../opa/satellite-contracts.rego](../opa/satellite-contracts.rego) | Artefacto de paridad OPA para validación de Satellite Contracts |
-| Pruebas OPA | [../opa/satellite-contracts.test.rego](../opa/satellite-contracts.test.rego) | Cobertura de pruebas OPA para la política Satellite Contracts |
-| Esquema de entrada OPA | [../opa/schemas/satellite-contracts.input.schema.json](../opa/schemas/satellite-contracts.input.schema.json) | JSON Schema para la entrada de la política OPA |
-
-## 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/satellite-contracts.rego rulesets/opa/satellite-contracts.test.rego -v
-```

package/rulesets/satellite-contracts/README.md

@@ -1,27 +0,0 @@
-# Satellite Contracts Ruleset
-
-> **Bilingual Navigation:** [Versión en Español](./README.es.md)
-
-Executable WS1 entrypoint for the Evolith Satellite Contracts ruleset.
-
-## Purpose
-
-This directory exposes `rulesets/satellite-contracts` as the canonical executable path checked by the intelligent data strength audit. The ruleset encodes the satellite evolith.yaml contract rules consumed by the native ruleset validator and CI evidence flows.
-
-## Artifacts
-
-| Artifact | Path | Purpose |
-|---|---|---|
-| Native ruleset | [satellite-contracts.rules.json](./satellite-contracts.rules.json) | Machine-readable satellite contract validation rules |
-| OPA policy | [../opa/satellite-contracts.rego](../opa/satellite-contracts.rego) | OPA policy parity artifact for Satellite Contracts validation |
-| OPA tests | [../opa/satellite-contracts.test.rego](../opa/satellite-contracts.test.rego) | OPA test coverage for the Satellite Contracts policy |
-| OPA input schema | [../opa/schemas/satellite-contracts.input.schema.json](../opa/schemas/satellite-contracts.input.schema.json) | JSON Schema for OPA policy input |
-
-## 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/satellite-contracts.rego rulesets/opa/satellite-contracts.test.rego -v
-```

package/rulesets/satellite-contracts/satellite-contracts.rules.json

@@ -1,183 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/satellite-contracts/satellite-contracts.rules.json",
-  "title": "Satellite Contract Rules",
-  "description": "Rules defining the required and optional structure of satellite evolith.yaml files. These contracts enable the federated governance model.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-01-01",
-  "contractFields": {
-    "required": [
-      {
-        "field": "apiVersion",
-        "path": "$.apiVersion",
-        "type": "string",
-        "constraint": "Must be 'evolith.dev/v1'",
-        "rationale": "API version enables future governance format evolution without breaking existing satellites."
-      },
-      {
-        "field": "kind",
-        "path": "$.kind",
-        "type": "string",
-        "constraint": "Must be 'Satellite'",
-        "rationale": "Kind distinguishes Evolith resources (Satellite, Policy, Standard) in the same repository."
-      },
-      {
-        "field": "metadata.name",
-        "path": "$.metadata.name",
-        "type": "string",
-        "constraint": "kebab-case, lowercase, alphanumeric + hyphens only",
-        "rationale": "Name is the satellite's identity in governance tooling and Architecture Board communications."
-      },
-      {
-        "field": "metadata.phase",
-        "path": "$.metadata.phase",
-        "type": "string",
-        "constraint": "Must be F1, F2, or F3",
-        "rationale": "Phase determines which architecture rules apply. F1 is mandatory starting point unless exception approved."
-      },
-      {
-        "field": "metadata.architectureVersion",
-        "path": "$.metadata.architectureVersion",
-        "type": "string",
-        "constraint": "semver format",
-        "rationale": "Tracks architectural evolution of the satellite independently of product version."
-      },
-      {
-        "field": "spec.coreRef.version",
-        "path": "$.spec.coreRef.version",
-        "type": "string",
-        "constraint": "semver format, must reference existing Evolith Core version",
-        "rationale": "Core version pin ensures reproducible governance validation."
-      },
-      {
-        "field": "spec.coreRef.rulesetVersion",
-        "path": "$.spec.coreRef.rulesetVersion",
-        "type": "string",
-        "constraint": "semver format",
-        "rationale": "Ruleset version allows Core to publish rule updates without bumping full Core version."
-      },
-      {
-        "field": "spec.runtime.language",
-        "path": "$.spec.runtime.language",
-        "type": "string",
-        "constraint": "Must be one of: TypeScript, CSharp, Kotlin, Go, Python",
-        "rationale": "Runtime language determines which runtime-specific ADRs and patterns apply."
-      },
-      {
-        "field": "spec.runtime.framework",
-        "path": "$.spec.runtime.framework",
-        "type": "string",
-        "rationale": "Framework identifies the specific framework (NestJS, ASP.NET Core, Spring Boot) for pattern enforcement."
-      },
-      {
-        "field": "spec.sdlc.currentPhase",
-        "path": "$.spec.sdlc.currentPhase",
-        "type": "integer",
-        "constraint": "Must be 1, 2, 3, 4, or 5",
-        "rationale": "SDLC phase determines which gate rules and artifact requirements apply."
-      }
-    ],
-    "optional": [
-      {
-        "field": "spec.coreRef.inheritancePath",
-        "path": "$.spec.coreRef.inheritancePath",
-        "type": "array",
-        "description": "Chain of inheritance if satellite extends another satellite",
-        "default": "[]"
-      },
-      {
-        "field": "spec.runtime.runtimeVersion",
-        "path": "$.spec.runtime.runtimeVersion",
-        "type": "string",
-        "description": "Runtime version (e.g., Node 20, .NET 8)"
-      },
-      {
-        "field": "spec.sdlc.gates",
-        "path": "$.spec.sdlc.gates",
-        "type": "object",
-        "description": "Gate completion dates for traceability"
-      },
-      {
-        "field": "spec.boundedContexts",
-        "path": "$.spec.boundedContexts",
-        "type": "array",
-        "description": "List of bounded contexts in this satellite"
-      },
-      {
-        "field": "spec.compliance.adrRegistry",
-        "path": "$.spec.compliance.adrRegistry",
-        "type": "array",
-        "description": "Local ADRs maintained by this satellite"
-      },
-      {
-        "field": "spec.compliance.coverageTarget",
-        "path": "$.spec.compliance.coverageTarget",
-        "type": "number",
-        "description": "Coverage target (minimum 80)"
-      },
-      {
-        "field": "spec.compliance.qualityWaivers",
-        "path": "$.spec.compliance.qualityWaivers",
-        "type": "array",
-        "description": "Active quality waivers with expiration dates"
-      }
-    ]
-  },
-  "rules": [
-    {
-      "id": "SVC-01",
-      "title": "Satellite must have exactly one evolith.yaml in repository root",
-      "enforcement": "CLI validates single evolith.yaml at repo root. Nested evolith.yaml files are prohibited.",
-      "description": "CLI validates single evolith.yaml at repo root. Nested evolith.yaml files are prohibited."
-    },
-    {
-      "id": "SVC-02",
-      "title": "Satellite name must be unique across all Evolith satellites",
-      "enforcement": "CLI checks against Evolith satellite registry before allowing first push.",
-      "description": "CLI checks against Evolith satellite registry before allowing first push."
-    },
-    {
-      "id": "SVC-03",
-      "title": "F1 phase satellites must reference core/ADR-0047 in spec.compliance.adrRegistry",
-      "enforcement": "Satellites in F1 phase must include core/ADR-0047 confirming modular monolith starting point.",
-      "description": "Satellites in F1 phase must include core/ADR-0047 confirming modular monolith starting point."
-    },
-    {
-      "id": "SVC-04",
-      "title": "Satellites in F2 or F3 must have extraction readiness score documented",
-      "enforcement": "Satellites with phase F2 or F3 must have core/ADR-0045 assessment with score >= 70% (F2) or >= 80% (F3).",
-      "description": "Satellites with phase F2 or F3 must have core/ADR-0045 assessment with score >= 70% (F2) or >= 80% (F3)."
-    },
-    {
-      "id": "SVC-05",
-      "title": "Core version referenced must exist in Evolith Core registry",
-      "enforcement": "CLI validates coreRef.version against Evolith Core releases. Unknown versions trigger error.",
-      "description": "CLI validates coreRef.version against Evolith Core releases. Unknown versions trigger error."
-    }
-  ],
-  "migrationRules": [
-    {
-      "id": "MIG-01",
-      "title": "Satellite can upgrade governance version via CLI upgrade command",
-      "command": "evolith upgrade --target-version <version>",
-      "description": "CLI automates version update, rule diff review, and CI validation"
-    },
-    {
-      "id": "MIG-02",
-      "title": "Phase transition (F1 → F2 → F3) requires Architecture Board approval artifact",
-      "description": "Phase transition is not automated. Board must review and explicitly approve before satellite updates metadata.phase"
-    },
-    {
-      "id": "MIG-03",
-      "title": "Satellite archival: satellite marks itself as Deprecated in evolith.yaml",
-      "description": "Deprecated satellites are retained for audit but no longer receive Core rule updates"
-    }
-  ],
-  "reference": {
-    "evolithYamlSchema": "../schema/evolith-yaml.schema.json",
-    "inheritanceRules": "./inheritance.rules.json",
-    "f1Rules": "../../reference/architecture/topologies/progressive-axis/modular-monolith/modular-monolith.rules.json",
-    "f2Rules": "../../reference/architecture/topologies/progressive-axis/distributed-modules/distributed-modules.rules.json",
-    "f3Rules": "../../reference/architecture/topologies/progressive-axis/microservices/microservices.rules.json"
-  }
-}

package/rulesets/schema/README.es.md

@@ -1,39 +0,0 @@
-# Índice de Schemas
-
-Definiciones de JSON Schema para validar los artefactos SDLC de Evolith.
-
-| Schema | Propósito | Artefacto | Fase |
-|---|---|---|---|
-| [adr.schema.json](./adr.schema.json) | Validar la estructura y campos requeridos del ADR | ADR | Todas |
-| [prd.schema.json](./prd.schema.json) | Validar la estructura y campos requeridos del PRD | PRD | 1 |
-| [discovery-canvas.schema.json](./discovery-canvas.schema.json) | Validar el registro de iniciativas del Discovery Canvas | Discovery Canvas | 1 |
-| [technical-feasibility.schema.json](./technical-feasibility.schema.json) | Validar la viabilidad técnica y los atributos de calidad (NFRs) | Technical Feasibility Canvas | 1 |
-| [ballpark-estimation.schema.json](./ballpark-estimation.schema.json) | Validar el T-Shirt sizing y la estimación de equipo | Ballpark Estimation | 1 |
-| [evolith-user-story.schema.json](./evolith-user-story.schema.json) | Validar la historia de usuario atómica con criterios BDD | User Story | 1 |
-| [agile-backlog.schema.json](./agile-backlog.schema.json) | Validar el backlog priorizado por Épica/Iniciativa | Agile Backlog | 1 |
-| [cli-impact-analysis.schema.json](./cli-impact-analysis.schema.json) | Validar los requisitos de capacidades del CLI | CLI Impact Analysis | 1-2 |
-| [functional-story.schema.json](./functional-story.schema.json) | Validar el cumplimiento de la Historia Funcional | Historia Funcional | 2 |
-| [technical-story.schema.json](./technical-story.schema.json) | Validar la estructura de la Historia Técnica | Historia Técnica | 3 |
-| [test-summary-report.schema.json](./test-summary-report.schema.json) | Validar el Test Summary Report | Test Summary Report | 4 |
-| [release-notes.schema.json](./release-notes.schema.json) | Validar la completitud de las Release Notes | Release Notes | 5 |
-| [evolith-yaml.schema.json](./evolith-yaml.schema.json) | Validar el contrato evolith.yaml del satélite | Gobernanza de satélite | Todas |
-| [topology-manifest.schema.json](./topology-manifest.schema.json) | Validar archivos topology.manifest.json para resolución del corpus Multi-Topology | Manifiesto topológico | Todas |
-| [gate-evidence.schema.json](./gate-evidence.schema.json) | Validar la evidencia estructurada de evaluación de gates (core/ADR-0073) | Gate Evidence | Todas |
-| [maturity-evidence.schema.json](./maturity-evidence.schema.json) | Validar registros de evidencia de estado de madurez | Maturity Evidence | Todas |
-| [output-envelope.schema.json](./output-envelope.schema.json) | Validar el envelope universal de salida de máquina (core/ADR-0073) | Salida CLI/MCP/REST | Todas |
-| [knowledge-intake.schema.json](./knowledge-intake.schema.json) | Validar candidatos de conocimiento externo gobernado | Candidato de ingesta de conocimiento | Todas |
-| [governance.input.schema.json](../opa/schemas/governance.input.schema.json) | Validar la estructura de entrada de la política OPA de gobernanza | Entrada de OPA Gobernanza | Todas |
-| [mcp.input.schema.json](../opa/schemas/mcp.input.schema.json) | Validar la estructura de entrada de la política OPA de MCP | Entrada de OPA MCP | Todas |
-| [version-pinning.input.schema.json](../opa/schemas/version-pinning.input.schema.json) | Validar la estructura de entrada de la política OPA de version-pinning | Entrada de OPA Version Pinning | Todas |
-| [cli-readiness.input.schema.json](../opa/schemas/cli-readiness.input.schema.json) | Validar la estructura de entrada de la política OPA de preparación del CLI | Entrada de OPA CLI Readiness | Todas |
-| [knowledge-intake.input.schema.json](../opa/schemas/knowledge-intake.input.schema.json) | Validar la estructura de entrada de la política OPA de ingesta de conocimiento | Entrada de OPA Knowledge Intake | Todas |
-| [taxonomy.input.schema.json](../opa/schemas/taxonomy.input.schema.json) | Validar la estructura de entrada de la política OPA de taxonomía | Entrada de OPA Taxonomy | Todas |
-| [ci-cd.input.schema.json](../opa/schemas/ci-cd.input.schema.json) | Validar la estructura de entrada de la política OPA de CI/CD | Entrada de OPA CI/CD | Todas |
-| [evidence.input.schema.json](../opa/schemas/evidence.input.schema.json) | Validar la estructura de entrada de la política OPA de evidencia | Entrada de OPA Evidence | Todas |
-| [abac-mcp-tool-access.input.schema.json](../opa/schemas/abac-mcp-tool-access.input.schema.json) | Validar la estructura de entrada de la política OPA de acceso a herramientas ABAC | Entrada de OPA ABAC Tool Access | Todas |
-
-**Cobertura de Fase 1:** 7 schemas (Discovery Canvas, Technical Feasibility Canvas, Ballpark Estimation, Evolith User Story, Agile Backlog, CLI Impact Analysis, PRD)
-
----
-
-Volver al [Rulesets Hub](../README.es.md)

package/rulesets/schema/README.md

@@ -1,39 +0,0 @@
-# Schema Index
-
-JSON Schema definitions for validating Evolith SDLC artifacts.
-
-| Schema | Purpose | Artifact | Phase |
-|---|---|---|---|
-| [adr.schema.json](./adr.schema.json) | Validate ADR structure and required fields | ADR | All |
-| [prd.schema.json](./prd.schema.json) | Validate PRD structure and required fields | PRD | 1 |
-| [discovery-canvas.schema.json](./discovery-canvas.schema.json) | Validate Discovery Canvas initiative registration | Discovery Canvas | 1 |
-| [technical-feasibility.schema.json](./technical-feasibility.schema.json) | Validate Technical Feasibility and quality attributes (NFRs) | Technical Feasibility Canvas | 1 |
-| [ballpark-estimation.schema.json](./ballpark-estimation.schema.json) | Validate T-Shirt sizing and team estimation | Ballpark Estimation | 1 |
-| [evolith-user-story.schema.json](./evolith-user-story.schema.json) | Validate atomic user story with BDD criteria | User Story | 1 |
-| [agile-backlog.schema.json](./agile-backlog.schema.json) | Validate prioritized backlog for Epic/Initiative | Agile Backlog | 1 |
-| [cli-impact-analysis.schema.json](./cli-impact-analysis.schema.json) | Validate CLI capability requirements | CLI Impact Analysis | 1-2 |
-| [functional-story.schema.json](./functional-story.schema.json) | Validate Functional Story compliance | Functional Story | 2 |
-| [technical-story.schema.json](./technical-story.schema.json) | Validate Technical Story structure | Technical Story | 3 |
-| [test-summary-report.schema.json](./test-summary-report.schema.json) | Validate Test Summary Report | Test Summary Report | 4 |
-| [release-notes.schema.json](./release-notes.schema.json) | Validate Release Notes completeness | Release Notes | 5 |
-| [evolith-yaml.schema.json](./evolith-yaml.schema.json) | Validate satellite evolith.yaml contract | Satellite governance | All |
-| [topology-manifest.schema.json](./topology-manifest.schema.json) | Validate topology.manifest.json files for Multi-Topology corpus resolution | Topology manifest | All |
-| [gate-evidence.schema.json](./gate-evidence.schema.json) | Validate structured gate-evaluation evidence (core/ADR-0073) | Gate Evidence | All |
-| [maturity-evidence.schema.json](./maturity-evidence.schema.json) | Validate maturity status evidence logs | Maturity Evidence | All |
-| [output-envelope.schema.json](./output-envelope.schema.json) | Validate the universal machine output envelope (core/ADR-0073) | CLI/MCP/REST output | All |
-| [knowledge-intake.schema.json](./knowledge-intake.schema.json) | Validate governed external knowledge candidates | Knowledge intake candidate | All |
-| [governance.input.schema.json](../opa/schemas/governance.input.schema.json) | Validate governance OPA policy input structure | OPA Governance Input | All |
-| [mcp.input.schema.json](../opa/schemas/mcp.input.schema.json) | Validate MCP OPA policy input structure | OPA MCP Input | All |
-| [version-pinning.input.schema.json](../opa/schemas/version-pinning.input.schema.json) | Validate version pinning OPA policy input structure | OPA Version Pinning Input | All |
-| [cli-readiness.input.schema.json](../opa/schemas/cli-readiness.input.schema.json) | Validate CLI readiness OPA policy input structure | OPA CLI Readiness Input | All |
-| [knowledge-intake.input.schema.json](../opa/schemas/knowledge-intake.input.schema.json) | Validate knowledge intake OPA policy input structure | OPA Knowledge Intake Input | All |
-| [taxonomy.input.schema.json](../opa/schemas/taxonomy.input.schema.json) | Validate taxonomy OPA policy input structure | OPA Taxonomy Input | All |
-| [ci-cd.input.schema.json](../opa/schemas/ci-cd.input.schema.json) | Validate CI/CD OPA policy input structure | OPA CI/CD Input | All |
-| [evidence.input.schema.json](../opa/schemas/evidence.input.schema.json) | Validate evidence OPA policy input structure | OPA Evidence Input | All |
-| [abac-mcp-tool-access.input.schema.json](../opa/schemas/abac-mcp-tool-access.input.schema.json) | Validate ABAC tool access OPA policy input structure | OPA ABAC Tool Access Input | All |
-
-**Phase 1 Coverage:** 7 schemas (Discovery Canvas, Technical Feasibility Canvas, Ballpark Estimation, Evolith User Story, Agile Backlog, CLI Impact Analysis, PRD)
-
----
-
-Back to [Rulesets Hub](../README.md)