@evolith/core-domain 1.0.1 → 1.0.2

package/rulesets/adr/generated/adr-nodejs-0008-progressive-multi-module-evolution-with-api-gateway-and-bff-.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0008-progressive-multi-module-evolution-with-api-gateway-and-bff-.rules.json",
-  "title": "ADR-0008 — Progressive Multi-Module Evolution with API Gateway and BFF Patterns Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0008 (nodejs track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0008",
-  "adrTitle": "Progressive Multi-Module Evolution with API Gateway and BFF Patterns",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "NODE-0008-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0008: Progressive Multi-Module Evolution with API Gateway and BFF Patterns",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0008 (nodejs track). ADR decision: Adopt a Progressive Multi Module and Distributed Backend For Frontend (BFF) Gateway Architecture : 1. Dedicated BFF Gateways : Tailor dedicated gateways for each client type rather than sharing one generic entry point: Web BFF : Handles cookie based sessions and aggregates payloads for rich desktop displays. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Adopt a Progressive Multi Module and Distributed Backend For Frontend (BFF) Gateway Architecture : 1. Dedicated BFF Gateways : Tailor dedicated gateways for each client type rather than sharing one generic entry point: Web BFF : Handles cookie based sessions and aggregates payloads for rich desktop displays.",
-      "rationale": "Derived from ADR-0008 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0008-progressive-multimodule-evolution-gateway-bff.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-nodejs-0012-advanced-authorization-rbac-abac-strategy.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0012-advanced-authorization-rbac-abac-strategy.rules.json",
-  "title": "ADR-0012 — Advanced Authorization (RBAC/ABAC) Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0012 (nodejs track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0012",
-  "adrTitle": "Advanced Authorization (RBAC/ABAC) Strategy",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "NODE-0012-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0012: Advanced Authorization (RBAC/ABAC) Strategy",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0012 (nodejs track). ADR decision: Implement a Hybrid Architecture bridging Role Based (RBAC) and Attribute Based (ABAC) access control: 1. NestJS Guard Framework : Deploy custom @Roles() and @Permissions() annotations on controllers. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Implement a Hybrid Architecture bridging Role Based (RBAC) and Attribute Based (ABAC) access control: 1. NestJS Guard Framework : Deploy custom @Roles() and @Permissions() annotations on controllers.",
-      "rationale": "Derived from ADR-0012 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0012-advanced-authorization-rbac-abac.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-nodejs-0021-high-performance-authentication-graph-compilation.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0021-high-performance-authentication-graph-compilation.rules.json",
-  "title": "ADR-0021 — High-Performance Authentication Graph Compilation Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0021 (nodejs track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0021",
-  "adrTitle": "High-Performance Authentication Graph Compilation",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "NODE-0021-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0021: High-Performance Authentication Graph Compilation",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0021 (nodejs track). ADR decision: Standardize authentication login gateways to yield lightweight, pre digested Hierarchical Authorization Graphs boosted via Distributed memory side caches: 1. Stateless Signing : Session legitimacy verification continues over asymmetric RS256 Token validation, rotated dynamically (RTR). Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Standardize authentication login gateways to yield lightweight, pre digested Hierarchical Authorization Graphs boosted via Distributed memory side caches: 1. Stateless Signing : Session legitimacy verification continues over asymmetric RS256 Token validation, rotated dynamically (RTR).",
-      "rationale": "Derived from ADR-0021 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0021-high-performance-auth-and-graph-compilation.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-nodejs-0022-contextual-authentication-and-pluggable-output-projections.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0022-contextual-authentication-and-pluggable-output-projections.rules.json",
-  "title": "ADR-0022 — Contextual Authentication and Pluggable Output Projections Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0022 (nodejs track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0022",
-  "adrTitle": "Contextual Authentication and Pluggable Output Projections",
-  "status": "Approved",
-  "date": "2026-05-08",
-  "rules": [
-    {
-      "id": "NODE-0022-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0022: Contextual Authentication and Pluggable Output Projections",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0022 (nodejs track). ADR decision: Separate Identity Validation logic entirely from output composition capabilities, enforcing specialized runtime projectors: 1. Pluggable Projector Map : The Core service emits a universal permission model. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Separate Identity Validation logic entirely from output composition capabilities, enforcing specialized runtime projectors: 1. Pluggable Projector Map : The Core service emits a universal permission model.",
-      "rationale": "Derived from ADR-0022 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0022-contextual-auth-and-pluggable-projections.md"
-  ],
-  "effectiveDate": "2026-05-08"
-}

