aw-spec-cli 0.1.7 → 0.1.9

package/assets/guardrails/domain/pharma/idmp.md

@@ -0,0 +1,26 @@
+# ISO IDMP — Identification of Medicinal Products
+
+> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
+
+## Alignment principle
+- The model SHALL align with the ISO IDMP suite (**ISO 11615/11616/11238/11239/11240**) **where applicable** — IDMP shapes the ubiquitous language + aggregate boundaries; it is **not** a wire format and does not replace the internal model (see [[domain-driven-design.domain]]).
+- Even where IDMP messages aren't yet exchanged, preserve the IDMP concept boundaries so future exchange is additive, not a rewrite.
+
+## Required concepts → model home
+| IDMP concept | Model home |
+|---|---|
+| **Medicinal Product** | `MedicinalProduct` aggregate root |
+| **Manufactured Item** | manufactured dose-form item (within the aggregate or a related entity) |
+| **Pharmaceutical Product** | administrable product = `DosageForm` + `Strength` + `RouteOfAdministration` |
+| **Substance** | `Substance` aggregate, UNII-identified (see [[terminology]]); referenced by `ActiveIngredient` |
+| **Marketing Authorization Holder** | `MarketingAuthorizationHolder` → FHIR `Organization` (see [[fhir]]) |
+| **Packaging** | `PackagingConfiguration` (Package NDC, description, quantity, UoM) (see [[ndc]]) |
+| **Strength** | `Strength` VO (numerator/denominator `Quantity`, UCUM) |
+| **Route of Administration** | `RouteOfAdministration` VO (coded) |
+
+## Identifiers & terminology
+- IDMP identifiers (**MPID**, **PhPID**) SHALL be representable as FHIR `Identifier`-shaped VOs when adopted; they coexist with NDC, not replace it (see [[ndc]]).
+- IDMP controlled vocabularies (dose form, route, units, packaging) bind to the Terminology module's code systems, never free text (see [[terminology]], [[atc]]).
+
+## Related
+- [[domain-driven-design.domain]] · [[ndc]] · [[terminology]] · [[atc]] · [[fhir]] · [[pharma-terms]]

package/assets/guardrails/domain/pharma/integration-terms.md

@@ -0,0 +1,21 @@
+# Glossary — Integration Terms (Pharma)
+
+> Ubiquitous language for pharma interoperability standards + identifiers. Commands: `/aw-spec-specify`. See [[pharma-terms]] (aggregates) + [[terminology]] (coding).
+
+| Term | Definition |
+|---|---|
+| **NDC** | US FDA product/package identifier (Labeler + Product + Package); the `NdcCode` VO; format-validated, unique (see [[ndc]]). |
+| **ISO IDMP** | Identification of Medicinal Products (ISO 11615/11616/11238/11239/11240); conceptual alignment; may carry MPID/PhPID (see [[idmp]]). |
+| **UNII** | FDA substance identity for ingredients/moieties; maps to FHIR `Substance.code` (see [[terminology]]). |
+| **RxNorm** | Normalized clinical-drug naming (US); optional product identifier (see [[terminology]]). |
+| **WHO ATC** | Therapeutic class codes; multiple per product, validated against configured sets (see [[atc]]). |
+| **SNOMED CT** | Terminology for dosage forms, routes, product classification (see [[terminology]]). |
+| **UCUM** | Units for strength + package quantity (see [[terminology]]). |
+| **FHIR** | Canonical external contract (R4 default, R5 additive); projects to `Medication`/`MedicationKnowledge`/`Substance`/`Organization` over aggregates (see [[fhir]]). |
+| **HL7** | **HL7 v2.x** legacy messaging via adapters where a consumer needs it; **HL7 FHIR** is the primary contract (see [[hl7]], [[fhir]]). |
+| **Provenance** | Source metadata for externally sourced data; may project to FHIR `Provenance` (see [[data-provenance]]). |
+| **CloudEvents** | CNCF durable async event-stream spec; carries product domain events (see [[eventing.domain]]). |
+| **OpenAPI / CapabilityStatement** | Versioned machine-readable contracts for REST / FHIR (see [[api-versioning.domain]]). |
+
+## Related
+- [[pharma-terms]] · [[terminology]] · [[ndc]] · [[idmp]] · [[atc]] · [[fhir]] · [[hl7]] · [[data-provenance]] · [[eventing.domain]] · [[api-versioning.domain]]

package/assets/guardrails/domain/pharma/ndc.md

