aw-spec-cli 0.1.5 → 0.1.7

package/assets/docs/domainspecs/healthcare/commandtechrulemap.md

@@ -1,119 +0,0 @@
-# Healthcare Domain — Command → Technical-Rule-File Map
-
-Per-command list of the **technical** rule files loaded (via `resolve-tech` + the
-`tech-select` module, into the sticky standards set) for the spec-anchored
-orchestrator pipeline. This is the technical counterpart of `comandrulemap.md`
-(which maps the DOMAIN rule files).
-
-**The model:** the technical rule files (the `docs/architecture` · `docs/security` ·
-`docs/interop` · `docs/governance` set that used to be HARDCODED in each workflow's
-`standards:` block) are now CONFIGURATION — tune this map, not the workflows. The
-technology base itself (`constitution.technical.md`) is NOT listed here — every
-consumer still refers to it directly, as-is.
-
-- All paths are workspace-relative technical rule files (domain-agnostic docs/…).
-- `resolve-tech --command <name>` collects the `- ` bullets under `## /<name>`.
-- This file is the **canonical technical mapping** for the healthcare domain; it is
-  selected whenever healthcare is the active domain (`.aw-spec/domain.json`).
-- A command with no heading here loads no mapped technical file (only the workflow's
-  universal `ai-rules.md` seed + `constitution.technical.md`, referred to directly).
-- `## /aw-spec-specify` is the one **modelling-methodology** slot (see the rule partition):
-  a domain-agnostic way of *modelling*, never a technology choice. Everything below it is a
-  HOW-phase technical set.
-
----
-
-## /aw-spec-specify
-<!-- MODELLING METHODOLOGY ONLY. Specify is the domain phase: the single technical input it
-     may take is a domain-agnostic way of MODELLING (DDD tactical patterns), never a
-     technology choice. Do NOT add an architecture / persistence / codegen file here — that
-     would break specify's domain purity (design/implement own those). The domain's own DDD
-     overlay (domain-driven-design.domain.md) arrives separately via comandrulemap. -->
-- docs/domain/domain-driven-design.md
-
-## /aw-spec-design
-<!-- The technical/architecture rule files the design author works from (alongside the
-     spec and constitution.technical.md). NO domain file here — domain reaches design
-     only as spec ids (BR-/CN-/DC-/IC-). -->
-- docs/architecture/clean-architecture.md
-- docs/architecture/cqrs.md
-- docs/architecture/eventing.md
-- docs/architecture/modular-monolith.md
-- docs/architecture/vertical-slices.md
-- docs/architecture/persistence.md
-- docs/architecture/folder-structure.md
-- docs/architecture/testing.md
-- docs/governance/api-versioning.md
-- docs/security/zero-trust.md
-- docs/security/authorization.md
-- docs/security/authorization-matrix.md
-- docs/security/auditing.md
-- docs/security/data-classification.md
-- docs/interop/ihe-conformance.md
-
-## /aw-spec-implement
-<!-- The FRAMEWORK / code-generation rule files the code generator builds against
-     (alongside design.md and constitution.technical.md). NO domain file — domain
-     reaches implement only through design.md. clean-architecture/cqrs are design
-     concerns; component wiring is a separate /aw-spec-orch add-component step. -->
-- docs/governance/coding-standards.md
-- docs/governance/dependency-policy.md
-- docs/architecture/folder-structure.md
-- docs/architecture/testing.md
-- docs/VerticalSlice/PACKAGING.md
-
-## /aw-spec-implement-delta
-<!-- The CR analog of implement — same FRAMEWORK / code-generation set (HOW to build).
-     The delta's code is generated against the master design.md + delta-design.md; no
-     domain file (domain reached the delta via delta-spec → delta-design). -->
-- docs/governance/coding-standards.md
-- docs/governance/dependency-policy.md
-- docs/architecture/folder-structure.md
-- docs/architecture/testing.md
-- docs/VerticalSlice/PACKAGING.md
-
-## /aw-spec-build
-<!-- The compile/fix reference set: the layering + coding rules the fixer respects when
-     repairing compile errors against the design intent. NO domain file (build loads
-     domain rules separately via domain-select) and no constitution.technical here. -->
-- docs/architecture/clean-architecture.md
-- docs/governance/coding-standards.md
-
-## /aw-spec-analyze-slice
-<!-- The design↔code conformance gate's TECHNICAL checklist: the code + tests are
-     validated against these (alongside the DOMAIN gate overlays, loaded separately via
-     resolve-domain `## /aw-spec-gate`). Validation input only — never authoring. -->
-- docs/architecture/testing.md
-- docs/governance/coding-standards.md
-
-## /aw-spec-constitution
-<!-- The technology-constitution base the TECHNICAL half of the split constitution
-     ratifies into constitution.technical.md. Loaded BEFORE the technical half and before
-     domain-select, so the technical author stays domain-free (the seam). NO domain file
-     here — the domain half's sources are the domain map's ## /aw-spec-constitution. -->
-- docs/technology-constitution.md
-
-## /aw-spec-run
-<!-- Execution / data migration: the persistence rules the migration step generates against.
-     NO domain file; run does not reference constitution.technical.md. -->
-- docs/architecture/persistence.md
-
----
-
-## Quick reference (command → technical file count)
-
-| Command | Technical rule files | Role |
-|---|---|---|
-| /aw-spec-specify | 1 | the modelling methodology (DDD) the domain model is expressed in — no technology |
-| /aw-spec-design | 15 | architecture/security/interop the design author mediates the spec against |
-| /aw-spec-implement | 5 | governance/architecture the code generator builds against (from design.md) |
-| /aw-spec-implement-delta | 5 | same code-generation set, scoped to the open change's delta-design |
-| /aw-spec-build | 2 | layering + coding rules the compile-fixer respects |
-| /aw-spec-analyze-slice | 2 | testing + coding rules the design↔code gate validates against |
-| /aw-spec-constitution | 1 | the technology-constitution base the technical half ratifies |
-| /aw-spec-run | 1 | persistence rules the execution / data-migration step generates against |
-
-> All migrated workflows are on this map. The conformance-gate workflows **analyze-design**
-> and **analyze-delta-design** are intentionally NOT here — they validate design/delta
-> against the spec + DOMAIN gate overlays only (comandrulemap `## /aw-spec-gate`), with no
-> technical gate checklist.

