@evolith/core-domain 1.0.1 → 1.0.2

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

@@ -1,213 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/governance/executive-scorecards.rules.json",
-  "title": "Executive Scorecards Rules",
-  "description": "Rules encoding DORA and SPACE metrics for executive visibility. These rules ensure Predictability, Adherencia (Architecture Drift Index), and Eficiencia across satellite products.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-06-06",
-  "scope": "satellite",
-  "category": "executive-metrics",
-  "principles": [
-    {
-      "id": "DORA-01",
-      "principle": "Deployment Frequency",
-      "statement": "Satellite products MUST measure and report deployment frequency. Target: at least once per week to production.",
-      "rationale": "Evololith Product Vision §6: Deployment Frequency is a core DORA metric. High deployment frequency indicates healthy CD pipeline.",
-      "severity": "MUST",
-      "validationQuery": "CI/CD pipeline exports deployment frequency metric. Report shows deployments/week to production.",
-      "blocking": false,
-      "metrics": {
-        "name": "Deployment Frequency",
-        "unit": "deployments per week",
-        "target": ">= 1",
-        "measurement": "Count of production deployments in trailing 4 weeks / 4",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "DORA-02",
-      "principle": "Lead Time for Changes",
-      "statement": "Satellite products MUST measure and report lead time from commit to production. Target: less than 7 days for medium changes.",
-      "rationale": "Evololith Product Vision §6: Lead Time measures how quickly changes flow from commit to production. Short lead time indicates efficient pipeline.",
-      "severity": "MUST",
-      "validationQuery": "CI/CD pipeline exports lead time metric. Report shows median days from first commit to production deployment.",
-      "blocking": false,
-      "metrics": {
-        "name": "Lead Time for Changes",
-        "unit": "days",
-        "target": "<= 7",
-        "measurement": "Median time from first commit of a change to production deployment",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "DORA-03",
-      "principle": "Change Failure Rate",
-      "statement": "Satellite products MUST measure and report change failure rate. Target: less than 15% of deployments cause failures.",
-      "rationale": "Evololith Product Vision §6: Change Failure Rate measures the percentage of deployments causing production failures.",
-      "severity": "MUST",
-      "validationQuery": "CI/CD pipeline exports change failure rate. Report shows % of deployments requiring rollback or hotfix.",
-      "blocking": false,
-      "metrics": {
-        "name": "Change Failure Rate",
-        "unit": "percentage",
-        "target": "<= 15%",
-        "measurement": "(Failed deployments / Total deployments) * 100 in trailing 4 weeks",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "DORA-04",
-      "principle": "Time to Restore",
-      "statement": "Satellite products MUST measure and report MTTR (Mean Time To Restore). Target: less than 1 hour for critical failures.",
-      "rationale": "Evolith Product Vision §6: Time to Restore measures how quickly the team recovers from failures. Low MTTR indicates effective incident response.",
-      "severity": "MUST",
-      "validationQuery": "Incident management system exports MTTR. Report shows median hours from failure detection to service restoration.",
-      "blocking": false,
-      "metrics": {
-        "name": "Time to Restore",
-        "unit": "hours",
-        "target": "<= 1",
-        "measurement": "Median time from failure detection to restoration for P1/P2 incidents",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "SPACE-01",
-      "principle": "Reliability (Observability)",
-      "statement": "Satellite products MUST have observability infrastructure (traces, logs, metrics) operational in production.",
-      "rationale": "Evololith Product Vision §6: Reliability ensures production systems are observable. Evolith ADR-0007 mandates OpenTelemetry.",
-      "severity": "MUST",
-      "validationQuery": "Production observability dashboard accessible. OpenTelemetry traces flowing. Error rate < 1%.",
-      "blocking": true,
-      "metrics": {
-        "name": "Error Rate",
-        "unit": "percentage",
-        "target": "<= 1%",
-        "measurement": "(Failed requests / Total requests) * 100 in trailing 24 hours",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards",
-        "reference/architecture/adrs/nodejs/0007-observability-telemetry-loki-opentelemetry.md"
-      ]
-    },
-    {
-      "id": "SPACE-02",
-      "principle": "Culture (Team Health)",
-      "statement": "Satellite products SHOULD measure team health quarterly. Target: > 70% positive sentiment.",
-      "rationale": "Evolith Product Vision §6: Culture measures team satisfaction and health. Teams that are healthy ship higher quality.",
-      "severity": "SHOULD",
-      "validationQuery": "Team health survey conducted quarterly. Results stored in product documentation. Trend tracked.",
-      "blocking": false,
-      "metrics": {
-        "name": "Team Health Score",
-        "unit": "percentage",
-        "target": ">= 70%",
-        "measurement": "% positive responses in quarterly team health survey",
-        "dashboardRequired": false
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "SPACE-03",
-      "principle": "Execution (Throughput)",
-      "statement": "Satellite products MUST measure and report sprint throughput. Target: > 80% of committed work delivered.",
-      "rationale": "Evolith Product Vision §6: Execution measures delivery effectiveness. Consistent throughput indicates predictable pipeline.",
-      "severity": "SHOULD",
-      "validationQuery": "Sprint metrics exported. Report shows % of story points delivered vs committed in trailing 4 sprints.",
-      "blocking": false,
-      "metrics": {
-        "name": "Sprint Throughput",
-        "unit": "percentage",
-        "target": ">= 80%",
-        "measurement": "(Delivered story points / Committed story points) * 100 in trailing 4 sprints",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "SPACE-04",
-      "principle": "Communication (Visibility)",
-      "statement": "Satellite products MUST have current SDLC state visible to all stakeholders. Target: phase gate status updated within 24h.",
-      "rationale": "Evolith Product Vision §6: Communication ensures stakeholders have real-time visibility into development state.",
-      "severity": "SHOULD",
-      "validationQuery": "Phase gate status board accessible. Updates made within 24h of state change. All stakeholders have access.",
-      "blocking": false,
-      "metrics": {
-        "name": "Gate Status Freshness",
-        "unit": "hours",
-        "target": "<= 24",
-        "measurement": "Max time between state change and status board update",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "SPACE-05",
-      "principle": "Sponsorship (Leadership Alignment)",
-      "statement": "Satellite products MUST have executive sponsor assigned and actively engaged. Sponsor must review quarterly status.",
-      "rationale": "Evolith Product Vision §6: Sponsorship ensures leadership alignment. Active sponsorship prevents strategic drift.",
-      "severity": "MUST",
-      "validationQuery": "evolith.yaml includes governance.executiveSponsor field. Quarterly review meeting documented.",
-      "blocking": false,
-      "metrics": {
-        "name": "Executive Engagement",
-        "unit": "reviews per quarter",
-        "target": ">= 1",
-        "measurement": "Count of executive sponsor reviews in trailing quarter",
-        "dashboardRequired": false
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    },
-    {
-      "id": "DRIFT-01",
-      "principle": "Architecture Drift Index",
-      "statement": "Satellite products MUST measure and report Architecture Drift Index. Target: < 10% drift from Evolith Core standards.",
-      "rationale": "Evolith Product Vision §6: Adherence measured via Architecture Drift Index. Drift > threshold indicates erosion of governance.",
-      "severity": "MUST",
-      "validationQuery": "Evolith CLI validate command run monthly. Report shows % of rules failed vs total applicable rules.",
-      "blocking": false,
-      "metrics": {
-        "name": "Architecture Drift Index",
-        "unit": "percentage",
-        "target": "<= 10%",
-        "measurement": "(Failed rules / Total applicable rules) * 100",
-        "dashboardRequired": true
-      },
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#6-executive-vision-scorecards"
-      ]
-    }
-  ],
-  "governance": {
-    "complianceVerification": "DORA+SPACE metrics verified quarterly during governance review. Evolith CLI validate command provides drift index.",
-    "exceptionProcess": "Architecture Board review required when any metric exceeds target for 2+ consecutive quarters.",
-    "dashboardRequirements": "Metrics marked dashboardRequired: true MUST be visible in Evolith Tracker or equivalent executive dashboard.",
-    "reportingCadence": "DORA metrics reported monthly. SPACE metrics reported quarterly."
-  },
-  "bilingual": {
-    "en": "Executive Scorecards Rules",
-    "es": "Reglas de Scorecards Ejecutivos"
-  }
-}

package/rulesets/governance/inheritance.rules.json

@@ -1,115 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/governance/inheritance.rules.json",
-  "title": "Evolith Core Inheritance Rules",
-  "description": "Rules governing how satellite repositories inherit governance, architecture, and SDLC rules from Evolith Core. Satellites cannot modify Core rules.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-01-01",
-  "principles": [
-    {
-      "id": "INH-01",
-      "principle": "Core Immutability",
-      "statement": "Evolith Core rulesets are immutable once published. Satellites inherit rules; they do not fork, modify, or override Core rules.",
-      "rationale": "If satellites could modify Core rules, the corporate governance baseline would fragment. Federated governance requires a single source of truth.",
-      "enforcement": "Evolith CLI validates satellite rulesets against Core version. Satellites cannot publish their own rulesets/ directory."
-    },
-    {
-      "id": "INH-02",
-      "principle": "Version Pinning",
-      "statement": "Satellites MUST pin to a specific Core version (coreRef.version) in their evolith.yaml. Unpinned or 'latest' references are prohibited.",
-      "rationale": "Version pinning ensures reproducible governance. 'Latest' creates drift where different satellites run different rule versions.",
-      "enforcement": "evolith-yaml.schema.json requires semver version in coreRef.version. CLI warns on missing pin."
-    },
-    {
-      "id": "INH-03",
-      "principle": "Upgrade Only, Never Downgrade",
-      "statement": "Satellite governance version can only increase. Downgrading to an older version requires Architecture Board exception.",
-      "rationale": "Governance downgrade creates compliance gaps. Exception process ensures downgrade is deliberate and documented.",
-      "enforcement": "CLI tracks governance version history. Downgrade triggers warning and requires --force flag with justification."
-    },
-    {
-      "id": "INH-04",
-      "principle": "Satellite Extension via Local ADRs",
-      "statement": "Satellites can define local ADRs for decisions not yet promoted to Core. These are tracked in evolith.yaml compliance.adrRegistry.",
-      "rationale": "Not every decision needs to be corporate. Satellites have local autonomy for product-specific choices, tracked separately from Core ADRs.",
-      "enforcement": "Local ADRs must haveEvolithSatellite tag in frontmatter. They are not subject to Core immutability rules."
-    },
-    {
-      "id": "INH-05",
-      "principle": "Promotion via Architecture Board",
-      "statement": "Local ADR promotion to Core requires Architecture Board review. Evidence from satellite implementation is required.",
-      "rationale": "Core ADRs must be validated across multiple contexts before being elevated. Single-satellite evidence is insufficient.",
-      "enforcement": "Promotion request includes: original satellite ADR, evidence of adoption, list of other satellites that could benefit."
-    },
-    {
-      "id": "INH-06",
-      "principle": "Mandatory Architecture Tracker",
-      "statement": "Satellite repositories MUST contain a DECISIONS.md file in their root directory to explicitly declare their architecture inheritance contract.",
-      "rationale": "Without DECISIONS.md, architectural divergences and adoption of Core rules remain invisible, creating hidden technical debt.",
-      "enforcement": "CLI validates the presence of DECISIONS.md in the root directory of all satellites."
-    }
-  ],
-  "inheritanceChain": {
-    "description": "Satellites inherit from Core only. Multi-level inheritance (satellite → satellite) is prohibited unless explicitly approved by Architecture Board.",
-    "levels": [
-      {
-        "level": 0,
-        "name": "Evolith Core",
-        "type": "Authority",
-        "description": "Source of truth for all governance, architecture, and SDLC rules. Only place where rulesets/ and schema/ are authoritative."
-      },
-      {
-        "level": 1,
-        "name": "Satellite Repository",
-        "type": "Inheritor",
-        "description": "Inherits Core rules via evolith.yaml. Cannot modify Core. Can define local ADRs and extend within allowed boundaries."
-      }
-    ],
-    "prohibited": [
-      "Satellite → Satellite inheritance (without Architecture Board exception)",
-      "Satellite modifying Core rulesets/ or schema/",
-      "Satellite creating parallel rulesets/ directory",
-      "Core referencing satellite rules as authoritative"
-    ]
-  },
-  "upgradeProcess": {
-    "steps": [
-      {
-        "step": 1,
-        "action": "Evolith CLI notifies satellite of new Core version",
-        "owner": "CLI automation"
-      },
-      {
-        "step": 2,
-        "action": "Satellite owner reviews changelog between current and new version",
-        "owner": "Satellite Architect"
-      },
-      {
-        "step": 3,
-        "action": "Update evolith.yaml coreRef.version to new version",
-        "owner": "Satellite Architect"
-      },
-      {
-        "step": 4,
-        "action": "Run CI validation against new ruleset version",
-        "owner": "CI pipeline"
-      },
-      {
-        "step": 5,
-        "action": "Fix any rule violations introduced by upgrade",
-        "owner": "Satellite team"
-      },
-      {
-        "step": 6,
-        "action": "Architecture Board reviews if breaking changes affected bounded contexts",
-        "owner": "Architecture Board"
-      }
-    ],
-    "breakGlass": "Emergency Core patches (security, legal) can be fast-tracked with Technology Director approval and immediate satellite notification."
-  },
-  "reference": {
-    "evolithYamlSchema": "../schema/evolith-yaml.schema.json",
-    "childRepoGuide": "reference/governance/standards/onboarding/child-repository-inheritance-guide.md",
-    "repositoryTaxonomy": "reference/governance/standards/repository-taxonomy.md"
-  }
-}

package/rulesets/governance/knowledge-intake.rules.json

@@ -1,18 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/governance/knowledge-intake.rules.json",
-  "title": "External Knowledge Intake Rules",
-  "version": "0.2.0",
-  "effectiveDate": "2026-06-20",
-  "scope": "evolith-core",
-  "category": "knowledge-intake",
-  "rules": [
-    { "id": "KI-R01", "title": "Provenance and rights are mandatory", "description": "Every candidate declares source class, locator, retrieval date, and rights status.", "severity": "MUST", "blocking": true },
-    { "id": "KI-R02", "title": "Winston owns review", "description": "Every candidate declares @winston as review owner, next review date, and review freshness.", "severity": "MUST", "blocking": true },
-    { "id": "KI-R03", "title": "Promotion requires executable evidence", "description": "Executable promotion requires ADR, Native rule, OPA policy, and fixtures.", "severity": "MUST", "blocking": true },
-    { "id": "KI-R04", "title": "Topology contract completeness", "description": "Every candidate declares maturity, preconditions, anti-patterns, alternatives, and related topologies.", "severity": "MUST", "blocking": true },
-    { "id": "KI-R05", "title": "Source registry linkage", "description": "Every candidate links to a valid SRC-* source registry entry and every SRC-* entry links back to its KI-* candidates.", "severity": "MUST", "blocking": true },
-    { "id": "KI-R06", "title": "Promotion state machine", "description": "Promotion transitions must follow candidate → evaluated → accepted → executable; any status may transition to retired. No skipping stages.", "severity": "MUST", "blocking": true },
-    { "id": "KI-R07", "title": "Promotion evidence and disposition", "description": "Non-candidate statuses require promoted_at and promoted_by. Accepted/executable require a non-null ADR. Retired requires a non-null disposition reason.", "severity": "MUST", "blocking": true }
-  ]
-}

package/rulesets/governance/open-core-boundary.rules.es.json

@@ -1,148 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://evolith.dev/rulesets/governance/open-core-boundary.rules.json",
-  "title": "Reglas de Frontera Open-Core",
-  "description": "Reglas que definen la frontera entre Evolith Core (código abierto, libremente disponible) y Evolith Enterprise (SaaS, pago). Estas reglas previenen la contaminación entre capas y protegen la estrategia Open-Core.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-06-06",
-  "scope": "all",
-  "category": "open-core",
-  "principles": [
-    {
-      "id": "OCB-01",
-      "principle": "Core Permanece Independiente de Licencia",
-      "statement": "Los rulesets, esquemas, ADRs y estándares de Evolith Core NO DEBEN referenciar ni depender de ninguna licencia comercial, feature flag de pago, o dependencia exclusiva de enterprise.",
-      "rationale": "Core es la fundación constitucional. Si requiere componentes comerciales, los productos satélite se vuelven dependientes de Evolith la empresa, no de Evolith el framework.",
-      "severity": "MUST",
-      "validationQuery": "Todos los rulesets, schemas y ADRs no tienen import/reference a paquetes enterprise-only, license keys, o feature flags. El análisis de código muestra cero dependencias de enterprise SDKs en artefactos Core.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-02",
-      "principle": "Features Enterprise Marcadas Explícitamente",
-      "statement": "Cualquier regla, schema o artefacto que sea solo Enterprise DEBE estar explícitamente marcado con 'availability: enterprise' en su metadata. Artefactos sin marcar por defecto son Core (abierto).",
-      "rationale": "Ambigüedad sobre qué es Core vs Enterprise crea confusión de compliance. Marcado explícito asegura fronteras claras.",
-      "severity": "MUST",
-      "validationQuery": "Artefactos Enterprise incluyen campo de metadata 'availability: enterprise'. Artefactos Core omiten el campo o setean 'availability: core'. Ningún artefacto sin este campo puede ser tratado como enterprise-only.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-03",
-      "principle": "ACLs Son Features Enterprise",
-      "statement": "Las implementaciones de Anti-Corruption Layer para Jira, Trello, Linear y sistemas externos similares son features Enterprise. Core provee las reglas ACL; las integraciones en sí pertenecen a Enterprise.",
-      "rationale": "Los ACLs son el vector de monetización para Evolith. Deben permanecer en la capa Enterprise para proteger el modelo de negocio mientras son gobernados por reglas Core.",
-      "severity": "MUST",
-      "validationQuery": "El código de implementación de ACL está etiquetado 'enterprise' en el repositorio. Los rulesets Core referencian requisitos ACL pero no incluyen código de implementación.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-04",
-      "principle": "CLI y MCP Permanecen Core",
-      "statement": "Las implementaciones de command-line interface y MCP server DEBEN permanecer completamente abiertas en Core. No pueden estar detrás de licencias pagadas o suscripciones enterprise.",
-      "rationale": "CLI y MCP son la capa de exposición primaria para Evolith Core. Hacerlos enterprise-only bloquearía la adopción y contradiría la misión de democratización.",
-      "severity": "MUST",
-      "validationQuery": "El código fuente de CLI tiene licencia MIT o Apache 2.0. La implementación del servidor MCP no tiene chequeo de licencia en runtime. Todos los comandos CLI funcionan sin credenciales enterprise.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-05",
-      "principle": "Features de Tracker No Pueden Penetrar Core",
-      "statement": "Features específicas de Evolith Tracker (SaaS dashboard, analítica avanzada, UI de gestión multi-tenancy, logs de auditoría UI) no pueden ser implementadas como reglas o estándares Core.",
-      "rationale": "Tracker es la capa comercial SaaS. Sus detalles de implementación no deben influir en las definiciones Core.",
-      "severity": "MUST",
-      "validationQuery": "Los rulesets Core no contain references a 'tracker', 'saas', 'dashboard', 'multi-tenant-ui', o conceptos similares específicos de Tracker. El namespace de reglas está limpio.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-06",
-      "principle": "Reference Corpus Es Core",
-      "statement": "El Reference Corpus (ADRs, estándares, blueprints, taxonomías, rulesets, schemas) es Core y libremente disponible. No hay nivel de acceso dentro de Core (ej., 'basic' vs 'premium' standards).",
-      "rationale": "Todos los estándares son iguales en Core. Poner algunos estándares detrás de paywall fragmentaría la baseline constitucional.",
-      "severity": "MUST",
-      "validationQuery": "Todos los documentos de reference/ son públicamente accesibles. Ningún documento referencia un nivel 'premium' o 'enterprise' dentro de Core.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-07",
-      "principle": "Innovaciones Enterprise Pueden Promocionar a Core",
-      "statement": "Features inicialmente desarrolladas en Evolith Enterprise (Tracker) pueden ser promocionadas a Core via el proceso estándar de ADR, siempre que beneficien al ecosistema más amplio.",
-      "rationale": "La capa enterprise es un motor de innovación. Features exitosas deben ascender a Core para beneficio universal, siguiendo el proceso de promoción de gobernanza federada.",
-      "severity": "SHOULD",
-      "validationQuery": "Features enterprise que abordan concerns arquitectónicos generales son rastreadas para promoción via revisión del Architecture Board. La promoción sigue el ciclo de vida estándar de ADR.",
-      "blocking": false,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#5-business-strategy-open-core",
-        "rulesets/governance/inheritance.rules.json"
-      ]
-    },
-    {
-      "id": "OCB-08",
-      "principle": "Core No Puede Requerir Enterprise para Funcionar",
-      "statement": "Los productos satélite deben poder implementar las reglas Core sin comprar o suscribirse a Evolith Enterprise. Las features Enterprise son aditivas, nunca bloqueantes.",
-      "rationale": "El Core debe permanecer independientemente viable. Si implementar Core requiere licencia enterprise, el modelo Open-Core colapsa.",
-      "severity": "MUST",
-      "validationQuery": "Test end-to-end ejecuta el ruleset Core contra un satélite sin credenciales enterprise. Todas las reglas Core se validan exitosamente sin integración enterprise.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.es.md#5-business-strategy-open-core"
-      ]
-    }
-  ],
-  "openCoreMatrix": {
-    "description": "Separación definitiva entre features Core (abierto) y Enterprise (pagado)",
-    "core": [
-      "Constitución Core (rulesets/, reference/)",
-      "ADRs y Estándares",
-      "Interfaces CLI y MCP",
-      "JSON Schemas para todos los tipos de artefacto",
-      "Reglas de Phase Gates",
-      "Reglas de fase de arquitectura (F1/F2/F3)",
-      "Reglas de herencia de gobernanza",
-      "Engineering manifesto",
-      "Definition of Done",
-      "Repository taxonomy",
-      "Agente de Análisis de Impacto"
-    ],
-    "enterprise": [
-      "Plataforma SaaS Evolith Tracker",
-      "Dashboards y scorecards avanzados",
-      "Implementaciones ACL (Jira, Trello, Linear)",
-      "Reports ejecutivos de auditoría",
-      "Gestión UI multi-tenant",
-      "Integración de soporte prioritario",
-      "Analítica y reportería enterprise",
-      "Automación de compliance más allá de reglas Core",
-      "Gestión de permisos más allá de ACL basado en archivos"
-    ]
-  },
-  "governance": {
-    "complianceVerification": "Las reglas de frontera Open-Core son verificadas durante pre-commit via impact-analysis-synchronizer.mjs cuando cualquier ruleset es modificado.",
-    "exceptionProcess": "Revisión del Architecture Board requerida para cualquier regla que difumine la frontera Core/Enterprise. La excepción debe incluir justificación de negocio y análisis de impacto de adopción.",
-    "metrics": [
-      "opencore.enterprise-leaks.count — features enterprise encontradas en artefactos Core",
-      "opencore.core-dependencies.count — reglas Core requiriendo features enterprise"
-    ]
-  },
-  "bilingual": {
-    "en": "Open-Core Boundary Rules",
-    "es": "Reglas de Frontera Open-Core"
-  }
-}

package/rulesets/governance/open-core-boundary.rules.json

@@ -1,148 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/governance/open-core-boundary.rules.json",
-  "title": "Open-Core Boundary Rules",
-  "description": "Rules defining the boundary between Evolith Core (open source, freely available) and Evolith Enterprise (SaaS, paid). These rules prevent contamination between layers and protect the Open-Core strategy.",
-  "version": "1.0.0",
-  "effectiveDate": "2026-06-06",
-  "scope": "all",
-  "category": "open-core",
-  "principles": [
-    {
-      "id": "OCB-01",
-      "principle": "Core Remains License-Agnostic",
-      "statement": "Evolith Core rulesets, schemas, ADRs, and standards MUST NOT reference or depend on any commercial license, paid feature flag, or enterprise-only dependency.",
-      "rationale": "Core is the constitutional foundation. If it requires commercial components, satellite products become dependent on Evolith the company, not Evolith the framework.",
-      "severity": "MUST",
-      "validationQuery": "All rulesets, schemas, and ADRs have no import/reference to enterprise-only packages, license keys, or feature flags. Code analysis shows zero enterprise SDK dependencies in Core artifacts.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-02",
-      "principle": "Enterprise Features Explicitly Marked",
-      "statement": "Any rule, schema, or artifact that is Enterprise-only MUST be explicitly marked with 'availability: enterprise' in its metadata. Unmarked artifacts default to Core (open).",
-      "rationale": "Ambiguity about what is Core vs Enterprise creates compliance confusion. Explicit marking ensures clear boundaries.",
-      "severity": "MUST",
-      "validationQuery": "Enterprise artifacts include metadata field 'availability: enterprise'. Core artifacts either omit the field or set 'availability: core'. No artifact without this field can be treated as enterprise-only.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-03",
-      "principle": "ACLs Are Enterprise Features",
-      "statement": "Anti-Corruption Layer implementations for Jira, Trello, Linear, and similar external systems are Enterprise features. Core provides the ACL rules; the integrations themselves belong to Enterprise.",
-      "rationale": "ACLs are the monetization vector for Evolith. They must remain in the Enterprise layer to protect the business model while being governed by Core rules.",
-      "severity": "MUST",
-      "validationQuery": "ACL implementation code is tagged 'enterprise' in repository. Core rulesets reference ACL requirements but do not include implementation code.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-04",
-      "principle": "CLI and MCP Remain Core",
-      "statement": "Command-line interface and MCP server implementations MUST remain fully open in Core. They cannot be gated behind paid licenses or enterprise subscriptions.",
-      "rationale": "CLI and MCP are the primary exposure layer for Evolith Core. Making them enterprise-only would block adoption and contradict the democratization mission.",
-      "severity": "MUST",
-      "validationQuery": "CLI source code is MIT or Apache 2.0 licensed. MCP server implementation has no license check at runtime. All CLI commands work without enterprise credentials.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-05",
-      "principle": "Tracker Features Cannot Penetrate Core",
-      "statement": "Features specific to Evolith Tracker (SaaS dashboard, advanced analytics, multi-tenancy management UI, audit logs UI) cannot be implemented as Core rules or standards.",
-      "rationale": "Tracker is the commercial SaaS layer. Its implementation details must not influence Core definitions.",
-      "severity": "MUST",
-      "validationQuery": "Core rulesets contain no references to 'tracker', 'saas', 'dashboard', 'multi-tenant-ui', or similar Tracker-specific concepts. Rules namespace is clean.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-06",
-      "principle": "Reference Corpus Is Core",
-      "statement": "The Reference Corpus (ADRs, standards, blueprints, taxonomies, rulesets, schemas) is Core and freely available. No tier of access within Core (e.g., 'basic' vs 'premium' standards).",
-      "rationale": "All standards are equal in Core. Paywalling some standards would fragment the constitutional baseline.",
-      "severity": "MUST",
-      "validationQuery": "All reference/ documents are publicly accessible. No document references a 'premium' or 'enterprise' tier within Core.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#5-business-strategy-open-core"
-      ]
-    },
-    {
-      "id": "OCB-07",
-      "principle": "Enterprise Innovations Can Promote to Core",
-      "statement": "Features initially developed in Evolith Enterprise (Tracker) can be promoted to Core via the standard ADR process, provided they benefit the broader ecosystem.",
-      "rationale": "The enterprise layer is an innovation engine. Successful features should ascend to Core for universal benefit, following the federated governance promotion process.",
-      "severity": "SHOULD",
-      "validationQuery": "Enterprise features that address通用 architectural concerns are tracked for promotion via Architecture Board review. Promotion follows standard ADR lifecycle.",
-      "blocking": false,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#5-business-strategy-open-core",
-        "rulesets/governance/inheritance.rules.json"
-      ]
-    },
-    {
-      "id": "OCB-08",
-      "principle": "Core Cannot Require Enterprise to Function",
-      "statement": "Satellite products must be able to implement Core rules without purchasing or subscribing to Evolith Enterprise. Enterprise features are additive, never blocking.",
-      "rationale": "The Core must remain independently viable. If implementing Core requires enterprise license, the Open-Core model collapses.",
-      "severity": "MUST",
-      "validationQuery": "End-to-end test runs Core ruleset against a satellite without enterprise credentials. All Core rules validate successfully without enterprise integration.",
-      "blocking": true,
-      "references": [
-        "reference/governance/standards/vision/evolith-product-vision-master.md#5-business-strategy-open-core"
-      ]
-    }
-  ],
-  "openCoreMatrix": {
-    "description": "Definitive separation between Core (open) and Enterprise (paid) features",
-    "core": [
-      "Core Constitution (rulesets/, reference/)",
-      "ADRs and Standards",
-      "CLI and MCP interfaces",
-      "JSON Schemas for all artifact types",
-      "Phase Gate rules",
-      "Architecture phase rules (F1/F2/F3)",
-      "Governance inheritance rules",
-      "Engineering manifesto",
-      "Definition of Done",
-      "Repository taxonomy",
-      "Impact Analysis Agent"
-    ],
-    "enterprise": [
-      "Evolith Tracker SaaS platform",
-      "Advanced dashboards and scorecards",
-      "ACL implementations (Jira, Trello, Linear)",
-      "Executive audit reports",
-      "Multi-tenant UI management",
-      "Priority support integration",
-      "Enterprise analytics and reporting",
-      "Compliance automation beyond Core rules",
-      "Permission management beyond file-based ACL"
-    ]
-  },
-  "governance": {
-    "complianceVerification": "Open-Core boundary rules checked during pre-commit via impact-analysis-synchronizer.mjs when any ruleset is modified.",
-    "exceptionProcess": "Architecture Board review required for any rule that blurs Core/Enterprise boundary. Exception must include business justification and adoption impact analysis.",
-    "metrics": [
-      "opencore.enterprise-leaks.count — Enterprise features found in Core artifacts",
-      "opencore.core-dependencies.count — Core rules requiring enterprise features"
-    ]
-  },
-  "bilingual": {
-    "en": "Open-Core Boundary Rules",
-    "es": "Reglas de Frontera Open-Core"
-  }
-}