@evolith/core-domain 1.0.1 → 1.0.2

package/rulesets/adr/generated/adr-0030-two-tier-distributed-gateway-model.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0030-two-tier-distributed-gateway-model.rules.json",
-  "title": "ADR-0030 — Two-Tier Distributed Gateway Model Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0030 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0030",
-  "adrTitle": "Two-Tier Distributed Gateway Model",
-  "status": "Approved",
-  "date": "2026-05-10",
-  "rules": [
-    {
-      "id": "CORE-0030-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0030: Two-Tier Distributed Gateway Model",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0030 (core track). ADR decision: Adopt a Two Tier Distributed Gateway Model to cleanly separate concerns: 1. Tier 1 Edge Gateway : High throughput barrier. Sits on the literal public cluster perimeter. Manages only non functional transversal rules: SSL, API key throttling, simple JWT origin signature validation, path forwarding, and WAF rules. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Adopt a Two Tier Distributed Gateway Model to cleanly separate concerns: 1. Tier 1 Edge Gateway : High throughput barrier. Sits on the literal public cluster perimeter. Manages only non functional transversal rules: SSL, API key throttling, simple JWT origin signature validation, path forwarding, and WAF rules.",
-      "rationale": "Derived from ADR-0030 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0030-two-tier-distributed-gateway-model.md"
-  ],
-  "effectiveDate": "2026-05-10"
-}