package/assets/docs/domainspecs/healthcare/consent.md

@@ -1,19 +0,0 @@
-# Consent Standards
-
-> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
-
-## First-class aggregate
-- Consent is a **first-class aggregate** (Patients module). A **withdrawn consent MUST block downstream PHI disclosure** for the purpose-of-use **immediately**; state changes emit `ConsentChangedEvent` (see [[eventing]]).
-- The access-control pipeline **MUST check consent before releasing PHI** outside the treating-provider context. Denial surfaces as `ConsentDeniedException` from the Domain (see [[domain-driven-design.domain]], [[authorization.domain]]).
-
-## Break-the-glass
-- Explicit **emergency-access command**: documented reason + high-priority audit + real-time alert; audit-mandatory (see [[auditing.domain]]).
-
-## Restriction-of-processing
-- GDPR restriction (Art. 18) + erasure (Art. 17) are first-class audited commands. Where law forbids erasing medical records, **restriction-of-processing is the fallback** (see [[hipaa]], [[persistence.domain]]).
-
-## FHIR mapping
-- **BPPC** + **FHIR Consent** profiles honored; Consent projects to the FHIR `Consent` resource (see [[fhir]]).
-
-## Related
-- [[hipaa]] · [[authorization.domain]] · [[auditing.domain]] · [[fhir]] · [[domain-driven-design.domain]]

package/assets/docs/domainspecs/healthcare/cqrs.domain.md

@@ -1,12 +0,0 @@
-# CQRS — Healthcare Domain Addenda
-
-> Technology base: [[cqrs]]. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
-
-## Pipeline
-- Append a **PHI-access-audit behavior** to the mediator pipeline (beyond generic logging + FluentValidation): emit an audit record for every command/query touching PHI (see [[auditing.domain]]).
-
-## Error codes
-Dot-namespaced slugs (see [[cqrs]]). Examples: `patient.not_found` · `claim.duplicate_submission` · `consent.denied` · `concurrency.conflict`.
-
-## Related
-- [[cqrs]] · [[auditing.domain]] · [[hipaa]] · [[domain-driven-design.domain]]

package/assets/docs/domainspecs/healthcare/data-classification.domain.md