package/rulesets/adr/generated/adr-nodejs-0023-centralized-authorization-core-strategy.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0023-centralized-authorization-core-strategy.rules.json",
-  "title": "ADR-0023 — Centralized Authorization Core Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0023 (nodejs track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0023",
-  "adrTitle": "Centralized Authorization Core Strategy",
-  "status": "Approved",
-  "date": "2026-05-09",
-  "rules": [
-    {
-      "id": "NODE-0023-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0023: Centralized Authorization Core Strategy",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0023 (nodejs track). ADR decision: Commit to building and deploying the system as the Centralized Authorization Nucleus serving all satellite company tools: 1. Kernel Consolidation : Centralize the responsibility of analyzing identities, aggregating active role trees, and executing logic gates into a single, highly hardened domain. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Commit to building and deploying the system as the Centralized Authorization Nucleus serving all satellite company tools: 1. Kernel Consolidation : Centralize the responsibility of analyzing identities, aggregating active role trees, and executing logic gates into a single, highly hardened domain.",
-      "rationale": "Derived from ADR-0023 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0023-centralized-ums-vs-decentralized-access.md"
-  ],
-  "effectiveDate": "2026-05-09"
-}

package/rulesets/adr/generated/adr-nodejs-0026-adaptive-mfa-and-passwordless-platform.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0026-adaptive-mfa-and-passwordless-platform.rules.json",
-  "title": "ADR-0026 — Adaptive MFA and Passwordless Platform Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0026 (nodejs track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0026",
-  "adrTitle": "Adaptive MFA and Passwordless Platform",
-  "status": "Approved",
-  "date": "2026-05-09",
-  "rules": [
-    {
-      "id": "NODE-0026-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0026: Adaptive MFA and Passwordless Platform",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0026 (nodejs track). ADR decision: Rollout an Adaptive Risk Managed MFA Framework driving the Core authentication pipeline: 1. Passwordless First : Infuse native WebAuthn (Passkeys) into authentication flows, empowering end users to bind high security hardware (TouchID, FaceID, Yubikeys) natively to logins. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Rollout an Adaptive Risk Managed MFA Framework driving the Core authentication pipeline: 1. Passwordless First : Infuse native WebAuthn (Passkeys) into authentication flows, empowering end users to bind high security hardware (TouchID, FaceID, Yubikeys) natively to logins.",
-      "rationale": "Derived from ADR-0026 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0026-mfa-passwordless-adaptive-authentication.md"
-  ],
-  "effectiveDate": "2026-05-09"
-}

package/rulesets/adr/generated/adr-nodejs-0027-dual-protocol-api-strategy-rest-grpc.rules.json

@@ -1,28 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0027-dual-protocol-api-strategy-rest-grpc.rules.json",
-  "title": "ADR-0027 — Dual-Protocol API Strategy (REST & gRPC) Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0027 (nodejs track). Classification: advisory. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0027",
-  "adrTitle": "Dual-Protocol API Strategy (REST & gRPC)",
-  "status": "Approved",
-  "date": "2026-05-09",
-  "rules": [
-    {
-      "id": "NODE-0027-01",
-      "severity": "SHOULD",
-      "category": "adr-conformance",
-      "title": "Honor design decision in ADR-0027: Dual-Protocol API Strategy (REST & gRPC)",
-      "description": "Design and implementation SHOULD honor the decision recorded in ADR-0027 (nodejs track). ADR decision: Orchestrate a strict Dual Protocol Runtime Edge paired with Kong Gateway orchestration: 1. Standard REST (Public) : All browser agents, client portal apps, and B2B gateways consume secure, documented JSON REST APIs over standard HTTPS. Manual attestation required — not machine-verifiable.",
-      "statement": "ADR decision: Orchestrate a strict Dual Protocol Runtime Edge paired with Kong Gateway orchestration: 1. Standard REST (Public) : All browser agents, client portal apps, and B2B gateways consume secure, documented JSON REST APIs over standard HTTPS.",
-      "rationale": "Derived from ADR-0027 \"Decision\" section. No machine-verifiable signals detected; treated as an advisory design decision.",
-      "blocking": false,
-      "enforcement": "advisory"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0027-dual-protocol-rest-grpc-api-gateway.md"
-  ],
-  "effectiveDate": "2026-05-09"
-}

