@evolith/core-domain 1.0.1 → 1.0.3

package/rulesets/adr/generated/adr-0051-enterprise-database-engine-selection-strategy.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0051-enterprise-database-engine-selection-strategy.rules.json",
-  "title": "ADR-0051 — Enterprise Database Engine Selection Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0051 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0051",
-  "adrTitle": "Enterprise Database Engine Selection Strategy",
-  "status": "Approved",
-  "date": "2026-05-14",
-  "rules": [
-    {
-      "id": "CORE-0051-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0051: Enterprise Database Engine Selection Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0051 (core track). ADR decision: The enterprise standard for database engines is now differentiated by runtime and data model requirements: Mandatory Engine: Microsoft SQL Server (Latest Stable Version) Rationale: native integration with Entity Framework Core, superior performance for enterprise workloads, and advanced management tooling (SSMS, SQL P… This ADR contains enforceable language (must, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: The enterprise standard for database engines is now differentiated by runtime and data model requirements: Mandatory Engine: Microsoft SQL Server (Latest Stable Version) Rationale: native integration with Entity Framework Core, superior performance for enterprise workloads, and advanced management tooling (SSMS, SQL P…",
-      "rationale": "Derived from ADR-0051 \"Decision\" section. Enforcement signals detected: must, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0051 via static analysis, lint rules, or pipeline gates covering: must, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0051-enterprise-database-engine-strategy.md"
-  ],
-  "effectiveDate": "2026-05-14"
-}