@@ -1,28 +0,0 @@
-# Data Classification — Healthcare Domain Addenda
-
-> Technology base: [[data-classification]]. NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`, `/aw-spec-gate`.
-
-## Categories
-| Class | Extra rules |
-|---|---|
-| **PHI** (clinical, demographic, identifiers) | Minimum-necessary; audited; encrypted |
-| **PII** (non-clinical identifiers) | Encrypted; minimum-necessary |
-| **PCI** (payment) | **Out of scope** — route to a PCI-DSS processor |
-| **Behavioral Health** (42 CFR Part 2) | Extra-sensitive; field-level encryption |
-| **Genetic** (GINA) | Extra-sensitive |
-| **Pediatric** (minors) | Extended retention; heightened protection |
-
-## Field-level encryption (required)
-SSN, government IDs, payment-card data, behavioral-health flags (see [[hipaa]], [[persistence.domain]]).
-
-## Logging
-- **NEVER** log/emit any PHI element, full SSN, government ID, or full payment-card data.
-- PHI-logging analyzer (CI gate): no Patient/Encounter/Observation/MedicationRequest field logged except the ID (see [[coding-standards.domain]]).
-
-## Export
-- Analytics/research/non-prod exports MUST pass **Safe-Harbor or Expert-Determination** de-identification.
-- **Production PHI in non-production is FORBIDDEN** (see [[hipaa]], [[testing.domain]]).
-- Bulk `$export` gated by authorization + de-identification (see [[fhir]]).
-
-## Related
-- [[data-classification]] · [[hipaa]] · [[auditing.domain]] · [[authorization.domain]] · [[persistence.domain]] · [[coding-standards.domain]]

package/assets/docs/domainspecs/healthcare/dependency-policy.domain.md

@@ -1,11 +0,0 @@
-# Dependency Policy — Healthcare Domain Addenda
-
-> Technology base: [[dependency-policy]]. Commands: `/aw-spec-gate`.
-
-## Reviews & libraries
-- Every new dependency gets a **HIPAA-suitability** review beyond the generic license/supply-chain check — e.g. reject a logging package that ships analytics by default (PHI-exfiltration risk) (see [[hipaa]], [[data-classification.domain]]).
-- FHIR: the **official FHIR .NET SDK**, version-matched to the endpoint (R4/R5; see [[fhir]]).
-- HL7 v2 / DICOM libraries are added **only** on explicit developer request — no AI-introduced healthcare-protocol dependencies (see [[hl7]], [[dicom]], [[ai-rules.domain]]).
-
-## Related
-- [[dependency-policy]] · [[fhir]] · [[hl7]] · [[dicom]] · [[hipaa]] · [[ai-rules.domain]]

package/assets/docs/domainspecs/healthcare/dicom.md

@@ -1,15 +0,0 @@
-# DICOM Standards
-
-> Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
-
-## DICOMweb façade
-- Supported via a **DICOMweb façade** — **QIDO-RS** (query), **WADO-RS** (retrieve), **STOW-RS** (store) — fronting a separately deployed PACS/VNA. Adapters live in `{Module}/Interop/Dicom/` (Radiology only).
-- The PACS/VNA endpoint is an Aspire resource referenced via `.WithReference(...)`; hosts/ports discovered through Aspire, never hard-coded.
-
-## Metadata only
-- **Only DICOM METADATA is persisted here** — pixel data lives in the PACS/VNA, referenced by study/series/instance UIDs.
-- Radiology aggregates: `ImagingOrder`, `ImagingStudy` (metadata), `DiagnosticReport`; results surface via FHIR projections (`ImagingStudy`, `DiagnosticReport`; see [[fhir]]).
-- Trace context propagates across DICOM outbound calls (see [[auditing]]).
-
-## Related
-- [[fhir]] · [[integration-terms]] · [[domain-driven-design]]

package/assets/docs/domainspecs/healthcare/domain-driven-design.domain.md

@@ -1,28 +0,0 @@
-# Domain-Driven Design — Healthcare Domain Model
-
-> Technology base: [[domain-driven-design]]. NON-NEGOTIABLE. Commands: `/aw-spec-specify`.
-
-## Modeling
-- Use the clinical/interop ubiquitous language (see [[clinical-terms]], [[integration-terms]]).
-- FHIR-aligned, but **FHIR resources are projections, not the system of record** (see [[fhir]]).
-- Coded concepts use industry terminologies, never free text (see [[terminology]]); coded value objects follow the FHIR pattern (`Codeable`, `Coding`, `Quantity`, `Period`, `Range`, `Ratio`, `Identifier`, `HumanName`, `Address`, `ContactPoint`).
-- Domain may throw `ConsentDeniedException` beyond generic Domain exceptions (see [[consent]]).
-
-## Aggregates & invariants
-- **Patient** — MRN unique per tenant; DOB <= today; merge only via `MergePatientsCommand` preserving audit; minimum-necessary projection by role/scope.
-- **Consent** — withdrawal blocks downstream PHI disclosure for the purpose-of-use immediately; emits `ConsentChangedEvent` (see [[consent]]).
-- **Appointment** — no overlap with a booked slot for the same Practitioner/Resource; no past booking; late cancellation (< N hrs) emits `LateCancellationEvent`.
-- **Encounter** — not Closed/Discharged while any open Order/Result/ChargeItem/unsigned ClinicalNote exists; admission requires active Coverage or documented self-pay.
-- **ClinicalNote** — Signed = immutable; addendum is a new linked note; deletion forbidden (supersede via Amend).
-- **MedicationRequest** — dispense forbidden on active allergy match, lethal interaction, or pediatric/renal contraindication without a documented override (prescriber, reason, timestamp).
-- **ControlledSubstanceLedger** — every dispense/waste must balance; append-only; daily reconciliation.
-- **LabOrder/ImagingOrder** — not Cancellable once a Specimen/Image is acquired; transition to Aborted with a reason.
-- **Claim** — total billed = sum(ChargeItem.amount); resubmission needs a new ClaimVersion; none after final adjudication unless an Appeal is opened.
-- **InventoryItem** — stock <= 0 forbidden; dispensing an expired Lot rejected; near-expiry emits `ExpiryAlertEvent`.
-- **AuditRecord** — append-only; no update/delete; retention >= 6 years (see [[auditing.domain]]).
-
-## AI guidance
-See [[ai-rules.domain]] — confirm signatures, use the official FHIR SDK, never invent codes, mask PHI.
-
-## Related
-- [[domain-driven-design]] · [[fhir]] · [[terminology]] · [[consent]] · [[clinical-terms]] · [[integration-terms]] · [[auditing.domain]] · [[persistence.domain]] · [[ai-rules.domain]]

package/assets/docs/domainspecs/healthcare/domain-requirements.md

@@ -1,55 +0,0 @@
-# DOMAIN REQUIREMENTS (project-specific)
-
-> Project-specific input, **updated independently per project**. The engineering constitution
-> (the technology base composed with `healthcare-constitution.md`) references this file; the
-> constitution stays domain-agnostic and supreme. Detailed domain *rules* are expanded in
-> `docs/` — this file holds the
-> per-project enumeration and headline profiles.
->
-> 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]  -> docs/domainspecs/healthcare/domain-driven-design.domain.md
-[DOMAIN: Persistence Profile]                 -> docs/domainspecs/healthcare/persistence.domain.md
-[DOMAIN: Security Profile]                     -> docs/domainspecs/healthcare/authorization.domain.md, docs/domainspecs/healthcare/data-classification.domain.md
-[DOMAIN: Testing Profile]                      -> docs/domainspecs/healthcare/testing.domain.md
-[DOMAIN: AI Policy Addenda]                    -> docs/domainspecs/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/docs/domainspecs/healthcare/eventing.domain.md

@@ -1,18 +0,0 @@
-# Eventing — Healthcare Domain Addenda
-
-> Technology base: [[eventing]]. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
-
-## Inbound feeds
-Each translated to internal commands via Interop adapters — never writing aggregates directly (see [[eventing]]):
-- HL7 v2 (ADT/ORM/ORU/SIU/MDM/DFT) — see [[hl7]]
-- External EHR FHIR pulls — see [[fhir]]
-- Lab / radiology result feeds; claim adjudication responses
-
-## Trace propagation
-- Trace context MUST propagate across **HL7v2 / DICOM / FHIR** outbound calls (beyond generic mediator/`HttpClient`/EF Core propagation).
-
-## Single source of truth
-- Authoritative system of record; consumers use FHIR / REST / CloudEvents / Bulk `$export` — **direct DB access FORBIDDEN** (see [[hipaa]]).
-
-## Related
-- [[eventing]] · [[hl7]] · [[fhir]] · [[dicom]] · [[hipaa]]

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

@@ -1,36 +0,0 @@
-# FHIR Standards
-
-> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
-
-## Architecture
-- **R4 is the default external contract**; R5 is **additive** under `/fhir/R5/...`.
-- FHIR is the canonical interop contract; internal REST is for first-party apps. Both serve from the **same authoritative aggregates** — no duplicate write paths.
-
-## Projector rules (system of record)
-- **FHIR resources are PROJECTIONS over the aggregates — NOT the system of record.**
-- Mapping lives in `{Module}/Interop/Fhir/<Resource>Projector.cs`, hand-written + round-trip tested (`domain -> FHIR -> domain`; see [[testing]]).
-- A second FHIR write path bypassing the aggregate is FORBIDDEN; FHIR representations **MUST NOT** replace internal DTOs (see [[vertical-slices]]).
-
-## Resources & terminology
-- FHIR types come from the **official FHIR .NET SDK**, version-matched (R4/R5) to the endpoint.
-- Coded fields map from `Codeable`/`Coding` VOs to FHIR `CodeableConcept`/`Coding` (see [[terminology]]).
-
-## Profiles & CapabilityStatement
-- Honor **US Core** + project IGs; declare profiles/extensions/value-sets/search-params in `StructureDefinition` resources packaged with the service.
-- Publish `CapabilityStatement` at `/fhir/metadata` (regenerates cleanly in CI; diff reviewed); `/metadata` + `/.well-known` may be `AllowAnonymous()`.
-- Breaking changes require a **new version path** + published CapabilityStatement diff (see [[api-versioning.domain]]); FHIR validator passes for every modified resource/profile/example (CI gate).
-
-## Bundle / search / concurrency
-- List endpoints use **Bundle/searchset** semantics (`_count`, `_offset`/`_page`, `_total`).
-- Errors use `OperationOutcome` (HTTP 422 for validation).
-- `If-Match` honored via the aggregate's concurrency token → FHIR **weak** ETag at the projection boundary (see [[persistence]]).
-
-## SMART & Bulk Data
-- SMART app launch (EHR + standalone) MUST be supported — **PKCE mandatory; implicit flow forbidden**; scopes enforced on every endpoint (see [[authorization.domain]]).
-- **Bulk `$export`** supported for authorized backend extraction; de-identification required for analytics/research (see [[hipaa]]).
-
-## IHE
-- PIX/PDQ, XDS/XDS.b or MHD, ATNA, CT, BPPC followed where they apply; deviations in `docs/interop/ihe-conformance.md` (see [[integration-terms]], [[auditing.domain]]).
-
-## Related
-- [[domain-driven-design.domain]] · [[terminology]] · [[hl7]] · [[dicom]] · [[consent]] · [[authorization.domain]] · [[api-versioning.domain]] · [[testing.domain]]

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

@@ -1,23 +0,0 @@
-# Folder Structure — Healthcare 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, PHI-access pipeline
-  Infrastructure/Auditing/      ATNA + FHIR AuditEvent emitter
-  <Module>/Domain/<ValueObject>.cs   coded VOs: Codeable, Coding, Quantity, HumanName, ...
-  <Module>/Interop/Fhir/        projectors, search-param handlers, IG profiles   (see [[fhir]])
-  <Module>/Interop/Hl7v2/       inbound parsers + outbound emitters              (see [[hl7]])
-  <Module>/Interop/Dicom/       DICOMweb adapters (Radiology only)               (see [[dicom]])
-tests/<SampleProjectName>.InteropTests/   FHIR-validator conformance             (see [[testing.domain]])
-tests/<SampleProjectName>.TestFixtures/   synthetic-PHI + terminology sentinels  (see [[testing.domain]])
-docs/interop/ihe-conformance.md · docs/interop/fhir-implementation-guide/
-docs/security/hipaa-controls.md · docs/security/gdpr-controls.md
-```
-- `Interop/` adapters translate to/from internal commands + projections (see [[vertical-slices.domain]]).
-- Coded value objects follow the FHIR pattern (see [[terminology]], [[coding-standards.domain]]).
-
-## Related
-- [[folder-structure]] · [[fhir]] · [[hl7]] · [[dicom]] · [[testing.domain]] · [[vertical-slices.domain]]

