aw-spec-cli 0.1.5 → 0.1.7

package/assets/docs/domainspecs/pharma/fhir.md

@@ -1,31 +0,0 @@
-# FHIR Standards — Pharma
-
-> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
-
-## Architecture & projectors
-- **R4 default**; R5 **additive** under `/fhir/R5/...`. FHIR is the canonical interop contract; it + any internal REST serve from the **same authoritative aggregates** — no duplicate write paths.
-- **FHIR resources are PROJECTIONS, NOT the system of record** — `MedicinalProduct` is authoritative (see [[domain-driven-design.domain]]).
-- Mapping in `{Module}/Interop/Fhir/<Resource>Projector.cs`, hand-written + round-trip tested (see [[testing.domain]]). A second FHIR write path bypassing the aggregate is FORBIDDEN; FHIR representations MUST NOT replace internal DTOs.
-
-## Resource mappings
-| Domain concept | FHIR resource |
-|---|---|
-| `MedicinalProduct` (dispensable identity) | **Medication** |
-| `MedicinalProduct` (classification/packaging/regulatory) | **MedicationKnowledge** |
-| `Substance` / `ActiveIngredient` | **Substance** |
-| `MarketingAuthorizationHolder` / `Manufacturer` / `Labeler` | **Organization** |
-
-- Identifiers → FHIR `Identifier` (`NdcCode` with NDC system URI; IDMP MPID/PhPID where adopted; see [[ndc]], [[idmp]]).
-- Names → `Medication.code` + name elements; coded fields → `CodeableConcept`/`Coding` (see [[terminology]]); ATC codings carry the ATC system URI (see [[atc]]).
-- `Strength` → `Medication.ingredient.strength` (`Ratio` of `Quantity`); `DosageForm` → `Medication.form`; route + packaging → `MedicationKnowledge`.
-
-## Conformance
-- FHIR types from the **official FHIR .NET SDK**, version-matched (R4/R5) (see [[ai-rules.domain]]).
-- Declare profiles/extensions/value-sets in `StructureDefinition` resources; FHIR validator passes for every modified resource/profile/example (CI gate).
-- Publish `CapabilityStatement` at `/fhir/metadata` (diff reviewed); `/metadata` + `/.well-known` may be `AllowAnonymous()`.
-
-## Bundle / search / concurrency
-- Bundle/searchset semantics (`_count`, `_offset`/`_page`, `_total`); errors via `OperationOutcome` (HTTP 422); `If-Match` → FHIR **weak** ETag at the projection boundary (see [[persistence.domain]]).
-
-## Related
-- [[domain-driven-design.domain]] · [[terminology]] · [[ndc]] · [[idmp]] · [[atc]] · [[hl7]] · [[integration-terms]] · [[persistence.domain]] · [[testing.domain]] · [[ai-rules.domain]]

package/assets/docs/domainspecs/pharma/folder-structure.domain.md

@@ -1,24 +0,0 @@
-# Folder Structure — Pharma Domain Addenda
-
-> Technology base: [[folder-structure]]. Commands: `/aw-spec-gate`. Replace `<SampleProjectName>`.
-
-## Additions to the base layout
-```
-src/<SampleProjectName>.Service/
-  Infrastructure/Security/      auth handlers, scope evaluators, change-authority checks
-  Infrastructure/Auditing/      immutable product-audit emitter (FHIR AuditEvent shape)
-  ProductRegistry/Domain/<ValueObject>.cs   NdcCode, AtcCode, Strength, DosageForm, ...
-  ProductRegistry/Domain/MedicinalProduct.cs   aggregate root  (see [[domain-driven-design.domain]])
-  ProductRegistry/Interop/Fhir/   Medication/MedicationKnowledge/Substance/Organization projectors  (see [[fhir]])
-  ProductRegistry/Interop/Hl7v2/  inbound parsers + outbound emitters (when needed)   (see [[hl7]])
-  Terminology/                  CodeSystem/ValueSet/ConceptMap + seed (NDC/RxNorm/SNOMED/UNII/ATC)  (see [[terminology]])
-  Provenance/                   ProvenanceRecord store for external data   (see [[data-provenance]])
-tests/<SampleProjectName>.InteropTests/   FHIR-validator conformance              (see [[testing.domain]])
-tests/<SampleProjectName>.TestFixtures/   synthetic/test NDC + terminology sentinels  (see [[testing.domain]])
-docs/interop/fhir-implementation-guide/ · docs/regulatory/compliance-controls.md
-```
-- `Interop/` adapters translate to/from internal commands + projections (see [[vertical-slices.domain]]).
-- Coded VOs follow the FHIR pattern (see [[terminology]], [[coding-standards.domain]]); version history + audit store are retention-protected (see [[persistence.domain]], [[auditing.domain]]).
-
-## Related
-- [[folder-structure]] · [[fhir]] · [[hl7]] · [[terminology]] · [[data-provenance]] · [[testing.domain]] · [[vertical-slices.domain]] · [[domain-driven-design.domain]]

