@evolith/core-domain 1.0.1 → 1.0.3

package/rulesets/topologies/edge-computing/README.md

@@ -1,81 +0,0 @@
-# Edge Computing Topology Profile
-
-> **Bilingual Navigation:** [Version en Espanol](./README.es.md)
-
-**Status:** Accepted  
-**Dimension:** `execution`  
-**Topology ID:** `edge-computing`  
-**Compatibility Alias:** `F2-compatible`  
-**Manifest:** [topology.manifest.json](./topology.manifest.json)
-
-Edge computing is an execution topology for workloads that must run close to users, devices, regions, or constrained network boundaries while remaining governed by the same Evolith Core architecture contracts.
-
-## Purpose
-
-Use this topology when latency, locality, offline tolerance, regulatory placement, or device-adjacent processing requires execution outside the central runtime.
-
-Edge workloads must remain governed by explicit synchronization, security, observability, deployment, and data-boundary rules. Edge placement is not permission to duplicate domain logic without ownership.
-
-## Governance Rules
-
-| Rule | Requirement |
-|---|---|
-| Locality rationale | Edge placement must be justified by latency, resiliency, locality, or regulatory constraints. |
-| Synchronization | State synchronization must be explicit, observable, and conflict-aware. |
-| Security | Edge nodes must enforce authentication, authorization, and secret handling appropriate to constrained environments. |
-| Observability | Edge workloads must report health, failure, and trace context despite intermittent connectivity. |
-| Domain ownership | Edge logic must not fork domain behavior outside the owning bounded context. |
-
-## Required Authority
-
-| Artifact | Role |
-|---|---|
-| [ADR-0079: Multi-Topology Reference Corpus](../../../adrs/core/0079-multi-topology-reference-corpus.md) | Governs topology manifests and composition. |
-| [ADR-0096: Edge Computing Architecture Governance](../../../adrs/core/0096-edge-computing-architecture-governance.md) | Governs edge-specific architecture constraints. |
-| [Edge Computing Architecture Rules](./edge-computing.rules.json) | Existing executable compatibility rules. |
-| [Topology Dimensions Model](../../topology-dimensions.md) | Defines composition and compatibility rules. |
-
-## Executable Contract
-
-Satellites adopting this topology must declare an `edge-computing.config.json` file in their root. This JSON acts as the executable machine-readable contract evaluated by the Evolith Governance Engine.
-
-```json
-{
-  "syncStrategy": "offline-first",
-  "edgeIsolation": true,
-  "conflictResolution": "last-write-wins"
-}
-```
-
-EC-R01 through EC-R03 require that contract, enforcing a declared synchronization strategy, edge node isolation for autonomous operation, and an explicit conflict resolution mode. The Native evaluator and [OPA policy](./edge-computing.rego) evaluate these fields.
-
-### Offline-First Persistence Patterns
-
-A critical aspect of the Edge Computing topology is handling intermittent connectivity. To comply with `EC-R01` (Mandatory Synchronization Strategy) and `EC-R03` (Conflict Resolution), edges must implement offline-first persistence patterns:
-
-1.  **Local-First Reads & Writes:** Use local databases (e.g., SQLite, IndexedDB) as the primary data store for the edge workload. This ensures the application remains fully functional during network partitions (`edgeIsolation: true`).
-2.  **Background Synchronization:** Utilize background workers or service workers to synchronize local changes with the central control plane when connectivity is restored.
-3.  **Conflict Resolution:** Explicitly declare and handle state conflicts resulting from offline modifications (e.g., `last-write-wins`, manual merging).
-
-## Composition
-
-`edge-computing` can combine with:
-
-| Topology | Why It Can Compose |
-|---|---|
-| `microservices` | Places individual service workloads at the edge with governed synchronization. |
-| `distributed-modules` | Extends module boundaries to edge locations with explicit sync contracts. |
-| `event-driven` | Coordinates edge state changes through observable event channels. |
-| `serverless` | Deploys managed execution units at edge locations with bounded initialization. |
-| `agentic-ai` | Runs AI-agent inference at the edge with offline-capable governance. |
-
-## Business Boundary
-
-This profile is technical-only. It does not define ROI, cost model, hardware spend, staffing, delivery timing, prioritization, or Funnel 0. Evolith Tracker owns those business concerns through its ACL.
-
-## Operational Budgets
-
-This topology declares architectural envelopes for latency, cold-start, and per-execution cost in `spec.operationalBudgets` of [`topology.manifest.json`](./topology.manifest.json). Operators verify satellites against these envelopes following the shared [Operational Budgets Runbook](../operational-budgets-runbook.md).
-
----
-[Back to Topology Hub](../../README.md)

