aw-spec-cli 0.1.4 → 0.1.5

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

@@ -1,6 +1,6 @@
 # Data Classification — Healthcare Domain Addenda
 
-> Technology base: [[data-classification]]. NON-NEGOTIABLE. Commands: `/aw-spec-specify`, `/aw-spec-plan`, `/aw-spec-implement`.
+> Technology base: [[data-classification]]. NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`, `/aw-spec-gate`.
 
 ## Categories
 | Class | Extra rules |

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

@@ -1,6 +1,6 @@
 # Dependency Policy — Healthcare Domain Addenda
 
-> Technology base: [[dependency-policy]]. Commands: `/aw-spec-plan`, `/aw-spec-implement`.
+> 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]]).

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

@@ -1,6 +1,6 @@
 # DICOM Standards
 
-> Commands: `/aw-spec-specify`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> 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).

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

@@ -1,6 +1,6 @@
 # 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`.
+> Technology base: [[domain-driven-design]]. NON-NEGOTIABLE. Commands: `/aw-spec-specify`.
 
 ## Modeling
 - Use the clinical/interop ubiquitous language (see [[clinical-terms]], [[integration-terms]]).

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

@@ -1,6 +1,6 @@
 # Eventing — Healthcare Domain Addenda
 
-> Technology base: [[eventing]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> 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]]):

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

@@ -1,6 +1,6 @@
 # FHIR Standards
 
-> NON-NEGOTIABLE. Commands: `/aw-spec-specify`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
 
 ## Architecture
 - **R4 is the default external contract**; R5 is **additive** under `/fhir/R5/...`.

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

@@ -1,6 +1,6 @@
 # Folder Structure — Healthcare Domain Addenda
 
-> Technology base: [[folder-structure]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`. Replace `<SampleProjectName>`.
+> Technology base: [[folder-structure]]. Commands: `/aw-spec-gate`. Replace `<SampleProjectName>`.
 
 ## Additions to the base layout
 ```

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

@@ -1,6 +1,6 @@
 # HIPAA / PHI Protection Standards
 
-> NON-NEGOTIABLE. Commands: `/aw-spec-specify`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> 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.

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

@@ -1,6 +1,6 @@
 # HL7 v2 Standards
 
-> Commands: `/aw-spec-specify`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> 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.

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

@@ -1,6 +1,6 @@
 # Glossary — Integration Terms
 
-> Ubiquitous language for interoperability standards + IHE profiles. Commands: `/aw-spec-specify`, `/aw-spec-clarify`, `/aw-spec-plan`.
+> Ubiquitous language for interoperability standards + IHE profiles. Commands: `/aw-spec-specify`.
 
 | Term | Definition |
 |---|---|

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

@@ -1,6 +1,6 @@
 # Persistence — Healthcare Domain Addenda
 
-> Technology base: [[persistence]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> 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).

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

@@ -1,6 +1,6 @@
 # Terminology Standards
 
-> NON-NEGOTIABLE. Commands: `/aw-spec-specify`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> 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.**

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

@@ -1,6 +1,6 @@
 # Testing — Healthcare Domain Addenda
 
-> Technology base: [[testing]]. Commands: `/aw-spec-tasks`, `/aw-spec-implement`.
+> 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]]).

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

@@ -1,6 +1,6 @@
 # Vertical Slices — Healthcare Domain Addenda
 
-> Technology base: [[vertical-slices]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> Technology base: [[vertical-slices]]. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
 
 ## Interop adapters in the slice
 `{Module}/Interop/` carries the external-protocol adapters:

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

@@ -1,6 +1,6 @@
 # Zero-Trust — Healthcare Domain Addenda
 
-> Technology base: [[zero-trust]]. Commands: `/aw-spec-plan`, `/aw-spec-implement`.
+> 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]].

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

@@ -1,6 +1,6 @@
 # API Versioning — Pharma Domain Addenda (FHIR)
 