package/assets/docs/domainspecs/pharma/hl7.md

@@ -1,17 +0,0 @@
-# HL7 Integration Readiness — Pharma
-
-> Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
-
-## Principle
-- The solution SHALL support **future integration with HL7-based systems**. The registry is the authoritative product source; HL7 surfaces are **adapters, not a parallel model**. FHIR is the primary contract (see [[fhir]]); HL7 v2 adapters are added where a downstream system (prescribing/dispensing/manufacturing/pharmacovigilance) needs them.
-
-## Adapter patterns
-- Inbound/outbound adapters live in `{Module}/Interop/Hl7v2/`; translate via `IMediator` — **MUST NOT** write aggregates directly (see [[eventing.domain]], [[domain-driven-design.domain]]). Bypassing them from an external feed is an AI refusal condition (see [[ai-rules.domain]]).
-- The egress adapter converts domain events (e.g. `MedicinalProductActivated`, `ClassificationChanged`) to outbound messages; conformance tested against an internal corpus (see [[testing.domain]]).
-- Codes in HL7 messages use standard terminologies (NDC, RxNorm, UNII, ATC) — never free text (see [[terminology]], [[ndc]], [[atc]]).
-
-## Future surfaces
-- Pharmacovigilance (ICH E2B/ICSR), manufacturing, dispensing integrations are **additive** — consume via FHIR / REST / CloudEvents; **direct DB access FORBIDDEN** (see [[eventing.domain]]).
-
-## Related
-- [[fhir]] · [[eventing.domain]] · [[terminology]] · [[ndc]] · [[atc]] · [[integration-terms]] · [[domain-driven-design.domain]] · [[testing.domain]] · [[ai-rules.domain]]

package/assets/docs/domainspecs/pharma/idmp.md

@@ -1,26 +0,0 @@
-# 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/docs/domainspecs/pharma/integration-terms.md

@@ -1,21 +0,0 @@
-# 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/docs/domainspecs/pharma/ndc.md

@@ -1,28 +0,0 @@
-# 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/docs/domainspecs/pharma/persistence.domain.md

@@ -1,23 +0,0 @@
-# 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/docs/domainspecs/pharma/pharma-terms.md

@@ -1,27 +0,0 @@
-# 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/docs/domainspecs/pharma/product-lifecycle.domain.md

@@ -1,30 +0,0 @@
-# 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/docs/domainspecs/pharma/regulatory-compliance.md

@@ -1,19 +0,0 @@
-# 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/docs/domainspecs/pharma/terminology.md

@@ -1,32 +0,0 @@
-# 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/docs/domainspecs/pharma/testing.domain.md

@@ -1,19 +0,0 @@
-# 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/docs/domainspecs/pharma/vertical-slices.domain.md

@@ -1,17 +0,0 @@
-# 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/docs/domainspecs/pharma/zero-trust.domain.md

@@ -1,12 +0,0 @@
-# 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/docs/glossary/ai-rules.md