package/rulesets/adr/generated/adr-nodejs-0029-adoption-of-tactical-ddd-primitives-library.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0029-adoption-of-tactical-ddd-primitives-library.rules.json",
-  "title": "ADR-0029 — Adoption of Tactical DDD Primitives Library Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0029 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0029",
-  "adrTitle": "Adoption of Tactical DDD Primitives Library",
-  "status": "Approved",
-  "date": "2026-05-09",
-  "rules": [
-    {
-      "id": "NODE-0029-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0029: Adoption of Tactical DDD Primitives Library",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0029 (nodejs track). ADR decision: Standardize on utilizing the @nestjslatam/ddd primitives ecosystem within core domains to accelerate velocity: 1. Pure Typescript Only : Adhering to core purity constraints, this specific package has 0 external NPM dependencies, making it totally safe for placement directly in the Domain innermost layer. This ADR contains enforceable language (dependencies, layer, import); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Standardize on utilizing the @nestjslatam/ddd primitives ecosystem within core domains to accelerate velocity: 1. Pure Typescript Only : Adhering to core purity constraints, this specific package has 0 external NPM dependencies, making it totally safe for placement directly in the Domain innermost layer.",
-      "rationale": "Derived from ADR-0029 \"Decision\" section. Enforcement signals detected: dependencies, layer, import.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0029 via static analysis, lint rules, or pipeline gates covering: dependencies, layer, import. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0029-tactical-ddd-primitives-library.md"
-  ],
-  "effectiveDate": "2026-05-09"
-}

package/rulesets/adr/generated/adr-nodejs-0038-enterprise-error-handling-result-pattern-strategy.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0038-enterprise-error-handling-result-pattern-strategy.rules.json",
-  "title": "ADR-0038 — Enterprise Error Handling & Result Pattern Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0038 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0038",
-  "adrTitle": "Enterprise Error Handling & Result Pattern Strategy",
-  "status": "Approved",
-  "date": "2026-05-11",
-  "rules": [
-    {
-      "id": "NODE-0038-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0038: Enterprise Error Handling & Result Pattern Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0038 (nodejs track). ADR decision: Establish a strictly typed, unified Error Propagation framework based on the Result Pattern (Functional Error Handling): Mandate that ALL Application Use Cases and Domain Entities return errors explicitly instead of throwing them. 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: Establish a strictly typed, unified Error Propagation framework based on the Result Pattern (Functional Error Handling): Mandate that ALL Application Use Cases and Domain Entities return errors explicitly instead of throwing them.",
-      "rationale": "Derived from ADR-0038 \"Decision\" section. Enforcement signals detected: layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0038 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/nodejs/0038-error-handling-result-pattern-strategy.md"
-  ],
-  "effectiveDate": "2026-05-11"
-}