package/assets/docs/domainspecs/healthcare/hipaa.md

@@ -1,34 +0,0 @@
-# HIPAA / PHI Protection Standards
-
-> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
-
-## Regime
-PHI/ePHI under **HIPAA** (Privacy + Security + Breach Notification), **HITECH**, **21st Century Cures Act** anti-information-blocking, and **GDPR** where EU subjects apply, plus regional rules.
-
-## Minimum necessary
-- Every PHI read/write endpoint enforces **minimum-necessary** — return only fields the caller's role + SMART scopes authorize.
-- Field-level redaction lives in **projection extensions**, not controllers (see [[fhir]], [[authorization.domain]]).
-
-## Audit & consent
-- Every PHI read/mutation, authentication, consent change, export, and break-the-glass MUST emit an immutable audit record (see [[auditing.domain]]).
-- Consent is a first-class aggregate; the pipeline checks it before releasing PHI outside the treating-provider context (see [[consent]]).
-
-## Encryption
-- **AES-256 at rest** (TDE + CMK), **TLS 1.2+** in transit (1.3 target), encrypted backups.
-- App-level field encryption for SSN, government IDs, payment-card data, behavioral-health flags (see [[data-classification.domain]]).
-
-## De-identification
-- Exports to analytics/research/non-prod MUST pass a **Safe-Harbor OR Expert-Determination** service.
-- **Production PHI in dev/test/demo/CI is FORBIDDEN** — use synthetic-PHI fixtures (see [[testing.domain]]). De-identification without a documented method is a refusal condition (see [[ai-rules.domain]]).
-
-## Retention & rights
-- `AuditRecord` >= 6 yrs; clinical per jurisdiction (US >= 6 yrs adult, longer for minors); financial >= 7 yrs; backups under the same CMK (see [[persistence.domain]]).
-- Access, amendment, restriction, accounting-of-disclosures, erasure (GDPR Art. 17) are first-class commands with their own audit; where law forbids erasing medical records, **restriction-of-processing** is the fallback (see [[consent]]).
-
-## Breach, BAA, SSoT
-- Anomalous access (volume spikes, off-hours mass reads, repeated denials) emits **Critical** alerts.
-- Any outbound integration transmitting PHI is gated by a **BAA flag**; absence MUST refuse the integration at startup.
-- Authoritative system of record; consumers use FHIR / REST / CloudEvents / Bulk `$export` — **direct DB access FORBIDDEN** (see [[eventing]]).
-
-## Related
-- [[auditing.domain]] · [[consent]] · [[data-classification.domain]] · [[authorization.domain]] · [[zero-trust.domain]] · [[persistence.domain]] · [[testing.domain]] · [[ai-rules.domain]]

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

