guardian-framework 0.1.105 → 0.1.110

package/templates/pi/skills/rust-enterprise-codegen.md

@@ -1021,3 +1021,49 @@ live-tests = []  # Flag for tests that hit real APIs
 *Version: 1.0.0*
 *Last updated: 2026-07-03*
 *Source: Guardian DDD patterns + context7 DDD reference (/jkazama/ddd-java, /ardalis/cleanarchitecture)*
+
+## Judgment Tables (ADR-008)
+
+Compact decision tables distilled from professional OOP/DDD practice (token-lean;
+the full rationale lives in the curriculum, not here).
+
+### Entity vs Value Object
+| Question | Entity | Value Object |
+|----------|--------|--------------|
+| Identity persists across state changes? | yes | no |
+| Change = mutate in place? | yes | replace entirely |
+| Equality by identity or by attributes? | identity | all attributes |
+| Immutable by nature? | no | yes |
+| Track change history? | yes | no |
+
+### Aggregate Boundaries
+- An aggregate is a **consistency boundary**, not a data grouping.
+- One aggregate modified per transaction; everything else via events.
+- Reference other aggregates **by identity**, never by object graph.
+- Design **small** aggregates; the root is the only entry point — behavior methods, no setters.
+
+### Service Classifier
+| Service | Layer | Contains | Named by |
+|---------|-------|----------|----------|
+| Domain service | domain/ | business process spanning entities | ubiquitous language |
+| Application service | application/ | use-case orchestration (thin) | technical intent |
+| Infrastructure service | infrastructure/ | technical impl (persistence, http, events) | implementation |
+| Persistence port (interface) | domain/ | aggregate persistence contract | aggregate language |
+| Persistence adapter | infrastructure/ | framework impl (ORM/DB) | — |
+
+### Event Triage (3 questions)
+Keep a candidate event only if ≥1 is true: (1) would a domain expert care?
+(2) does it cross an aggregate boundary? (3) do we need an audit trail?
+Otherwise it is an implementation detail. Publish from the aggregate;
+dispatch **after** save from the application service.
+
+### Transaction & Persistence Placement
+| Concern | Location | Why |
+|---------|----------|-----|
+| Transaction handle scope | application service only | one aggregate per transaction |
+| Repository trait | domain/ (crate) | dependency inversion |
+| Repository impl (sqlx/diesel) | infrastructure/ | framework out of domain |
+| Value object | domain/ (struct/type, immutable) | replace, don't mutate |
+| HTTP (axum/actix) | interfaces/ | web out of domain |
+
+*Distilled 2026-09-03 from professional OOP/DDD curriculum (Modules 0–6) — ADR-008/009.*

package/templates/pi/skills/typescript-enterprise-codegen.md

@@ -431,3 +431,49 @@ tsconfig.json
 *Version: 1.0.0*
 *Last updated: 2026-07-03*
 *Source: Guardian DDD patterns + TypeScript best practices + context7 (/microsoft/typescript)*
+
+## Judgment Tables (ADR-008)
+
+Compact decision tables distilled from professional OOP/DDD practice (token-lean;
+the full rationale lives in the curriculum, not here).
+
+### Entity vs Value Object
+| Question | Entity | Value Object |
+|----------|--------|--------------|
+| Identity persists across state changes? | yes | no |
+| Change = mutate in place? | yes | replace entirely |
+| Equality by identity or by attributes? | identity | all attributes |
+| Immutable by nature? | no | yes |
+| Track change history? | yes | no |
+
+### Aggregate Boundaries
+- An aggregate is a **consistency boundary**, not a data grouping.
+- One aggregate modified per transaction; everything else via events.
+- Reference other aggregates **by identity**, never by object graph.
+- Design **small** aggregates; the root is the only entry point — behavior methods, no setters.
+
+### Service Classifier
+| Service | Layer | Contains | Named by |
+|---------|-------|----------|----------|
+| Domain service | domain/ | business process spanning entities | ubiquitous language |
+| Application service | application/ | use-case orchestration (thin) | technical intent |
+| Infrastructure service | infrastructure/ | technical impl (persistence, http, events) | implementation |
+| Persistence port (interface) | domain/ | aggregate persistence contract | aggregate language |
+| Persistence adapter | infrastructure/ | framework impl (ORM/DB) | — |
+
+### Event Triage (3 questions)
+Keep a candidate event only if ≥1 is true: (1) would a domain expert care?
+(2) does it cross an aggregate boundary? (3) do we need an audit trail?
+Otherwise it is an implementation detail. Publish from the aggregate;
+dispatch **after** save from the application service.
+
+### Transaction & Persistence Placement
+| Concern | Location | Why |
+|---------|----------|-----|
+| Unit of Work / transaction scope | application service only | one aggregate per transaction |
+| Repository interface | domain/ (interfaces/port) | dependency inversion |
+| Repository impl (TypeORM/Prisma) | infrastructure/ | framework out of domain |
+| Value object | domain/ (class/record, immutable) | replace, don't mutate |
+| DI wiring | composition root (infrastructure) | explicit assembly |
+
+*Distilled 2026-09-03 from professional OOP/DDD curriculum (Modules 0–6) — ADR-008/009.*