-> Technology base: [[api-versioning]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> Technology base: [[api-versioning]]. Commands: `/aw-spec-specify`, `/aw-spec-gate`.
 
 ## FHIR versioning
 - R4 default; R5 **additive** under a versioned path (`/fhir/R5/...`).

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

@@ -1,6 +1,6 @@
 # ATC — WHO Anatomical Therapeutic Chemical Classification
 
-> NON-NEGOTIABLE. Commands: `/aw-spec-specify`, `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> NON-NEGOTIABLE. Commands: `/aw-spec-constitution`, `/aw-spec-specify`.
 
 ## Value Object
 - ATC is the **`AtcCode` value object** — immutable, equality by value (see [[domain-driven-design.domain]]); carries code, ATC system URI, **ATC edition/version** (WHO updates annually), display.

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

@@ -1,26 +1,90 @@
 # Auditing — Pharma Domain Addenda
 
-> Technology base: [[auditing]]. NON-NEGOTIABLE. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> Technology base: [[auditing]]. NON-NEGOTIABLE. Consumed by `/aw-spec-specify` (LIFTS the
+> auditing requirement into the spec) and `/aw-spec-gate` (VALIDATES the spec/design realise it).
+> `/aw-spec-design` and `/aw-spec-implement` never load this file — auditing reaches them through
+> the spec's **declared audit level per aggregate**, and the enablement mechanics live in the
+> technical base [[auditing]]. Keep this file technology-agnostic (levels + rules, **no code**).
 
-## Setup
-- Auditing is **MANDATORY** for `MedicinalProduct` and its entities (ActiveIngredient, PackagingConfiguration, MarketingAuthorization).
-- Enable via `.EnableAdvancedAuditing()` + `AddAuditing(... UseEfCoreAuditing(...).UseAppWeaverDataStore())`.
-- Audit tables: shared `AppWeaver.DataStore`, schema `Auditing`, prefix `Audit_`.
-- An audit pipeline behavior runs on every mediator request (see [[cqrs.domain]], [[eventing.domain]]).
+## Two auditing levels (framework-supported)
 
-## Audit-mandatory operations
-Product **creation**, **modification**, **retirement** (Discontinued/Withdrawn), **identifier changes** (NDC/Package NDC), **classification changes** (ATC) — plus every lifecycle transition and authorized admin action (see [[product-lifecycle.domain]], [[ndc]], [[atc]]).
+AppWeaver auditing has exactly **two levels**; the framework's audit interceptor populates every
+audit field automatically (handlers NEVER assign audit fields):
 
-## Record (immutable)
-```
-{ user, timestamp, action, resourceType, resourceId, previousValue, newValue, correlationId }
-```
-**User, Timestamp, Action, Previous Value, New Value** are spec-required and MUST always be populated.
+| Level | Captures | Depth |
+|---|---|---|
+| **Basic** | who/when lifecycle — created / modified / (soft-)deleted, by whom and when; one audit entry per aggregate root per save (who · action · resource type · resource id · timestamp · correlation) | entity-level (Created/Updated/Deleted) — **no** before/after values |
+| **Advanced** | everything Basic captures **plus field-level before/after** — each changed property's previous → new value | entity-level **+ property-level previous/new value** |
+
+- **Advanced is REQUIRED whenever the spec asks for "previous value / new value"** — before/after
+  values exist ONLY at the Advanced tier.
+- Child entities fold their changes into the owning aggregate root's audit entry.
+
+> Code realisation — marker interfaces (Basic = `IAuditedObject` / `IFullAuditedObject`; Advanced =
+> `+ IFieldAudited`), the one-time composition, and the audit query API — lives in the technical
+> base. See [[auditing]]; `/aw-spec-design` and `/aw-spec-implement` get the HOW from there.
+
+## Aggregate assignment rule (how specify decides the level)
+
+`/aw-spec-specify` MUST assign an audit level to every aggregate it models and LIFT it into the
+spec as an explicit, developer-editable declaration:
+
+- The **main aggregate** of the requirement (the aggregate root the story is about) → **Advanced**.
+- **Supporting aggregates** (collaborating/referenced roots) → **Basic** by default.
+- A developer MAY raise or lower a level afterwards by editing the spec declaration — the level is
+  a **spec** decision, never a design or implementation one. `/aw-spec-design` then follows the
+  declared level.
+
+Lift it as one line the gate can check, e.g. under Constraints:
+
+> **CN-0xx**: Auditing level — `<MainAggregate>` uses **Advanced** (field-level before/after)
+> auditing; `<SupportingAggregate…>` use **Basic** (lifecycle) auditing; creation is
+> audit-mandatory and append-only. — lifted from auditing.domain.
+
+Declare the **level** — do NOT enumerate the audit record's field shape in the spec (next section).
+
+## Spec-required vs framework-emitted (what the gate checks)
+
+The audit record's field shape is **framework-emitted** — the interceptor populates it; it is NOT
+spec-authored content. Fields the platform always supplies:
+
+- `resourceType`, `resourceId`, `correlationId`, `tenantId`, and the physical record layout.
+
+Split for the gate:
+
+- **Spec-required** (specify lifts it; the gate checks the spec + design carry it): the **audit
+  level per aggregate**; that creation is **audit-mandatory** and **append-only**; and the
+  business-meaningful capture — **User, Timestamp, Action, Previous Value, New Value** (the last
+  two imply Advanced).
+- **Framework-emitted** (NEVER a spec/design gap — always populated by the platform): the fields
+  listed above. The gate MUST NOT raise a LIFT-FAILURE for them; they are guaranteed by the
+  framework, not authored in the spec.
+
+## Queryable audit (framework-provided)
+
+The audit store is queryable out of the box (by resource identity, by user, by tenant, and by
+action/time with paging — see [[auditing]]). A spec "queryable creation audit record for
+compliance" success criterion is therefore satisfied by the framework's audit query API; design
+references it and does **NOT** need a bespoke audit read port/model.
+
+## Setup (pharma)
+
+- Auditing is **MANDATORY** for `MedicinalProduct` (**Advanced**) and its child entities
+  (`ActiveIngredient`, `PackagingConfiguration`, `MarketingAuthorization` — folded into the
+  product's audit entry).
+- Audit-mandatory operations: product **creation**, **modification**, **retirement**
+  (Discontinued/Withdrawn), **identifier changes** (NDC / Package NDC), **classification changes**
+  (ATC) — plus every lifecycle transition and authorized admin action (see
+  [[product-lifecycle.domain]], [[ndc]], [[atc]]).
 
 ## Immutability & retention
-- `AuditRecord` is **append-only** — no update/delete (see [[domain-driven-design.domain]], [[persistence.domain]]).
-- Retained per regulatory policy, queryable for the full window; exportable, MAY project to FHIR `AuditEvent` / `Provenance` (see [[fhir]], [[data-provenance]]).
-- Audit + domain events + version snapshots give end-to-end traceability (see [[regulatory-compliance]], [[eventing.domain]]).
+
+- Audit records (log · entity change · property change) are **append-only** — no update, no delete
+  (see [[domain-driven-design.domain]], [[persistence.domain]]).
+- Retained per regulatory policy, queryable for the full window; exportable, MAY project to FHIR
+  `AuditEvent` / `Provenance` (see [[fhir]], [[data-provenance]]).
+- Audit + domain events + version snapshots give end-to-end traceability (see
+  [[regulatory-compliance]], [[eventing.domain]]).
 
 ## Related
 - [[auditing]] · [[regulatory-compliance]] · [[data-provenance]] · [[persistence.domain]] · [[product-lifecycle.domain]] · [[ndc]] · [[atc]] · [[cqrs.domain]] · [[eventing.domain]] · [[fhir]] · [[domain-driven-design.domain]]

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

@@ -1,6 +1,6 @@
 # Authorization — Pharma Domain Addenda
 
-> Technology base: [[authorization]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> Technology base: [[authorization]]. Commands: `/aw-spec-constitution`, `/aw-spec-specify`, `/aw-spec-gate`.
 
 ## Roles
 `SystemAdmin`, `RegulatoryOfficer`, `ProductSteward`, `TerminologyManager`, `DataManager`, `ReadOnlyConsumer`, `ExternalSystem`. Per-route matrix: `docs/security/authorization-matrix.md`.

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

@@ -1,6 +1,6 @@
 # Coding Standards — Pharma Domain Addenda
 
-> Technology base: [[coding-standards]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+> Technology base: [[coding-standards]]. Commands: `/aw-spec-gate`.
 
 ## Coded value objects
 - Follow the FHIR pattern: `Codeable`, `Coding`, `Quantity`, `Ratio`, `Identifier` (see [[terminology]], [[fhir]]).

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

@@ -1,186 +1,108 @@
 # Pharma Domain — Command → Rule-File Map
 
-Per-AW-Spec-command list of the **pharma 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 medicinal-product-registration project.
-
-- All paths are workspace-relative and live in this folder: `docs/domainspecs/pharma/`.
-- A skill can read this file and load every path under the matching command heading.
-- This file is the **canonical source** for the pharma domain mapping; `/aw-spec-select-domain`
-  selects this folder as active.
+Per-command list of the **pharma domain** rule files loaded (via `resolve-domain` +
+the `domain-select` module, into the sticky standards set) for the spec-anchored
+orchestrator pipeline.
+
+**The model (see `.aw-spec/RULE-PARTITION.md`):** domain files feed
+only three consumers — **specify** (authors them into the spec as FR/BR/CN-/DC-/IC-),
+**constitution** (the domain principles), and the **gates** (conformance checklist).
+**design** and **implement** load **NO** domain file — the domain reaches them solely
+through the spec/design (as CN-/DC-/IC- ids). This is what keeps design authoring from
+the spec + technical standards and the tech base swappable.
+
+- All paths are workspace-relative and live in `docs/domainspecs/pharma/`.
+- `resolve-domain --command <name>` collects the `- ` bullets under `## /<name>`.
+- This file is the **canonical source** for the pharma domain mapping; `/aw-spec-orch
+  select-domain` selects this folder as active.
 
 ---
 
 ## /aw-spec-constitution
+<!-- Domain identity/regulatory/interop sources that become domain principles XVI+ in
+     constitution.domain.md (authored from docs/pharma-constitution.my-ref.md + these). -->
 - docs/domainspecs/pharma/domain-requirements.md
-- docs/domainspecs/pharma/regulatory-compliance.md
-- docs/domainspecs/pharma/ai-rules.domain.md
-
-## /aw-spec-specify
-- docs/domainspecs/pharma/domain-requirements.md
-- docs/domainspecs/pharma/pharma-terms.md
-- docs/domainspecs/pharma/integration-terms.md
-- docs/domainspecs/pharma/domain-driven-design.domain.md
-- docs/domainspecs/pharma/product-lifecycle.domain.md
 - docs/domainspecs/pharma/ndc.md
 - docs/domainspecs/pharma/idmp.md
-- docs/domainspecs/pharma/terminology.md
 - docs/domainspecs/pharma/atc.md
-- docs/domainspecs/pharma/fhir.md
-- docs/domainspecs/pharma/hl7.md
-- docs/domainspecs/pharma/regulatory-compliance.md
-- docs/domainspecs/pharma/data-provenance.md
-- docs/domainspecs/pharma/data-classification.domain.md
-- docs/domainspecs/pharma/ai-rules.domain.md
-
-## /aw-spec-clarify
-- docs/domainspecs/pharma/domain-driven-design.domain.md
-- docs/domainspecs/pharma/product-lifecycle.domain.md
-- docs/domainspecs/pharma/ndc.md
 - docs/domainspecs/pharma/terminology.md
-- docs/domainspecs/pharma/atc.md
-- docs/domainspecs/pharma/regulatory-compliance.md
 - docs/domainspecs/pharma/pharma-terms.md
-- docs/domainspecs/pharma/integration-terms.md
-
-## /aw-spec-plan
-- docs/domainspecs/pharma/folder-structure.domain.md
-- docs/domainspecs/pharma/cqrs.domain.md
-- docs/domainspecs/pharma/vertical-slices.domain.md
-- docs/domainspecs/pharma/persistence.domain.md
-- docs/domainspecs/pharma/testing.domain.md
-- docs/domainspecs/pharma/eventing.domain.md
-- docs/domainspecs/pharma/domain-driven-design.domain.md
 - docs/domainspecs/pharma/product-lifecycle.domain.md
-- docs/domainspecs/pharma/ndc.md
-- docs/domainspecs/pharma/idmp.md
-- docs/domainspecs/pharma/fhir.md
-- docs/domainspecs/pharma/hl7.md
-- docs/domainspecs/pharma/terminology.md
-- docs/domainspecs/pharma/atc.md
 - docs/domainspecs/pharma/regulatory-compliance.md
 - docs/domainspecs/pharma/data-provenance.md
-- docs/domainspecs/pharma/zero-trust.domain.md
-- docs/domainspecs/pharma/authorization.domain.md
-- docs/domainspecs/pharma/auditing.domain.md
-- docs/domainspecs/pharma/data-classification.domain.md
-- docs/domainspecs/pharma/coding-standards.domain.md
-- docs/domainspecs/pharma/dependency-policy.domain.md
-- docs/domainspecs/pharma/api-versioning.domain.md
-- docs/domainspecs/pharma/ai-rules.domain.md
-
-## /aw-spec-tasks
-- docs/domainspecs/pharma/folder-structure.domain.md
-- docs/domainspecs/pharma/vertical-slices.domain.md
-- docs/domainspecs/pharma/cqrs.domain.md
-- docs/domainspecs/pharma/persistence.domain.md
-- docs/domainspecs/pharma/testing.domain.md
-- docs/domainspecs/pharma/eventing.domain.md
-- docs/domainspecs/pharma/domain-driven-design.domain.md
-- docs/domainspecs/pharma/product-lifecycle.domain.md
-- docs/domainspecs/pharma/ndc.md
 - docs/domainspecs/pharma/fhir.md
 - docs/domainspecs/pharma/hl7.md
-- docs/domainspecs/pharma/authorization.domain.md
-- docs/domainspecs/pharma/auditing.domain.md
-- docs/domainspecs/pharma/coding-standards.domain.md
-- docs/domainspecs/pharma/ai-rules.domain.md
-
-## /aw-spec-analyze
-- docs/domainspecs/pharma/ndc.md
-- docs/domainspecs/pharma/terminology.md
-- docs/domainspecs/pharma/product-lifecycle.domain.md
-- docs/domainspecs/pharma/regulatory-compliance.md
+- docs/domainspecs/pharma/data-classification.domain.md
 - docs/domainspecs/pharma/auditing.domain.md
-- docs/domainspecs/pharma/coding-standards.domain.md
+- docs/domainspecs/pharma/authorization.domain.md
+- docs/domainspecs/pharma/zero-trust.domain.md
 - docs/domainspecs/pharma/ai-rules.domain.md
 
-## /aw-spec-implement
-- docs/domainspecs/pharma/folder-structure.domain.md
-- docs/domainspecs/pharma/vertical-slices.domain.md
-- docs/domainspecs/pharma/cqrs.domain.md
-- docs/domainspecs/pharma/persistence.domain.md
-- docs/domainspecs/pharma/testing.domain.md
-- docs/domainspecs/pharma/eventing.domain.md
+## /aw-spec-specify
+<!-- The FULL domain set. Specify models the domain COMPLETELY and LIFTS the constraint
+     overlays into the spec's CN-/DC-/IC- sections (design/implement never see these files). -->
+- docs/domainspecs/pharma/domain-requirements.md
 - docs/domainspecs/pharma/domain-driven-design.domain.md
 - docs/domainspecs/pharma/product-lifecycle.domain.md
 - docs/domainspecs/pharma/ndc.md
 - docs/domainspecs/pharma/idmp.md
-- docs/domainspecs/pharma/fhir.md
-- docs/domainspecs/pharma/hl7.md
-- docs/domainspecs/pharma/terminology.md
 - docs/domainspecs/pharma/atc.md
+- docs/domainspecs/pharma/pharma-terms.md
+- docs/domainspecs/pharma/terminology.md
+- docs/domainspecs/pharma/integration-terms.md
 - docs/domainspecs/pharma/regulatory-compliance.md
 - docs/domainspecs/pharma/data-provenance.md
-- docs/domainspecs/pharma/authorization.domain.md
-- docs/domainspecs/pharma/auditing.domain.md
+- docs/domainspecs/pharma/fhir.md
+- docs/domainspecs/pharma/hl7.md
 - docs/domainspecs/pharma/data-classification.domain.md
+- docs/domainspecs/pharma/persistence.domain.md
+- docs/domainspecs/pharma/cqrs.domain.md
+- docs/domainspecs/pharma/eventing.domain.md
+- docs/domainspecs/pharma/auditing.domain.md
+- docs/domainspecs/pharma/authorization.domain.md
 - docs/domainspecs/pharma/zero-trust.domain.md
-- docs/domainspecs/pharma/coding-standards.domain.md
-- docs/domainspecs/pharma/dependency-policy.domain.md
 - docs/domainspecs/pharma/api-versioning.domain.md
-- docs/domainspecs/pharma/ai-rules.domain.md
+- docs/domainspecs/pharma/vertical-slices.domain.md
 
-## /aw-spec-fast-implement
+## /aw-spec-design
+_None — design loads no domain file. Domain reaches design only through the spec (BR-/CN-/DC-/IC-)._
 
-> 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.
+## /aw-spec-implement
+_None — implement loads no domain file. Domain reaches implement only through design.md. Framework
+components are added separately via `/aw-spec-orch add-component`._
 
-- docs/domainspecs/pharma/folder-structure.domain.md
-- docs/domainspecs/pharma/cqrs.domain.md
-- docs/domainspecs/pharma/vertical-slices.domain.md
+## /aw-spec-gate
+<!-- Conformance checklist for the gates (analyze-design · analyze-slice): the domain-derived
+     constraints design/implement were NOT given as authoring input, VALIDATED against the
+     output. Domain re-enters here as a check, never as authoring input. -->
 - docs/domainspecs/pharma/persistence.domain.md
-- docs/domainspecs/pharma/testing.domain.md
+- docs/domainspecs/pharma/cqrs.domain.md
 - docs/domainspecs/pharma/eventing.domain.md
-- docs/domainspecs/pharma/domain-driven-design.domain.md
-- docs/domainspecs/pharma/product-lifecycle.domain.md
-- docs/domainspecs/pharma/ndc.md
-- docs/domainspecs/pharma/idmp.md
-- docs/domainspecs/pharma/fhir.md
-- docs/domainspecs/pharma/hl7.md
-- docs/domainspecs/pharma/terminology.md
-- docs/domainspecs/pharma/atc.md
-- docs/domainspecs/pharma/regulatory-compliance.md
-- docs/domainspecs/pharma/data-provenance.md
-- docs/domainspecs/pharma/zero-trust.domain.md
-- docs/domainspecs/pharma/authorization.domain.md
 - docs/domainspecs/pharma/auditing.domain.md
+- docs/domainspecs/pharma/authorization.domain.md
+- docs/domainspecs/pharma/zero-trust.domain.md
 - docs/domainspecs/pharma/data-classification.domain.md
+- docs/domainspecs/pharma/api-versioning.domain.md
+- docs/domainspecs/pharma/vertical-slices.domain.md
+- docs/domainspecs/pharma/folder-structure.domain.md
 - docs/domainspecs/pharma/coding-standards.domain.md
 - docs/domainspecs/pharma/dependency-policy.domain.md
-- docs/domainspecs/pharma/api-versioning.domain.md
+- docs/domainspecs/pharma/testing.domain.md
 - docs/domainspecs/pharma/ai-rules.domain.md
 
-## /aw-spec-minimal-implementation
-
-> Single-step set for pharma — 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/pharma/pharma-terms.md
-- docs/domainspecs/pharma/domain-driven-design.domain.md
-- docs/domainspecs/pharma/folder-structure.domain.md
-- docs/domainspecs/pharma/cqrs.domain.md
-- docs/domainspecs/pharma/vertical-slices.domain.md
-- docs/domainspecs/pharma/product-lifecycle.domain.md
-- docs/domainspecs/pharma/ndc.md
-- docs/domainspecs/pharma/idmp.md
-- docs/domainspecs/pharma/atc.md
-
 ---
 
-## Quick reference (command → file count)
+## Quick reference (command → domain file count)
+
+| Command | Domain rule files | Role |
+|---|---|---|
+| /aw-spec-constitution | 16 | domain principles (XVI+) |
+| /aw-spec-specify | 22 | author into spec (lift → CN-/DC-/IC-) |
+| /aw-spec-design | 0 | none — spec is the only domain input |
+| /aw-spec-implement | 0 | none — design is the only domain input |
+| /aw-spec-gate | 14 | conformance checklist (validate, don't author) |
 
-| Command | Domain rule files |
-|---|---|
-| /aw-spec-constitution | 3 |
-| /aw-spec-specify | 15 |
-| /aw-spec-clarify | 8 |
-| /aw-spec-plan | 24 |
-| /aw-spec-tasks | 15 |
-| /aw-spec-analyze | 7 |
-| /aw-spec-implement | 24 |
-| /aw-spec-fast-implement | 24 |
-| /aw-spec-minimal-implementation | 9 |
+> Retired in the orchestrator pipeline: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-taskplan`,
+> `/aw-spec-clarify`, `/aw-spec-analyze` (clarify folds into specify; plan/tasks into design). The
+> collapsed tiers `/aw-spec-fast-implement` and `/aw-spec-minimal-implementation` are pending a ruling
+> (they fold design+implement into one pass, which needs internal context staging to keep the partition).