package/rulesets/topologies/edge-computing/adoption.es.md

@@ -1,268 +0,0 @@
-# Guía de Adopción de Computación en el Borde
-
-> **Navegación Bilingüe:** [English](./adoption.md) | [Español](./adoption.es.md)
-
-**Propietario:** Ingeniería de Plataforma
-**Topología:** Computación en el Borde
-
-## Criterios de Entrada
-
-Antes de adoptar la computación en el borde, evalúe si su workload cumple con los criterios de entrada.
-
-### Matriz de Evaluación
-
-| Criterio | Requisito | Medición | Umbral |
-|----------|-----------|----------|--------|
-| Latencia | De cara al usuario, baja latencia | Latencia de extremo a extremo | < 200ms |
-| Localidad de Datos | Específico del usuario o región | Patrón de acceso a datos | > 80% local |
-| Regulatorio | Residencia de datos requerida | Auditoría de cumplimiento | Requerido |
-| Disponibilidad | Capacidad sin conexión necesaria | Análisis de conectividad | Intermitente |
-| Costo | Alto volumen de solicitudes | Conteo de solicitudes | > 100K/día |
-
-### Lista de Verificación de Criterios de Entrada
-
-```bash
-# Evaluar preparación para adopción del borde
-edge-cli adoption evaluate \
-  --service product-api \
-  --check-latency \
-  --check-locality \
-  --check-regulatory \
-  --check-offline
-
-# Salida:
-# SERVICE: product-api
-# LATENCY_BENEFIT: 65ms (PASS)
-# DATA_LOCALITY: 92% local (PASS)
-# REGULATORY: GDPR required (PASS)
-# OFFLINE_NEEDED: yes (PASS)
-# ADOPTION_SCORE: 95/100
-# RECOMMENDATION: ADOPT
-```
-
-### Flujo de Decisión
-
-```
-Evaluación del Workload
-       │
-       ├── Latencia < 200ms?
-       │       ├── SÍ → Proceder
-       │       └── NO → Evaluar alternativas en la nube
-       │
-       ├── Localidad de datos > 80%?
-       │       ├── SÍ → Proceder
-       │       └── NO → Considerar enfoque híbrido
-       │
-       ├── Regulatorio requerido?
-       │       ├── SÍ → Borde requerido
-       │       └── NO → Evaluar costo-beneficio
-       │
-       └── Sin conexión necesario?
-               ├── SÍ → Borde requerido
-               └── NO → Evaluar alternativas
-```
-
-## Aprovisionamiento de Nodos
-
-Aprovisionar nodos del borde según los requisitos de su workload.
-
-### Flujo de Aprovisionamiento
-
-```bash
-# Aprovisionar nodos del borde para un nuevo despliegue
-edge-cli node provision \
-  --cluster edge-cluster-01 \
-  --nodes 4 \
-  --role compute \
-  --specs "cpu=4,memory=8Gi,storage=50Gi" \
-  --region us-west-2 \
-  --zone-usability high
-
-# Salida:
-# PROVISIONING: 4 nodes
-# CLUSTER: edge-cluster-01
-# REGION: us-west-2
-# SPECS: cpu=4,memory=8Gi,storage=50Gi
-# STATUS: provisioning...
-# NODES:
-#   - edge-node-01: provisioning
-#   - edge-node-02: provisioning
-#   - edge-node-03: provisioning
-#   - edge-node-04: provisioning
-```
-
-### Guía de Dimensionamiento de Nodos
-
-| Tipo de Workload | CPU | Memoria | Almacenamiento | Caso de Uso |
-|------------------|-----|---------|----------------|-------------|
-| Contenido estático | 2 | 4Gi | 20Gi | CDN, activos |
-| Caché de API | 4 | 8Gi | 50Gi | APIs REST |
-| Cómputo pesado | 8 | 16Gi | 100Gi | Inferencia ML |
-| Almacenamiento pesado | 4 | 8Gi | 200Gi | Almacenamiento de medios |
-
-### Aprovisionamiento Automatizado
-
-```yaml
-# infrastructure/edge-nodes.yaml
-provisioning:
-  cluster: edge-cluster-01
-  nodes:
-    - name: edge-node-01
-      role: compute
-      specs:
-        cpu: 4
-        memory: 8Gi
-        storage: 50Gi
-      region: us-west-2
-      zone: us-west-2a
-    - name: edge-node-02
-      role: compute
-      specs:
-        cpu: 4
-        memory: 8Gi
-        storage: 50Gi
-      region: us-west-2
-      zone: us-west-2b
-  networking:
-    vpc: edge-vpc-01
-    subnet: edge-subnet-01
-    security_groups:
-      - edge-sg-compute
-      - edge-sg-monitoring
-```
-
-## Pipeline de Despliegue
-
-Desplegar workloads en el borde utilizando un pipeline controlado.
-
-### Etapas del Pipeline
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│  Pipeline de Despliegue del Borde                           │
-│  ┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐       │
-│  │ Compilar│→ │ Probar  │→ │ Estaging│→ │ Despleg │       │
-│  │         │  │         │  │         │  │         │       │
-│  │ Compilar│  │ Unit    │  │ Canary  │  │ Rolling │       │
-│  │ Empaquet│  │ Integ.  │  │ Shadow  │  │ Blue/Grn│       │
-│  │ Validar │  │ E2E     │  │ Carga   │  │ Rápido  │       │
-│  └─────────┘  └─────────┘  └─────────┘  └─────────┘       │
-└─────────────────────────────────────────────────────────────┘
-```
-
-### Configuración del Pipeline
-
-```yaml
-# .edge-deploy.yaml
-pipeline:
-  stages:
-    - name: build
-      steps:
-        - edge-cli build --optimize
-        - edge-cli package --minify
-        - edge-cli validate --check-deps
-    
-    - name: test
-      steps:
-        - edge-cli test unit --coverage 80%
-        - edge-cli test integration --timeout 60s
-        - edge-cli test e2e --browser chrome
-    
-    - name: stage
-      steps:
-        - edge-cli deploy --target canary --percentage 10%
-        - edge-cli monitor --duration 300s
-        - edge-cli analyze --error-rate 0.1%
-    
-    - name: deploy
-      strategy: rolling
-      batch_size: 25%
-      pause_on_failure: true
-      rollback_on_error: true
-```
-
-### Estrategias de Despliegue
-
-| Estrategia | Velocidad | Riesgo | Retroceso | Caso de Uso |
-|------------|-----------|--------|-----------|-------------|
-| Rolling | Media | Bajo | Fácil | Predeterminado |
-| Blue/Green | Rápida | Medio | Rápido | Crítico |
-| Canary | Lenta | Bajo | Fácil | Experimental |
-| Shadow | Media | Bajo | Ninguno | Validación |
-
-## Lista de Verificación de Adopción
-
-Utilizar esta lista de verificación para asegurar una adopción exitosa del borde.
-
-### Pre-Adopción
-
-- [ ] Workload cumple criterios de entrada
-- [ ] Requisitos de latencia validados
-- [ ] Cumplimiento de residencia de datos verificado
-- [ ] Análisis costo-beneficio completado
-- [ ] Capacitación del equipo programada
-
-### Infraestructura
-
-- [ ] Nodos del borde aprovisionados
-- [ ] Conectividad de red establecida
-- [ ] Políticas de seguridad configuradas
-- [ ] Monitoreo y alertas configurados
-- [ ] Respaldo y recuperación probados
-
-### Despliegue
-
-- [ ] Aplicación adaptada para el borde
-- [ ] Datos primero local implementados
-- [ ] Estrategias de sincronización configuradas
-- [ ] Resolución de conflictos probada
-- [ ] Modo sin conexión validado
-
-### Operaciones
-
-- [ ] Manuales operativos creados
-- [ ] Turno de guardia establecido
-- [ ] Líneas base de rendimiento establecidas
-- [ ] Seguimiento de costos habilitado
-- [ ] Revisiones regulares programadas
-
-### Post-Adopción
-
-- [ ] Métricas de rendimiento recolectadas
-- [ ] Retroalimentación del usuario recopilada
-- [ ] Optimización de costos revisada
-- [ ] Lecciones aprendidas documentadas
-- [ ] Plan de escalabilidad preparado
-
-## Cronograma de Migración
-
-### Semana 1-2: Evaluación
-
-- Evaluar workloads para elegibilidad en el borde
-- Validar requisitos de latencia y residencia de datos
-- Completar análisis costo-beneficio
-- Seleccionar workload piloto
-
-### Semana 3-4: Infraestructura
-
-- Aprovisionar nodos del borde
-- Configurar redes y seguridad
-- Configurar monitoreo y alertas
-- Probar conectividad y conmutación por error
-
-### Semana 5-6: Aplicación
-
-- Adaptar aplicación para despliegue en el borde
-- Implementar patrones de datos primero local
-- Configurar estrategias de sincronización
-- Probar capacidades sin conexión
-
-### Semana 7-8: Despliegue
-
-- Desplegar en entorno canary
-- Ejecutar pruebas de carga y validación
-- Desplegar en producción (rolling)
-- Monitorear y optimizar
-
----
-[Volver al Perfil de Computación en el Borde](./README.es.md)

package/rulesets/topologies/edge-computing/adoption.md

@@ -1,268 +0,0 @@
-# Edge Computing — Adoption Guide
-
-> **Bilingual Navigation:** [English](./adoption.md) | [Español](./adoption.es.md)
-
-**Owner:** Platform Engineering
-**Topology:** Edge Computing
-
-## Entry Criteria
-
-Before adopting edge computing, evaluate whether your workload meets the entry criteria.
-
-### Evaluation Matrix
-
-| Criterion | Requirement | Measurement | Threshold |
-|-----------|-------------|-------------|-----------|
-| Latency | User-facing, low-latency | End-to-end latency | < 200ms |
-| Data Locality | User or region-specific | Data access pattern | > 80% local |
-| Regulatory | Data residency required | Compliance audit | Required |
-| Availability | Offline capability needed | Connectivity analysis | Intermittent |
-| Cost | High request volume | Request count | > 100K/day |
-
-### Entry Criteria Checklist
-
-```bash
-# Evaluate edge adoption readiness
-edge-cli adoption evaluate \
-  --service product-api \
-  --check-latency \
-  --check-locality \
-  --check-regulatory \
-  --check-offline
-
-# Output:
-# SERVICE: product-api
-# LATENCY_BENEFIT: 65ms (PASS)
-# DATA_LOCALITY: 92% local (PASS)
-# REGULATORY: GDPR required (PASS)
-# OFFLINE_NEEDED: yes (PASS)
-# ADOPTION_SCORE: 95/100
-# RECOMMENDATION: ADOPT
-```
-
-### Decision Flow
-
-```
-Workload Assessment
-       │
-       ├── Latency < 200ms?
-       │       ├── YES → Proceed
-       │       └── NO → Evaluate cloud alternatives
-       │
-       ├── Data locality > 80%?
-       │       ├── YES → Proceed
-       │       └── NO → Consider hybrid approach
-       │
-       ├── Regulatory required?
-       │       ├── YES → Edge required
-       │       └── NO → Evaluate cost-benefit
-       │
-       └── Offline needed?
-               ├── YES → Edge required
-               └── NO → Evaluate alternatives
-```
-
-## Node Provisioning
-
-Provision edge nodes based on your workload requirements.
-
-### Provisioning Workflow
-
-```bash
-# Provision edge nodes for a new deployment
-edge-cli node provision \
-  --cluster edge-cluster-01 \
-  --nodes 4 \
-  --role compute \
-  --specs "cpu=4,memory=8Gi,storage=50Gi" \
-  --region us-west-2 \
-  --zone-usability high
-
-# Output:
-# PROVISIONING: 4 nodes
-# CLUSTER: edge-cluster-01
-# REGION: us-west-2
-# SPECS: cpu=4,memory=8Gi,storage=50Gi
-# STATUS: provisioning...
-# NODES:
-#   - edge-node-01: provisioning
-#   - edge-node-02: provisioning
-#   - edge-node-03: provisioning
-#   - edge-node-04: provisioning
-```
-
-### Node Sizing Guide
-
-| Workload Type | CPU | Memory | Storage | Use Case |
-|---------------|-----|--------|---------|----------|
-| Static content | 2 | 4Gi | 20Gi | CDN, assets |
-| API cache | 4 | 8Gi | 50Gi | REST APIs |
-| Compute-heavy | 8 | 16Gi | 100Gi | ML inference |
-| Storage-heavy | 4 | 8Gi | 200Gi | Media storage |
-
-### Automated Provisioning
-
-```yaml
-# infrastructure/edge-nodes.yaml
-provisioning:
-  cluster: edge-cluster-01
-  nodes:
-    - name: edge-node-01
-      role: compute
-      specs:
-        cpu: 4
-        memory: 8Gi
-        storage: 50Gi
-      region: us-west-2
-      zone: us-west-2a
-    - name: edge-node-02
-      role: compute
-      specs:
-        cpu: 4
-        memory: 8Gi
-        storage: 50Gi
-      region: us-west-2
-      zone: us-west-2b
-  networking:
-    vpc: edge-vpc-01
-    subnet: edge-subnet-01
-    security_groups:
-      - edge-sg-compute
-      - edge-sg-monitoring
-```
-
-## Deployment Pipeline
-
-Deploy workloads to the edge using a controlled pipeline.
-
-### Pipeline Stages
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│  Edge Deployment Pipeline                                   │
-│  ┌─────────┐  ┌─────────┐  ┌─────────┐  ┌─────────┐       │
-│  │ Build   │→ │ Test    │→ │ Stage   │→ │ Deploy  │       │
-│  │         │  │         │  │         │  │         │       │
-│  │ Compile │  │ Unit    │  │ Canary  │  │ Rolling │       │
-│  │ Package │  │ Integ.  │  │ Shadow  │  │ Blue/Grn│       │
-│  │ Validate│  │ E2E     │  │ Load    │  │ Fast    │       │
-│  └─────────┘  └─────────┘  └─────────┘  └─────────┘       │
-└─────────────────────────────────────────────────────────────┘
-```
-
-### Pipeline Configuration
-
-```yaml
-# .edge-deploy.yaml
-pipeline:
-  stages:
-    - name: build
-      steps:
-        - edge-cli build --optimize
-        - edge-cli package --minify
-        - edge-cli validate --check-deps
-    
-    - name: test
-      steps:
-        - edge-cli test unit --coverage 80%
-        - edge-cli test integration --timeout 60s
-        - edge-cli test e2e --browser chrome
-    
-    - name: stage
-      steps:
-        - edge-cli deploy --target canary --percentage 10%
-        - edge-cli monitor --duration 300s
-        - edge-cli analyze --error-rate 0.1%
-    
-    - name: deploy
-      strategy: rolling
-      batch_size: 25%
-      pause_on_failure: true
-      rollback_on_error: true
-```
-
-### Deployment Strategies
-
-| Strategy | Speed | Risk | Rollback | Use Case |
-|----------|-------|------|----------|----------|
-| Rolling | Medium | Low | Easy | Default |
-| Blue/Green | Fast | Medium | Fast | Critical |
-| Canary | Slow | Low | Easy | Experimental |
-| Shadow | Medium | Low | None | Validation |
-
-## Adoption Checklist
-
-Use this checklist to ensure successful edge adoption.
-
-### Pre-Adoption
-
-- [ ] Workload meets entry criteria
-- [ ] Latency requirements validated
-- [ ] Data residency compliance verified
-- [ ] Cost-benefit analysis completed
-- [ ] Team training scheduled
-
-### Infrastructure
-
-- [ ] Edge nodes provisioned
-- [ ] Network connectivity established
-- [ ] Security policies configured
-- [ ] Monitoring and alerting set up
-- [ ] Backup and recovery tested
-
-### Deployment
-
-- [ ] Application adapted for edge
-- [ ] Local-first data implemented
-- [ ] Sync strategies configured
-- [ ] Conflict resolution tested
-- [ ] Offline mode validated
-
-### Operations
-
-- [ ] Runbooks created
-- [ ] On-call rotation established
-- [ ] Performance baselines set
-- [ ] Cost tracking enabled
-- [ ] Regular reviews scheduled
-
-### Post-Adoption
-
-- [ ] Performance metrics collected
-- [ ] User feedback gathered
-- [ ] Cost optimization reviewed
-- [ ] Lessons learned documented
-- [ ] Scaling plan prepared
-
-## Migration Timeline
-
-### Week 1-2: Assessment
-
-- Evaluate workloads for edge eligibility
-- Validate latency and data residency requirements
-- Complete cost-benefit analysis
-- Select pilot workload
-
-### Week 3-4: Infrastructure
-
-- Provision edge nodes
-- Configure networking and security
-- Set up monitoring and alerting
-- Test connectivity and failover
-
-### Week 5-6: Application
-
-- Adapt application for edge deployment
-- Implement local-first data patterns
-- Configure sync strategies
-- Test offline capabilities
-
-### Week 7-8: Deployment
-
-- Deploy to canary environment
-- Run load tests and validation
-- Deploy to production (rolling)
-- Monitor and optimize
-
----
-[Back to Edge Computing Profile](./README.md)

