aw-spec-cli 0.1.4 → 0.1.6

package/assets/docs/domainspecs/UIVisualization/state-management.domain.md

@@ -1,67 +0,0 @@
-# State Management (CQRS analog) — UI Visualization Domain
-
-> The front-end read/write separation. NON-NEGOTIABLE.
-> Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## Read / write separation
-
-CQRS maps to the client store as **queries = selectors** and **commands = actions**:
-
-- **Queries (reads)** — components read slices of the Zustand store via the hook
-  (`const { compounds } = useDataStore()`). Reads are pure; no side effects in render.
-- **Commands (writes)** — every mutation is a **named store action**, never a raw `set` from a
-  component. Actions: `loadExcel(partial)`, `resetToSample()`, `toggleCurve(id)`,
-  `setSourceMode(mode, fileName)`.
-
-A component MUST NOT mutate store state directly — it dispatches an action, exactly as a backend
-endpoint dispatches a command via the mediator instead of touching the `DbContext`.
-
-## Store shape
-
-- A single `useDataStore` (Zustand) holds: the active **dataset** (the project's chart data), the
-  **source mode** (`'sample' | 'excel' | 'api'`), and any **view state** (e.g. selected series ids).
-- The store seeds from **sample data** so charts render on first paint with zero backend
-  (see [[data-source.domain]]).
-- Loading new data is a single command that swaps the dataset and flips `sourceMode` — charts
-  re-render reactively with no per-chart wiring.
-
-## Canonical example (agent reference)
-
-```ts
-// store/data-store.ts
-'use client'
-import { create } from 'zustand'
-import { SAMPLE } from '@/lib/sample-data'
-
-type SourceMode = 'sample' | 'excel' | 'api'
-
-interface DataStore {
-  dataset: typeof SAMPLE
-  sourceMode: SourceMode
-  // commands (writes) — the ONLY way to mutate
-  loadExcel: (partial: Partial<typeof SAMPLE>) => void
-  resetToSample: () => void
-}
-
-export const useDataStore = create<DataStore>((set) => ({
-  dataset: SAMPLE,
-  sourceMode: 'sample',
-  loadExcel: (partial) =>
-    set(s => ({ dataset: { ...s.dataset, ...partial }, sourceMode: 'excel' })),
-  resetToSample: () => set({ dataset: SAMPLE, sourceMode: 'sample' }),
-}))
-```
-
-## Rules
-
-- One store module (`store/data-store.ts`). Split into slices only when it exceeds ~150 lines.
-- Actions are the command surface — name them as verbs; keep them pure-ish (compute → `set`).
-- Cross-component data load may also broadcast a `window` `CustomEvent`
-  (`appweaver:excel-loaded`) — the front-end analog of a **domain event**.
-- No data fetching inside the store for Phase 1; the **data-source** layer owns ingest and hands
-  the result to a command (see [[data-source.domain]]).
-
-## Related
-- [[data-source.domain]] — where datasets come from
-- [[clean-architecture.domain]] — the data layer feeds pages, never imports charts
-- [[component-contracts.domain]]

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

@@ -1,52 +0,0 @@
-# Testing — UI Visualization Domain
-
-> Test profile for the viz front-end. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## What to test (priority order)
-
-1. **Adapters** (highest value) — pure mapping functions: domain type → generic props. Assert the
-   produced `series`/`arms`/`curves`/`matrix` and labels match the input. No DOM needed.
-2. **Data layer** — the Excel parser and any workbook→domain mapper: given a fixture workbook (or
-   row array), assert the parsed dataset (counts, fields, null handling, derived curves).
-3. **Store actions** — `loadExcel`, `resetToSample`, `toggleCurve` change state as specified
-   (see [[state-management.domain]]).
-4. **Smoke render** — each selected chart renders without throwing when given representative data
-   (mock `plotly.js-dist-min` so no real canvas is needed).
-
-## How
-
-- **Vitest** (or Jest) + **@testing-library/react** for component smoke tests.
-- **Mock Plotly**: `vi.mock('plotly.js-dist-min', () => ({ react: vi.fn(), purge: vi.fn() }))` —
-  assert the wrapper called `react` with the expected trace count, not pixels.
-- Adapters and parsers are plain functions — unit-test them directly, no mocks.
-- A `build` (type-check + `next build`) is the compile-time gate; keep it green.
-
-## Example (agent reference)
-
-```ts
-import { describe, it, expect } from 'vitest'
-import { compoundsToBubbleSeries } from '@/components/charts/CompoundScatterPlot'
-
-it('groups compounds by target into series with log-scaled y', () => {
-  const series = compoundsToBubbleSeries([
-    { name: 'A', target: 'EGFR', molecularWeight: 393, ic50_nM: 10, selectivityRatio: 40 },
-  ])
-  expect(series).toHaveLength(1)
-  expect(series[0].seriesLabel).toBe('EGFR')
-  expect(series[0].points[0].y).toBeCloseTo(1) // log10(10)
-})
-```
-
-> Tip: export the mapping function from the adapter (e.g. `compoundsToBubbleSeries`) so it is
-> unit-testable without rendering.
-
-## Rules
-
-- Don't assert on Plotly's internal DOM — assert on the **inputs** you hand Plotly.
-- One fixture workbook per project lives beside the parser tests; mirror the shipped
-  `public/sample-data.xlsx` columns.
-- Only test charts that are **selected** for the project (see [[domain-requirements]]).
-
-## Related
-- [[component-contracts.domain]] · [[state-management.domain]] · [[data-source.domain]] ·
-  [[coding-standards.domain]]

package/assets/docs/domainspecs/UIVisualization/ui-viz-terms.md

@@ -1,39 +0,0 @@
-# Ubiquitous Language — UI Visualization Domain
-
-> Shared vocabulary for the visualization front-end. Commands: `/aw-spec-specify`, `/aw-spec-clarify`.
-
-## Core terms
-
-- **Generic chart** — a domain-agnostic, props-driven Plotly component in
-  `components/charts/generic/`. Knows nothing about any project domain. The 10 in the catalog.
-- **Adapter** — a thin component mapping a project/domain type into a generic chart's props; lives
-  in `components/charts/` (not `generic/`). The only place domain vocabulary meets a chart.
-- **Base wrapper** — `PlotlyChart`; the single SSR-safe Plotly mount every chart renders through.
-- **Data source** — origin of chart data: `sample` (hard-coded), `excel` (client upload), or
-  `api` (Phase-2 REST). The store's `sourceMode`.
-- **Dataset** — the project's chart-ready data held in the store; the contract between data source
-  and charts.
-- **Command (action)** — a named store mutation (`loadExcel`, `resetToSample`, `toggleCurve`).
-- **Query (selector)** — a read of store state from a component via `useDataStore`.
-- **Chart selection** — the developer-specified subset of the catalog to scaffold (or "all plots").
-- **Fill-height** — responsive sizing: a chart with no `height` fills its flex parent.
-- **Series / arm / curve / panel / trace** — per-chart data groupings (see each `chart-*` file).
-- **meta / metadata** — open key/value bag for tooltip enrichment; never a typed domain field.
-
-## Chart friendly-name ↔ component
-
-| Friendly name(s) | Component |
-|---|---|
-| Heatmap | `Heatmap` |
-| Bubble / Bubble chart | `BubbleChart` |
-| S-Curve / Sigmoid / Dose-Response | `SCurveChart` |
-| Survival / Kaplan-Meier / KM / Retention | `SurvivalCurveChart` |
-| Volcano | `VolcanoPlot` |
-| Dim. Reduction / PCA / t-SNE / UMAP | `DimRedPlot` |
-| Parallel Coords / parcoords | `ParallelCoordinatesPlot` |
-| Violin / Distribution | `ViolinPlot` |
-| Network / Graph / Node-Edge | `NetworkGraph` |
-| Trellis / Facet / Small-multiples | `TrellisGrid` |
-
-## Related
-- [[domain-requirements]] · [[component-contracts.domain]] · [[charting-standards.domain]]

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

@@ -1,34 +0,0 @@
-# AI Operational Rules — Healthcare 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 ICD/SNOMED/LOINC/CPT codes (see [[terminology]]).
-
-## Generation
-- A complete slice adds a FHIR projector + FHIR-validator test when applicable (see [[fhir]], [[testing.domain]]).
-- Generated FHIR resources MUST honor declared IG profiles and pass the FHIR validator (see [[fhir]]).
-- Comments are reserved for clinical intent (generic rule in [[ai-rules]]).
-
-## PHI masking
-- MUST NOT log, echo, or commit any field of `Patient`/`Encounter`/`Observation`/`MedicationRequest`/`ClinicalNote`/`DiagnosticReport`/`Claim`/`Coverage` other than the strongly-typed ID.
-- Apply field-level redaction in every generated example payload (see [[data-classification.domain]], [[hipaa]]).
-
-## Tests
-- MUST use the synthetic-PHI fixture library (`<SampleProjectName>.TestFixtures`); never inline fabricated PHI.
-- Never invent ICD/SNOMED/LOINC/CPT/HCPCS/RxNorm/CVX codes — use a sentinel constant (see [[testing.domain]], [[terminology]]).
-
-## Security-touching code
-- MUST NOT modify authorization handlers, scope evaluators, consent checks, audit emitters, or encryption code without an explicit security-reviewer-attached prompt (see [[authorization.domain]], [[auditing.domain]], [[consent]]).
-- FHIR profile changes: regenerate the IG artifacts + CapabilityStatement in the **same commit** (see [[fhir]], [[api-versioning.domain]]).
-
-## Refusal conditions — extend [[ai-rules]]; refuse to:
-- Embed any PHI test fixture in code/config.
-- Disable a consent check globally.
-- Bypass Interop adapters by writing aggregates directly from an external feed (see [[hl7]], [[eventing.domain]]).
-- Generate de-identification logic without a documented method (Safe Harbor / Expert Determination) (see [[hipaa]]).
-- Return PHI in error messages, logs, or trace attributes (see [[data-classification.domain]]).
-
-## Related
-- [[ai-rules]] · [[fhir]] · [[terminology]] · [[hipaa]] · [[consent]] · [[data-classification.domain]] · [[auditing.domain]] · [[authorization.domain]] · [[testing.domain]]

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

@@ -1,17 +0,0 @@
-# API Versioning — Healthcare Domain Addenda (FHIR)
-
-> Technology base: [[api-versioning]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## FHIR versioning
-- R4 default; R5 is **additive** under a versioned path (`/fhir/R5/...`).
-- Breaking FHIR changes require a **new version path** + a published CapabilityStatement diff (see [[fhir]]).
-- FHIR list endpoints use Bundle/searchset semantics (`_count`, `_offset`/`_page`, `_total`).
-
-## 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/AsyncAPI); regenerates cleanly in CI; diff reviewed for breaking changes (see [[fhir]], [[coding-standards.domain]]).
-
-## Related
-- [[api-versioning]] · [[fhir]] · [[persistence.domain]] · [[coding-standards.domain]]

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

@@ -1,29 +0,0 @@
-# Auditing — Healthcare Domain Addenda (ATNA)
-
-> Technology base: [[auditing]]. NON-NEGOTIABLE. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## Setup
-- Auditing is **MANDATORY** for every PHI-bearing aggregate.
-- Enable via `.EnableAdvancedAuditing()` + `AddAuditing(... UseEfCoreAuditing(...).UseAppWeaverDataStore())`.
-- Audit tables: shared `AppWeaver.DataStore`, schema `Auditing`, prefix `Audit_`.
-- A **PHI-access-audit** pipeline behavior runs on every mediator request (see [[cqrs.domain]]).
-
-## Record (immutable)
-Every PHI read/mutation, authentication, consent change, export, and break-the-glass MUST emit:
-```
-{ timestamp, subjectId, subjectRole, patientId, action, resourceType,
-  resourceId, outcome, sourceIp, correlationId, reason }
-```
-
-## Audit-mandatory operations
-Every PHI read/write; every authentication; every consent change; every export (`$export`, bulk/report download); every break-the-glass; every privileged admin action; every IdP/role change. See [[authorization.domain]].
-
-## Retention & format
-- **Append-only**; retained **>= 6 years**; exportable as FHIR `AuditEvent` (see [[domain-driven-design.domain]], [[persistence.domain]]).
-
-## Telemetry & breach
-- **PHI, full SSN, payment-card numbers, government IDs MUST NEVER** appear in logs, metric labels, exception messages, or traces (see [[data-classification.domain]]).
-- Anomalous PHI access (volume spikes, off-hours mass reads, repeated denials) emits **Critical** alerts (see [[hipaa]]).
-
-## Related
-- [[auditing]] · [[hipaa]] · [[data-classification.domain]] · [[authorization.domain]] · [[consent]] · [[fhir]] · [[cqrs.domain]] · [[persistence.domain]]

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

@@ -1,26 +0,0 @@
-# Authorization — Healthcare Domain Addenda
-
-> Technology base: [[authorization]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## Roles
-`SystemAdmin`, `ComplianceOfficer`, `Physician`, `Nurse`, `LabTechnician`, `Radiologist`, `Pharmacist`, `BillingClerk`, `FrontDesk`, `Patient`, `ExternalSystem`, `ResearchAnalyst` (de-identified scope only). Per-route matrix: `docs/security/authorization-matrix.md`.
-
-## SMART-on-FHIR scopes
-- Scopes (`patient/*.read`, `user/Observation.read`, `system/*.write`, `launch/patient`) MUST be enforced on **every FHIR endpoint**.
-- App launch (EHR + standalone): **PKCE mandatory; implicit flow FORBIDDEN** (see [[fhir]]).
-
-## PHI minimum-necessary
-- The PHI-access pipeline returns only fields the caller's role + scopes authorize; field-level redaction lives in projection extensions (see [[hipaa]], [[data-classification.domain]]).
-
-## Consent & break-the-glass
-- Pipeline checks **consent state** before releasing PHI outside the treating-provider context (see [[consent]]).
-- Break-the-glass = explicit emergency-access command: documented reason + high-priority audit + real-time alert (see [[consent]], [[auditing.domain]]).
-
-## Audit-mandatory
-Every PHI read/write, authentication, consent change, export, break-the-glass, privileged admin action, IdP/role change (see [[auditing.domain]]).
-
-## Anonymous allowlist
-- Adds `/metadata` (FHIR CapabilityStatement) to the generic allowlist (see [[fhir]]).
-
-## Related
-- [[authorization]] · [[hipaa]] · [[consent]] · [[auditing.domain]] · [[data-classification.domain]] · [[fhir]]

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

@@ -1,20 +0,0 @@
-# Glossary — Clinical Terms
-
-> Ubiquitous language for clinical aggregates. Commands: `/aw-spec-specify`, `/aw-spec-clarify`, `/aw-spec-plan`. See [[domain-driven-design.domain]] (modeling) + [[terminology]] (coding).
-
-| Term | Definition |
-|---|---|
-| **MRN** | Patient identifier, **unique per tenant** on `Patient` (Patients); cross-referenced via PIX/PDQ (see [[integration-terms]]). |
-| **Encounter** | Clinical interaction (inpatient/outpatient/emergency); owns Admission/Transfer/Discharge; not Closeable with open Orders/Results/ChargeItems/unsigned ClinicalNotes (Encounters). |
-| **Observation** | A discrete measurement/finding — vitals/social history (EMR) or lab result (Lab); coded LOINC/SNOMED (see [[terminology]]). |
-| **Coverage** | Patient insurance record (Insurance); required (or documented self-pay) before admission. |
-| **PractitionerRole** | A Practitioner's role within an Organization/Location (Identity) — drives role-based auth (see [[authorization.domain]]). |
-| **CarePlan** | A planned set of clinical activities (EMR). |
-| **DiagnosticReport** | A finalized result set with interpretation — radiology (Radiology) or lab (Lab). |
-| **ClinicalNote** | Documentation entry; once **Signed** immutable; corrections are addenda; deletion forbidden (supersede via Amend). |
-| **ProblemList / AllergyIntolerance / MedicationStatement / Immunization / Procedure / ServiceRequest** | EMR aggregates; coded SNOMED/ICD/RxNorm/CVX as applicable. |
-| **MedicationRequest / MedicationDispense / MedicationAdministration** | Pharmacy aggregates; dispense blocked on allergy/interaction/contraindication without documented override. |
-| **Consent** | First-class aggregate governing PHI disclosure; withdrawal blocks disclosure immediately (see [[consent]]). |
-
-## Related
-- [[integration-terms]] · [[domain-driven-design.domain]] · [[terminology]] · [[fhir]]

package/assets/docs/domainspecs/healthcare/coding-standards.domain.md

@@ -1,26 +0,0 @@
-# Coding Standards — Healthcare Domain Addenda
-
-> Technology base: [[coding-standards]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## Coded value objects
-- Follow the FHIR pattern: `Codeable`, `Coding`, `Quantity`, `Period`, `Range`, `Ratio`, `Identifier`, `HumanName`, `Address`, `ContactPoint` (see [[terminology]]).
-- The Domain may additionally throw `ConsentDeniedException` (see [[consent]]).
-
-## Forbidden patterns — extend [[coding-standards]]
-- **H1.** Hard delete of any clinical/financial/audit/PHI-bearing aggregate (see [[persistence.domain]]).
-- **H2.** Hard-coded IdP issuer / FHIR server / HL7 endpoint URLs, or PHI test fixtures, in source.
-- **H3.** Logging/emitting any PHI element, full SSN/government ID (see [[data-classification.domain]]).
-- **H4.** Storing patient data (names, MRNs, DOBs, diagnoses, meds, labs, imaging) as free text when a coded vocabulary applies (see [[terminology]]).
-- **H5.** A second FHIR write path bypassing the canonical aggregate (see [[fhir]]).
-- **H6.** Storing/transmitting PHI to any non-production environment (see [[hipaa]]).
-- **H7.** FHIR errors not using `OperationOutcome` with HTTP 422 (see [[fhir]]).
-
-## Quality gates — extend [[coding-standards]]
-- **HG1.** FHIR CapabilityStatement regenerates cleanly; diff reviewed (see [[fhir]]).
-- **HG2.** FHIR validator passes for every modified resource/profile/example.
-- **HG3.** Grep: no PHI string literals in tests outside sanctioned fixtures; no MediatR/AutoMapper.
-- **HG4.** PHI-logging analyzer passes — no Patient/Encounter/Observation/MedicationRequest field logged except the ID (see [[data-classification.domain]]).
-- **HG5.** Security-reviewer sign-off for any PHI-access change.
-
-## Related
-- [[coding-standards]] · [[terminology]] · [[fhir]] · [[hipaa]] · [[consent]] · [[data-classification.domain]] · [[persistence.domain]]

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

@@ -1,166 +0,0 @@
-# Healthcare Domain — Command → Rule-File Map
-
-Per-AW-Spec-command list of the **healthcare domain** rule files in this folder.
-Technology standards already auto-load inside each command; the files below are the
-domain-specific ones to load **in addition** for a healthcare project.
-
-- All paths are workspace-relative and live in this folder: `docs/domainspecs/healthcare/`.
-- A skill can read this file and load every path under the matching command heading.
-- This file is the **canonical source** for the healthcare domain mapping;
-  `/aw-spec-select-domain` selects this folder as active.
-
----
-
-## /aw-spec-constitution
-- docs/domainspecs/healthcare/domain-requirements.md
-- docs/domainspecs/healthcare/ai-rules.domain.md
-
-## /aw-spec-specify
-- docs/domainspecs/healthcare/domain-requirements.md
-- docs/domainspecs/healthcare/clinical-terms.md
-- docs/domainspecs/healthcare/integration-terms.md
-- docs/domainspecs/healthcare/domain-driven-design.domain.md
-- docs/domainspecs/healthcare/fhir.md
-- docs/domainspecs/healthcare/hl7.md
-- docs/domainspecs/healthcare/dicom.md
-- docs/domainspecs/healthcare/terminology.md
-- docs/domainspecs/healthcare/hipaa.md
-- docs/domainspecs/healthcare/consent.md
-- docs/domainspecs/healthcare/data-classification.domain.md
-- docs/domainspecs/healthcare/ai-rules.domain.md
-
-## /aw-spec-clarify
-- docs/domainspecs/healthcare/domain-driven-design.domain.md
-- docs/domainspecs/healthcare/hl7.md
-- docs/domainspecs/healthcare/hipaa.md
-- docs/domainspecs/healthcare/consent.md
-- docs/domainspecs/healthcare/clinical-terms.md
-- docs/domainspecs/healthcare/integration-terms.md
-
-## /aw-spec-plan
-- docs/domainspecs/healthcare/folder-structure.domain.md
-- docs/domainspecs/healthcare/cqrs.domain.md
-- docs/domainspecs/healthcare/vertical-slices.domain.md
-- docs/domainspecs/healthcare/persistence.domain.md
-- docs/domainspecs/healthcare/testing.domain.md
-- docs/domainspecs/healthcare/eventing.domain.md
-- docs/domainspecs/healthcare/domain-driven-design.domain.md
-- docs/domainspecs/healthcare/fhir.md
-- docs/domainspecs/healthcare/hl7.md
-- docs/domainspecs/healthcare/dicom.md
-- docs/domainspecs/healthcare/terminology.md
-- docs/domainspecs/healthcare/hipaa.md
-- docs/domainspecs/healthcare/consent.md
-- docs/domainspecs/healthcare/zero-trust.domain.md
-- docs/domainspecs/healthcare/authorization.domain.md
-- docs/domainspecs/healthcare/auditing.domain.md
-- docs/domainspecs/healthcare/data-classification.domain.md
-- docs/domainspecs/healthcare/coding-standards.domain.md
-- docs/domainspecs/healthcare/dependency-policy.domain.md
-- docs/domainspecs/healthcare/api-versioning.domain.md
-- docs/domainspecs/healthcare/ai-rules.domain.md
-
-## /aw-spec-tasks
-- docs/domainspecs/healthcare/folder-structure.domain.md
-- docs/domainspecs/healthcare/vertical-slices.domain.md
-- docs/domainspecs/healthcare/cqrs.domain.md
-- docs/domainspecs/healthcare/persistence.domain.md
-- docs/domainspecs/healthcare/testing.domain.md
-- docs/domainspecs/healthcare/eventing.domain.md
-- docs/domainspecs/healthcare/domain-driven-design.domain.md
-- docs/domainspecs/healthcare/fhir.md
-- docs/domainspecs/healthcare/hl7.md
-- docs/domainspecs/healthcare/authorization.domain.md
-- docs/domainspecs/healthcare/auditing.domain.md
-- docs/domainspecs/healthcare/coding-standards.domain.md
-- docs/domainspecs/healthcare/ai-rules.domain.md
-
-## /aw-spec-analyze
-- docs/domainspecs/healthcare/hl7.md
-- docs/domainspecs/healthcare/hipaa.md
-- docs/domainspecs/healthcare/auditing.domain.md
-- docs/domainspecs/healthcare/coding-standards.domain.md
-- docs/domainspecs/healthcare/ai-rules.domain.md
-
-## /aw-spec-implement
-- docs/domainspecs/healthcare/folder-structure.domain.md
-- docs/domainspecs/healthcare/vertical-slices.domain.md
-- docs/domainspecs/healthcare/cqrs.domain.md
-- docs/domainspecs/healthcare/persistence.domain.md
-- docs/domainspecs/healthcare/testing.domain.md
-- docs/domainspecs/healthcare/eventing.domain.md
-- docs/domainspecs/healthcare/domain-driven-design.domain.md
-- docs/domainspecs/healthcare/fhir.md
-- docs/domainspecs/healthcare/hl7.md
-- docs/domainspecs/healthcare/terminology.md
-- docs/domainspecs/healthcare/hipaa.md
-- docs/domainspecs/healthcare/consent.md
-- docs/domainspecs/healthcare/authorization.domain.md
-- docs/domainspecs/healthcare/auditing.domain.md
-- docs/domainspecs/healthcare/data-classification.domain.md
-- docs/domainspecs/healthcare/zero-trust.domain.md
-- docs/domainspecs/healthcare/coding-standards.domain.md
-- docs/domainspecs/healthcare/dependency-policy.domain.md
-- docs/domainspecs/healthcare/api-versioning.domain.md
-- docs/domainspecs/healthcare/ai-rules.domain.md
-
-## /aw-spec-fast-implement
-
-> Fast path that collapses plan + tasks + analyze + implement into one pass. This list is the
-> **deduplicated union** of those four commands' headings above (here, equal to `/aw-spec-plan`).
-> Load it **once** for the whole pass — do not reload per phase.
-
-- docs/domainspecs/healthcare/folder-structure.domain.md
-- docs/domainspecs/healthcare/cqrs.domain.md
-- docs/domainspecs/healthcare/vertical-slices.domain.md
-- docs/domainspecs/healthcare/persistence.domain.md
-- docs/domainspecs/healthcare/testing.domain.md
-- docs/domainspecs/healthcare/eventing.domain.md
-- docs/domainspecs/healthcare/domain-driven-design.domain.md
-- docs/domainspecs/healthcare/fhir.md
-- docs/domainspecs/healthcare/hl7.md
-- docs/domainspecs/healthcare/dicom.md
-- docs/domainspecs/healthcare/terminology.md
-- docs/domainspecs/healthcare/hipaa.md
-- docs/domainspecs/healthcare/consent.md
-- docs/domainspecs/healthcare/zero-trust.domain.md
-- docs/domainspecs/healthcare/authorization.domain.md
-- docs/domainspecs/healthcare/auditing.domain.md
-- docs/domainspecs/healthcare/data-classification.domain.md
-- docs/domainspecs/healthcare/coding-standards.domain.md
-- docs/domainspecs/healthcare/dependency-policy.domain.md
-- docs/domainspecs/healthcare/api-versioning.domain.md
-- docs/domainspecs/healthcare/ai-rules.domain.md
-
-## /aw-spec-minimal-implementation
-
-> Single-step set for healthcare — the **per-domain knob** (edit freely). `/aw-spec-minimal-implementation`
-> loads these to interpret and implement the requirement in one pass; genuinely-external runtime
-> services (terminology server, FHIR endpoint) are stubbed behind ports. For an audited build use
-> `## /aw-spec-fast-implement`.
-
-- docs/domainspecs/healthcare/clinical-terms.md
-- docs/domainspecs/healthcare/domain-driven-design.domain.md
-- docs/domainspecs/healthcare/folder-structure.domain.md
-- docs/domainspecs/healthcare/vertical-slices.domain.md
-- docs/domainspecs/healthcare/fhir.md
-- docs/domainspecs/healthcare/hl7.md
-- docs/domainspecs/healthcare/terminology.md
-- docs/domainspecs/healthcare/hipaa.md
-- docs/domainspecs/healthcare/ai-rules.domain.md
-
----
-
-## Quick reference (command → file count)
-
-| Command | Domain rule files |
-|---|---|
-| /aw-spec-constitution | 2 |
-| /aw-spec-specify | 12 |
-| /aw-spec-clarify | 6 |
-| /aw-spec-plan | 21 |
-| /aw-spec-tasks | 13 |
-| /aw-spec-analyze | 5 |
-| /aw-spec-implement | 20 |
-| /aw-spec-fast-implement | 21 |
-| /aw-spec-minimal-implementation | 9 |

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

@@ -1,19 +0,0 @@
-# Consent Standards
-
-> NON-NEGOTIABLE. Commands: `/aw-spec-specify`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## 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-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## 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-specify`, `/aw-spec-plan`, `/aw-spec-implement`.
-
-## 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-plan`, `/aw-spec-implement`.
-
-## 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-specify`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## 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`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## 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]]