@@ -0,0 +1,28 @@
+# NDC — National Drug Code Standards
+
+> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
+
+## Value Object
+- **NDC SHALL be a Value Object** (`NdcCode`) — immutable, equality by value (see [[domain-driven-design.domain]]).
+- Product-level NDC lives on `MedicinalProduct`; package-level (`PackageIdentifier` / Package NDC) on each `PackagingConfiguration`.
+- Free-text storage of an NDC is a Forbidden Pattern.
+
+## Segments & format
+- Three segments: **Labeler Code**, **Product Code**, **Package Code** — retain each segment discretely **plus** the canonical formatted string (boundaries MUST NOT be lost to a concatenated string).
+- Common configurations (5-4-2, 5-3-2, 4-4-2 10-digit + the 11-digit normalized form) SHALL be representable as **data, not compiled constants**.
+- The Labeler Code is FDA-assigned to the **Labeler** organization; the registry does not mint Labeler Codes (see [[domain-requirements]]).
+
+## Uniqueness
+- **NDC uniqueness SHALL be enforced** — a product NDC maps to <=1 active `MedicinalProduct`; a Package NDC to <=1 `PackagingConfiguration`.
+- Duplicate detection runs at registration + any identifier change; enforced at the aggregate boundary **and** a persistence-level unique constraint (see [[persistence.domain]], [[auditing.domain]]).
+
+## Validation
+- **NDC validation rules SHALL be configurable** (segment lengths, allowed configurations, check rules = value-set data).
+- Runs on registration, identifier change, and external import (see [[data-provenance]]); an invalid NDC raises a domain error — the Domain MUST NOT persist it.
+- Never invent NDC values or Labeler Codes — validate external codes against the configured rules + FDA NDC directory via the Terminology module (see [[terminology]], [[ai-rules.domain]]).
+
+## FHIR mapping
+- `NdcCode` → FHIR `Identifier` (NDC system URI); also participates in `Medication.code` as a `CodeableConcept` coding (see [[fhir]]).
+
+## Related
+- [[domain-driven-design.domain]] · [[idmp]] · [[terminology]] · [[fhir]] · [[data-provenance]] · [[persistence.domain]] · [[auditing.domain]] · [[ai-rules.domain]]

package/assets/guardrails/domain/pharma/persistence.domain.md

@@ -0,0 +1,23 @@
+# Persistence — Pharma Domain Addenda
+
+> Technology base: [[persistence]]. NON-NEGOTIABLE. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
+
+## Version history
+- Maintain a **version history** of product information: each approved change produces a new, immutable **`ProductVersion`** snapshot.
+- **Historical versions remain queryable** — a read model exposes prior versions by product + effective time; superseded versions are never overwritten or purged. Snapshots complement audit (who/what/when; see [[auditing.domain]]) and provenance (source; see [[data-provenance]]).
+
+## Retention-protected data
+- Hard delete FORBIDDEN for `MedicinalProduct` and all product history — delete logically via `MarkAsDeleted(...)` / lifecycle retirement.
+- **Product retirement** (Discontinued/Withdrawn) is a state change, not a delete (see [[product-lifecycle.domain]]).
+- `AuditRecord` is **append-only** — no delete (see [[auditing.domain]]).
+- Retention: registry + version history per regulatory policy (registration lifetime + statutory tail); `AuditRecord` per [[auditing.domain]]; daily encrypted backups.
+
+## Constraints & concurrency
+- Persistence-level **unique constraints** on NDC and Package NDC, beyond the aggregate check (see [[ndc]], [[domain-driven-design.domain]]).
+- Optimistic concurrency token → FHIR **weak** ETag at the projection boundary (see [[fhir]]).
+
+## Dev data
+- Fixtures use synthetic data + **synthetic/clearly-marked test NDCs** — never real identifiers that could collide with the FDA NDC directory (see [[ndc]], [[testing.domain]]).
+
+## Related
+- [[persistence]] · [[auditing.domain]] · [[data-provenance]] · [[product-lifecycle.domain]] · [[ndc]] · [[fhir]] · [[domain-driven-design.domain]] · [[testing.domain]]

package/assets/guardrails/domain/pharma/pharma-terms.md