@@ -1,15 +0,0 @@
-# HL7 v2 Standards
-
-> Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
-
-## Adapters (not a parallel model)
-- HL7 v2.x (**ADT, ORM, ORU, SIU, MDM, DFT**) MUST be supported via an **ingress adapter** → internal commands; an **egress adapter** converts domain events → outbound messages.
-- Adapters live in `{Module}/Interop/Hl7v2/`; translate via `IMediator` — **MUST NOT** write aggregates directly (see [[eventing]], [[domain-driven-design]]). Bypassing them from an external feed is an AI refusal condition (see [[ai-rules.domain]]).
-- Conformance tested against an **internal corpus** (see [[testing]]).
-
-## MLLP
-- The HL7v2 broker (MLLP) is an Aspire resource referenced via `.WithReference(...)`; hosts/ports discovered through Aspire, never hard-coded.
-- Ingest target: **50 messages/sec per channel**; trace context propagates across HL7v2 outbound calls (see [[auditing]]).
-
-## Related
-- [[fhir]] · [[eventing]] · [[integration-terms]] · [[domain-driven-design]] · [[testing]]

package/assets/docs/domainspecs/healthcare/integration-terms.md

@@ -1,21 +0,0 @@
-# Glossary — Integration Terms
-
-> Ubiquitous language for interoperability standards + IHE profiles. Commands: `/aw-spec-specify`.
-
-| Term | Definition |
-|---|---|
-| **HL7** | **HL7 v2.x** = legacy pipe-delimited messaging (ADT/ORM/ORU/SIU/MDM/DFT) via adapters (see [[hl7]]); **HL7 FHIR** = the resource-based standard (see [[fhir]]). |
-| **FHIR** | Canonical external contract (R4 default, R5 additive); resources are projections over aggregates (see [[fhir]]). |
-| **DICOM** | Imaging standard via DICOMweb (QIDO/WADO/STOW-RS); only metadata persisted here (see [[dicom]]). |
-| **PIX / PDQ** | Patient Identifier Cross-referencing / Demographics Query (IHE) — used by Patients. |
-| **ATNA** | Audit Trail + Node Authentication (IHE); audit records exportable as FHIR `AuditEvent` (see [[auditing.domain]]). |
-| **MHD / XDS / XDS.b** | Document-sharing profiles (IHE); MHD is the FHIR-based lightweight alternative to XDS. |
-| **CT** | Consistent Time (IHE) — synchronized clocks across nodes. |
-| **BPPC** | Basic Patient Privacy Consents (IHE consent profile; see [[consent]]). |
-| **SMART on FHIR** | OAuth2/OIDC app-launch for third-party apps; PKCE mandatory (see [[authorization.domain]]). |
-| **Bulk Data / `$export`** | FHIR Bulk Data spec for population-level extraction; de-identified for analytics (see [[hipaa]]). |
-| **CloudEvents** | CNCF durable async event-stream spec over the broker (see [[eventing]]). |
-| **OpenAPI / CapabilityStatement / AsyncAPI** | Versioned machine-readable contracts for REST / FHIR / events (see [[api-versioning]]). |
-
-## Related
-- [[clinical-terms]] · [[fhir]] · [[hl7]] · [[dicom]] · [[eventing.domain]] · [[auditing.domain]] · [[authorization.domain]] · [[api-versioning.domain]]