package/rulesets/adr/generated/adr-0031-schema-per-bounded-context-and-domain-event-catalog.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0031-schema-per-bounded-context-and-domain-event-catalog.rules.json",
-  "title": "ADR-0031 — Schema-per-Bounded-Context and Domain Event Catalog Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0031 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0031",
-  "adrTitle": "Schema-per-Bounded-Context and Domain Event Catalog",
-  "status": "Approved",
-  "date": "2026-05-11",
-  "rules": [
-    {
-      "id": "CORE-0031-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0031: Schema-per-Bounded-Context and Domain Event Catalog",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0031 (core track). ADR decision: Each bounded context will own a dedicated PostgreSQL schema . All tables belonging to a context must be created within its schema. Cross schema joins within the monolith remain permitted (same DB connection), but must be treated as integration contracts, not implementation details. This ADR contains enforceable language (must, dependencies, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Each bounded context will own a dedicated PostgreSQL schema . All tables belonging to a context must be created within its schema. Cross schema joins within the monolith remain permitted (same DB connection), but must be treated as integration contracts, not implementation details.",
-      "rationale": "Derived from ADR-0031 \"Decision\" section. Enforcement signals detected: must, dependencies, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0031 via static analysis, lint rules, or pipeline gates covering: must, dependencies, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0031-schema-per-context-domain-event-catalog.md"
-  ],
-  "effectiveDate": "2026-05-11"
-}

package/rulesets/adr/generated/adr-0033-transactional-outbox-pattern-for-async-messaging.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0033-transactional-outbox-pattern-for-async-messaging.rules.json",
-  "title": "ADR-0033 — Transactional Outbox Pattern for Async Messaging Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0033 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0033",
-  "adrTitle": "Transactional Outbox Pattern for Async Messaging",
-  "status": "Proposed (Approved via Maturity Roadmap)",
-  "date": "2026-05-11",
-  "rules": [
-    {
-      "id": "CORE-0033-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0033: Transactional Outbox Pattern for Async Messaging",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0033 (core track). ADR decision: Formally adopt the Transactional Outbox Pattern to guarantee atomic state propagation between the relational store and async event channels: 1. Outbox Table : Every bounded context includes an outbox events table inside its isolated PostgreSQL schema. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Formally adopt the Transactional Outbox Pattern to guarantee atomic state propagation between the relational store and async event channels: 1. Outbox Table : Every bounded context includes an outbox events table inside its isolated PostgreSQL schema.",
-      "rationale": "Derived from ADR-0033 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0033-transactional-outbox-pattern.md"
-  ],
-  "effectiveDate": "2026-05-11"
-}

package/rulesets/adr/generated/adr-0034-cqrs-pattern-application-matrix.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0034-cqrs-pattern-application-matrix.rules.json",
-  "title": "ADR-0034 — CQRS Pattern Application Matrix Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0034 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0034",
-  "adrTitle": "CQRS Pattern Application Matrix",
-  "status": "Approved",
-  "date": "2026-05-11",
-  "rules": [
-    {
-      "id": "CORE-0034-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0034: CQRS Pattern Application Matrix",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0034 (core track). ADR decision: Adopt the following Evaluation Matrix to determine if a specific Use Case requires Full CQRS enforcement: Criteria : Basic CRUD operations, simple state changes, low to medium concurrent access. This ADR contains enforceable language (must, required, enforce); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt the following Evaluation Matrix to determine if a specific Use Case requires Full CQRS enforcement: Criteria : Basic CRUD operations, simple state changes, low to medium concurrent access.",
-      "rationale": "Derived from ADR-0034 \"Decision\" section. Enforcement signals detected: must, required, enforce.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0034 via static analysis, lint rules, or pipeline gates covering: must, required, enforce. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0034-cqrs-pattern-applicability-matrix.md"
-  ],
-  "effectiveDate": "2026-05-11"
-}

package/rulesets/adr/generated/adr-0035-distributed-saga-pattern-implementation-strategy.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0035-distributed-saga-pattern-implementation-strategy.rules.json",
-  "title": "ADR-0035 — Distributed Saga Pattern Implementation Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0035 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0035",
-  "adrTitle": "Distributed Saga Pattern Implementation Strategy",
-  "status": "Approved",
-  "date": "2026-05-11",
-  "rules": [
-    {
-      "id": "CORE-0035-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0035: Distributed Saga Pattern Implementation Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0035 (core track). ADR decision: Adopt the following corporate matrix to define the implementation strategy for long running or multi service transactions: Before deploying a Saga, verify if the business process can be contained within a Single Bounded Context . This ADR contains enforceable language (must, required); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt the following corporate matrix to define the implementation strategy for long running or multi service transactions: Before deploying a Saga, verify if the business process can be contained within a Single Bounded Context .",
-      "rationale": "Derived from ADR-0035 \"Decision\" section. Enforcement signals detected: must, required.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0035 via static analysis, lint rules, or pipeline gates covering: must, required. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0035-distributed-saga-pattern-strategy.md"
-  ],
-  "effectiveDate": "2026-05-11"
-}

package/rulesets/adr/generated/adr-0036-message-bus-delivery-flow-control-strategy.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0036-message-bus-delivery-flow-control-strategy.rules.json",
-  "title": "ADR-0036 — Message Bus Delivery & Flow Control Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0036 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0036",
-  "adrTitle": "Message Bus Delivery & Flow Control Strategy",
-  "status": "Approved",
-  "date": "2026-05-11",
-  "rules": [
-    {
-      "id": "CORE-0036-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0036: Message Bus Delivery & Flow Control Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0036 (core track). ADR decision: Adopt the following Event Delivery Decision Framework mapping business context to infrastructure queue behaviors: Definition : Asynchronous processing with no guarantee of order, maximum horizontal consumer parallelism. This ADR contains enforceable language (must, required, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt the following Event Delivery Decision Framework mapping business context to infrastructure queue behaviors: Definition : Asynchronous processing with no guarantee of order, maximum horizontal consumer parallelism.",
-      "rationale": "Derived from ADR-0036 \"Decision\" section. Enforcement signals detected: must, required, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0036 via static analysis, lint rules, or pipeline gates covering: must, required, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0036-message-bus-delivery-strategy-fifo-dlq.md"
-  ],
-  "effectiveDate": "2026-05-11"
-}

package/rulesets/adr/generated/adr-0037-enterprise-performance-concurrency-chaos-verification-strate.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0037-enterprise-performance-concurrency-chaos-verification-strate.rules.json",
-  "title": "ADR-0037 — Enterprise Performance, Concurrency & Chaos Verification Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0037 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0037",
-  "adrTitle": "Enterprise Performance, Concurrency & Chaos Verification Strategy",
-  "status": "Approved",
-  "date": "2026-05-11",
-  "rules": [
-    {
-      "id": "CORE-0037-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0037: Enterprise Performance, Concurrency & Chaos Verification Strategy",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0037 (core track). ADR decision: Establish the Strategic Verification Framework for performance, load, and operational resilience: Load & Performance Testing : k6 (Grafana). Mandatory due to its TypeScript native scripting, low footprint, and deep integration with OTel tracing metrics. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Establish the Strategic Verification Framework for performance, load, and operational resilience: Load & Performance Testing : k6 (Grafana). Mandatory due to its TypeScript native scripting, low footprint, and deep integration with OTel tracing metrics.",
-      "rationale": "Derived from ADR-0037 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0037-performance-concurrency-chaos-strategy.md"
-  ],
-  "effectiveDate": "2026-05-11"
-}

package/rulesets/adr/generated/adr-0039-deployment-topology-abstraction-environment-switcher.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0039-deployment-topology-abstraction-environment-switcher.rules.json",
-  "title": "ADR-0039 — Deployment Topology Abstraction & Environment Switcher Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0039 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0039",
-  "adrTitle": "Deployment Topology Abstraction & Environment Switcher",
-  "status": "Approved",
-  "date": "2026-05-11",
-  "rules": [
-    {
-      "id": "CORE-0039-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0039: Deployment Topology Abstraction & Environment Switcher",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0039 (core track). ADR decision: We decree a Strict Factory Driven Abstraction strategy for deployment switching: 1. Unified Environment Selector : Introduce a mandatory environment variable DEPLOYMENT TOPOLOGY with enum values [SAAS CLOUD, ON PREMISE ISOLATED] . This ADR contains enforceable language (must not, must, dependency); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: We decree a Strict Factory Driven Abstraction strategy for deployment switching: 1. Unified Environment Selector : Introduce a mandatory environment variable DEPLOYMENT TOPOLOGY with enum values [SAAS CLOUD, ON PREMISE ISOLATED] .",
-      "rationale": "Derived from ADR-0039 \"Decision\" section. Enforcement signals detected: must not, must, dependency.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0039 via static analysis, lint rules, or pipeline gates covering: must not, must, dependency. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0039-deployment-topology-abstraction-switcher.md"
-  ],
-  "effectiveDate": "2026-05-11"
-}

package/rulesets/adr/generated/adr-0041-dual-engine-policy-evaluation-native-opa.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0041-dual-engine-policy-evaluation-native-opa.rules.json",
-  "title": "ADR-0041 — Dual-Engine Policy Evaluation (Native + OPA) Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0041 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0041",
-  "adrTitle": "Dual-Engine Policy Evaluation (Native + OPA)",
-  "status": "Accepted",
-  "date": "",
-  "rules": [
-    {
-      "id": "CORE-0041-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0041: Dual-Engine Policy Evaluation (Native + OPA)",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0041 (core track). ADR decision: We will implement a Dual Engine Policy Evaluation Strategy using a Strategy Pattern ( IRuleEvaluatorStrategy ). 1. Native Engine (TypeScript) : Maintains the existing custom logic for baseline rules. This ADR contains enforceable language (must, dependencies, ci/cd); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: We will implement a Dual Engine Policy Evaluation Strategy using a Strategy Pattern ( IRuleEvaluatorStrategy ). 1. Native Engine (TypeScript) : Maintains the existing custom logic for baseline rules.",
-      "rationale": "Derived from ADR-0041 \"Decision\" section. Enforcement signals detected: must, dependencies, ci/cd.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0041 via static analysis, lint rules, or pipeline gates covering: must, dependencies, ci/cd. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0041-dual-engine-policy-evaluation.md"
-  ]
-}

package/rulesets/adr/generated/adr-0044-configurable-security-persistence-strategy-agnosticism-vs-na.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0044-configurable-security-persistence-strategy-agnosticism-vs-na.rules.json",
-  "title": "ADR-0044 — Configurable Security Persistence Strategy (Agnosticism vs. Native RLS) Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0044 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0044",
-  "adrTitle": "Configurable Security Persistence Strategy (Agnosticism vs. Native RLS)",
-  "status": "Proposed",
-  "date": "2026-05-12",
-  "rules": [
-    {
-      "id": "CORE-0044-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0044: Configurable Security Persistence Strategy (Agnosticism vs. Native RLS)",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0044 (core track). ADR decision: Adopt a Configurable Persistence Strategy utilizing the Strategy Pattern in the Infrastructure layer. The active approach will be determined at system bootstrap by a structural configuration flag ( SECURITY STRATEGY MODE ). This ADR contains enforceable language (layer, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt a Configurable Persistence Strategy utilizing the Strategy Pattern in the Infrastructure layer. The active approach will be determined at system bootstrap by a structural configuration flag ( SECURITY STRATEGY MODE ).",
-      "rationale": "Derived from ADR-0044 \"Decision\" section. Enforcement signals detected: layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0044 via static analysis, lint rules, or pipeline gates covering: layer, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0044-configurable-security-persistence-strategy.md"
-  ],
-  "effectiveDate": "2026-05-12"
-}

package/rulesets/adr/generated/adr-0045-microservice-extraction-readiness-criteria.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0045-microservice-extraction-readiness-criteria.rules.json",
-  "title": "ADR-0045 — Microservice Extraction Readiness Criteria Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0045 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0045",
-  "adrTitle": "Microservice Extraction Readiness Criteria",
-  "status": "Approved",
-  "date": "2026-05-12",
-  "rules": [
-    {
-      "id": "CORE-0045-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0045: Microservice Extraction Readiness Criteria",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0045 (core track). ADR decision: Formalize the \"2 out of 4\" rule as the mandatory quantitative trigger for extracting a Bounded Context into an independent service. This ADR contains enforceable language (must, ci/cd, threshold); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Formalize the \"2 out of 4\" rule as the mandatory quantitative trigger for extracting a Bounded Context into an independent service.",
-      "rationale": "Derived from ADR-0045 \"Decision\" section. Enforcement signals detected: must, ci/cd, threshold.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0045 via static analysis, lint rules, or pipeline gates covering: must, ci/cd, threshold. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0045-microservice-extraction-readiness-criteria.md"
-  ],
-  "effectiveDate": "2026-05-12"
-}

package/rulesets/adr/generated/adr-0046-unified-traceability-via-w3c-tracecontext.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0046-unified-traceability-via-w3c-tracecontext.rules.json",
-  "title": "ADR-0046 — Unified Traceability via W3C TraceContext Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0046 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0046",
-  "adrTitle": "Unified Traceability via W3C TraceContext",
-  "status": "Approved",
-  "date": "2026-05-12",
-  "rules": [
-    {
-      "id": "CORE-0046-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0046: Unified Traceability via W3C TraceContext",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0046 (core track). ADR decision: We hereby mandate the absolute unification of infrastructure and application telemetry governed by the following engineering directives: 1. Correlation Unification (Pivot to W3C) : The application MUST deprecate manual correlation identifier generation . 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: We hereby mandate the absolute unification of infrastructure and application telemetry governed by the following engineering directives: 1. Correlation Unification (Pivot to W3C) : The application MUST deprecate manual correlation identifier generation .",
-      "rationale": "Derived from ADR-0046 \"Decision\" section. Enforcement signals detected: must, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0046 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/0046-unified-observability-tracecontext.md"
-  ],
-  "effectiveDate": "2026-05-12"
-}

package/rulesets/adr/generated/adr-0047-progressive-architecture-evolution-framework-modular-monolit.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0047-progressive-architecture-evolution-framework-modular-monolit.rules.json",
-  "title": "ADR-0047 — Progressive Architecture Evolution Framework: Modular Monolith → Microservices Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0047 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0047",
-  "adrTitle": "Progressive Architecture Evolution Framework: Modular Monolith → Microservices",
-  "status": "Approved",
-  "date": "2026-05-12",
-  "rules": [
-    {
-      "id": "CORE-0047-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0047: Progressive Architecture Evolution Framework: Modular Monolith → Microservices",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0047 (core track). ADR decision: mermaid graph TD A[Is this a new product or MVP?] B[Modular Monolith — Phase 1] B C{Do at least 2 of 4\\nADR 0045 criteria hold\\nfor 15 sustained days?} C B C D[Extract Bounded Context → Microservice] A E{Does the team have\\nproven DevOps maturity?} E F[Refactor first as\\nModular Monolith] F C E D A G[See Section 8 — E… This ADR contains enforceable language (must, ci/cd); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: mermaid graph TD A[Is this a new product or MVP?] B[Modular Monolith — Phase 1] B C{Do at least 2 of 4\\nADR 0045 criteria hold\\nfor 15 sustained days?} C B C D[Extract Bounded Context → Microservice] A E{Does the team have\\nproven DevOps maturity?} E F[Refactor first as\\nModular Monolith] F C E D A G[See Section 8 — E…",
-      "rationale": "Derived from ADR-0047 \"Decision\" section. Enforcement signals detected: must, ci/cd.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0047 via static analysis, lint rules, or pipeline gates covering: must, ci/cd. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0047-architectural-patterns-monolith-soa-microservices.md"
-  ],
-  "effectiveDate": "2026-05-12"
-}

package/rulesets/adr/generated/adr-0048-enterprise-taxonomy-standardization-and-reference-layout.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0048-enterprise-taxonomy-standardization-and-reference-layout.rules.json",
-  "title": "ADR-0048 — Enterprise Taxonomy Standardization and Reference Layout Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0048 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0048",
-  "adrTitle": "Enterprise Taxonomy Standardization and Reference Layout",
-  "status": "Accepted",
-  "date": "",
-  "rules": [
-    {
-      "id": "CORE-0048-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0048: Enterprise Taxonomy Standardization and Reference Layout",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0048 (core track). ADR decision: It has been decided to adopt and enforce the Enterprise Taxonomy and Repository Structuring Policy as a global, immutable, and inheritable standard for this repository and all satellite ecosystems. This ADR contains enforceable language (must, naming, structure, enforce); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: It has been decided to adopt and enforce the Enterprise Taxonomy and Repository Structuring Policy as a global, immutable, and inheritable standard for this repository and all satellite ecosystems.",
-      "rationale": "Derived from ADR-0048 \"Decision\" section. Enforcement signals detected: must, naming, structure, enforce.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0048 via static analysis, lint rules, or pipeline gates covering: must, naming, structure, enforce. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0048-enterprise-taxonomy-reference-layout.md"
-  ]
-}

package/rulesets/adr/generated/adr-0049-naming-semantics-clean-code-policy-e2e-and-global.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0049-naming-semantics-clean-code-policy-e2e-and-global.rules.json",
-  "title": "ADR-0049 — Naming Semantics & Clean Code Policy (E2E and Global) Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0049 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0049",
-  "adrTitle": "Naming Semantics & Clean Code Policy (E2E and Global)",
-  "status": "Accepted",
-  "date": "2026-05-13",
-  "rules": [
-    {
-      "id": "CORE-0049-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0049: Naming Semantics & Clean Code Policy (E2E and Global)",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0049 (core track). ADR decision: Compliance with Clean Code standards is enforced for all naming and semantics in the E2E development lifecycle. lowerCamelCase : Variables, object instances, functions, and interface members. This ADR contains enforceable language (must, prohibited, naming, enforce, enforced); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Compliance with Clean Code standards is enforced for all naming and semantics in the E2E development lifecycle. lowerCamelCase : Variables, object instances, functions, and interface members.",
-      "rationale": "Derived from ADR-0049 \"Decision\" section. Enforcement signals detected: must, prohibited, naming, enforce, enforced.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0049 via static analysis, lint rules, or pipeline gates covering: must, prohibited, naming, enforce, enforced. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0049-naming-semantics-clean-code-policy.md"
-  ],
-  "effectiveDate": "2026-05-13"
-}

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"
-}