@@ -0,0 +1,27 @@
+# Glossary — Pharmaceutical Terms
+
+> Ubiquitous language for the medicinal product registry. Commands: `/aw-spec-constitution`, `/aw-spec-specify`. See [[domain-driven-design.domain]] (modeling), [[terminology]] (coding), [[integration-terms]] (interop).
+
+| Term | Definition |
+|---|---|
+| **MedicinalProduct** | The **Aggregate Root** — authoritative record of a registered medicine (ProductRegistry); owns ingredients, packaging, marketing authorization; aligned to IDMP *Medicinal Product* (see [[idmp]], [[domain-driven-design.domain]]). |
+| **NDC** | US FDA product identifier (Labeler + Product + Package); the `NdcCode` VO; unique, format-validated (see [[ndc]]). |
+| **PackageIdentifier** | Package-level NDC on a `PackagingConfiguration` (see [[ndc]]). |
+| **ActiveIngredient** | **Entity**: Name, UNII, Strength, Strength Unit; **>= 1** per product (see [[domain-driven-design.domain]]). |
+| **Substance / ActiveMoiety** | Chemical substance + active moiety; UNII-identified (see [[terminology]]); FHIR `Substance`. |
+| **Strength** | Active-ingredient amount per dose unit — `Strength` VO (numerator/denominator `Quantity`, UCUM) (see [[terminology]]). |
+| **DosageForm** | Physical form (tablet/capsule/solution); coded (SNOMED CT); `DosageForm` VO (see [[terminology]]). |
+| **RouteOfAdministration** | Administration path (oral/IV/topical); coded; `RouteOfAdministration` VO (see [[terminology]]). |
+| **AtcCode** | WHO ATC class code; **multiple per product**; validated against configured sets (see [[atc]]). |
+| **MarketingStatus** | Regulatory marketing state (`MarketingStatus` VO); distinct from lifecycle state (see [[product-lifecycle.domain]]). |
+| **MarketingAuthorization** | **Entity** — authorization granted by a regulator; IDMP-aligned (see [[idmp]]). |
+| **MarketingAuthorizationHolder (MAH)** | Organization holding the authorization; FHIR `Organization`. |
+| **Labeler** | Firm whose Labeler Code forms the first NDC segment (see [[ndc]]). |
+| **PackagingConfiguration** | **Entity**: Package NDC, Description, Quantity, Unit of Measure; **>= 1** per product (see [[domain-driven-design.domain]]). |
+| **ManufacturedItem / PharmaceuticalProduct** | IDMP concepts: manufactured dose-form item + administrable product (see [[idmp]]). |
+| **ProvenanceRecord** | Provenance for externally sourced data (source, method, timestamp, agent) (see [[data-provenance]]). |
+| **AuditRecord** | Append-only audit entry for create/modify/retire/identifier/classification changes (see [[auditing.domain]]). |
+| **ProductVersion** | Queryable historical snapshot of product information (see [[persistence.domain]]). |
+
+## Related
+- [[domain-driven-design.domain]] · [[idmp]] · [[ndc]] · [[atc]] · [[terminology]] · [[fhir]] · [[integration-terms]] · [[product-lifecycle.domain]] · [[data-provenance]]

package/assets/guardrails/domain/pharma/product-lifecycle.domain.md

@@ -0,0 +1,30 @@
+# Product Lifecycle — Medicinal Product State Machine
+
+> Technology base: [[domain-driven-design]]. NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
+
+## States
+`Draft` → `Under Review` → `Approved` → `Active` → `Discontinued` / `Withdrawn`
+- Lifecycle state is owned by the aggregate root and is distinct from the `MarketingStatus` value object, though the two MUST stay consistent (see [[domain-driven-design.domain]]).
+
+## Valid transitions (guarded; any other rejected as `lifecycle.invalid_transition`)
+| From | Allowed to |
+|---|---|
+| Draft | Under Review |
+| Under Review | Approved, Draft (returned for correction) |
+| Approved | Active |
+| Active | Discontinued, Withdrawn |
+| Discontinued | Withdrawn |
+| Withdrawn | *(terminal)* |
+
+The allowed set MAY be configurable policy, but the default above is enforced; no transition bypasses the guard.
+
+## Guards
+- Leaving **Draft** requires registration completeness (all required attributes, >= 1 ingredient, >= 1 packaging, valid NDC/dosage form/route/ATC) (see [[domain-driven-design.domain]], [[ndc]], [[terminology]], [[atc]]).
+- Approve/activate/retire are **authorized** actions — only `RegulatoryOfficer` (see [[authorization.domain]]).
+- Retirement is a **logical** state change, never a hard delete (see [[persistence.domain]], [[auditing.domain]]).
+
+## Events
+Each transition emits a domain event (`MedicinalProductSubmittedForReview`/`Approved`/`Activated`/`Discontinued`/`Withdrawn`) and is audit-mandatory (see [[eventing.domain]], [[auditing.domain]]).
+
+## Related
+- [[domain-driven-design.domain]] · [[authorization.domain]] · [[ndc]] · [[terminology]] · [[atc]] · [[eventing.domain]] · [[auditing.domain]] · [[persistence.domain]]

package/assets/guardrails/domain/pharma/regulatory-compliance.md