package/rulesets/topologies/edge-computing/cli/cli-flows.es.md

@@ -1,41 +0,0 @@
-# Edge Computing — Flujos CLI
-
-> **Navegación Bilingüe:** [English Version](./cli-flows.md)
-
-**Validadores declarados:** `validate-architecture`, `validate-topology`
-
-## Validate
-
-```bash
-evolith validate --topology edge-computing
-evolith validate --topology edge-computing --arch-level F2
-evolith validate --topology edge-computing --format json
-```
-
-## Inspect
-
-```bash
-evolith topology inspect edge-computing
-evolith topology inspect edge-computing --include-targets
-```
-
-## Drift
-
-```bash
-evolith drift detect --topology edge-computing
-evolith drift detect --topology edge-computing --format json
-```
-
-## Scaffold
-
-```bash
-evolith architecture scaffold --topology edge-computing
-evolith architecture scaffold --topology edge-computing --dry-run
-```
-
-## Gate Evaluation
-
-```bash
-evolith gate evaluate --topology edge-computing
-evolith gate evaluate --topology edge-computing --phase F1
-```

package/rulesets/topologies/edge-computing/cli/cli-flows.md

@@ -1,53 +0,0 @@
-# Edge Computing — CLI Flows
-
-> **Bilingual Navigation:** [Versión en Español](./cli-flows.es.md)
-
-**Validators declarados:** `validate-architecture`, `validate-topology`
-
-The following CLI commands are available for the Edge Computing topology.
-
-## Validate
-
-```bash
-evolith validate --topology edge-computing
-evolith validate --topology edge-computing --arch-level F2
-evolith validate --topology edge-computing --format json
-```
-
-Validates an Edge Computing configuration against the topology's native rules (`edge-computing.rules.json`) and OPA Rego policies (`edge-computing.rego`), checking offline resilience, resource limits, and deployment constraints.
-
-## Inspect
-
-```bash
-evolith topology inspect edge-computing
-evolith topology inspect edge-computing --include-targets
-```
-
-Returns the parsed Edge Computing topology manifest, deployment target metadata, and corpus artifact references.
-
-## Drift
-
-```bash
-evolith drift detect --topology edge-computing
-evolith drift detect --topology edge-computing --format json
-```
-
-Detects configuration drift between the Edge Computing topology's declared ruleset and the current workspace state.
-
-## Scaffold
-
-```bash
-evolith architecture scaffold --topology edge-computing
-evolith architecture scaffold --topology edge-computing --dry-run
-```
-
-Scaffolds an Edge Computing topology workspace with the canonical corpus structure, manifest, config schema, and OPA policies.
-
-## Gate Evaluation
-
-```bash
-evolith gate evaluate --topology edge-computing
-evolith gate evaluate --topology edge-computing --phase F1
-```
-
-Evaluates Edge Computing phase gates, validating extraction readiness and deployment boundary integrity.