@@ -1,59 +0,0 @@
-# AI Operational Rules
-
-> Pure technology (domain-agnostic) — domain AI rules in [[ai-rules.domain]]. Applies to all AI agents (Claude Code, Augment, Copilot, etc.). Commands: **ALL**.
-
-AI agents MUST treat the constitution as **ground truth**, overriding pre-trained habits and
-any contradictory documentation found inside the repo.
-
-## Context loading rules / retrieval expectations
-
-- Before generating or editing code, **inspect the relevant vertical slice**
-  (`<Module>/Features/<Feature>/`) and the aggregate it mutates (see [[vertical-slices]]).
-- **Confirm symbol signatures via repository search** rather than inferring from generic
-  framework knowledge — `IRepository<T>` here is AppWeaver's, not a generic one
-  (see [[cqrs]], [[persistence]]).
-
-## AI generation rules
-
-- New features are generated as **complete vertical slices**: Command/Query + Handler +
-  Endpoint + Validator + (when applicable) Specification + DTO + mapping extension + Unit test
-  + Integration test.
-- Do **NOT** introduce new top-level dependencies (see [[dependency-policy]]).
-- Do **NOT** create speculative abstractions (single-implementation interfaces, generic
-  wrappers around existing framework types) — YAGNI.
-- Generated tests follow Test-First Engineering and **MUST fail before** the production change
-  is in place (see [[testing]]).
-
-## Output formatting conventions
-
-- Do **NOT** write inline rationale comments explaining why a pattern was chosen — the
-  constitution is the rationale (see [[coding-standards]]).
-
-## Migration generation policy
-
-- AI MAY scaffold EF Core migrations but **MUST NOT run them** against shared environments.
-  Production migrations require DBA sign-off and an SRE-executed rollout (see [[persistence]]).
-
-## Operating envelope
-
-- Edits limited to the scope explicitly requested. Drive-by refactors of unrelated files are
-  forbidden.
-- File creation constrained to the Mandatory Folder Structure; new folders require an amendment.
-- All AI-authored commits are self-contained: source change + tests + affected
-  DTOs/mappings + migration (when schema changes).
-
-## Refusal conditions (generic) — refuse and ask for clarification when a request would:
-
-- Violate a NON-NEGOTIABLE principle.
-- Introduce a Forbidden Pattern (see [[coding-standards]]).
-- Require a cross-aggregate transaction (see [[cqrs]], [[domain-driven-design]]).
-- Embed a secret, connection string, or production hostname in code or config.
-- Disable a soft-delete filter, tenancy filter, audit interceptor, scope check, or auth policy
-  globally.
-
-> Domain-specific generation rules, data masking, terminology codes, and refusal conditions are in [[ai-rules.domain]].
-
-## Related
-
-- [[coding-standards]] · [[dependency-policy]] · [[testing]] · [[persistence]] ·
-  [[vertical-slices]] · [[ai-rules.domain]]

package/assets/docs/governance/api-versioning.md