@@ -0,0 +1,19 @@
+# Regulatory & Compliance Standards — Pharma
+
+> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
+
+> Umbrella for the compliance requirements — mechanisms live in the linked files.
+
+## Posture
+- Built for **regulatory compliance readiness** — auditability, traceability, data integrity, provenance designed in.
+- GxP-relevant records follow **ALCOA+** (Attributable, Legible, Contemporaneous, Original, Accurate + Complete, Consistent, Enduring, Available).
+
+## Requirements
+- **Audit trail** — immutable records for product creation, modification, retirement, identifier changes, classification changes; each carries User, Timestamp, Action, Previous Value, New Value (see [[auditing.domain]]).
+- **Provenance** — capture source/method/agent/timestamp for externally sourced data (see [[data-provenance]]).
+- **Versioning** — full, queryable version history of product information (see [[persistence.domain]]).
+- **Traceability** — every change to identifiers (NDC), classification (ATC), ingredients, packaging, marketing status, lifecycle is traceable command → event → audit record → version snapshot (see [[eventing.domain]], [[auditing.domain]], [[persistence.domain]]).
+- **Authorized actions** — registration, approval, retirement are authorized operations (see [[authorization.domain]], [[product-lifecycle.domain]]).
+
+## Related
+- [[auditing.domain]] · [[data-provenance]] · [[persistence.domain]] · [[eventing.domain]] · [[product-lifecycle.domain]] · [[authorization.domain]] · [[domain-driven-design.domain]]

package/assets/guardrails/domain/pharma/terminology.md

@@ -0,0 +1,32 @@
+# Terminology Standards — Pharma
+
+> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
+
+## Coded value objects
+- **Coded data MUST use industry terminologies — free-text strings for coded concepts are FORBIDDEN.**
+- Every code-bearing field is a **`Codeable` value object** `{ system, code, version, display }` (mirrors FHIR `CodeableConcept`/`Coding`; see [[fhir]]).
+
+## Standard terminologies
+| Concept | Terminology | Conformance |
+|---|---|---|
+| Product / package identity | **NDC** | SHALL (see [[ndc]]) |
+| Substances / active ingredients | **UNII** | SHOULD |
+| Substance / clinical drug | **RxNorm** | SHOULD |
+| Dosage form / route / classification | **SNOMED CT** | SHOULD |
+| Therapeutic classification | **WHO ATC** | SHALL (see [[atc]]) |
+| Units (strength, package qty) | **UCUM** | SHALL |
+
+- **UNII** is the substance identity for IDMP `Substance` alignment (see [[idmp]]) and maps to FHIR `Substance.code`.
+
+## Validation
+- Hard-coded coded literals FORBIDDEN outside the Terminology module's seed data.
+- Never invent NDC/UNII/RxNorm/SNOMED/ATC/UCUM codes — confirm against value sets (see [[ai-rules.domain]]).
+- Invalid dosage forms/routes rejected at validation time; the bound value set is configuration (see [[domain-driven-design.domain]]).
+
+## Terminology module
+- Lookup/validation/expansion **MUST** go through a dedicated **Terminology module** (internal cache or external TS via FHIR `$expand` / `$validate-code`).
+- Aggregates: `CodeSystem`, `ValueSet`, `ConceptMap` (subsets; expansions cached from RxNorm/SNOMED/FDA UNII-NDC/WHO ATC).
+- Code-set versions are pinned + recorded; a terminology release (e.g. WHO ATC annual update) is a tracked, audited change (see [[auditing.domain]]).
+
+## Related
+- [[ndc]] · [[atc]] · [[idmp]] · [[fhir]] · [[domain-driven-design.domain]] · [[testing.domain]] · [[ai-rules.domain]]

package/assets/guardrails/domain/pharma/testing.domain.md

@@ -0,0 +1,19 @@
+# Testing — Pharma Domain Addenda
+
+> Technology base: [[testing]]. Commands: `/aw-spec-gate`.
+
+## What MUST be tested
+- **Aggregate invariants** — required attributes; >= 1 ActiveIngredient; >= 1 PackagingConfiguration; NDC uniqueness + format; invalid dosage forms/routes rejected (see [[domain-driven-design.domain]], [[ndc]], [[terminology]]).
+- **Lifecycle state machine** — every allowed transition passes; every disallowed one is rejected (see [[product-lifecycle.domain]]).
+- **NDC validation** — segment configurations, configurable rules, duplicate detection (see [[ndc]]).
+- **Terminology binding** — ATC/UNII/SNOMED/RxNorm/UCUM validated against value sets; invented codes rejected (see [[terminology]], [[atc]]).
+- **FHIR round-trip** — `domain -> FHIR -> domain` for Medication/MedicationKnowledge/Substance/Organization; FHIR validator passes (CI gate; see [[fhir]]).
+- **Audit & versioning** — every audited op writes an immutable record (User/Timestamp/Action/Previous/New); historical versions remain queryable (see [[auditing.domain]], [[persistence.domain]]).
+- **Provenance** — external imports attach a `ProvenanceRecord` (see [[data-provenance]]).
+
+## Test data & gates
+- Use **synthetic/clearly-marked test NDCs and codes** — never real identifiers that could collide with the FDA NDC directory (see [[persistence.domain]], [[ndc]]); pin the terminology code-set version under test (see [[terminology]]).
+- CI: FHIR validator passes for every modified resource/profile/example; HL7 outbound conformance checked against the internal corpus (see [[hl7]]).
+
+## Related
+- [[testing]] · [[domain-driven-design.domain]] · [[product-lifecycle.domain]] · [[ndc]] · [[terminology]] · [[atc]] · [[fhir]] · [[auditing.domain]] · [[persistence.domain]] · [[data-provenance]] · [[hl7]]

