@evolith/core-domain 1.0.1 → 1.0.3

package/rulesets/adr/adr-0040-multi-runtime.rules.json

@@ -1,131 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/adr-0040-multi-runtime.rules.json",
-  "title": "ADR-0040 — Multi-Runtime Selection Matrix Rules",
-  "description": "Machine-readable rules encoding ADR-0040 Multi-Runtime Selection. Defines runtime selection by workload profile and inter-runtime communication rules.",
-  "version": "1.0.0",
-  "adrId": "ADR-0040",
-  "adrTitle": "Multi-Runtime Selection Matrix & Inter-Runtime Contracts",
-  "status": "Approved",
-  "date": "2026-05-11",
-  "effectiveDate": "2026-05-11",
-  "rules": [
-    {
-      "id": "RUNT-01",
-      "severity": "MUST",
-      "category": "runtime-selection",
-      "title": "Runtime selected by workload profile only",
-      "description": "Teams MUST select the target runtime based exclusively on the specific workload profile. Language selection must not be based on subjective preference.",
-      "rationale": "ADR-0040 §Decision: Optimized cost/performance. Each workload runs on the engine most efficient for its memory/CPU profile.",
-      "validationQuery": "Runtime selection documented in evolith.yaml and justified by workload profile analysis.",
-      "blocking": true
-    },
-    {
-      "id": "RUNT-02",
-      "severity": "MUST",
-      "category": "web-apis",
-      "title": "Web APIs and BFF use Node.js/TypeScript",
-      "description": "MANDATE: Node.js/TypeScript for Web APIs, BFF, and I/O-bound workloads. Rationale: High I/O concurrency, rapid delivery, extensive community ecosystem.",
-      "rationale": "ADR-0040 §Runtime Selection Matrix: Web APIs, BFF, I/O Bound → Node.js/TypeScript.",
-      "validationQuery": "Web API and BFF services run on Node.js. No .NET or other runtimes for these workloads without explicit ADR exception.",
-      "blocking": true,
-      "workload": "Web APIs, BFF, I/O Bound",
-      "runtime": "Node.js/TypeScript"
-    },
-    {
-      "id": "RUNT-03",
-      "severity": "MUST",
-      "category": "compute-workloads",
-      "title": "High compute and batch use .NET (C#)",
-      "description": "MANDATE: .NET (C#) for High Compute, ETL, and Batch workloads. Rationale: Superior multi-threading performance, typed raw compute, heavy math.",
-      "rationale": "ADR-0040 §Runtime Selection Matrix: High Compute, ETL, Batch → .NET (C#).",
-      "validationQuery": "High compute services (ETL, batch processing, mathematical computation) run on .NET. Documented workload classification in evolith.yaml.",
-      "blocking": true,
-      "workload": "High Compute, ETL, Batch",
-      "runtime": ".NET (C#)"
-    },
-    {
-      "id": "RUNT-04",
-      "severity": "MUST",
-      "category": "mobile-workloads",
-      "title": "Mobile with hardware access uses Android/Kotlin",
-      "description": "MANDATE: Android (Kotlin) for Operative Mobility workloads with direct hardware peripheral access (Scanners, GPS, Cameras) and strict offline mode requirements.",
-      "rationale": "ADR-0040 §Runtime Selection Matrix: Operative Mobility → Android (Kotlin).",
-      "validationQuery": "Mobile apps requiring hardware access run on Android/Kotlin. iOS considered only with Architecture Board exception.",
-      "blocking": true,
-      "workload": "Operative Mobility",
-      "runtime": "Android (Kotlin)"
-    },
-    {
-      "id": "RUNT-05",
-      "severity": "MUST NOT",
-      "category": "runtime-coupling",
-      "title": "Direct runtime dependency forbidden",
-      "description": "Direct runtime dependency is forbidden. Communication between disparate runtimes MUST traverse explicitly defined boundaries. No Node.js code directly importing .NET assemblies or vice versa.",
-      "rationale": "ADR-0040 §Decision: Runtime isolation prevents tight coupling that prevents independent evolution.",
-      "validationQuery": "No direct cross-runtime imports. All inter-runtime calls go through protocol boundaries (gRPC/REST).",
-      "blocking": true
-    },
-    {
-      "id": "RUNT-06",
-      "severity": "MUST",
-      "category": "sync-interop",
-      "title": "Synchronous inter-op uses gRPC",
-      "description": "Synchronous Inter-Op between runtimes (Node.js ↔ .NET) MUST mandatorily utilize gRPC (Protocol Buffers) for low-latency type-safe transmission.",
-      "rationale": "ADR-0040 §Inter-Runtime Communications Rule: gRPC for synchronous inter-op.",
-      "validationQuery": "Node.js ↔ .NET synchronous calls use gRPC. Contract tests validate proto compatibility.",
-      "blocking": true,
-      "scenario": "Synchronous Inter-Op"
-    },
-    {
-      "id": "RUNT-07",
-      "severity": "MUST",
-      "category": "async-interop",
-      "title": "Asynchronous inter-op uses message broker",
-      "description": "Asynchronous Inter-Op utilizes RabbitMQ/Kafka with contract validation via JSON-Schema or Protobuf. Contracts must be centrally stored and versioned.",
-      "rationale": "ADR-0040 §Inter-Runtime Communications Rule: RabbitMQ/Kafka for async inter-op with schema validation.",
-      "validationQuery": "Async events validated against schema. Message broker contracts centralized in shared library.",
-      "blocking": false,
-      "scenario": "Asynchronous Inter-Op"
-    },
-    {
-      "id": "RUNT-08",
-      "severity": "MUST",
-      "category": "contract-registry",
-      "title": "Contracts centrally stored and versioned",
-      "description": "All inter-runtime contracts must be centrally stored and versioned using semantic versioning. Changes require Pact JS/Net backward compatibility verification.",
-      "rationale": "ADR-0040 §Contract Registry: Centralized versioning prevents contract drift.",
-      "validationQuery": "Contract registry exists and is referenced by all inter-runtime communicating services.",
-      "blocking": true
-    }
-  ],
-  "runtimeMatrix": [
-    {
-      "workload": "Web APIs, BFF, I/O Bound",
-      "runtime": "Node.js/TypeScript",
-      "rationale": "High I/O concurrency, rapid delivery"
-    },
-    {
-      "workload": "High Compute, ETL, Batch",
-      "runtime": ".NET (C#)",
-      "rationale": "Superior multi-threading, typed compute"
-    },
-    {
-      "workload": "Operative Mobility",
-      "runtime": "Android (Kotlin)",
-      "rationale": "Direct hardware access, strict offline mode"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0040-multi-runtime-selection-contracts.md",
-    "reference/architecture/adrs/dotnet/0041-canonical-dotnet-backend-architecture.md"
-  ],
-  "exitCriteria": {
-    "description": "Runtime selection documented per service. Inter-runtime communication uses gRPC/RabbitMQ. Contracts versioned centrally.",
-    "validationTools": [
-      "evolits.yaml validation",
-      "gRPC",
-      "Pact"
-    ]
-  }
-}

