aw-spec-cli 0.1.4 → 0.1.5

package/assets/docs/UI.Visualization/unpack-reference-foundation.sh

@@ -1,218 +0,0 @@
-#!/usr/bin/env bash
-#
-# unpack-reference-foundation.sh — bash/macOS port of unpack-reference-foundation.ps1
-#
-# SYNOPSIS
-#   Unpack an AW-Spec reference pack file into a target project, renaming the
-#   sentinel app name to the caller's app name.
-#
-# DESCRIPTION
-#   Reads --pack-file (produced by pack-reference-foundation.sh/.ps1), takes the sentinel
-#   from its header (override with --sentinel), derives four case forms of the target app
-#   name, and writes every file block to --out-dir with the sentinel rewritten in both file
-#   CONTENTS and file/dir PATHS. Text blocks are rewritten and written as UTF-8; base64
-#   blocks are decoded as-is. Refuses to overwrite existing files unless --force.
-#
-# EXAMPLE
-#   ./unpack-reference-foundation.sh \
-#       --pack-file ./UI.Visualization.Reference.pack.txt \
-#       --target-app-name MyApp \
-#       --out-dir ../../
-#
-set -euo pipefail
-
-# ------------------------------------------------------------------ defaults ---
-PACK_FILE=''
-TARGET_APP_NAME=''
-OUT_DIR='.'
-SENTINEL=''
-FORCE=0
-DRYRUN=0
-
-usage() {
-  cat >&2 <<'EOF'
-Usage: unpack-reference-foundation.sh --pack-file <file> --target-app-name <name>
-                                      [--out-dir <dir>] [--sentinel <name>]
-                                      [--force] [--dry-run]
-
-  -p, --pack-file <file>        Reference pack file to unpack               (required)
-  -t, --target-app-name <name>  New app name to rename the sentinel into    (required)
-  -o, --out-dir <dir>           Output root                   (default: .)
-      --sentinel <name>         Override the sentinel from the pack header
-      --force                   Overwrite files that already exist
-      --dry-run                 List what would be written, write nothing
-  -h, --help                    Show this help
-
-Positional fallback: unpack-reference-foundation.sh <pack-file> <target-app-name> [out-dir]
-EOF
-}
-
-# -------------------------------------------------------------- arg parsing ---
-while [ $# -gt 0 ]; do
-  case "$1" in
-    -p|--pack-file)        PACK_FILE="${2:?--pack-file needs a value}";             shift 2 ;;
-    -t|--target-app-name)  TARGET_APP_NAME="${2:?--target-app-name needs a value}"; shift 2 ;;
-    -o|--out-dir)          OUT_DIR="${2:?--out-dir needs a value}";                 shift 2 ;;
-    --sentinel)            SENTINEL="${2:?--sentinel needs a value}";               shift 2 ;;
-    --force)               FORCE=1; shift ;;
-    --dry-run)             DRYRUN=1; shift ;;
-    -h|--help)             usage; exit 0 ;;
-    --)                    shift; break ;;
-    -*)                    echo "Error: unknown option: $1" >&2; usage; exit 2 ;;
-    *)
-      if   [ -z "$PACK_FILE" ];       then PACK_FILE="$1"
-      elif [ -z "$TARGET_APP_NAME" ]; then TARGET_APP_NAME="$1"
-      else OUT_DIR="$1"
-      fi
-      shift ;;
-  esac
-done
-
-[ -n "$PACK_FILE" ]       || { echo "Error: --pack-file is required." >&2; usage; exit 2; }
-[ -n "$TARGET_APP_NAME" ] || { echo "Error: --target-app-name is required." >&2; usage; exit 2; }
-[ -f "$PACK_FILE" ]       || { echo "Error: pack file not found: $PACK_FILE" >&2; exit 1; }
-
-case "$TARGET_APP_NAME" in
-  *[!A-Za-z0-9._-]*)
-    echo "Error: --target-app-name may contain only letters, digits, '.', '_' or '-': $TARGET_APP_NAME" >&2
-    exit 2 ;;
-esac
-
-# ------------------------------------------------ sentinel from header --------
-if [ -z "$SENTINEL" ]; then
-  SENTINEL="$(LC_ALL=C sed -n 's/^#[[:space:]]*sentinel:[[:space:]]*\(.*[^[:space:]]\)[[:space:]]*$/\1/p' "$PACK_FILE" | head -n1)"
-fi
-[ -n "$SENTINEL" ] || { echo "Error: Sentinel not found in pack header; supply it with --sentinel." >&2; exit 1; }
-
-# ------------------------------------------------ derive case forms -----------
-to_lower() { printf '%s' "$1" | LC_ALL=C tr '[:upper:]' '[:lower:]'; }
-
-S_DOT="$SENTINEL";               T_DOT="$TARGET_APP_NAME"
-S_UND="${SENTINEL//./_}";        T_UND="${TARGET_APP_NAME//./_}"
-s_low="$(to_lower "$SENTINEL")"; t_low="$(to_lower "$TARGET_APP_NAME")"
-S_HYP="${s_low//./-}";           T_HYP="${t_low//./-}"
-S_LDOT="$s_low";                 T_LDOT="$t_low"
-
-FROM=(); TO=()
-add_form() {
-  local from="$1" to="$2" e
-  [ -n "$from" ] || return 0
-  [ "$from" = "$to" ] && return 0
-  if [ "${#FROM[@]}" -gt 0 ]; then
-    for e in "${FROM[@]}"; do [ "$e" = "$from" ] && return 0; done
-  fi
-  FROM+=("$from"); TO+=("$to")
-}
-add_form "$S_DOT"  "$T_DOT"
-add_form "$S_UND"  "$T_UND"
-add_form "$S_HYP"  "$T_HYP"
-add_form "$S_LDOT" "$T_LDOT"
-
-# Sort indices by FROM length descending
-ORDER=()
-{
-  local_n="${#FROM[@]}"
-  used=(); for ((k = 0; k < local_n; k++)); do used[$k]=0; done
-  for ((pass = 0; pass < local_n; pass++)); do
-    best=-1; bestlen=-1
-    for ((j = 0; j < local_n; j++)); do
-      if [ "${used[$j]}" -eq 0 ] && [ "${#FROM[$j]}" -gt "$bestlen" ]; then
-        bestlen="${#FROM[$j]}"; best="$j"
-      fi
-    done
-    used[$best]=1; ORDER+=("$best")
-  done
-}
-
-REPL_OUT=''
-apply_repl() {
-  local text="$1" idx from to
-  if [ "${#ORDER[@]}" -gt 0 ]; then
-    for idx in "${ORDER[@]}"; do
-      from="${FROM[$idx]}"; to="${TO[$idx]}"
-      text="${text//"$from"/$to}"
-    done
-  fi
-  REPL_OUT="$text"
-}
-
-# ------------------------------------------------ output root ----------------
-[ -d "$OUT_DIR" ] || mkdir -p "$OUT_DIR"
-OUT_ROOT="$(cd "$OUT_DIR" && pwd -P)"
-
-# ------------------------------------------------ base64 decoder (portable) --
-B64D=()
-if   printf 'aGk=' | base64 -d        >/dev/null 2>&1; then B64D=(base64 -d)
-elif printf 'aGk=' | base64 -D        >/dev/null 2>&1; then B64D=(base64 -D)
-elif printf 'aGk=' | base64 --decode  >/dev/null 2>&1; then B64D=(base64 --decode)
-else                                                        B64D=(openssl base64 -d -A)
-fi
-
-# ------------------------------------------------ parse file blocks ----------
-rels=(); encs=(); contents=()
-in_block=0; cur_rel=''; cur_enc=''; cur_content=''; first_line=1
-file_re='^<<<FILE path="([^"]+)"( encoding="([^"]+)")?>>>[[:space:]]*$'
-
-while IFS= read -r line || [ -n "$line" ]; do
-  line="${line%$'\r'}"
-  if [ "$in_block" -eq 0 ]; then
-    if [[ "$line" =~ $file_re ]]; then
-      cur_rel="${BASH_REMATCH[1]}"
-      cur_enc="${BASH_REMATCH[3]:-}"
-      in_block=1; first_line=1; cur_content=''
-    fi
-  else
-    if [ "$line" = '<<<ENDFILE>>>' ]; then
-      rels+=("$cur_rel"); encs+=("$cur_enc"); contents+=("$cur_content")
-      in_block=0
-    elif [ "$first_line" -eq 1 ]; then
-      cur_content="$line"; first_line=0
-    else
-      cur_content="$cur_content"$'\n'"$line"
-    fi
-  fi
-done < "$PACK_FILE"
-
-[ "${#rels[@]}" -gt 0 ] || { echo "Error: No <<<FILE>>> blocks found in pack: $PACK_FILE" >&2; exit 1; }
-
-# ------------------------------------------------ resolve destinations -------
-dests=()
-for ((i = 0; i < ${#rels[@]}; i++)); do
-  apply_repl "${rels[$i]}"
-  dests+=("$OUT_ROOT/$REPL_OUT")
-done
-
-# ------------------------------------------------ conflict guard -------------
-if [ "$FORCE" -eq 0 ] && [ "$DRYRUN" -eq 0 ]; then
-  conflicts=()
-  for d in "${dests[@]}"; do [ -e "$d" ] && conflicts+=("$d"); done
-  if [ "${#conflicts[@]}" -gt 0 ]; then
-    echo "Error: Refusing to overwrite existing files (re-run with --force):" >&2
-    printf '  %s\n' "${conflicts[@]}" >&2
-    exit 1
-  fi
-fi
-
-# ------------------------------------------------ write ----------------------
-written=0
-for ((i = 0; i < ${#rels[@]}; i++)); do
-  rel="${rels[$i]}"; enc="${encs[$i]}"; dest="${dests[$i]}"
-  if [ "$DRYRUN" -eq 1 ]; then
-    echo "WOULD WRITE  $rel  ->  $dest"
-    continue
-  fi
-  mkdir -p "$(dirname "$dest")"
-  if [ "$enc" = 'base64' ]; then
-    printf '%s' "${contents[$i]}" | tr -d '[:space:]' | "${B64D[@]}" > "$dest"
-  else
-    apply_repl "${contents[$i]}"
-    printf '%s' "$REPL_OUT" > "$dest"
-  fi
-  written=$((written + 1))
-done
-
-if [ "$DRYRUN" -eq 1 ]; then
-  echo "DryRun: ${#rels[@]} file(s) would be written to $OUT_ROOT (sentinel '$SENTINEL' -> '$TARGET_APP_NAME')."
-else
-  echo "Unpacked $written file(s) to $OUT_ROOT (sentinel '$SENTINEL' -> '$TARGET_APP_NAME')."
-fi

package/assets/docs/command.txt

@@ -1,295 +0,0 @@
-================================================================================
-AW-SPEC COMMAND SHEET — Feature: Patient Registration  (Patient / RegisterPatient)
-================================================================================
-Run these in order, one per turn, from /aw-spec-specify to /aw-spec-implement.
-All six numbered steps are REQUIRED for this feature — clarify and analyze are
-correctness gates, not optional extras (see their sections for why).
-
-CONVENTIONS USED BELOW
-- @paths are Claude Code file mentions; they are inlined as context. Paths are
-  relative to the workspace root (e:\Work\Company\Project), so they start with `docs/...`.
-- "MANUAL TEXT" = the plain prompt you type as part of the command.
-- The spec folder convention is specs/<Aggregate>/<Feature>; starting the feature
-  description with the token `Patient/RegisterPatient` makes /aw-spec-specify create
-  specs/Patient/RegisterPatient/ and pin it in .aw-spec/feature.json. Every later
-  command (clarify/plan/tasks/analyze/implement) auto-resolves that folder from
-  feature.json — you do NOT pass the aggregate/feature token again.
-- The constitution (.aw-spec/memory/constitution.md) AND the domain-agnostic technical
-  standards are AUTO-LOADED by each command (see each SKILL.md) — you
-  do NOT pass those with @.
-- The DOMAIN-SPECIFIC files shown per step come from the active domain's comandrulemap.md
-  (active domain = .aw-spec/domain.json, set via /aw-spec-select-domain). Each command offers
-  them in a selection box (Select all / Pick a subset / None); the @ mentions below are an
-  equivalent, OPTIONAL shortcut and are always loaded in addition to the auto-loaded set.
-
-INTEROPERABILITY SCOPE FOR THIS FEATURE
-  Patient registration is an interoperability-heavy feature. It MUST support:
-   - Inbound HL7 v2 ADT^A04 (Register a Patient) via an Interop/Hl7v2 adapter that
-     converts the message to the RegisterPatientCommand (never writes to the aggregate
-     directly), over MLLP, with ACK handling.
-   - Outbound ADT emission on PatientRegisteredEvent (egress adapter).
-   - External FHIR R4 Patient projection + PIX/PDQ identity cross-reference.
-  Therefore docs/domainspecs/healthcare/hl7.md and the eventing docs are part of the context from
-  specify through implement.
-
-SETUP (one-time per project) — set the active domain
-  /aw-spec-select-domain              (lists docs/domainspecs/ folders; writes .aw-spec/domain.json)
-  /aw-spec-select-domain healthcare   (or set it directly)
-  -> For this demo the domain is `healthcare` (already set). If the domain is unset or its
-     comandrulemap.md is missing, every command first asks "Continue without domain rules?
-     (Continue / Exit)" before running.
-
-PREREQUISITE (one-time, only if the constitution has not been ratified yet)
-  /aw-spec-constitution @docs/healthcare-constitution.md @docs/domainspecs/healthcare/domain-requirements.md
-  -> docs/technology-constitution.md auto-loads (technology base); pass only the domain addenda.
-  -> Ratifies .aw-spec/memory/constitution.md. Not part of the per-feature loop.
-
-
-================================================================================
-STEP 1 — /aw-spec-specify   (create the feature spec)
-================================================================================
-PURPOSE
-  Create specs/Patient/RegisterPatient/spec.md (WHAT/WHY, no implementation detail)
-  and pin the folder in .aw-spec/feature.json. A git feature branch is created by the
-  before_specify hook.
-
-CONTEXT FILES TO ADD
-  docs/domainspecs/healthcare/domain-requirements.md          (bounded contexts: Patient aggregates)
-  docs/domainspecs/healthcare/clinical-terms.md             (MRN, Encounter, Coverage, ...)
-  docs/domainspecs/healthcare/integration-terms.md          (FHIR, HL7, PIX/PDQ, ATNA, ADT)
-  docs/domainspecs/healthcare/domain-driven-design.domain.md  (Patient invariants)
-  docs/domainspecs/healthcare/fhir.md                          (Patient FHIR projection)
-  docs/domainspecs/healthcare/hl7.md                           (HL7 v2 ADT ingestion/egress)  <-- HL7
-  docs/domainspecs/healthcare/dicom.md                         (imaging identifiers; optional for registration)
-  docs/domainspecs/healthcare/terminology.md                   (coded fields)
-  docs/domainspecs/healthcare/hipaa.md                          (PHI / minimum-necessary)
-  docs/domainspecs/healthcare/consent.md                        (Consent at registration)
-  docs/domainspecs/healthcare/data-classification.domain.md   (PHI/PII categories)
-  docs/domainspecs/healthcare/ai-rules.domain.md              (PHI masking, no invented codes)
-
-COMMAND (copy-paste, single line)
-/aw-spec-specify Patient/RegisterPatient Register a new patient into the master patient index. Capture demographics (legal HumanName, date of birth, administrative sex, contact points, address) and assign a tenant-unique MRN. Invariants: MRN is unique per tenant; date-of-birth must not be in the future; minimum-necessary projection by role/scope. Interoperability: inbound HL7 v2 ADT^A04 (Register a Patient) messages MUST be ingested through an Interop/Hl7v2 adapter that converts to the RegisterPatientCommand (no direct aggregate writes) over MLLP with ACK handling, and an outbound ADT emitter fires on PatientRegisteredEvent; also expose an external FHIR R4 Patient projection and PIX/PDQ identity cross-reference. Surfaces: internal REST POST /patients returning the created Patient, the FHIR R4 Patient endpoint, and the HL7 v2 ADT ingress channel. Every PHI read/write must produce an ATNA audit record. Out of scope: patient merge, portal self-registration. @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
-
-MANUAL TEXT (the prompt portion, for reference)
-  Patient/RegisterPatient Register a new patient into the master patient index. Capture
-  demographics (legal HumanName, date of birth, administrative sex, contact points,
-  address) and assign a tenant-unique MRN. Optionally link an insurance Coverage and
-  capture initial patient Consent. Invariants: MRN is unique per tenant; date-of-birth
-  must not be in the future; minimum-necessary projection by role/scope.
-  Interoperability: inbound HL7 v2 ADT^A04 (Register a Patient) messages MUST be ingested
-  through an Interop/Hl7v2 adapter that converts to the RegisterPatientCommand (no direct
-  aggregate writes) over MLLP with ACK handling, and an outbound ADT emitter fires on
-  PatientRegisteredEvent; also expose an external FHIR R4 Patient projection and PIX/PDQ
-  identity cross-reference. Surfaces: internal REST POST /patients returning the created
-  PatientDto with an ETag, the FHIR R4 Patient endpoint, and the HL7 v2 ADT ingress
-  channel. Every PHI read/write must produce an ATNA audit record. Out of scope: patient
-  merge, portal self-registration.
-
-NOTES
-  - The leading `Patient/RegisterPatient` token sets the spec folder; keep PascalCase.
-  - Expect output: SPEC_FILE = specs/Patient/RegisterPatient/spec.md.
-
-
-================================================================================
-STEP 2 — /aw-spec-clarify   (REQUIRED — feature-correctness gate)
-================================================================================
-WHY THIS MATTERS (do not skip)
-  Clarify finds underspecified areas and asks up to 5 targeted questions, then writes the
-  answers back into spec.md. Building plan/tasks/code on an ambiguous spec is the most
-  expensive mistake in the pipeline — for a PHI + HL7 feature the ambiguities have real
-  cost. Resolve at least:
-   - HL7 scope: only ADT^A04, or also A28 (add person) / A31 (update) / A08 (update info)?
-     Which MSH sending/receiving apps? MLLP vs file drop? ACK mode (AA/AE/AR) and NAK on
-     duplicate MRN?
-   - Identity: who assigns the MRN (this system vs source)? PIX/PDQ matching rules and
-     duplicate/merge-candidate handling on inbound ADT.
-   - Consent: is Consent mandatory at registration or optional? purpose-of-use default.
-   - Demographics: required vs optional fields; terminology bindings (administrative sex,
-     marital status); multiple-birth/aliases.
-   - Coverage: required at registration or deferred.
-  Re-run until no high-impact (scope/PHI/interop) ambiguity remains.
-
-CONTEXT FILES TO ADD
-  docs/domainspecs/healthcare/domain-driven-design.domain.md
-  docs/domainspecs/healthcare/hl7.md                          (HL7 ADT clarifications)  <-- HL7
-  docs/domainspecs/healthcare/hipaa.md
-  docs/domainspecs/healthcare/consent.md
-  docs/domainspecs/healthcare/clinical-terms.md
-  docs/domainspecs/healthcare/integration-terms.md
-
-COMMAND
-/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
-
-MANUAL TEXT
-  (none — answer the questions it asks; the answers are written back into spec.md)
-
-
-================================================================================
-STEP 3 — /aw-spec-plan   (create the implementation plan / design)
-================================================================================
-PURPOSE
-  Produce plan.md (+ research/data-model/contracts) under specs/Patient/RegisterPatient/.
-  This is where the engineering standards matter most — load the architecture stack,
-  the HL7 adapter rules, and the eventing rules for inbound feeds.
-
-CONTEXT FILES TO ADD
-  Architecture (technology):
-    docs/architecture/folder-structure.md
-    docs/architecture/clean-architecture.md
-    docs/architecture/modular-monolith.md
-    docs/architecture/cqrs.md
-    docs/architecture/vertical-slices.md
-    docs/architecture/persistence.md
-    docs/architecture/eventing.md
-    docs/domainspecs/healthcare/eventing.domain.md       (HL7/FHIR inbound feeds)  <-- HL7
-    docs/architecture/testing.md
-  Domain (healthcare, this slice):
-    docs/domain/domain-driven-design.md
-    docs/domainspecs/healthcare/domain-driven-design.domain.md
-    docs/domainspecs/healthcare/fhir.md
-    docs/domainspecs/healthcare/hl7.md                          (HL7 v2 adapter pattern)  <-- HL7
-    docs/domainspecs/healthcare/dicom.md                        (imaging identifiers; optional for registration)
-    docs/domainspecs/healthcare/terminology.md
-    docs/domainspecs/healthcare/hipaa.md
-    docs/domainspecs/healthcare/consent.md
-  Security:
-    docs/security/authorization.md  + .domain.md
-    docs/security/auditing.md        + .domain.md
-    docs/domainspecs/healthcare/data-classification.domain.md
-  Governance + AI rules:
-    docs/governance/coding-standards.md  + .domain.md
-    docs/glossary/ai-rules.md            + .domain.md
-
-COMMAND (copy-paste, single line)
-/aw-spec-plan Implement RegisterPatient as a complete vertical slice in the Patients module following the loaded standards: Patient aggregate root (Vogen PatientId, MRN value object, HumanName/Address/ContactPoint value objects), RegisterPatientCommand + handler (transaction + PatientRegisteredEvent), SecureFastEndpoint POST /patients with ETag, PatientDto + hand-written ToDto, EF configuration + migration, FHIR R4 Patient projector, and the PHI-access audit behavior. Interop: an Interop/Hl7v2 inbound adapter that parses ADT^A04 and dispatches RegisterPatientCommand via IMediator (no direct aggregate writes), MLLP transport + ACK, and an outbound ADT emitter subscribed to PatientRegisteredEvent; plan PIX/PDQ identity cross-reference. Use AppWeaver.Mediator/Repository/ServiceDefaults per the docs; PostgreSQL prod / SQLite dev; no MediatR/AutoMapper. @docs/architecture/folder-structure.md @docs/architecture/clean-architecture.md @docs/architecture/modular-monolith.md @docs/architecture/cqrs.md @docs/architecture/vertical-slices.md @docs/architecture/persistence.md @docs/architecture/eventing.md @docs/domainspecs/healthcare/eventing.domain.md @docs/architecture/testing.md @docs/domain/domain-driven-design.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/security/authorization.md @docs/domainspecs/healthcare/authorization.domain.md @docs/security/auditing.md @docs/domainspecs/healthcare/auditing.domain.md @docs/domainspecs/healthcare/data-classification.domain.md @docs/governance/coding-standards.md @docs/domainspecs/healthcare/coding-standards.domain.md @docs/glossary/ai-rules.md @docs/domainspecs/healthcare/ai-rules.domain.md
-
-MANUAL TEXT (the prompt portion, for reference)
-  Implement RegisterPatient as a complete vertical slice in the Patients module following
-  the loaded standards: Patient aggregate root (Vogen PatientId, MRN value object,
-  HumanName/Address/ContactPoint value objects), RegisterPatientCommand + handler
-  (transaction + PatientRegisteredEvent), SecureFastEndpoint POST /patients with ETag,
-  PatientDto + hand-written ToDto, EF configuration + migration, FHIR R4 Patient projector,
-  and the PHI-access audit behavior. Interop: an Interop/Hl7v2 inbound adapter that parses
-  ADT^A04 and dispatches RegisterPatientCommand via IMediator (no direct aggregate writes),
-  MLLP transport + ACK, and an outbound ADT emitter subscribed to PatientRegisteredEvent;
-  plan PIX/PDQ identity cross-reference. Use AppWeaver.Mediator/Repository/ServiceDefaults
-  per the docs; PostgreSQL prod / SQLite dev; no MediatR/AutoMapper.
-
-NOTES
-  - No aggregate/feature token here — the folder is resolved from feature.json.
-
-
-================================================================================
-STEP 4 — /aw-spec-tasks   (generate the dependency-ordered task list)
-================================================================================
-PURPOSE
-  Produce tasks.md from plan.md under specs/Patient/RegisterPatient/.
-
-CONTEXT FILES TO ADD
-  docs/architecture/folder-structure.md
-  docs/architecture/vertical-slices.md   (+ .domain.md)
-  docs/architecture/cqrs.md               (+ .domain.md)
-  docs/architecture/persistence.md        (+ .domain.md)
-  docs/architecture/testing.md            (+ .domain.md)
-  docs/architecture/eventing.md           (+ .domain.md)
-  docs/domainspecs/healthcare/domain-driven-design.domain.md
-  docs/domainspecs/healthcare/fhir.md
-  docs/domainspecs/healthcare/hl7.md                       (HL7 adapter tasks)  <-- HL7
-  docs/security/authorization.md          (+ .domain.md)
-  docs/security/auditing.md               (+ .domain.md)
-  docs/governance/coding-standards.md     (+ .domain.md)
-  docs/glossary/ai-rules.md               (+ .domain.md)
-
-COMMAND (copy-paste, single line)
-/aw-spec-tasks Break the plan into ordered, testable tasks for the RegisterPatient slice: value objects + tests, Patient aggregate + invariant tests, EF config + migration, RegisterPatientCommand/Validator/Handler + handler tests (happy/validation/not-found/conflict), SecureFastEndpoint + integration test, FHIR Patient projector + round-trip test, HL7 v2 ADT^A04 inbound parser + outbound emitter with HL7 conformance tests against an internal corpus, PatientRegisteredEvent + publish, PHI-audit wiring. Tests precede implementation. @docs/architecture/folder-structure.md @docs/architecture/vertical-slices.md @docs/domainspecs/healthcare/vertical-slices.domain.md @docs/architecture/cqrs.md @docs/domainspecs/healthcare/cqrs.domain.md @docs/architecture/persistence.md @docs/domainspecs/healthcare/persistence.domain.md @docs/architecture/testing.md @docs/domainspecs/healthcare/testing.domain.md @docs/architecture/eventing.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/security/authorization.md @docs/domainspecs/healthcare/authorization.domain.md @docs/security/auditing.md @docs/domainspecs/healthcare/auditing.domain.md @docs/governance/coding-standards.md @docs/domainspecs/healthcare/coding-standards.domain.md @docs/glossary/ai-rules.md @docs/domainspecs/healthcare/ai-rules.domain.md
-
-MANUAL TEXT (the prompt portion, for reference)
-  Break the plan into ordered, testable tasks for the RegisterPatient slice: value objects
-  + tests, Patient aggregate + invariant tests, EF config + migration,
-  RegisterPatientCommand/Validator/Handler + handler tests
-  (happy/validation/not-found/conflict), SecureFastEndpoint + integration test, FHIR
-  Patient projector + round-trip test, HL7 v2 ADT^A04 inbound parser + outbound emitter
-  with HL7 conformance tests against an internal corpus, PatientRegisteredEvent + publish,
-  PHI-audit wiring. Tests precede implementation.
-
-
-================================================================================
-STEP 5 — /aw-spec-analyze   (REQUIRED — cross-artifact correctness gate)
-================================================================================
-WHY THIS MATTERS (do not skip)
-  Analyze is a non-destructive consistency/quality check across spec.md, plan.md, and
-  tasks.md, run AFTER tasks and BEFORE implement. It is the last gate before code, and for
-  a regulated, interoperable feature it catches exactly the failures that are most costly
-  after implementation:
-   - Requirements in the spec with no covering task (e.g. ADT^A04 ingest, PIX/PDQ, Consent
-     capture, audit on every PHI write).
-   - Tasks with no basis in the spec (scope creep).
-   - Constitution NON-NEGOTIABLE gaps: missing ATNA audit task, hard-delete instead of
-     soft-delete, missing ETag/If-Match concurrency, PHI in logs, free-text where a coded
-     value object is required, a second FHIR write path, banned packages.
-   - Terminology / naming drift between artifacts.
-  Fix everything it flags by amending spec/plan/tasks, then re-run until clean.
-
-CONTEXT FILES TO ADD
-  docs/domainspecs/healthcare/hl7.md                       (verify HL7 coverage)  <-- HL7
-  docs/domainspecs/healthcare/hipaa.md
-  docs/domainspecs/healthcare/auditing.domain.md
-  docs/governance/coding-standards.md     (+ .domain.md)
-  docs/domainspecs/healthcare/ai-rules.domain.md
-
-COMMAND
-/aw-spec-analyze @docs/domainspecs/healthcare/hl7.md @docs/domainspecs/healthcare/hipaa.md @docs/domainspecs/healthcare/auditing.domain.md @docs/governance/coding-standards.md @docs/domainspecs/healthcare/coding-standards.domain.md @docs/domainspecs/healthcare/ai-rules.domain.md
-
-MANUAL TEXT
-  (none — review the report, then amend spec/plan/tasks for any finding and re-run)
-
-
-================================================================================
-STEP 6 — /aw-spec-implement   (execute the tasks / write the code)
-================================================================================
-PURPOSE
-  Execute tasks.md and produce the actual source under src/ following the standards.
-  Add the full implementation context: tasks-set + HL7 + dependency/versioning +
-  FHIR/terminology + data-classification/zero-trust.
-
-CONTEXT FILES TO ADD
-  (everything from STEP 4) PLUS:
-    docs/domainspecs/healthcare/hl7.md                      (already in step 4 — keep)  <-- HL7
-    docs/governance/dependency-policy.md   (+ .domain.md)
-    docs/governance/api-versioning.md      (+ .domain.md)
-    docs/domainspecs/healthcare/terminology.md
-    docs/security/data-classification.md    (+ .domain.md)
-    docs/security/zero-trust.md             (+ .domain.md)
-
-COMMAND (copy-paste, single line)
-/aw-spec-implement Implement the RegisterPatient tasks exactly per the loaded standards. Generate the complete vertical slice (Domain/Persistence/Features/Shared), the Interop/Hl7v2 ADT^A04 inbound adapter + outbound ADT emitter (MLLP + ACK, no direct aggregate writes), the FHIR R4 Patient projector, unit + integration + FHIR-validator + HL7-conformance tests, and the EF migration. Honor every NON-NEGOTIABLE: Result pattern, ETag/If-Match concurrency, soft-delete, ATNA audit, minimum-necessary, no PHI in logs, coded value objects, inbound feeds via adapters only, no banned packages. Do not run migrations against shared environments. @docs/architecture/folder-structure.md @docs/architecture/vertical-slices.md @docs/domainspecs/healthcare/vertical-slices.domain.md @docs/architecture/cqrs.md @docs/domainspecs/healthcare/cqrs.domain.md @docs/architecture/persistence.md @docs/domainspecs/healthcare/persistence.domain.md @docs/architecture/testing.md @docs/domainspecs/healthcare/testing.domain.md @docs/architecture/eventing.md @docs/domainspecs/healthcare/eventing.domain.md @docs/domain/domain-driven-design.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/security/authorization.md @docs/domainspecs/healthcare/authorization.domain.md @docs/security/auditing.md @docs/domainspecs/healthcare/auditing.domain.md @docs/security/data-classification.md @docs/domainspecs/healthcare/data-classification.domain.md @docs/security/zero-trust.md @docs/domainspecs/healthcare/zero-trust.domain.md @docs/governance/coding-standards.md @docs/domainspecs/healthcare/coding-standards.domain.md @docs/governance/dependency-policy.md @docs/domainspecs/healthcare/dependency-policy.domain.md @docs/governance/api-versioning.md @docs/domainspecs/healthcare/api-versioning.domain.md @docs/glossary/ai-rules.md @docs/domainspecs/healthcare/ai-rules.domain.md
-
-MANUAL TEXT (the prompt portion, for reference)
-  Implement the RegisterPatient tasks exactly per the loaded standards. Generate the
-  complete vertical slice (Domain/Persistence/Features/Shared), the Interop/Hl7v2 ADT^A04
-  inbound adapter + outbound ADT emitter (MLLP + ACK, no direct aggregate writes), the
-  FHIR R4 Patient projector, unit + integration + FHIR-validator + HL7-conformance tests,
-  and the EF migration. Honor every NON-NEGOTIABLE: Result pattern, ETag/If-Match
-  concurrency, soft-delete, ATNA audit, minimum-necessary, no PHI in logs, coded value
-  objects, inbound feeds via adapters only, no banned packages. Do not run migrations
-  against shared environments.
-
-
-================================================================================
-QUICK REFERENCE — order of operations (all required for this feature)
-================================================================================
-  (0) /aw-spec-select-domain  ... one-time: set active domain (healthcare) -> .aw-spec/domain.json
- (0b) /aw-spec-constitution   ... one-time, if not yet ratified
-   1. /aw-spec-specify        ... Patient/RegisterPatient + domain/glossary + HL7 context
-   2. /aw-spec-clarify        ... correctness gate: resolve HL7/PHI/identity ambiguities
-   3. /aw-spec-plan           ... architecture + domain + HL7/eventing + security + governance
-   4. /aw-spec-tasks          ... tasks-set + HL7 adapter/conformance tasks
-   5. /aw-spec-analyze        ... correctness gate: spec<->plan<->tasks + NON-NEGOTIABLE coverage
-   6. /aw-spec-implement      ... full build: slice + HL7 adapters + FHIR + tests + migration
-
-All steps after /aw-spec-specify auto-resolve specs/Patient/RegisterPatient/ from
-.aw-spec/feature.json — do not repeat the Patient/RegisterPatient token.
-
-HL7 v2 is threaded through every step (docs/domainspecs/healthcare/hl7.md + docs/domainspecs/healthcare/eventing.domain.md) because inbound
-ADT^A04 ingestion and outbound ADT emission are first-class surfaces of this feature, not an
-afterthought — interoperability is a NON-NEGOTIABLE constitution principle (XIV).

package/assets/docs/domainspecs/UIVisualization/chart-bubble.md

@@ -1,70 +0,0 @@
-# BubbleChart — Chart Rule
-
-> Load **only when "Bubble" (or "all plots") is in the selection** (see [[domain-requirements]]).
-> Component: `BubbleChart` in `components/charts/generic/BubbleChart.tsx`. Built on [[charting-standards.domain]].
-
-## Purpose
-Multi-dimensional scatter — each point encodes **x, y, size, colour, label** (up to 5 dimensions).
-Use for potency vs MW, portfolio risk/return, effort vs impact, market mapping.
-
-## Props contract
-```ts
-interface BubblePoint { x: number; y: number; size: number; label: string; meta?: Record<string, string|number> }
-interface BubbleSeries { seriesLabel: string; color?: string; points: BubblePoint[] }
-
-interface BubbleChartProps {
-  series: BubbleSeries[]        // REQUIRED — one series per colour/category
-  xLabel: string               // REQUIRED
-  yLabel: string               // REQUIRED
-  sizeLabel?: string           // shown as "Bubble size ∝ …" annotation
-  title?: string
-  xAxisType?: 'linear' | 'log'
-  yAxisType?: 'linear' | 'log'
-  sizeRange?: [number, number] // [minPx, maxPx] bubble diameter (default [8,40])
-  xRefLine?: number; xRefLabel?: string   // optional vertical reference line
-  yRefLine?: number; yRefLabel?: string   // optional horizontal reference line
-  height?: number
-  showLabels?: boolean         // annotate points with their label
-}
-```
-
-## Rules
-- Bubble sizes are **normalised across the whole dataset** to `sizeRange` — pass raw magnitudes;
-  the chart scales them. Don't pre-scale to pixels.
-- Group points into **series by the categorical dimension** (target, region, product line) so
-  colour + legend come for free.
-- Use `xAxisType="log"` / `yAxisType="log"` or pre-`log10` the value (e.g. IC₅₀) — pick one,
-  document it in the axis label.
-
-## Adapter example (agent reference)
-```tsx
-'use client'
-import { BubbleChart } from '@/components/charts/generic'
-import type { Compound } from '@/lib/types/pharma'
-
-export function compoundsToBubbleSeries(compounds: Compound[]) {
-  const targets = [...new Set(compounds.map(c => c.target))]
-  return targets.map(t => ({
-    seriesLabel: t,
-    points: compounds.filter(c => c.target === t).map(c => ({
-      x: c.molecularWeight, y: Math.log10(c.ic50_nM),
-      size: c.selectivityRatio, label: c.name,
-      meta: { Status: c.status, 'IC₅₀': `${c.ic50_nM} nM` },
-    })),
-  }))
-}
-
-export default function CompoundScatterPlot({ compounds, height }: { compounds: Compound[]; height?: number }) {
-  return (
-    <BubbleChart series={compoundsToBubbleSeries(compounds)}
-      xLabel="Molecular Weight (Da)" yLabel="log₁₀(IC₅₀, nM)" sizeLabel="Selectivity Ratio"
-      xRefLine={500} xRefLabel="Ro5 MW limit" sizeRange={[7, 28]} height={height} />
-  )
-}
-```
-
-## Scaffolds when selected
-- generic `BubbleChart` + `app/bubble/page.tsx` + nav tab + optional adapter.
-
-## Related
-- [[charting-standards.domain]] · [[component-contracts.domain]] · [[clean-architecture.domain]]

package/assets/docs/domainspecs/UIVisualization/chart-dimred.md

@@ -1,58 +0,0 @@
-# DimRedPlot — Chart Rule
-
-> Load **only when "Dim. Reduction / PCA / t-SNE / UMAP" (or "all plots") is selected** (see [[domain-requirements]]).
-> Component: `DimRedPlot` in `components/charts/generic/DimRedPlot.tsx`. Built on [[charting-standards.domain]].
-
-## Purpose
-2-D scatter of **pre-computed** dimensionality-reduction coordinates, coloured by group, with
-optional cluster-centroid labels and density contours. Use for single-cell clustering, customer
-segments, NLP embeddings, chemical-space maps, anomaly scatter.
-
-## Props contract
-```ts
-interface DimRedPoint {
-  x: number; y: number         // reduced coordinates (caller ran PCA/t-SNE/UMAP)
-  label: string
-  group: string                // category → colour + legend entry
-  meta?: Record<string, string|number>
-}
-interface DimRedPlotProps {
-  points: DimRedPoint[]        // REQUIRED
-  method?: string              // badge: "PCA", "t-SNE", "UMAP" (default "DR")
-  xLabel?: string; yLabel?: string   // e.g. "PC1 (34.2% var)", "UMAP 1"
-  colorByLabel?: string        // legend header / tooltip ("Cell type", "Segment")
-  showClusterLabels?: boolean  // centroid label per group (default true)
-  showDensityContours?: boolean // KDE contour per group (default false)
-  markerSize?: number          // default 5
-  title?: string; height?: number
-}
-```
-
-## Rules
-- The chart **does not run** PCA/t-SNE/UMAP — coordinates are computed upstream (Python,
-  backend, or a JS lib) and passed in. Document the method in `method` + axis labels.
-- `group` drives colour and the legend; keep group count modest (≤ ~12) for distinct colours.
-- Turn on `showDensityContours` for large, overlapping point clouds; off for small datasets.
-
-## Page/adapter example (agent reference)
-```tsx
-'use client'
-import { DimRedPlot } from '@/components/charts/generic'
-
-// cells already have umap1/umap2 + cellType from the pipeline
-export default function CellUmap({ cells }: { cells: { id: string; umap1: number; umap2: number; cellType: string }[] }) {
-  return (
-    <DimRedPlot
-      points={cells.map(c => ({ x: c.umap1, y: c.umap2, label: c.id, group: c.cellType }))}
-      method="UMAP" xLabel="UMAP 1" yLabel="UMAP 2" colorByLabel="Cell type" showClusterLabels
-    />
-  )
-}
-```
-
-## Scaffolds when selected
-- generic `DimRedPlot` + `app/dimred/page.tsx` + nav tab + optional adapter (+ a place to compute
-  or fetch coordinates).
-
-## Related
-- [[charting-standards.domain]] · [[component-contracts.domain]] · [[clean-architecture.domain]]