package/assets/guardrails/domain/pharma/vertical-slices.domain.md

@@ -0,0 +1,17 @@
+# Vertical Slices — Pharma Domain Addenda
+
+> Technology base: [[vertical-slices]]. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
+
+## Interop adapters in the slice
+`{Module}/Interop/` carries the pharma external-protocol adapters:
+```
+Fhir/    Medication / MedicationKnowledge / Substance / Organization projectors   (see [[fhir]])
+Hl7v2/   inbound parsers + outbound emitters (added when a consumer needs them)   (see [[hl7]])
+```
+
+## Rules
+- FHIR resources live in a **parallel projection layer** and **MUST NOT** replace internal `Shared` DTOs; projections, never the system of record (see [[fhir]], [[domain-driven-design.domain]]).
+- Domain DTOs (`MedicinalProductDto`, `ActiveIngredientDto`, `PackagingConfigurationDto`) — no setters, required `init`, base64 `RowVersionBase64` (see [[coding-standards.domain]]).
+
+## Related
+- [[vertical-slices]] · [[fhir]] · [[hl7]] · [[domain-driven-design.domain]] · [[coding-standards.domain]]

package/assets/guardrails/domain/pharma/zero-trust.domain.md

@@ -0,0 +1,12 @@
+# Zero-Trust — Pharma Domain Addenda
+
+> Technology base: [[zero-trust]]. Commands: `/aw-spec-constitution`, `/aw-spec-specify`, `/aw-spec-gate`.
+
+## Rules
+- All registry traffic MUST be TLS-encrypted; commercially-sensitive pre-market data in transit MUST be TLS-protected; at-rest: see [[data-classification.domain]], [[persistence.domain]].
+- FHIR/REST scopes (`system/Medication.read`, `system/*.write` for authorized backends) enforced on every endpoint + propagated through the pipeline. **No patient-context (SMART) launch** — product master data (see [[authorization.domain]], [[fhir]]).
+- Mutating operations **re-check change authority** at the handler edge (only `RegulatoryOfficer` approves/retires; identifier/classification changes are privileged) (see [[authorization.domain]]).
+- Trace context MUST propagate across outbound **FHIR / HL7v2** calls and the CloudEvents stream (see [[eventing.domain]], [[auditing.domain]]).
+
+## Related
+- [[zero-trust]] · [[authorization.domain]] · [[data-classification.domain]] · [[persistence.domain]] · [[auditing.domain]] · [[eventing.domain]] · [[fhir]]

package/assets/guardrails/projects/dotnet-default-project/domain/domain-requirements.md