package/rulesets/adr/generated/adr-nodejs-0043-data-access-and-orm-strategy-for-node-js.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0043-data-access-and-orm-strategy-for-node-js.rules.json",
-  "title": "ADR-0043 — Data Access and ORM Strategy for Node.js Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0043 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0043",
-  "adrTitle": "Data Access and ORM Strategy for Node.js",
-  "status": "Approved",
-  "date": "2026-05-12",
-  "rules": [
-    {
-      "id": "NODE-0043-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0043: Data Access and ORM Strategy for Node.js",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0043 (nodejs track). ADR decision: Adopt TypeORM using the Data Mapper pattern as the enterprise standard for relational databases (PostgreSQL). Justification : Fully aligned with our Hexagonal Architecture ([ADR 0002](0002 clean architecture nestjs.md)). This ADR contains enforceable language (must, prohibited, layer, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt TypeORM using the Data Mapper pattern as the enterprise standard for relational databases (PostgreSQL). Justification : Fully aligned with our Hexagonal Architecture ([ADR 0002](0002 clean architecture nestjs.md)).",
-      "rationale": "Derived from ADR-0043 \"Decision\" section. Enforcement signals detected: must, prohibited, layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0043 via static analysis, lint rules, or pipeline gates covering: must, prohibited, layer, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0043-data-access-orm-strategy.md"
-  ],
-  "effectiveDate": "2026-05-12"
-}

package/rulesets/adr/generated/adr-nodejs-0044-frontend-clean-architecture-layer-boundaries-react.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0044-frontend-clean-architecture-layer-boundaries-react.rules.json",
-  "title": "ADR-0044 — Frontend Clean Architecture Layer Boundaries (React) Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0044 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0044",
-  "adrTitle": "Frontend Clean Architecture Layer Boundaries (React)",
-  "status": "Accepted",
-  "date": "2026-06-07",
-  "rules": [
-    {
-      "id": "NODE-0044-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0044: Frontend Clean Architecture Layer Boundaries (React)",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0044 (nodejs track). ADR decision: Apply Clean Architecture (Hexagonal) to React frontends with strict layer boundaries and an inward dependency rule. 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: Apply Clean Architecture (Hexagonal) to React frontends with strict layer boundaries and an inward dependency rule.",
-      "rationale": "Derived from ADR-0044 \"Decision\" section. Enforcement signals detected: must not, must, dependency, dependencies, layer, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0044 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/nodejs/0044-frontend-clean-architecture-layer-boundaries.md"
-  ],
-  "effectiveDate": "2026-06-07"
-}

package/rulesets/adr/generated/adr-nodejs-0045-frontend-state-management-zustand-tanstack-query-dual-strate.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0045-frontend-state-management-zustand-tanstack-query-dual-strate.rules.json",
-  "title": "ADR-0045 — Frontend State Management — Zustand + TanStack Query Dual Strategy Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0045 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0045",
-  "adrTitle": "Frontend State Management — Zustand + TanStack Query Dual Strategy",
-  "status": "Accepted",
-  "date": "2026-06-07",
-  "rules": [
-    {
-      "id": "NODE-0045-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0045: Frontend State Management — Zustand + TanStack Query Dual Strategy",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0045 (nodejs track). ADR decision: Adopt a dual strategy state management approach: TanStack Query is the canonical solution for all data that originates from an API endpoint. This ADR contains enforceable language (must not, must, import); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt a dual strategy state management approach: TanStack Query is the canonical solution for all data that originates from an API endpoint.",
-      "rationale": "Derived from ADR-0045 \"Decision\" section. Enforcement signals detected: must not, must, import.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0045 via static analysis, lint rules, or pipeline gates covering: must not, must, import. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0045-zustand-tanstack-query-state-management.md"
-  ],
-  "effectiveDate": "2026-06-07"
-}

package/rulesets/adr/generated/adr-nodejs-0046-prohibition-of-raw-technical-identifiers-in-user-interfaces.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0046-prohibition-of-raw-technical-identifiers-in-user-interfaces.rules.json",
-  "title": "ADR-0046 — Prohibition of Raw Technical Identifiers in User Interfaces Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0046 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0046",
-  "adrTitle": "Prohibition of Raw Technical Identifiers in User Interfaces",
-  "status": "Accepted",
-  "date": "2026-06-07",
-  "rules": [
-    {
-      "id": "NODE-0046-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0046: Prohibition of Raw Technical Identifiers in User Interfaces",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0046 (nodejs track). ADR decision: Raw technical identifiers (UUIDs, GUIDs, surrogate keys, internal database IDs) must never be rendered directly in a user facing interface unless a specific, justified business requirement explicitly requires it. This ADR contains enforceable language (must, layer, enforce); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Raw technical identifiers (UUIDs, GUIDs, surrogate keys, internal database IDs) must never be rendered directly in a user facing interface unless a specific, justified business requirement explicitly requires it.",
-      "rationale": "Derived from ADR-0046 \"Decision\" section. Enforcement signals detected: must, layer, enforce.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0046 via static analysis, lint rules, or pipeline gates covering: must, layer, enforce. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0046-no-raw-identifiers-in-ui.md"
-  ],
-  "effectiveDate": "2026-06-07"
-}

package/rulesets/adr/generated/adr-nodejs-0047-actionable-user-error-contract-and-correlated-diagnostics.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0047-actionable-user-error-contract-and-correlated-diagnostics.rules.json",
-  "title": "ADR-0047 — Actionable User Error Contract and Correlated Diagnostics Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0047 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0047",
-  "adrTitle": "Actionable User Error Contract and Correlated Diagnostics",
-  "status": "Accepted",
-  "date": "2026-06-07",
-  "rules": [
-    {
-      "id": "NODE-0047-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0047: Actionable User Error Contract and Correlated Diagnostics",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0047 (nodejs track). ADR decision: Adopt a two channel error contract : 1. User feedback channel — exposes only approved, actionable business or validation information. 2. Diagnostic channel — retains technical details in structured logs and telemetry correlated through a server generated error identifier. This ADR contains enforceable language (must not, must, required, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt a two channel error contract : 1. User feedback channel — exposes only approved, actionable business or validation information. 2. Diagnostic channel — retains technical details in structured logs and telemetry correlated through a server generated error identifier.",
-      "rationale": "Derived from ADR-0047 \"Decision\" section. Enforcement signals detected: must not, must, required, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0047 via static analysis, lint rules, or pipeline gates covering: must not, must, required, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0047-actionable-user-error-contract.md"
-  ],
-  "effectiveDate": "2026-06-07"
-}

package/rulesets/adr/generated/adr-nodejs-0048-feature-flag-system-scope-and-structured-criteria-model.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0048-feature-flag-system-scope-and-structured-criteria-model.rules.json",
-  "title": "ADR-0048 — Feature Flag System Scope and Structured Criteria Model Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0048 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0048",
-  "adrTitle": "Feature Flag System Scope and Structured Criteria Model",
-  "status": "Accepted",
-  "date": "2026-06-07",
-  "rules": [
-    {
-      "id": "NODE-0048-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0048: Feature Flag System Scope and Structured Criteria Model",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0048 (nodejs track). ADR decision: FeatureFlag must be an Aggregate Root in the Configuration bounded context. This ADR contains enforceable language (must not, must, required, structure); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: FeatureFlag must be an Aggregate Root in the Configuration bounded context.",
-      "rationale": "Derived from ADR-0048 \"Decision\" section. Enforcement signals detected: must not, must, required, structure.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0048 via static analysis, lint rules, or pipeline gates covering: must not, must, required, structure. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0048-feature-flag-system-scope-criteria-model.md"
-  ],
-  "effectiveDate": "2026-06-07"
-}

package/rulesets/adr/generated/adr-nodejs-0074-monorepo-orchestration-with-nx.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0074-monorepo-orchestration-with-nx.rules.json",
-  "title": "ADR-0074 — Monorepo Orchestration with Nx Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0074 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0074",
-  "adrTitle": "Monorepo Orchestration with Nx",
-  "status": "Approved",
-  "date": "2026-06-12",
-  "rules": [
-    {
-      "id": "NODE-0074-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0074: Monorepo Orchestration with Nx",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0074 (nodejs track). ADR decision: Adopt Nx as the monorepo orchestration tool for Node.js, combined with npm workspaces for native package resolution. nx.json defines build, test, and lint dependency graphs for intelligent caching and parallel execution. This ADR contains enforceable language (dependency, layer, lint, eslint, enforce, boundaries); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt Nx as the monorepo orchestration tool for Node.js, combined with npm workspaces for native package resolution. nx.json defines build, test, and lint dependency graphs for intelligent caching and parallel execution.",
-      "rationale": "Derived from ADR-0074 \"Decision\" section. Enforcement signals detected: dependency, layer, lint, eslint, enforce, boundaries.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0074 via static analysis, lint rules, or pipeline gates covering: dependency, layer, lint, eslint, enforce, boundaries. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0074-monorepo-orchestration-nx.md"
-  ],
-  "effectiveDate": "2026-06-12"
-}

package/rulesets/adr/generated/adr-nodejs-0075-application-gateway-bff-with-nestjs.rules.json

@@ -1,29 +0,0 @@
-{
-  "$schema": "../../schema/ruleset-standard.schema.json",
-  "$id": "https://evolith.dev/rulesets/adr/generated/adr-nodejs-0075-application-gateway-bff-with-nestjs.rules.json",
-  "title": "ADR-0075 — Application Gateway (BFF) with NestJS Rules (generated)",
-  "description": "Auto-generated ruleset encoding ADR-0075 (nodejs track). Classification: executable. Generated by .harness/scripts/generate-adr-rulesets.mjs — do not edit by hand.",
-  "version": "1.0.0",
-  "adrId": "ADR-0075",
-  "adrTitle": "Application Gateway (BFF) with NestJS",
-  "status": "Approved",
-  "date": "2026-06-12",
-  "rules": [
-    {
-      "id": "NODE-0075-01",
-      "severity": "MUST",
-      "category": "adr-conformance",
-      "title": "Conform to ADR-0075: Application Gateway (BFF) with NestJS",
-      "description": "Implementations MUST conform to the decision recorded in ADR-0075 (nodejs track). ADR decision: Adopt NestJS as the Application Gateway (BFF) framework. NestJS provides a robust dependency injection container, native gRPC and REST support, and enforced modularity. It is safely deployed behind the Tier 1 Edge Gateway. This ADR contains enforceable language (dependency, enforce, enforced); conformance is expected to be verifiable via static analysis, linting, CI gates, or structural checks.",
-      "statement": "ADR decision: Adopt NestJS as the Application Gateway (BFF) framework. NestJS provides a robust dependency injection container, native gRPC and REST support, and enforced modularity. It is safely deployed behind the Tier 1 Edge Gateway.",
-      "rationale": "Derived from ADR-0075 \"Decision\" section. Enforcement signals detected: dependency, enforce, enforced.",
-      "validationQuery": "Verify codebase/CI compliance with ADR-0075 via static analysis, lint rules, or pipeline gates covering: dependency, enforce, enforced. Concrete checks to be wired into the harness.",
-      "blocking": true,
-      "enforcement": "executable"
-    }
-  ],
-  "references": [
-    "reference/architecture/adrs/nodejs/0075-application-gateway-bff-nestjs.md"
-  ],
-  "effectiveDate": "2026-06-12"
-}

package/rulesets/architecture/README.es.md

@@ -1,21 +0,0 @@
-# Índice de Reglas Arquitectónicas del Progressive-Axis
-
-Reglas que gobiernan el modelo de compatibilidad `progressive-axis` desde monolito modular hacia modulos distribuidos y microservicios.
-
-F1, F2 y F3 permanecen soportados como aliases de compatibilidad para CLI, MCP, Service CORE API y contratos de satelite existentes. No representan todo el universo topologico. Los perfiles multi-topologia fuera de este eje se resuelven mediante `topology.manifest.json` y el modelo dimensional en [Modelo de Dimensiones Topologicas](../../reference/architecture/topologies/topology-dimensions.es.md).
-
-| Fase | Archivo de Reglas | Descripción |
-|---|---|---|
-| **F1 — Monolito Modular** | [f1-modular-monolith.rules.json](../../reference/architecture/topologies/progressive-axis/modular-monolith/modular-monolith.rules.json) | Topología canónica de inicio; gates de preparación para extracción |
-| **F2 — Módulos Distribuidos** | [f2-distributed-modules.rules.json](../../reference/architecture/topologies/progressive-axis/distributed-modules/distributed-modules.rules.json) | Límites de módulos formalizados; contratos inter-módulo establecidos |
-| **F3 — Microservicios** | [f3-microservices.rules.json](../../reference/architecture/topologies/progressive-axis/microservices/microservices.rules.json) | Desplegabilidad autónoma; preparación para service mesh |
-
-| Alias de Compatibilidad | Topologia Canonica |
-|---|---|
-| `--arch-level F1` | `--topology modular-monolith` |
-| `--arch-level F2` | `--topology distributed-modules` |
-| `--arch-level F3` | `--topology microservices` |
-
----
-
-Volver al [Rulesets Hub](../README.es.md)

package/rulesets/architecture/README.md

@@ -1,21 +0,0 @@
-# Progressive-Axis Architecture Rules Index
-
-Rules governing the `progressive-axis` compatibility model from modular monolith to distributed modules to microservices.
-
-F1, F2, and F3 remain supported compatibility aliases for existing CLI, MCP, Service CORE API, and satellite contracts. They are not the full topology universe. Multi-topology profiles outside this axis are resolved through `topology.manifest.json` and the dimensional model in [Topology Dimensions Model](../../reference/architecture/topologies/topology-dimensions.md).
-
-| Phase | Rule File | Description |
-|---|---|---|
-| **F1 — Modular Monolith** | [f1-modular-monolith.rules.json](../../reference/architecture/topologies/progressive-axis/modular-monolith/modular-monolith.rules.json) | Canonical starting topology; extraction readiness gates |
-| **F2 — Distributed Modules** | [f2-distributed-modules.rules.json](../../reference/architecture/topologies/progressive-axis/distributed-modules/distributed-modules.rules.json) | Module boundaries formalized; inter-module contracts established |
-| **F3 — Microservices** | [f3-microservices.rules.json](../../reference/architecture/topologies/progressive-axis/microservices/microservices.rules.json) | Autonomous deployability; service mesh readiness |
-
-| Compatibility Alias | Canonical Topology |
-|---|---|
-| `--arch-level F1` | `--topology modular-monolith` |
-| `--arch-level F2` | `--topology distributed-modules` |
-| `--arch-level F3` | `--topology microservices` |
-
----
-
-Back to [Rulesets Hub](../README.md)

package/rulesets/architecture/opa/progressive-axis.rego

@@ -1,50 +0,0 @@
-package evolith.architecture.progressive_axis
-
-import rego.v1
-
-# ---------------------------------------------------------------------------
-# Progressive-Axis Architecture Compliance (ARCH-01..ARCH-05)
-# Validates cross-cutting eligibility rules for F1→F2→F3 topology transitions.
-# Topology-specific rules live co-located with each topology manifest.
-# ---------------------------------------------------------------------------
-
-valid_topologies := {"modular-monolith", "distributed-modules", "microservices"}
-
-upgrade_path := {
-	"modular-monolith": "distributed-modules",
-	"distributed-modules": "microservices",
-}
-
-violations contains {"id": "ARCH-01", "message": "evolith.yaml must declare a topology field matching a valid progressive-axis topology (modular-monolith, distributed-modules, microservices)"} if {
-	not valid_topologies[input.satellite.topology]
-}
-
-violations contains {"id": "ARCH-02", "message": msg} if {
-	from := input.satellite.previousTopology
-	to := input.satellite.topology
-	from != to
-	valid_topologies[from]
-	valid_topologies[to]
-	upgrade_path[from] != to
-	msg := sprintf("Topology transition from '%v' to '%v' is not allowed — must follow the progressive axis upgrade path (modular-monolith → distributed-modules → microservices)", [from, to])
-}
-
-violations contains {"id": "ARCH-03", "message": "An ADR must exist and be in accepted state before topology selection is finalised"} if {
-	not input.satellite.topologyAdrAccepted
-}
-
-violations contains {"id": "ARCH-04", "message": "topology.manifest.json must be present and declare the active topology"} if {
-	not input.satellite.hasTopologyManifest
-}
-
-violations contains {"id": "ARCH-05", "message": msg} if {
-	level := input.satellite.archLevel
-	topology := input.satellite.topology
-	expected := {
-		"F1": "modular-monolith",
-		"F2": "distributed-modules",
-		"F3": "microservices",
-	}
-	expected[level] != topology
-	msg := sprintf("Architecture compatibility alias '%v' does not match declared topology '%v' (expected: '%v')", [level, topology, expected[level]])
-}