package/rulesets/adr/generated/adr-0052-unit-testing-isolation-strategy-mocks-vs-stubs.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0052-unit-testing-isolation-strategy-mocks-vs-stubs.rules.json",
-  "title": "ADR-0052 — Unit Testing Isolation Strategy (Mocks vs Stubs) Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0052 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0052",
-  "adrTitle": "Unit Testing Isolation Strategy (Mocks vs Stubs)",
-  "status": "Approved",
-  "date": "2026-05-14",
-  "rules": [
-    {
-      "id": "CORE-0052-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0052: Unit Testing Isolation Strategy (Mocks vs Stubs)",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0052 (core track). ADR decision: We adopt a Double Centric Isolation Strategy aligned with Hexagonal Architecture principles. Stub (Indirect Input): Used to provide the SUT (System Under Test) with necessary data or state. This ADR contains enforceable language (must, forbidden, required, layer, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: We adopt a Double Centric Isolation Strategy aligned with Hexagonal Architecture principles. Stub (Indirect Input): Used to provide the SUT (System Under Test) with necessary data or state.",
-      "rationale": "Derived from ADR-0052 \"Decision\" section. Enforcement signals detected: must, forbidden, required, layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0052 via static analysis, lint rules, or pipeline gates covering: must, forbidden, required, layer, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0052-unit-testing-isolation-strategy.md"
-  ],
-  "effectiveDate": "2026-05-14"
-}

package/rulesets/adr/generated/adr-0053-integration-and-e2e-testing-strategy.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0053-integration-and-e2e-testing-strategy.rules.json",
-  "title": "ADR-0053 — Integration and E2E Testing Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0053 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0053",
-  "adrTitle": "Integration and E2E Testing Strategy",
-  "status": "Approved",
-  "date": "2026-05-14",
-  "rules": [
-    {
-      "id": "CORE-0053-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0053: Integration and E2E Testing Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0053 (core track). ADR decision: We establish a mandatory strategy for heavy weight testing layers. Definition: Verifying a single Infrastructure Adapter against its real external counterpart. Mandatory Rule: MUST use Testcontainers to spin up real instances of SQL Server, PostgreSQL, Redis, or MongoDB. This ADR contains enforceable language (must, layer, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: We establish a mandatory strategy for heavy weight testing layers. Definition: Verifying a single Infrastructure Adapter against its real external counterpart. Mandatory Rule: MUST use Testcontainers to spin up real instances of SQL Server, PostgreSQL, Redis, or MongoDB.",
-      "rationale": "Derived from ADR-0053 \"Decision\" section. Enforcement signals detected: must, layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0053 via static analysis, lint rules, or pipeline gates covering: must, layer, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0053-integration-e2e-testing-strategy.md"
-  ],
-  "effectiveDate": "2026-05-14"
-}

package/rulesets/adr/generated/adr-0054-database-design-and-normalization-standards.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0054-database-design-and-normalization-standards.rules.json",
-  "title": "ADR-0054 — Database Design and Normalization Standards Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0054 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0054",
-  "adrTitle": "Database Design and Normalization Standards",
-  "status": "Approved",
-  "date": "2026-05-14",
-  "rules": [
-    {
-      "id": "CORE-0054-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0054: Database Design and Normalization Standards",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0054 (core track). ADR decision: We establish a dual track modeling standard based on the nature of the persistence engine. All relational models MUST follow the Third Normal Form (3NF) as the default baseline. This ADR contains enforceable language (must, forbidden, dependency, naming); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: We establish a dual track modeling standard based on the nature of the persistence engine. All relational models MUST follow the Third Normal Form (3NF) as the default baseline.",
-      "rationale": "Derived from ADR-0054 \"Decision\" section. Enforcement signals detected: must, forbidden, dependency, naming.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0054 via static analysis, lint rules, or pipeline gates covering: must, forbidden, dependency, naming. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0054-database-design-normalization-standards.md"
-  ],
-  "effectiveDate": "2026-05-14"
-}

package/rulesets/adr/generated/adr-0055-microfrontends-architecture-strategy.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0055-microfrontends-architecture-strategy.rules.json",
-  "title": "ADR-0055 — Microfrontends Architecture Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0055 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0055",
-  "adrTitle": "Microfrontends Architecture Strategy",
-  "status": "Proposed (Phase 3 Readiness)",
-  "date": "",
-  "rules": [
-    {
-      "id": "CORE-0055-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0055: Microfrontends Architecture Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0055 (core track). ADR decision: We will adopt a Microfrontend (MFE) strategy only as a Phase 3+ extraction strategy , not as the initial frontend baseline. Evolith products MUST follow this progression: Microfrontends MUST NOT be used as a default starting architecture, a trend driven choice, or a substitute for clean modular frontend design. This ADR contains enforceable language (must not, must, boundaries); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: We will adopt a Microfrontend (MFE) strategy only as a Phase 3+ extraction strategy , not as the initial frontend baseline. Evolith products MUST follow this progression: Microfrontends MUST NOT be used as a default starting architecture, a trend driven choice, or a substitute for clean modular frontend design.",
-      "rationale": "Derived from ADR-0055 \"Decision\" section. Enforcement signals detected: must not, must, boundaries.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0055 via static analysis, lint rules, or pipeline gates covering: must not, must, boundaries. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0055-microfrontends-architecture-strategy.md"
-  ]
-}

package/rulesets/adr/generated/adr-0056-enterprise-naming-design-conventions-multi-language-multi-pl.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0056-enterprise-naming-design-conventions-multi-language-multi-pl.rules.json",
-  "title": "ADR-0056 — Enterprise Naming & Design Conventions - Multi-Language, Multi-Platform Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0056 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0056",
-  "adrTitle": "Enterprise Naming & Design Conventions - Multi-Language, Multi-Platform",
-  "status": "Accepted — extends and expands the scope of [ADR-0049 (Naming Semantics & Clean Code Policy)](./0049-naming-semantics-clean-code-policy.md) to all layers of the enterprise ecosystem (code, API, database, events, data warehouse, DDD tactical patterns).",
-  "date": "2026-05-15",
-  "rules": [
-    {
-      "id": "CORE-0056-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0056: Enterprise Naming & Design Conventions - Multi-Language, Multi-Platform",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0056 (core track). ADR decision: Adopt a single, binding, automated enforcement naming standard with the following pillars: 1. Ubiquitous Language as the Source of Truth. Every name in code, API, database, and events originates from the domain glossary not from implementation preferences. This ADR contains enforceable language (must, layer, lint, naming, ci gate, enforce); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt a single, binding, automated enforcement naming standard with the following pillars: 1. Ubiquitous Language as the Source of Truth. Every name in code, API, database, and events originates from the domain glossary not from implementation preferences.",
-      "rationale": "Derived from ADR-0056 \"Decision\" section. Enforcement signals detected: must, layer, lint, naming, ci gate, enforce.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0056 via static analysis, lint rules, or pipeline gates covering: must, layer, lint, naming, ci gate, enforce. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0056-enterprise-naming-design-conventions.md"
-  ],
-  "effectiveDate": "2026-05-15"
-}

package/rulesets/adr/generated/adr-0057-architecture-intelligence-catalog.rules.json

@@ -1,27 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0057-architecture-intelligence-catalog.rules.json",
-  "title": "ADR-0057 — Architecture Intelligence Catalog Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0057 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0057",
-  "adrTitle": "Architecture Intelligence Catalog",
-  "status": "Accepted",
-  "date": "",
-  "rules": [
-    {
-      "id": "CORE-0057-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0057: Architecture Intelligence Catalog",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0057 (core track). ADR decision: Evolith adopts an Architecture Intelligence Catalog under: text reference/knowledge/architecture intelligence/ This catalog is used to: curate architectural ideas analyze tradeoffs classify adoption maturity document pattern cards connect external inspiration with Evolith governance prepare selected knowledge for AI a… Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Evolith adopts an Architecture Intelligence Catalog under: text reference/knowledge/architecture intelligence/ This catalog is used to: curate architectural ideas analyze tradeoffs classify adoption maturity document pattern cards connect external inspiration with Evolith governance prepare selected knowledge for AI a…",
-      "rationale": "Derived from ADR-0057 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0057-architecture-intelligence-catalog.md"
-  ]
-}

package/rulesets/adr/generated/adr-0058-ai-consumable-architecture-knowledge.rules.json

@@ -1,27 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0058-ai-consumable-architecture-knowledge.rules.json",
-  "title": "ADR-0058 — AI-Consumable Architecture Knowledge Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0058 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0058",
-  "adrTitle": "AI-Consumable Architecture Knowledge",
-  "status": "Accepted",
-  "date": "",
-  "rules": [
-    {
-      "id": "CORE-0058-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0058: AI-Consumable Architecture Knowledge",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0058 (core track). ADR decision: Evolith will prepare selected architecture knowledge for AI consumption using explicit structure, stable taxonomy, and traceable links to authoritative artifacts. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Evolith will prepare selected architecture knowledge for AI consumption using explicit structure, stable taxonomy, and traceable links to authoritative artifacts.",
-      "rationale": "Derived from ADR-0058 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0058-ai-consumable-architecture-knowledge.md"
-  ]
-}

package/rulesets/adr/generated/adr-0067-modular-monolith-persistence-boundaries.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0067-modular-monolith-persistence-boundaries.rules.json",
-  "title": "ADR-0067 — Modular Monolith Persistence Boundaries Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0067 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0067",
-  "adrTitle": "Modular Monolith Persistence Boundaries",
-  "status": "Accepted",
-  "date": "",
-  "rules": [
-    {
-      "id": "CORE-0067-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0067: Modular Monolith Persistence Boundaries",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0067 (core track). ADR decision: Evolith requires modular monolith implementations to define explicit persistence boundaries per module, bounded context, or domain capability. Each module must own its persistence model and must not directly mutate persistence structures owned by another module. This ADR contains enforceable language (must not, must, naming, structure, enforce, enforced); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Evolith requires modular monolith implementations to define explicit persistence boundaries per module, bounded context, or domain capability. Each module must own its persistence model and must not directly mutate persistence structures owned by another module.",
-      "rationale": "Derived from ADR-0067 \"Decision\" section. Enforcement signals detected: must not, must, naming, structure, enforce, enforced.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0067 via static analysis, lint rules, or pipeline gates covering: must not, must, naming, structure, enforce, enforced. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0067-modular-monolith-schema-per-domain.md"
-  ]
-}

package/rulesets/adr/generated/adr-0068-documentation-release-gitflow.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0068-documentation-release-gitflow.rules.json",
-  "title": "ADR-0068 — Documentation Release GitFlow Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0068 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0068",
-  "adrTitle": "Documentation Release GitFlow",
-  "status": "Proposed",
-  "date": "2026-05-29",
-  "rules": [
-    {
-      "id": "CORE-0068-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0068: Documentation Release GitFlow",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0068 (core track). ADR decision: We will adopt Documentation Release GitFlow as the mandatory release workflow for both Evolith Arch32 and UMS repositories. This extends ADR 0050 with documentation specific branch naming, quality gates, and release tagging conventions. This ADR contains enforceable language (naming, quality gate); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: We will adopt Documentation Release GitFlow as the mandatory release workflow for both Evolith Arch32 and UMS repositories. This extends ADR 0050 with documentation specific branch naming, quality gates, and release tagging conventions.",
-      "rationale": "Derived from ADR-0068 \"Decision\" section. Enforcement signals detected: naming, quality gate.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0068 via static analysis, lint rules, or pipeline gates covering: naming, quality gate. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0068-documentation-release-gitflow.md"
-  ],
-  "effectiveDate": "2026-05-29"
-}

package/rulesets/adr/generated/adr-0069-ai-agent-context-protocol-integration.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0069-ai-agent-context-protocol-integration.rules.json",
-  "title": "ADR-0069 — AI Agent Context Protocol Integration Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0069 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0069",
-  "adrTitle": "AI Agent Context Protocol Integration",
-  "status": "Approved",
-  "date": "2026-06-06",
-  "rules": [
-    {
-      "id": "CORE-0069-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0069: AI Agent Context Protocol Integration",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0069 (core track). ADR decision: Adopt a standardized AI Agent Context Protocol implementation to expose architectural governance natively to AI assistants. The integration must provide: Tools : Executable validation functions that agents can invoke (e.g., repository validation against rulesets). Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Adopt a standardized AI Agent Context Protocol implementation to expose architectural governance natively to AI assistants. The integration must provide: Tools : Executable validation functions that agents can invoke (e.g., repository validation against rulesets).",
-      "rationale": "Derived from ADR-0069 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0069-ai-agent-context-protocol-integration.md"
-  ],
-  "effectiveDate": "2026-06-06"
-}

package/rulesets/adr/generated/adr-0070-lean-root-repository-taxonomy.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0070-lean-root-repository-taxonomy.rules.json",
-  "title": "ADR-0070 — Lean Root Repository Taxonomy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0070 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0070",
-  "adrTitle": "Lean Root Repository Taxonomy",
-  "status": "Accepted",
-  "date": "2026-06-07",
-  "rules": [
-    {
-      "id": "CORE-0070-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0070: Lean Root Repository Taxonomy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0070 (core track). ADR decision: Adopt the Lean Root (also called Clean Root) architectural pattern for all Evolith satellite repositories, enforcing a strict binary dichotomy at the repository root. This ADR contains enforceable language (must, lint, ci/cd, enforce); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt the Lean Root (also called Clean Root) architectural pattern for all Evolith satellite repositories, enforcing a strict binary dichotomy at the repository root.",
-      "rationale": "Derived from ADR-0070 \"Decision\" section. Enforcement signals detected: must, lint, ci/cd, enforce.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0070 via static analysis, lint rules, or pipeline gates covering: must, lint, ci/cd, enforce. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0070-lean-root-repository-taxonomy.md"
-  ],
-  "effectiveDate": "2026-06-07"
-}

package/rulesets/adr/generated/adr-0071-domain-layer-base-class-and-inheritance-strategy.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0071-domain-layer-base-class-and-inheritance-strategy.rules.json",
-  "title": "ADR-0071 — Domain Layer Base Class and Inheritance Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0071 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0071",
-  "adrTitle": "Domain Layer Base Class and Inheritance Strategy",
-  "status": "Accepted",
-  "date": "2026-06-07",
-  "rules": [
-    {
-      "id": "CORE-0071-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0071: Domain Layer Base Class and Inheritance Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0071 (core track). ADR decision: Evolith satellites may adopt Option A (current shell inheritance) as a controlled and documented pragmatic compromise, subject to the constraints below. This ADR contains enforceable language (must not, must, dependency, dependencies, layer, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Evolith satellites may adopt Option A (current shell inheritance) as a controlled and documented pragmatic compromise, subject to the constraints below.",
-      "rationale": "Derived from ADR-0071 \"Decision\" section. Enforcement signals detected: must not, must, dependency, dependencies, layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0071 via static analysis, lint rules, or pipeline gates covering: must not, must, dependency, dependencies, layer, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0071-domain-layer-base-class-inheritance-strategy.md"
-  ],
-  "effectiveDate": "2026-06-07"
-}

package/rulesets/adr/generated/adr-0072-utc-date-storage-browser-timezone-detection-and-language-res.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0072-utc-date-storage-browser-timezone-detection-and-language-res.rules.json",
-  "title": "ADR-0072 — UTC Date Storage, Browser Timezone Detection, and Language Resolution Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0072 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0072",
-  "adrTitle": "UTC Date Storage, Browser Timezone Detection, and Language Resolution",
-  "status": "Accepted",
-  "date": "2026-06-07",
-  "rules": [
-    {
-      "id": "CORE-0072-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0072: UTC Date Storage, Browser Timezone Detection, and Language Resolution",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0072 (core track). ADR decision: Rule: Every date or timestamp stored in any database table, domain event, outbox message, or API response body must be UTC. Implementation guidelines per runtime: Rationale: UTC is the only unambiguous anchor for distributed systems. This ADR contains enforceable language (must not, must, naming); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Rule: Every date or timestamp stored in any database table, domain event, outbox message, or API response body must be UTC. Implementation guidelines per runtime: Rationale: UTC is the only unambiguous anchor for distributed systems.",
-      "rationale": "Derived from ADR-0072 \"Decision\" section. Enforcement signals detected: must not, must, naming.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0072 via static analysis, lint rules, or pipeline gates covering: must not, must, naming. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0072-utc-dates-timezone-language-resolution.md"
-  ],
-  "effectiveDate": "2026-06-07"
-}

package/rulesets/adr/generated/adr-0073-unified-cli-mcp-output-contract-and-gate-evidence-schema.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0073-unified-cli-mcp-output-contract-and-gate-evidence-schema.rules.json",
-  "title": "ADR-0073 — Unified CLI/MCP Output Contract and Gate Evidence Schema Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0073 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0073",
-  "adrTitle": "Unified CLI/MCP Output Contract and Gate Evidence Schema",
-  "status": "Approved — Evolith Architecture Board, 2026-06-10. Closes [GT-01](../../../governance/standards/vision/gap-reference-catalog.md#gt-01).",
-  "date": "2026-06-10",
-  "rules": [
-    {
-      "id": "CORE-0073-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0073: Unified CLI/MCP Output Contract and Gate Evidence Schema",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0073 (core track). ADR decision: Adopt option 3 . This ADR contains enforceable language (must, prohibited, layer, naming); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt option 3 .",
-      "rationale": "Derived from ADR-0073 \"Decision\" section. Enforcement signals detected: must, prohibited, layer, naming.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0073 via static analysis, lint rules, or pipeline gates covering: must, prohibited, layer, naming. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0073-unified-cli-output-contract.md"
-  ],
-  "effectiveDate": "2026-06-10"
-}

package/rulesets/adr/generated/adr-0074-evolith-core-api-native-exposure-layer.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0074-evolith-core-api-native-exposure-layer.rules.json",
-  "title": "ADR-0074 — Evolith Core API Native Exposure Layer Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0074 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0074",
-  "adrTitle": "Evolith Core API Native Exposure Layer",
-  "status": "Approved — Evolith Architecture Board, 2026-06-13.",
-  "date": "2026-06-13",
-  "rules": [
-    {
-      "id": "CORE-0074-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0074: Evolith Core API Native Exposure Layer",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0074 (core track). ADR decision: Adopt option 3 . We will construct the Evolith Core API as a NestJS application in the apps/core api directory. Ratified elements: 1. Network Sovereignty: Evolith Core is the sole owner of its domain, rulesets, and evaluation logic. This ADR contains enforceable language (dependency, layer, structure, enforce, boundaries); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt option 3 . We will construct the Evolith Core API as a NestJS application in the apps/core api directory. Ratified elements: 1. Network Sovereignty: Evolith Core is the sole owner of its domain, rulesets, and evaluation logic.",
-      "rationale": "Derived from ADR-0074 \"Decision\" section. Enforcement signals detected: dependency, layer, structure, enforce, boundaries.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0074 via static analysis, lint rules, or pipeline gates covering: dependency, layer, structure, enforce, boundaries. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0074-evolith-core-api-exposure-layer.md"
-  ],
-  "effectiveDate": "2026-06-13"
-}

package/rulesets/adr/generated/adr-0075-core-api-authentication-strategy.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0075-core-api-authentication-strategy.rules.json",
-  "title": "ADR-0075 — Core API Authentication Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0075 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0075",
-  "adrTitle": "Core API Authentication Strategy",
-  "status": "Superseded by ADR-0080",
-  "date": "2026-06-14",
-  "rules": [
-    {
-      "id": "CORE-0075-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0075: Core API Authentication Strategy",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0075 (core track). ADR decision: Implement a two tier authentication model: Machine to machine communication between the Tracker and Core API API keys validated via x api key header Keys stored as environment variables, hashed with SHA 256 and compared using constant time comparison ( timingSafeEqual ) ApiKeyAuthGuard registered as global APP GUARD @… Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Implement a two tier authentication model: Machine to machine communication between the Tracker and Core API API keys validated via x api key header Keys stored as environment variables, hashed with SHA 256 and compared using constant time comparison ( timingSafeEqual ) ApiKeyAuthGuard registered as global APP GUARD @…",
-      "rationale": "Derived from ADR-0075 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0075-core-api-auth-strategy.md"
-  ],
-  "effectiveDate": "2026-06-14"
-}

package/rulesets/adr/generated/adr-0076-domain-oriented-microservice-architecture-doma.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0076-domain-oriented-microservice-architecture-doma.rules.json",
-  "title": "ADR-0076 — Domain-Oriented Microservice Architecture (DOMA) Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0076 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0076",
-  "adrTitle": "Domain-Oriented Microservice Architecture (DOMA)",
-  "status": "Approved — Evolith Architecture Board, 2026-06-14.",
-  "date": "2026-06-14",
-  "rules": [
-    {
-      "id": "CORE-0076-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0076: Domain-Oriented Microservice Architecture (DOMA)",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0076 (core track). ADR decision: Evolith adopts DOMA as the F3 decomposition principle: 1. Domains are the unit of grouping. Each microservice belongs to exactly one bounded business domain (e.g. Discovery, Construction, Release). Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Evolith adopts DOMA as the F3 decomposition principle: 1. Domains are the unit of grouping. Each microservice belongs to exactly one bounded business domain (e.g. Discovery, Construction, Release).",
-      "rationale": "Derived from ADR-0076 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0076-domain-oriented-microservice-architecture.md"
-  ],
-  "effectiveDate": "2026-06-14"
-}

package/rulesets/adr/generated/adr-0077-masstransit-v9-commercial-pivot-stay-on-v8-monitor-opentrans.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0077-masstransit-v9-commercial-pivot-stay-on-v8-monitor-opentrans.rules.json",
-  "title": "ADR-0077 — MassTransit v9 Commercial Pivot — Stay on v8, Monitor OpenTransit Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0077 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0077",
-  "adrTitle": "MassTransit v9 Commercial Pivot — Stay on v8, Monitor OpenTransit",
-  "status": "Approved — Evolith Architecture Board, 2026-06-15.",
-  "date": "2026-06-15",
-  "rules": [
-    {
-      "id": "CORE-0077-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0077: MassTransit v9 Commercial Pivot — Stay on v8, Monitor OpenTransit",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0077 (core track). ADR decision: Stay on MassTransit v8 (8.3.x) through the end of year 2026 support window, and monitor OpenTransit as the primary post 2026 OSS continuation path. Rationale: The recommendation maximises the remaining v8 support window (6 months) to: Avoid an immediate, costly migration to Rebus or a driver rewrite. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Stay on MassTransit v8 (8.3.x) through the end of year 2026 support window, and monitor OpenTransit as the primary post 2026 OSS continuation path. Rationale: The recommendation maximises the remaining v8 support window (6 months) to: Avoid an immediate, costly migration to Rebus or a driver rewrite.",
-      "rationale": "Derived from ADR-0077 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0077-masstransit-v9-commercial-pivot.md"
-  ],
-  "effectiveDate": "2026-06-15"
-}

package/rulesets/adr/generated/adr-0078-domain-financial-separation-governance.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0078-domain-financial-separation-governance.rules.json",
-  "title": "ADR-0078 — Domain Financial Separation Governance Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0078 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0078",
-  "adrTitle": "Domain Financial Separation Governance",
-  "status": "Accepted",
-  "date": "2026-06-18",
-  "rules": [
-    {
-      "id": "CORE-0078-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0078: Domain Financial Separation Governance",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0078 (core track). ADR decision: Purge all references to financial parameters from Evolith Core and delegate all financial tracking, budgets, and business ROI logic exclusively to Evolith Tracker. All specifications and templates in Core must substitute business/financial concepts with Technical Constraints and Quality Attributes (NFRs): 1. This ADR contains enforceable language (must, prohibited); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Purge all references to financial parameters from Evolith Core and delegate all financial tracking, budgets, and business ROI logic exclusively to Evolith Tracker. All specifications and templates in Core must substitute business/financial concepts with Technical Constraints and Quality Attributes (NFRs): 1.",
-      "rationale": "Derived from ADR-0078 \"Decision\" section. Enforcement signals detected: must, prohibited.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0078 via static analysis, lint rules, or pipeline gates covering: must, prohibited. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0078-domain-financial-separation-governance.md"
-  ],
-  "effectiveDate": "2026-06-18"
-}