@@ -1,99 +0,0 @@
-# API Versioning Policy
-
-> Pure technology (domain-agnostic) — domain (e.g. FHIR) versioning in [[api-versioning.domain]]. Commands: `/aw-spec-design`.
-
-## REST versioning
-
-- Internal REST (FastEndpoints) serves first-party apps and operational tooling.
-- List endpoints accept `pageNumber` (1-based) + `pageSize` and return `PagedResult<TDto>`
-  (see [[vertical-slices]]).
-- Breaking changes to internal REST require a **versioned route prefix** (`v2/...`).
-- Endpoints MUST NOT swallow exceptions; the central exception handler owns the contract.
-
-## ETag / concurrency at the edge
-
-- The server sets the ETag header on every create/read/update via `SetETagFromBase64(...)`.
-- Update/Delete extract `If-Match` via `GetIfMatchBase64Token()`; mismatch -> `409
-  concurrency.conflict`. ETag tokens are strong; `W/` weak prefixes stripped on read.
-  See [[persistence]].
-
-## Machine-readable schemas
-
-- The service publishes versioned, machine-readable schemas:
-  - **OpenAPI** for REST,
-  - **AsyncAPI** for events (see [[eventing]]).
-- All schemas regenerate cleanly in CI; diffs are reviewed for breaking changes
-  (see [[coding-standards]]).
-- (FHIR CapabilityStatement — see [[api-versioning.domain]].)
-
-## Deprecation lifecycle & sunset policy
-
-- **Breaking changes are MAJOR version bumps** (per the constitution's governance SemVer).
-- A superseded REST version remains available through a documented deprecation window before
-  sunset; the deprecation and sunset are announced via the published schema diffs and the
-  governance amendment process.
-
-## Canonical example (agent reference — `<SampleProjectName>` sample)
-
-ETag round-trip: the endpoint reads `If-Match` on update and sets the `ETag` on success;
-the handler compares the token and translates an EF conflict to `409 concurrency.conflict`:
-
-```csharp
-// Endpoint (PUT /projects/{id:guid})
-var id = Route<Guid>("id");
-var token = HttpContext.Request.GetIfMatchBase64Token();      // extract If-Match
-
-var result = await _mediator.Send(new UpdateProjectCommand(
-    id, req.Name, req.Description, req.StartDate, req.EndDate, req.OwnerId, token), ct);
-
-if (result.IsSuccess && !string.IsNullOrWhiteSpace(result.Value?.RowVersionBase64))
-    HttpContext.Response.SetETagFromBase64(result.Value!.RowVersionBase64);   // set ETag
-return result;
-```
-
-```csharp
-// Handler — compare the supplied token, and catch EF's concurrency exception
-var current = entity.RowVersion is { Length: > 0 } rv ? Convert.ToBase64String(rv) : string.Empty;
-if (string.IsNullOrWhiteSpace(request.RowVersionBase64) ||
-    !string.Equals(current, request.RowVersionBase64, StringComparison.Ordinal))
-    return Result<ProjectDto>.Failure(new Error(
-        "concurrency.conflict", "Resource was modified by another process. Reload and retry.",
-        409, "projects"));
-
-entity.Update(request.Name, request.Description, request.StartDate, request.EndDate, ownerId);
-await _repo.UpdateAsync(entity, ct);
-
-try { await _uow.SaveChangesAsync(ct); }
-catch (DbUpdateConcurrencyException)
-{
-    return Result<ProjectDto>.Failure(new Error(
-        "concurrency.conflict", "Resource was modified by another process. Reload and retry.",
-        409, "projects"));
-}
-```
-
-ETag token helpers — strong tokens; strip `W/` weak prefix and quotes on read:
-
-```csharp
-// <SampleProjectName>.Service/Utilities/HttpRequestETagExtensions.cs
-public static string GetIfMatchBase64Token(this HttpRequest request, string? fallback = null)
-{
-    var token = request.Headers.IfMatch.FirstOrDefault();
-    return !string.IsNullOrWhiteSpace(token) ? SanitizeETagToken(token) : (fallback ?? string.Empty);
-}
-
-public static string SanitizeETagToken(string? raw)
-{
-    if (string.IsNullOrWhiteSpace(raw)) return string.Empty;
-    var token = raw.Trim();
-    if (token.StartsWith("W/")) token = token[2..].Trim();   // strip weak prefix
-    return token.Trim('"');                                  // strip quotes
-}
-
-// On success the endpoint sets the strong ETag from the DTO's RowVersionBase64:
-HttpContext.Response.SetETagFromBase64(result.Value!.RowVersionBase64);
-```
-
-## Related
-
-- [[vertical-slices]] · [[persistence]] · [[eventing]] · [[coding-standards]] · [[api-versioning.domain]]

package/assets/docs/governance/coding-standards.md

@@ -1,87 +0,0 @@
-# Coding Standards
-
-> Pure technology (domain-agnostic) — domain forbidden patterns & CI gates in [[coding-standards.domain]]. Commands: `/aw-spec-implement`, `/aw-spec-implement-delta`, `/aw-spec-build`, `/aw-spec-analyze-slice`.
-
-## Naming conventions
-
-- Solution and projects: `<SampleProjectName>.<Role>` (e.g. `<SampleProjectName>.Api`,
-  `<SampleProjectName>.AppHost`, `<SampleProjectName>.ServiceDefaults`).
-- Namespaces mirror the folder path exactly; **file-scoped namespaces only**.
-- Aggregates: `class <Aggregate> : EntityBase<<Aggregate>Id>, IAggregateRoot,
-  IFullAuditedObject, ISoftDeletable, IConcurrencyTracked, IHasDomainEvents,
-  INamedEntity<<Aggregate>Id>`.
-- Commands/Queries: `record <Verb><Aggregate>Command(...) : ICommand<Result<TDto>>`.
-- DTOs: `record <Aggregate>Dto { public required Guid Id { get; init; } ... }` — no setters;
-  required init for non-nullable members.
-
-## Nullable & language rules
-
-- C# language version: latest LTS; **nullable reference types ENABLED**; implicit usings
-  ENABLED; **`TreatWarningsAsErrors` for Release**.
-
-## Async conventions
-
-- Every I/O-bound method ends with `Async` and accepts a `CancellationToken` as the **last
-  parameter**.
-- `async void` is forbidden outside event handlers.
-- Blocking calls (`.Result`, `.Wait()`, `Task.Run` to fake async) in request-handling paths
-  are FORBIDDEN.
-
-## Error / exception conventions
-
-- Exceptions are thrown by the **Domain only** (`DomainException`,
-  `InvariantViolationException`). Application code returns `Result<T>` (see [[cqrs]]).
-- Never catch-all `catch (Exception)` that swallows or rewraps without rethrow, except in the
-  central exception handler.
-- Never return HTTP 200 with an error body — use correct status codes (4xx client, 5xx server,
-  409 concurrency).
-
-## Documentation expectations
-
-- XML doc comments on public types and aggregate methods.
-- Inline comments only where intent is non-obvious. Commented-out code MUST be removed before
-  merge.
-- Do not write inline rationale comments explaining pattern choices — the constitution is the
-  rationale (see [[ai-rules]]).
-
-## Forbidden patterns (generic; rejected at review, build-warning where statically detectable)
-
-1. MediatR — use `AppWeaver.Mediator` (see [[dependency-policy]]).
-2. AutoMapper / Mapster reflection mapping — hand-written `ToDto()` only.
-3. Anemic domain models (see [[domain-driven-design]]).
-4. Repository as data-access god object (see [[persistence]]).
-5. Cross-aggregate EF navigation properties — strongly-typed ID only.
-6. Hard-coded connection strings, secrets, ports, or issuer URLs in source (see [[zero-trust]]).
-7. Static service locator — use constructor DI.
-8. Direct `DbContext` access from Endpoints or Features outside repo/spec surface.
-9. Blocking calls in request paths.
-10. Catch-all that swallows/rewraps without rethrow (outside central handler).
-11. `AllowAnonymous()` on sensitive-data/mutating endpoints in a CI-protected branch.
-12. Logging/emitting secrets, tokens, keys, or payment-card data (see [[data-classification]]).
-13. Multiple aggregate mutations in one transaction (see [[cqrs]], [[eventing]]).
-14. `DateTime.UtcNow` / `Guid.NewGuid()` in aggregates/handlers/SUT — use `IClock` /
-    `IGuidGenerator` (see [[testing]]).
-15. HTTP 200 with an error body.
-16. Analytics/reporting by querying the OLTP DB directly — emit events (see [[eventing]]).
-
-> Domain-specific forbidden patterns are in [[coding-standards.domain]].
-
-## Quality gates (CI) — generic, must pass before merge
-
-1. `dotnet build` succeeds with `TreatWarningsAsErrors=true` for Release.
-2. `dotnet test` passes for UnitTests + IntegrationTests.
-3. Code coverage on changed files meets the Testing Profile threshold (see [[testing]]).
-4. EF Core migrations apply cleanly to a fresh PostgreSQL instance (see [[persistence]]).
-5. OpenAPI document generation succeeds; diff reviewed for breaking changes.
-6. AsyncAPI regenerates cleanly for any domain-event contract change (see [[eventing]]).
-7. Static analysis (Roslyn analyzers, nullable warnings, banned-API analyzer) — zero errors.
-8. Grep checks: no `AllowAnonymous()` on production endpoints, no hard-coded secrets, no
-   MediatR/AutoMapper references.
-9. Constitution compliance review checked off in the PR template.
-
-> Domain-specific CI gates are in [[coding-standards.domain]].
-
-## Related
-
-- [[dependency-policy]] · [[api-versioning]] · [[domain-driven-design]] · [[cqrs]] ·
-  [[persistence]] · [[testing]] · [[ai-rules]] · [[coding-standards.domain]]

package/assets/docs/governance/dependency-policy.md

@@ -1,40 +0,0 @@
-# Dependency Policy
-
-> Pure technology (domain-agnostic) — domain package rules in [[dependency-policy.domain]]. Commands: `/aw-spec-implement`, `/aw-spec-implement-delta`.
-
-## Package governance
-
-- **All package versions are governed by `Directory.Packages.props`** (Central Package
-  Management). `PackageReference` entries in `.csproj` MUST NOT specify a `Version`.
-- New dependencies are added via `dotnet add package`.
-
-## Approved / preferred packages
-
-- Mediator: **`AppWeaver.Mediator`**.
-- Mapping: **hand-written `ToDto()` extension methods** (no reflection mapper).
-- Observability: **`AppWeaver.ServiceDefaults`** (OpenTelemetry + Serilog + resilience +
-  discovery) — see [[auditing]].
-- Validation: FluentValidation (via the mediator pipeline behavior; see [[cqrs]]).
-
-## Banned packages
-
-- **MediatR** — MUST NOT appear in any `Directory.Packages.props` entry (CI grep gate).
-- **AutoMapper / Mapster** (reflection mapping) — forbidden (see [[coding-standards]]).
-- Any logging package that ships analytics/telemetry exfiltration by default — rejected.
-
-## Supply-chain rules
-
-- New dependencies are reviewed for **license and supply-chain risk** before adoption.
-- AI agents **MUST NOT** introduce new top-level dependencies; new framework capabilities are
-  requested explicitly by the developer (see [[ai-rules]]).
-- Do not create speculative abstractions (single-implementation interfaces, generic wrappers
-  around existing framework types) — YAGNI is enforced.
-
-## Licensing expectations
-
-- Dependencies must carry a license compatible with the intended commercial deployment;
-  copyleft licenses that would force source disclosure of the service are rejected.
-
-## Related
-
-- [[coding-standards]] · [[cqrs]] · [[auditing]] · [[ai-rules]] · [[dependency-policy.domain]]