package/rulesets/adr/adr-0050-gitflow-branching.rules.json

@@ -1,176 +0,0 @@
-{
-  "$schema": "../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/adr-0050-gitflow-branching.rules.json",
-  "title": "ADR-0050 — GitFlow Branching Strategy Rules",
-  "description": "Machine-readable rules encoding ADR-0050 GitFlow Branching Strategy. Contractual branch naming, promotion policies, merge policies, and release tagging.",
-  "version": "1.1.0",
-  "adrId": "ADR-0050",
-  "adrTitle": "GitFlow Branching Strategy",
-  "status": "Approved",
-  "effectiveDate": "2026-05-08",
-  "rules": [
-    {
-      "id": "GIT-01",
-      "severity": "MUST",
-      "category": "branch-naming",
-      "title": "Branch names follow pattern: type/ticket-id-description",
-      "description": "All branches MUST follow naming pattern: {type}/{ticket-id}-{short-description}. Types: feature/, bugfix/, hotfix/, release/, chore/.",
-      "rationale": "ADR-0050 §Decision: Consistent naming enables automation and team coordination.",
-      "validationQuery": "Branch names match pattern ^[a-z]+/[A-Z]+-[0-9]+-[a-z-]+$",
-      "blocking": true,
-      "examples": [
-        "feature/UMS-123-user-onboarding",
-        "bugfix/ADR-456-fix-grpc-timeout",
-        "hotfix/PROD-789-security-patch"
-      ]
-    },
-    {
-      "id": "GIT-02",
-      "severity": "MUST",
-      "category": "branch-naming",
-      "title": "Protected branches enforce direct push prohibition",
-      "description": "Direct push to protected branches (main, develop, qa, uat, release/*) is prohibited. All changes MUST come through pull requests with code review.",
-      "rationale": "ADR-0050 §Decision: Protected branches require PR workflow for audit trail and review.",
-      "validationQuery": "GitHub/GitLab branch protection rules block direct push to main, develop, qa, uat, release/*.",
-      "blocking": true,
-      "protectedBranches": [
-        "main",
-        "develop",
-        "qa",
-        "uat",
-        "release/*"
-      ]
-    },
-    {
-      "id": "GIT-03",
-      "severity": "MUST",
-      "category": "code-review",
-      "title": "PR requires minimum 1 approved review",
-      "description": "Every pull request MUST have at least one approved code review before merge. Reviews must verify code quality, test coverage, and compliance with architectural standards.",
-      "rationale": "ADR-0050 §Decision: Code review is mandatory for architectural compliance and knowledge sharing.",
-      "validationQuery": "PR merge blocked without minimum 1 approval. Reviewer cannot be the PR author.",
-      "blocking": true
-    },
-    {
-      "id": "GIT-04",
-      "severity": "MUST",
-      "category": "release-tagging",
-      "title": "Release tags follow semver format",
-      "description": "Release tags MUST follow semantic versioning format: v{major}.{minor}.{patch} (e.g., v1.0.0, v2.3.1). Tags are created at release point from main branch.",
-      "rationale": "ADR-0050 §Decision: Semver tags provide clear, auditable release history.",
-      "validationQuery": "Release tags match pattern ^v[0-9]+\\.[0-9]+\\.[0-9]+$",
-      "blocking": true
-    },
-    {
-      "id": "GIT-05",
-      "severity": "MUST",
-      "category": "merge-policy",
-      "title": "Feature branches merge via squash or rebase",
-      "description": "Feature branches merge into develop using squash or rebase strategy to maintain clean history. Fast-forward merge when possible.",
-      "rationale": "ADR-0050 §Decision: Squash/rebase keeps feature history clean while preserving commit granularity in PR.",
-      "validationQuery": "Feature → develop merges use squash or rebase. No merge commits on feature branches.",
-      "blocking": false
-    },
-    {
-      "id": "GIT-06",
-      "severity": "MUST",
-      "category": "hotfix-flow",
-      "title": "Hotfixes follow expedited merge path",
-      "description": "Hotfixes branch from main (tagged release), apply fix, merge back to main AND develop simultaneously. Hotfixes skip code freeze restrictions but still require review.",
-      "rationale": "ADR-0050 §Decision: Hotfixes need expedited path but cannot bypass review entirely.",
-      "validationQuery": "Hotfix branch merges to both main and develop. Both merges include same fix commit.",
-      "blocking": true
-    },
-    {
-      "id": "GIT-07",
-      "severity": "MUST NOT",
-      "category": "branch-lifetime",
-      "title": "Stale branches must be deleted after merge",
-      "description": "Branches MUST be deleted after successful merge. Feature/bugfix branches older than 30 days without activity are flagged as stale and subject to archive or removal.",
-      "rationale": "ADR-0050 §Decision: Branch proliferation creates confusion about current state of development.",
-      "validationQuery": "Merged branches auto-deleted. Stale branch detection runs weekly.",
-      "blocking": false
-    },
-    {
-      "id": "GIT-08",
-      "severity": "MUST",
-      "category": "commit-messages",
-      "title": "Commit messages follow Conventional Commits",
-      "description": "Commit messages MUST follow Conventional Commits format: type(scope): description. Types: feat, fix, docs, style, refactor, test, chore.",
-      "rationale": "ADR-0050 §Decision: Conventional Commits enables automated changelog generation and semantic release.",
-      "validationQuery": "Commit messages validated via commitlint or equivalent. Non-conforming commits blocked in CI.",
-      "blocking": true,
-      "pattern": "^(feat|fix|docs|style|refactor|test|chore)(\\([a-z-]+\\))?: .+"
-    },
-    {
-      "id": "GIT-09",
-      "severity": "MUST",
-      "category": "promotion-policy",
-      "title": "Environment promotion follows develop to qa to uat to main",
-      "description": "Promotions MUST follow the sequence develop -> qa -> uat -> main, with release/* inserted between uat and main when release hardening needs isolation.",
-      "rationale": "ADR-0050 §Promotion Criteria: Environment branches represent deployable states and require evidence-based promotion.",
-      "validationQuery": "Promotion PR source and target follow develop->qa, qa->uat, uat->release/* or uat->main, release/*->main.",
-      "blocking": true
-    },
-    {
-      "id": "GIT-10",
-      "severity": "MUST",
-      "category": "code-review",
-      "title": "Higher environments require stronger approval",
-      "description": "Pull requests into qa, uat, main, release/*, and hotfix/* MUST require at least two approvals unless an explicit incident exception applies.",
-      "rationale": "ADR-0050 §Pull Requests, Reviews, and Merge: Promotion branches need stronger review because they represent deployable environment states.",
-      "validationQuery": "Branch protection or repository rules require minimum two approvals for qa, uat, main, release/*, and hotfix/*.",
-      "blocking": true
-    }
-  ],
-  "branchTypes": [
-    {
-      "type": "feature/",
-      "lifetime": "until merged",
-      "target": "develop"
-    },
-    {
-      "type": "bugfix/",
-      "lifetime": "until merged",
-      "target": "develop"
-    },
-    {
-      "type": "hotfix/",
-      "lifetime": "hours to days",
-      "target": "main + develop"
-    },
-    {
-      "type": "release/",
-      "lifetime": "1-4 weeks",
-      "target": "main"
-    },
-    {
-      "type": "chore/",
-      "lifetime": "until merged",
-      "target": "develop"
-    },
-    {
-      "type": "qa",
-      "lifetime": "permanent",
-      "target": "uat"
-    },
-    {
-      "type": "uat",
-      "lifetime": "permanent",
-      "target": "main or release/*"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0050-gitflow-branching-strategy.md"
-  ],
-  "exitCriteria": {
-    "description": "Branch naming validated in CI. Protected branches enforce PR workflow and promotion sequence. Release tags follow semver.",
-    "validationTools": [
-      "commitlint",
-      "branch protection rules",
-      "GitHub Actions",
-      "CODEOWNERS",
-      "CodeQL"
-    ]
-  }
-}

package/rulesets/adr/generated/adr-0001-monorepo-orchestration-principle.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0001-monorepo-orchestration-principle.rules.json",
-  "title": "ADR-0001 — Monorepo Orchestration Principle Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0001 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0001",
-  "adrTitle": "Monorepo Orchestration Principle",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "CORE-0001-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0001: Monorepo Orchestration Principle",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0001 (core track). ADR decision: Adopt a Monorepo Orchestration Principle . All applications and shared libraries within a tightly coupled bounded context or product suite must reside in a single repository. The repository must be managed by an intelligent build orchestration tool capable of performing: Dependency graph analysis. This ADR contains enforceable language (must, dependency); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt a Monorepo Orchestration Principle . All applications and shared libraries within a tightly coupled bounded context or product suite must reside in a single repository. The repository must be managed by an intelligent build orchestration tool capable of performing: Dependency graph analysis.",
-      "rationale": "Derived from ADR-0001 \"Decision\" section. Enforcement signals detected: must, dependency.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0001 via static analysis, lint rules, or pipeline gates covering: must, dependency. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0001-monorepo-orchestration-principle.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-0006-microservices-transition-via-sidecar-pattern.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0006-microservices-transition-via-sidecar-pattern.rules.json",
-  "title": "ADR-0006 — Microservices Transition via Sidecar Pattern Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0006 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0006",
-  "adrTitle": "Microservices Transition via Sidecar Pattern",
-  "status": "Approved - Backlog (Phase 3 Milestone)",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "CORE-0006-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0006: Microservices Transition via Sidecar Pattern",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0006 (core track). ADR decision: Adopt the Sidecar Pattern as the standard distributed application runtime when splitting the monolith into independent services. Migration milestones: To prevent premature over engineering, Sidecars are NOT active by default in Milestone 2. 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: Adopt the Sidecar Pattern as the standard distributed application runtime when splitting the monolith into independent services. Migration milestones: To prevent premature over engineering, Sidecars are NOT active by default in Milestone 2.",
-      "rationale": "Derived from ADR-0006 \"Decision\" section. Enforcement signals detected: must, layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0006 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/0006-microservices-transition-sidecar-pattern.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-0009-strict-dependency-pinning-and-automated-vulnerability-manage.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0009-strict-dependency-pinning-and-automated-vulnerability-manage.rules.json",
-  "title": "ADR-0009 — Strict Dependency Pinning and Automated Vulnerability Management Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0009 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0009",
-  "adrTitle": "Strict Dependency Pinning and Automated Vulnerability Management",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "CORE-0009-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0009: Strict Dependency Pinning and Automated Vulnerability Management",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0009 (core track). ADR decision: Adopt a Zero Tolerance, Automated Dependency Governance Strategy : 1. Exact Version Pinning : Enforce static versioning across all package.json files by removing all ^ and ~ prefixes. This ADR contains enforceable language (must, dependency, pinning, enforce); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt a Zero Tolerance, Automated Dependency Governance Strategy : 1. Exact Version Pinning : Enforce static versioning across all package.json files by removing all ^ and ~ prefixes.",
-      "rationale": "Derived from ADR-0009 \"Decision\" section. Enforcement signals detected: must, dependency, pinning, enforce.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0009 via static analysis, lint rules, or pipeline gates covering: must, dependency, pinning, enforce. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0009-strict-dependency-pinning-vulnerability-management.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-0011-fault-tolerance-and-resiliency-patterns.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0011-fault-tolerance-and-resiliency-patterns.rules.json",
-  "title": "ADR-0011 — Fault Tolerance and Resiliency Patterns Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0011 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0011",
-  "adrTitle": "Fault Tolerance and Resiliency Patterns",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "CORE-0011-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0011: Fault Tolerance and Resiliency Patterns",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0011 (core track). ADR decision: Implement explicit Resilience Patterns protecting all outbound system exits: 1. Distributed Circuit Breaker (Opossum + Redis) : Wrap outbound network calls in high level infrastructure adapters. 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: Implement explicit Resilience Patterns protecting all outbound system exits: 1. Distributed Circuit Breaker (Opossum + Redis) : Wrap outbound network calls in high level infrastructure adapters.",
-      "rationale": "Derived from ADR-0011 \"Decision\" section. Enforcement signals detected: must, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0011 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/0011-fault-tolerance-resiliency-patterns.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-0013-cloud-infrastructure-topology-and-disaster-recovery-dr.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0013-cloud-infrastructure-topology-and-disaster-recovery-dr.rules.json",
-  "title": "ADR-0013 — Cloud Infrastructure Topology and Disaster Recovery (DR) Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0013 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0013",
-  "adrTitle": "Cloud Infrastructure Topology and Disaster Recovery (DR)",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "CORE-0013-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0013: Cloud Infrastructure Topology and Disaster Recovery (DR)",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0013 (core track). ADR decision: Design infrastructure topology targeting Cloud Native patterns enforcing high resilience and instant failover potential: 1. Automated Orchestration : Deployment evolves by architectural phase. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Design infrastructure topology targeting Cloud Native patterns enforcing high resilience and instant failover potential: 1. Automated Orchestration : Deployment evolves by architectural phase.",
-      "rationale": "Derived from ADR-0013 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0013-cloud-infrastructure-topology-dr.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-0014-multi-layer-distributed-caching-strategy.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0014-multi-layer-distributed-caching-strategy.rules.json",
-  "title": "ADR-0014 — Multi-Layer Distributed Caching Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0014 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0014",
-  "adrTitle": "Multi-Layer Distributed Caching Strategy",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "CORE-0014-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0014: Multi-Layer Distributed Caching Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0014 (core track). ADR decision: Evolve to a comprehensive Multi Layer Tiered Caching Strategy utilizing CDN edge caching and distributed cache nodes to intercept and resolve read requests as close to the user as possible: The system supports the integration of a Content Delivery Network (CDN) deployed in front of the Edge Gateway. 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: Evolve to a comprehensive Multi Layer Tiered Caching Strategy utilizing CDN edge caching and distributed cache nodes to intercept and resolve read requests as close to the user as possible: The system supports the integration of a Content Delivery Network (CDN) deployed in front of the Edge Gateway.",
-      "rationale": "Derived from ADR-0014 \"Decision\" section. Enforcement signals detected: layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0014 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/0014-multi-layer-distributed-caching-strategy.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-0015-event-driven-architecture-eda-for-intra-domain-communication.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0015-event-driven-architecture-eda-for-intra-domain-communication.rules.json",
-  "title": "ADR-0015 — Event-Driven Architecture (EDA) for Intra-Domain Communication Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0015 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0015",
-  "adrTitle": "Event-Driven Architecture (EDA) for Intra-Domain Communication",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "CORE-0015-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0015: Event-Driven Architecture (EDA) for Intra-Domain Communication",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0015 (core track). ADR decision: We will adopt an asynchronous Event Driven Architecture (EDA) for all cross bounded context communication: The domain will never import a concrete message broker. This ADR contains enforceable language (must, required, layer, boundaries, import); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: We will adopt an asynchronous Event Driven Architecture (EDA) for all cross bounded context communication: The domain will never import a concrete message broker.",
-      "rationale": "Derived from ADR-0015 \"Decision\" section. Enforcement signals detected: must, required, layer, boundaries, import.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0015 via static analysis, lint rules, or pipeline gates covering: must, required, layer, boundaries, import. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0015-event-driven-architecture-intra-domain.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-0016-immutable-business-audit-trail-and-change-tracking.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0016-immutable-business-audit-trail-and-change-tracking.rules.json",
-  "title": "ADR-0016 — Immutable Business Audit Trail and Change Tracking Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0016 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0016",
-  "adrTitle": "Immutable Business Audit Trail and Change Tracking",
-  "status": "Approved",
-  "date": "2026-05-09",
-  "rules": [
-    {
-      "id": "CORE-0016-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0016: Immutable Business Audit Trail and Change Tracking",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0016 (core track). ADR decision: Deploy a Hybrid Audit Strategy balancing performant direct reading with deep historical archiving: 1. Metadata Layer (Row Level) : Physical entities inherit standard persistent audit columns: created at , created by , updated at , updated by , and a concurrency tracking version integer. 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: Deploy a Hybrid Audit Strategy balancing performant direct reading with deep historical archiving: 1. Metadata Layer (Row Level) : Physical entities inherit standard persistent audit columns: created at , created by , updated at , updated by , and a concurrency tracking version integer.",
-      "rationale": "Derived from ADR-0016 \"Decision\" section. Enforcement signals detected: layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0016 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/0016-immutable-business-audit-trail.md"
-  ],
-  "effectiveDate": "2026-05-09"
-}

package/rulesets/adr/generated/adr-0017-feature-flagging-strategy-for-progressive-delivery.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0017-feature-flagging-strategy-for-progressive-delivery.rules.json",
-  "title": "ADR-0017 — Feature Flagging Strategy for Progressive Delivery Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0017 (core track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0017",
-  "adrTitle": "Feature Flagging Strategy for Progressive Delivery",
-  "status": "Approved",
-  "date": "2026-05-09",
-  "rules": [
-    {
-      "id": "CORE-0017-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0017: Feature Flagging Strategy for Progressive Delivery",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0017 (core track). ADR decision: Treat dynamic feature routing as standard Infrastructure injection , completely disjoint from persistence architectures: 1. Service Decoupling : Avoid physical db toggles table creation. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Treat dynamic feature routing as standard Infrastructure injection , completely disjoint from persistence architectures: 1. Service Decoupling : Avoid physical db toggles table creation.",
-      "rationale": "Derived from ADR-0017 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/core/0017-feature-flagging-strategy.md"
-  ],
-  "effectiveDate": "2026-05-09"
-}

package/rulesets/adr/generated/adr-0019-tactical-design-patterns-for-future-proofing.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-0019-tactical-design-patterns-for-future-proofing.rules.json",
-  "title": "ADR-0019 — Tactical Design Patterns for Future-Proofing Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0019 (core track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0019",
-  "adrTitle": "Tactical Design Patterns for Future-Proofing",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "CORE-0019-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0019: Tactical Design Patterns for Future-Proofing",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0019 (core track). ADR decision: Mandate specific Functional and Structure patterns protecting core purity: 1. The Result Pattern : Eliminate raw error throwing from inside application use cases. Methods strictly return a typed functional Result<V, E wrapper. 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: Mandate specific Functional and Structure patterns protecting core purity: 1. The Result Pattern : Eliminate raw error throwing from inside application use cases. Methods strictly return a typed functional Result<V, E wrapper.",
-      "rationale": "Derived from ADR-0019 \"Decision\" section. Enforcement signals detected: must, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0019 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/0019-tactical-design-patterns-future-proofing.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}