package/assets/docs/domainspecs/healthcare/persistence.domain.md

@@ -1,20 +0,0 @@
-# Persistence — Healthcare Domain Addenda
-
-> Technology base: [[persistence]]. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
-
-## Soft delete & retention
-- Hard delete FORBIDDEN for any aggregate holding **clinical/financial/PHI** data — delete logically via `MarkAsDeleted(...)`. All aggregates are soft-deleted (no exemptions).
-- `AuditRecord` is **append-only** — no delete (see [[auditing.domain]]).
-- Retention: `AuditRecord` >= 6 years; clinical per jurisdiction (US >= 6 yrs adult, longer for minors); financial >= 7 years; backups under the same CMK.
-- GDPR Art. 17 erasure → **restriction-of-processing** where law forbids erasing medical records (see [[consent]], [[hipaa]]).
-
-## Encryption
-- Production PostgreSQL: **TDE with customer-managed keys (CMK)**.
-- App-level field encryption for SSN, government IDs, payment-card data, behavioral-health flags (see [[data-classification.domain]], [[hipaa]]).
-
-## Tenancy & dev data
-- Multi-hospital deployments MAY opt into tenant-per-database; default tenant-per-row.
-- SQLite dev fixtures contain **no PHI** — production PHI in dev/test/CI is FORBIDDEN (see [[hipaa]]).
-
-## Related
-- [[persistence]] · [[hipaa]] · [[auditing.domain]] · [[data-classification.domain]] · [[consent]]

package/assets/docs/domainspecs/healthcare/terminology.md