@@ -0,0 +1,58 @@
+# DOMAIN REQUIREMENTS (project-specific)
+
+> Project-specific input, **authored by the project owner** and updated independently per
+> project. It is the last file in the set mapped under `## /aw-spec-constitution` in
+> `domain-rule-bindings.md`, and the only one there expected to differ between two projects on this
+> corpus; the standard industry rules beside it are shared. Its mapping is optional — a project
+> that has not authored it yet ratifies the standard set alone.
+>
+> This file holds the per-project enumeration and headline profiles. Detailed domain *rules*
+> are expanded in the sibling files in this folder.
+>
+> Replace `<SampleProjectName>` and the bounded-context list below for a new project.
+
+=====================================================================
+[DOMAIN: Bounded Contexts / Modules]
+=====================================================================
+- Patients — aggregates: Patient (master patient index), Consent, RelatedPerson; cross-references via PIX/PDQ.
+- Appointments — aggregates: Appointment, Slot, Schedule, Waitlist.
+- Encounters — aggregates: Encounter (inpatient, outpatient, emergency), Admission, Transfer, Discharge.
+- EMR — aggregates: ClinicalNote, ProblemList, AllergyIntolerance, MedicationStatement, Observation (vitals, social history), Immunization, CarePlan, ServiceRequest, Procedure.
+- Radiology — aggregates: ImagingOrder, ImagingStudy (DICOM metadata), DiagnosticReport (radiology); pixel data lives in PACS/VNA.
+- Lab — aggregates: LabOrder, Specimen, Observation (lab result), DiagnosticReport (lab).
+- Pharmacy — aggregates: MedicationRequest, MedicationDispense, MedicationAdministration, Formulary, ControlledSubstanceLedger.
+- Billing — aggregates: ChargeItem, Invoice, Claim, ClaimResponse, PaymentReconciliation, Account, AdjustmentEntry.
+- Insurance — aggregates: Coverage, Payer, Plan, EligibilityRequest, EligibilityResponse, PriorAuth.
+- Inventory — aggregates: InventoryItem, Lot, StockMovement, Reservation, ExpiryAlert.
+- Interoperability — aggregates: IntegrationEndpoint, MessageEnvelope (HL7v2), FhirSubscription, BulkExportJob.
+- PatientPortal — aggregates: PortalAccount (identity-bound), MessageThread, AppointmentRequest, RecordAccessRequest.
+- Identity — aggregates: Practitioner, PractitionerRole, Organization, Location, HealthcareService.
+- Auditing — aggregates: AuditRecord (append-only, ATNA + FHIR AuditEvent shape).
+- Terminology — aggregates: CodeSystem, ValueSet, ConceptMap (project-managed subsets; expansions cached from external TS).
+
+=====================================================================
+[DOMAIN: subsection pointers]
+=====================================================================
+[DOMAIN: Aggregates and Business Invariants]  -> guardrails/domain/healthcare/domain-driven-design.domain.md
+[DOMAIN: Persistence Profile]                 -> guardrails/domain/healthcare/persistence.domain.md
+[DOMAIN: Security Profile]                     -> guardrails/domain/healthcare/authorization.domain.md, guardrails/domain/healthcare/data-classification.domain.md
+[DOMAIN: Testing Profile]                      -> guardrails/domain/healthcare/testing.domain.md
+[DOMAIN: AI Policy Addenda]                    -> guardrails/domain/healthcare/ai-rules.domain.md
+[DOMAIN: Platform Topology]                    -> below
+
+=====================================================================
+[DOMAIN: Platform Topology]
+=====================================================================
+- Target runtime: Kubernetes (AKS, EKS, or on-prem). Single-region by default; multi-region active/passive for DR.
+- External dependencies (Aspire resources): PostgreSQL (primary), Redis (cache + portal session), a message broker (Azure Service Bus, AWS SQS/SNS, or RabbitMQ) for CloudEvents, an OTel collector, the configured IdP, an external Terminology Service (optional), a FHIR validator container, a PACS/VNA endpoint (DICOMweb), an HL7v2 broker (MLLP), an SMTP/SMS gateway, an object store (S3/Blob) for binaries.
+- Scale targets: P95 read latency < 200 ms at 200 RPS per module; FHIR search P95 < 500 ms; HL7v2 ingest sustains 50 messages/sec per channel.
+- Disaster recovery: RPO <= 15 minutes, RTO <= 4 hours; daily encrypted backups with 35-day retention plus monthly archive >= 7 years.
+
+=====================================================================
+[DOMAIN: Governance Overrides]
+=====================================================================
+- Principal Engineers (approvers): TBD — fill at ratification.
+- Security/Compliance Officer (mandatory approver for any PHI/security change): TBD.
+- Domain Owners (per module): TBD — assign one clinical and one technical owner per bounded context.
+- Quarterly review cadence: first business week of each quarter; security review additionally after every significant regulatory update.
+- Exception process: a time-boxed waiver via a Waiver Request issue, approved by a Principal Engineer + the Compliance Officer, with a mandatory expiry <= 90 days and a remediation plan recorded in the issue.

package/assets/guardrails/projects/dotnet-default-project/domain-rule-bindings.md