@@ -1,30 +0,0 @@
-# Terminology Standards
-
-> 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`) — store code, code-system OID/URI, version, display.
-
-## Standard terminologies
-| Domain | Terminology |
-|---|---|
-| Diagnoses | ICD-10-CM (US) / ICD-10 (WHO); ICD-11 where required |
-| Procedures (billing / clinical / inpatient) | CPT, HCPCS Level II / SNOMED CT / ICD-10-PCS |
-| Lab observations / document types | LOINC |
-| Clinical concepts (problems, findings, body sites, allergies) | SNOMED CT |
-| Medications | RxNorm (US); NDC (dispense identity); ATC (analytics) |
-| Units of measure | UCUM |
-| Vaccines | CVX (CDC); MVX (manufacturers) |
-
-## Validation
-- Hard-coded coded literals FORBIDDEN outside the Terminology module's seed data.
-- Never invent ICD/SNOMED/LOINC/CPT/HCPCS/RxNorm/CVX codes — confirm against the module's value sets (see [[ai-rules.domain]]).
-- Free-text storage where a coded vocabulary applies is a Forbidden Pattern.
-
-## 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` (project-managed subsets; expansions cached).
-
-## Related
-- [[fhir]] · [[domain-driven-design.domain]] · [[clinical-terms]] · [[testing.domain]] · [[ai-rules.domain]]

package/assets/docs/domainspecs/healthcare/testing.domain.md

@@ -1,15 +0,0 @@
-# Testing — Healthcare Domain Addenda
-
-> Technology base: [[testing]]. Commands: `/aw-spec-gate`.
-
-## FHIR & interop tests
-- FHIR endpoints MUST validate against the official **FHIR validator** + project IGs; profile changes ship with test updates in the **same commit** (see [[fhir]]).
-- FHIR projectors MUST have a round-trip test (`domain -> FHIR -> domain`).
-- Contract tests: FHIR validator + Inferno (or equiv) for US Core/the IG; HL7 v2 conformance against an internal corpus (see [[hl7]]); CloudEvents schema validation by every consumer harness (see [[eventing.domain]]).
-
-## Test data
-- MUST use the synthetic-PHI fixture library (`<SampleProjectName>.TestFixtures`); **production PHI in dev/test/demo/CI is FORBIDDEN** (see [[hipaa]]).
-- Coded values use sentinel constants (e.g. `TerminologyFixtures.IcdSampleHypertension`) — never invented ICD/SNOMED/LOINC/CPT codes (see [[terminology]], [[ai-rules.domain]]).
-
-## Related
-- [[testing]] · [[fhir]] · [[hl7]] · [[terminology]] · [[hipaa]] · [[ai-rules.domain]]

package/assets/docs/domainspecs/healthcare/vertical-slices.domain.md

@@ -1,18 +0,0 @@
-# Vertical Slices — Healthcare Domain Addenda
-
-> Technology base: [[vertical-slices]]. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
-
-## Interop adapters in the slice
-`{Module}/Interop/` carries the external-protocol adapters:
-```
-Fhir/    projectors, search-param handlers, IG profiles   (see [[fhir]])
-Hl7v2/   inbound parsers + outbound emitters              (see [[hl7]])
-Dicom/   DICOMweb adapters (Radiology only)               (see [[dicom]])
-```
-
-## Rules
-- FHIR resources live in a **parallel projection layer** and **MUST NOT** replace internal `Shared` DTOs (see [[fhir]]).
-- Domain DTOs (`PatientDto`, `EncounterDto`) — no setters, required `init`, base64 `RowVersionBase64`.
-
-## Related
-- [[vertical-slices]] · [[fhir]] · [[hl7]] · [[dicom]]

package/assets/docs/domainspecs/healthcare/zero-trust.domain.md

@@ -1,12 +0,0 @@
-# Zero-Trust — Healthcare Domain Addenda
-
-> Technology base: [[zero-trust]]. Commands: `/aw-spec-constitution`, `/aw-spec-specify`, `/aw-spec-gate`.
-
-## Rules
-- **PHI in transit MUST be TLS-encrypted**; at-rest encryption: see [[hipaa]], [[data-classification.domain]].
-- External IdP MUST be SMART-on-FHIR-capable; tokens/scopes enforced on every FHIR endpoint and propagated through the pipeline (see [[authorization.domain]], [[fhir]]).
-- IHE **ATNA** node authentication applies to inter-node communication (see [[auditing.domain]]).
-- Trace context MUST propagate across outbound **HL7v2 / DICOM / FHIR** calls (see [[eventing.domain]]).
-
-## Related
-- [[zero-trust]] · [[authorization.domain]] · [[auditing.domain]] · [[hipaa]] · [[fhir]]

package/assets/docs/domainspecs/pharma/ai-rules.domain.md

@@ -1,32 +0,0 @@
-# AI Operational Rules — Pharma Domain Addenda
-
-> Technology base: [[ai-rules]]. Commands: **ALL**.
-
-## Context & codes
-- FHIR types: use the **official FHIR .NET SDK**, version-matched (R4/R5) to the endpoint (see [[fhir]]).
-- Confirm coded values against the Terminology module's value sets; never invent NDC/UNII/RxNorm/SNOMED/ATC/UCUM codes (see [[terminology]], [[ndc]], [[atc]]).
-- Align aggregates to ISO IDMP concept boundaries, not ad-hoc shapes (see [[idmp]]).
-
-## Generation
-- `MedicinalProduct` is the Aggregate Root. Generate `NdcCode`/`ProductName`/`GenericName`/`Strength`/`DosageForm`/`RouteOfAdministration`/`AtcCode`/`MarketingStatus`/`PackageIdentifier` as **value objects**, and `ActiveIngredient`/`PackagingConfiguration`/`MarketingAuthorization` as **entities** (see [[domain-driven-design.domain]]).
-- A complete slice adds (when applicable): FHIR projector + FHIR-validator test, audit emission, version snapshot (see [[fhir]], [[auditing.domain]], [[persistence.domain]], [[testing.domain]]).
-- FHIR resources are projections — never a second FHIR write path bypassing the aggregate (see [[fhir]]).
-- Comments are reserved for regulatory/domain intent (generic rule in [[ai-rules]]).
-
-## Identifier & code safety
-- MUST NOT fabricate NDC values or Labeler Codes; MUST NOT invent ATC/UNII/RxNorm/SNOMED codes — use a sentinel constant (e.g. `TerminologyFixtures.AtcSample`) or the Terminology module (see [[testing.domain]], [[terminology]], [[ndc]], [[atc]]).
-- MUST attach a `ProvenanceRecord` on any external-import path (see [[data-provenance]]).
-
-## Security- & compliance-touching code
-- MUST NOT modify audit emitters, version-history writers, lifecycle-transition guards, or identifier-uniqueness checks without an explicit reviewer-attached prompt (see [[auditing.domain]], [[persistence.domain]], [[product-lifecycle.domain]], [[ndc]]).
-
-## Refusal conditions — extend [[ai-rules]]; refuse to:
-- Invent or hard-code NDC/ATC/UNII/RxNorm/SNOMED codes outside terminology seed data (see [[terminology]]).
-- Persist a product with an invalid NDC, invalid dosage form, invalid route, or unvalidated ATC code (see [[ndc]], [[terminology]], [[atc]]).
-- Hard-delete a `MedicinalProduct`, its history, or an `AuditRecord` (use lifecycle retirement / logical delete) (see [[persistence.domain]], [[auditing.domain]]).
-- Allow an invalid lifecycle transition or remove a transition guard (see [[product-lifecycle.domain]]).
-- Bypass Interop adapters by writing aggregates directly from an external feed (see [[hl7]], [[eventing.domain]]).
-- Suppress or weaken audit emission for create/modify/retire/identifier/classification changes (see [[auditing.domain]], [[regulatory-compliance]]).
-
-## Related
-- [[ai-rules]] · [[domain-driven-design.domain]] · [[ndc]] · [[idmp]] · [[atc]] · [[terminology]] · [[fhir]] · [[auditing.domain]] · [[persistence.domain]] · [[product-lifecycle.domain]] · [[data-provenance]] · [[testing.domain]]

package/assets/docs/domainspecs/pharma/api-versioning.domain.md

@@ -1,20 +0,0 @@
-# API Versioning — Pharma Domain Addenda (FHIR)
-
-> Technology base: [[api-versioning]]. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
-
-## FHIR versioning
-- R4 default; R5 **additive** under a versioned path (`/fhir/R5/...`).
-- Breaking changes to the Medication / MedicationKnowledge / Substance / Organization surface require a **new version path** + a published CapabilityStatement diff (see [[fhir]]).
-- FHIR list endpoints use Bundle/searchset semantics (`_count`, `_offset`/`_page`, `_total`).
-
-## NDC identifier stability
-- `NdcCode` is a **stable identifier** — never silently rewritten. A correction is an explicit, audited identifier-change emitting `ProductIdentifierChanged`, preserved in version history (see [[ndc]], [[auditing.domain]], [[persistence.domain]], [[eventing.domain]]). ATC reclassification is likewise a versioned, audited event (see [[atc]]).
-
-## Concurrency at the edge
-- FHIR resources honor `If-Match` via the aggregate's concurrency token → FHIR **weak** ETag at the projection boundary (see [[persistence.domain]]).
-
-## CapabilityStatement
-- Published for FHIR (beyond generic OpenAPI); regenerates cleanly in CI; diff reviewed for breaking changes (see [[fhir]], [[coding-standards.domain]]).
-
-## Related
-- [[api-versioning]] · [[fhir]] · [[ndc]] · [[atc]] · [[persistence.domain]] · [[eventing.domain]] · [[auditing.domain]] · [[coding-standards.domain]]