@@ -0,0 +1,113 @@
+# dotnet-default-project — Command → Domain-Rule-File Map
+
+Per-command list of the **domain** rule files this project loads (via `resolve-domain`
++ the `domain-select` module, into the sticky standards set) for the spec-anchored
+orchestrator pipeline. This project draws its domain from the **healthcare** corpus.
+
+**The model:** domain files feed
+only three consumers — **specify** (authors them into the spec as FR/BR/CN-/DC-/IC-),
+**constitution** (the domain principles), and the **gates** (conformance checklist).
+**design** and **implement** load **NO** domain file — the domain reaches them solely
+through the spec/design (as CN-/DC-/IC- ids).
+
+- All paths are workspace-relative. The **standard industry rules** live in
+  `guardrails/domain/healthcare/` — shared, reusable by every project that maps them. The
+  one file this project authors, `domain/domain-requirements.md`, lives beside this map.
+- A mapped file that does not exist is skipped rather than failing the run, so a project
+  that has not authored its `domain-requirements.md` yet still gets the standard set.
+- `resolve-domain --command <name>` collects the `- ` bullets under `## /<name>`.
+- To govern a different industry, repoint these bullets at another
+  `guardrails/domain/<industry>/` corpus — `guardrails/domain/pharma/` also ships. Nothing
+  else changes: the technical map, the workflows and the engine are untouched.
+- This file is the **canonical domain mapping** for this project; `/appweaver
+  select-domain` selects this project folder as active.
+
+---
+
+## /aw-spec-constitution
+<!-- What the DOMAIN half ratifies into constitution.domain.md as domain principles XVI+.
+     The industry constitution first, then the STANDARD industry rules — identity,
+     regulatory, interop, security overlays — which every project on this corpus shares, and
+     LAST the PROJECT-SUPPLIED domain-requirements.md the project team authors. Only that
+     last file is expected to differ between two projects on the same corpus, and its mapping is
+     OPTIONAL: the project owner supplies the file, and where it is absent the set loads
+     without it rather than failing. -->
+- guardrails/domain/healthcare/domain-constitution.md
+- guardrails/domain/healthcare/clinical-terms.md
+- guardrails/domain/healthcare/terminology.md
+- guardrails/domain/healthcare/consent.md
+- guardrails/domain/healthcare/hipaa.md
+- guardrails/domain/healthcare/fhir.md
+- guardrails/domain/healthcare/hl7.md
+- guardrails/domain/healthcare/dicom.md
+- guardrails/domain/healthcare/data-classification.domain.md
+- guardrails/domain/healthcare/auditing.domain.md
+- guardrails/domain/healthcare/authorization.domain.md
+- guardrails/domain/healthcare/zero-trust.domain.md
+- guardrails/domain/healthcare/ai-rules.domain.md
+- guardrails/projects/dotnet-default-project/domain/domain-requirements.md
+
+## /aw-spec-specify
+<!-- The FULL domain set. Specify models the domain COMPLETELY and LIFTS the constraint
+     overlays into the spec's CN-/DC-/IC- sections (design/implement never see these files). -->
+- guardrails/projects/dotnet-default-project/domain/domain-requirements.md
+- guardrails/domain/healthcare/domain-driven-design.domain.md
+- guardrails/domain/healthcare/clinical-terms.md
+- guardrails/domain/healthcare/terminology.md
+- guardrails/domain/healthcare/integration-terms.md
+- guardrails/domain/healthcare/consent.md
+- guardrails/domain/healthcare/hipaa.md
+- guardrails/domain/healthcare/fhir.md
+- guardrails/domain/healthcare/hl7.md
+- guardrails/domain/healthcare/dicom.md
+- guardrails/domain/healthcare/data-classification.domain.md
+- guardrails/domain/healthcare/persistence.domain.md
+- guardrails/domain/healthcare/cqrs.domain.md
+- guardrails/domain/healthcare/eventing.domain.md
+- guardrails/domain/healthcare/auditing.domain.md
+- guardrails/domain/healthcare/authorization.domain.md
+- guardrails/domain/healthcare/zero-trust.domain.md
+- guardrails/domain/healthcare/api-versioning.domain.md
+- guardrails/domain/healthcare/vertical-slices.domain.md
+
+## /aw-spec-design
+_None — design loads no domain file. Domain reaches design only through the spec (BR-/CN-/DC-/IC-)._
+
+## /aw-spec-implement
+_None — implement loads no domain file. Domain reaches implement only through design.md. Framework
+components are added separately via `/appweaver add-component`._
+
+## /aw-spec-gate
+<!-- Conformance checklist for the gates (analyze-design · analyze-slice): the domain-derived
+     constraints design/implement were NOT given as authoring input, VALIDATED against the
+     output. Domain re-enters here as a check, never as authoring input. -->
+- guardrails/domain/healthcare/persistence.domain.md
+- guardrails/domain/healthcare/cqrs.domain.md
+- guardrails/domain/healthcare/eventing.domain.md
+- guardrails/domain/healthcare/auditing.domain.md
+- guardrails/domain/healthcare/authorization.domain.md
+- guardrails/domain/healthcare/zero-trust.domain.md
+- guardrails/domain/healthcare/data-classification.domain.md
+- guardrails/domain/healthcare/api-versioning.domain.md
+- guardrails/domain/healthcare/vertical-slices.domain.md
+- guardrails/domain/healthcare/folder-structure.domain.md
+- guardrails/domain/healthcare/coding-standards.domain.md
+- guardrails/domain/healthcare/dependency-policy.domain.md
+- guardrails/domain/healthcare/testing.domain.md
+- guardrails/domain/healthcare/ai-rules.domain.md
+
+---
+
+## Quick reference (command → domain file count)
+
+| Command | Domain rule files | Role |
+|---|---|---|
+| /aw-spec-constitution | 14 | domain principles (XVI+) — the industry constitution + standard industry rules + the project's own requirements |
+| /aw-spec-specify | 19 | author into spec (lift → CN-/DC-/IC-) |
+| /aw-spec-design | 0 | none — spec is the only domain input |
+| /aw-spec-implement | 0 | none — design is the only domain input |
+| /aw-spec-gate | 14 | conformance checklist (validate, don't author) |
+
+> Retired in the orchestrator pipeline: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-taskplan`,
+> `/aw-spec-clarify`, `/aw-spec-analyze` (clarify folds into specify; plan/tasks into design). The
+> collapsed tiers `/aw-spec-fast-implement` and `/aw-spec-minimal-implementation` are pending a ruling.

package/assets/guardrails/projects/dotnet-default-project/frontend/ui-requirements.md

@@ -0,0 +1,43 @@
+# UI Requirements — project-supplied
+
+> **This file is authored by the project team, not by the corpus.**
+> `guardrails/technology/nextjs/ui-constitution.md` is the standard frontend rule set for that
+> stack, reusable by every project that maps it. This file is where one project's own experience
+> decisions go.
+
+It is mapped under `## /aw-spec-ui-constitution` in `tech-rule-bindings.md`, so its
+content is ratified into `constitution.ui.md` alongside the standard rules.
+
+Keep it **domain-free**, exactly like the standard set: regulatory and terminology rules
+belong to `domain-constitution.md`, and reach the UI lane through the spec.
+
+## Declared Lane
+
+<!-- The lane id, its stack and the root it owns. Must match .appweaver/stacks.json where that
+     file exists — STACK-MISMATCH: is the failure, not a silent rewrite. -->
+
+## Design System
+
+<!-- Which design system and token set this project adopts, its version, and who may change
+     it. UX-II makes it the only source of visual truth; this says WHICH one. -->
+
+## Conformance Target
+
+<!-- The accessibility conformance level this project commits to, and the waiver authority.
+     UX-I makes it non-negotiable; this names the level. -->
+
+## Performance Budget
+
+<!-- Core Web Vitals thresholds and the per-route JavaScript budget CI enforces. UX-IX makes
+     the budget a gate; this sets the numbers. -->
+
+## Deviations from the Standard Rules
+
+<!-- Each deviation: which UX-* principle, what this project does instead, why, and who
+     approved it. Empty is the expected state for a new project. -->
+
+## Ratification Metadata
+
+- **Version:** 0.1.0
+- **Ratified:** `<YYYY-MM-DD>`
+- **Last Amended:** `<YYYY-MM-DD>`

package/assets/guardrails/projects/dotnet-default-project/service/technical-requirements.md

@@ -0,0 +1,40 @@
+# Technical Requirements — project-supplied
+
+> **This file is authored by the project team, not by the corpus.** The rules this project's
+> technical map lists live in `guardrails/technology/dotnet-webapi/` — the standard set for that
+> stack, reusable by every project that maps it. This file is where one project's own technology
+> decisions go, and it is the only technical file a second project on the same stack replaces.
+
+It is mapped under `## /aw-spec-constitution` in `tech-rule-bindings.md`, so its content
+is ratified into `constitution.technical.md` alongside the standard rules — which is what
+lets a project's own constraints become governed principles rather than folklore.
+
+Where this file is silent, the standard rules govern unchanged. Where it adds a constraint,
+say which standard rule it extends, so the ratified principle can cite both.
+
+## Project Identity
+
+<!-- Project name, mission, the bounded contexts it owns, and its deployment posture. -->
+
+## Technology Decisions
+
+<!-- The choices this project has made WITHIN the standard rules: target framework version,
+     database engine and hosting, messaging broker, identity provider, cloud target. State
+     the decision, not the tutorial. -->
+
+## Deviations from the Standard Rules
+
+<!-- Each deviation: which standard rule, what this project does instead, why, and who
+     approved it. A deviation with no approver is a defect, not a decision. Empty is the
+     expected state for a new project. -->
+
+## Project-Specific Constraints
+
+<!-- Performance budgets, availability targets, data residency, integration deadlines, or
+     anything else that must become a governed principle for THIS project. -->
+
+## Ratification Metadata
+
+- **Version:** 0.1.0
+- **Ratified:** `<YYYY-MM-DD>`
+- **Last Amended:** `<YYYY-MM-DD>`