aw-spec-cli 0.1.19 → 0.1.20

package/assets/.appweaver/orchestrator/workflows/aw-spec-analyze-slice.orch.yaml

@@ -136,7 +136,7 @@ workflow:
     action: verify_context
     require_non_empty: feature_dir
     on_empty: stop
-    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the aggregate, e.g. Order), then re-run analyze-slice."
+    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the feature, e.g. Order or PatientRegistration), then re-run analyze-slice."
 
   # The bounded context's DOMAIN MODEL — in every pass's context beside the spec, and the
   # authority the conformance pass scores against. Since the model split the spec no longer
@@ -162,6 +162,38 @@ workflow:
       - { name: domain_model,        from: "$.domain_model" }
       - { name: domain_model_exists, from: "$.domain_model_exists" }
 
+  # WHICH PART OF THAT MODEL THIS GATE SCORES. The model is filed by aggregate, the specs
+  # tree by feature. For a feature that is one capability over a shared aggregate
+  # (PatientRegistration over Patient) no section carries the feature's name, and scoring
+  # "the BR-nnn under this feature's section" found none and PASSED — every invariant the
+  # feature relies on silently demoted to a non-blocking note. Resolved from the spec's
+  # Acts-on line, then the boundary map, then the feature name.
+  - id: feature_aggregates
+    action: execute_script
+    script: { ref: xref }
+    subcommand: feature-aggregates
+    args: ["--feature-dir", "{{feature_dir}}"]
+    outputs:
+      - { name: owned_sections, from: "$.owned_sections" }
+      - { name: one_to_one,     from: "$.one_to_one" }
+
+  # WHICH OF THOSE INVARIANTS BLOCK. A feature that alone answers for an aggregate owns
+  # its section outright, and every BR-nnn under it has to be enforced in this code. A
+  # feature that shares the aggregate with other features — whatever it is named —
+  # answers only for what its spec cites: the rest of that section is the other features'
+  # code, and blocking on it would fail each of them for work another one does. The
+  # engine has no conditional prompt text, so the rule is chosen by an ordered pair of
+  # sets and handed to the pass as one sentence.
+  - id: model_scope_capability
+    action: set
+    vars:
+      model_scope_rule: "this feature SHARES those sections with other features, so BLOCKING covers only the BR-nnn this feature's spec CITES from them; any other BR-nnn stated there belongs to another feature and is a model_notes entry, not a violation"
+  - id: model_scope_owned
+    condition: "{{one_to_one}} == true"
+    action: set
+    vars:
+      model_scope_rule: "this feature is the ONLY one that answers for that section, so BLOCKING covers EVERY BR-nnn stated there, whether or not the spec cites it"
+
   # Is a change OPEN on this feature? Read for NAVIGATION only — see the vars note. Safe
   # on the bootstrap path: with no active_version.json, version-read returns
   # active_change="" / has_change=false and exits 0, so nothing here is conditional on it.
@@ -316,8 +348,9 @@ workflow:
           authority on what the domain IS. The spec cites invariants by id; this document
           states them. It describes the WHOLE context while this gate scores ONE feature,
           so scope matters:
-            • BLOCKING — every BR-nnn stated under `## Aggregate: {{feature}}`, the section
-              this slice owns. The rule has to be enforced somewhere in this code, and the
+            • BLOCKING — the invariants of the section(s) this feature answers for,
+              {{owned_sections}}: {{model_scope_rule}}. Each blocking rule has to be
+              enforced somewhere in this code, and the
               enforcement has to say what the model says. An owned invariant with no
               enforcement, or one enforced with a different threshold, condition or
               direction than the model states, is a `violations` entry with the BR id as
@@ -326,7 +359,7 @@ workflow:
             • BLOCKING — the ubiquitous language of that same section. An entity, field or
               state the code names differently from the model is a violation; the model's
               name is the right one.
-            • NOT BLOCKING — anything the model states under ANOTHER aggregate's section.
+            • NOT BLOCKING — anything the model states under any section not named above.
               This slice does not own those and often should not enforce them. Report each
               one this code appears to touch as a `model_notes` entry, naming the owning
               aggregate, and carry on.
@@ -335,8 +368,8 @@ workflow:
           invariant's text from its id, and never treat a rule the model does not state
           as one.
 
-          ok=true ONLY when no checklist rule is violated AND no invariant this aggregate
-          owns is unenforced or contradicted. `model_notes` never affects ok.
+          ok=true ONLY when no checklist rule is violated AND no BLOCKING invariant above
+          is unenforced or contradicted. `model_notes` never affects ok.
         outputs:
           - { name: conformance_ok,         from: "$.ok" }
           - { name: conformance_violations, from: "$.violations" }
@@ -352,8 +385,8 @@ workflow:
           Fix these domain-conformance violations in the feature's code (in context),
           keeping the design's behaviour intact. A violation whose `rule` is an overlay
           rule is fixed against the gate checklist in the standards; one whose `rule` is a
-          BR-nnn is fixed against the text domain-model.md states for it under
-          `## Aggregate: {{feature}}` — enforce what the model says, where the code
+          BR-nnn is fixed against the text domain-model.md states for it under its section
+          among {{owned_sections}} — enforce what the model says, where the code
           already owns that decision, and name entities and fields the way the model names
           them. Do NOT weaken or delete a test to hide a violation, and do NOT edit
           domain-model.md or the spec to match the code: this is a gate on the code, and a

package/assets/.appweaver/orchestrator/workflows/aw-spec-build.orch.yaml

@@ -82,7 +82,7 @@ workflow:
     action: verify_context
     require_non_empty: feature_dir
     on_empty: stop
-    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the aggregate, e.g. Order), then re-run build."
+    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the feature, e.g. Order or PatientRegistration), then re-run build."
 
   # Require A LANE — not a KIND of lane. build-compile runs EVERY declared lane's own
   # build command, so a two-lane project compiles both (the case the old first-match-wins

package/assets/.appweaver/orchestrator/workflows/aw-spec-characterize.orch.yaml

@@ -106,7 +106,7 @@ workflow:
     action: verify_context
     require_non_empty: feature_dir
     on_empty: stop
-    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the aggregate, e.g. Order), then re-run characterize."
+    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the feature, e.g. Order or PatientRegistration), then re-run characterize."
 
   - id: verify_spec
     action: verify_context

package/assets/.appweaver/orchestrator/workflows/aw-spec-close-delta.orch.yaml

@@ -136,7 +136,7 @@ workflow:
     action: verify_context
     require_non_empty: feature_dir
     on_empty: stop
-    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the aggregate, e.g. Order), then re-run close-delta."
+    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the feature, e.g. Order or PatientRegistration), then re-run close-delta."
 
   # 2. WHICH CHANGE IS BEING CLOSED. The evidence is changes/<CR-id>/ on disk; a change
   #    already closed has moved to changes/archive/. On the BOOTSTRAP path (implement →

package/assets/.appweaver/orchestrator/workflows/aw-spec-deploy.orch.yaml

@@ -36,7 +36,7 @@ workflow:
     action: verify_context
     require_non_empty: feature_dir
     on_empty: stop
-    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the aggregate, e.g. Order), then re-run deploy."
+    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the feature, e.g. Order or PatientRegistration), then re-run deploy."
 
   # Pre-deploy hooks (e.g. a final smoke/build gate configured by the project).
   - id: resolve_pre_hooks

package/assets/.appweaver/orchestrator/workflows/aw-spec-finalize-delta.orch.yaml

@@ -176,11 +176,12 @@ vars:
   merge_wave: "1"
   snapshot_dir: ""            # changes/<id>/pre-merge/ — the before-image recall-delta restores
   snapshot_count: "0"
-  # THE OKF OVERVIEW'S SUBJECT. The kit's working assumption is feature == aggregate; the
-  # Overview step is the one place it is load-bearing rather than cosmetic, because it
-  # selects a `## Aggregate:` section BY NAME. delta_aggregates is what the change's own
-  # model delta declares, so the common case is exact rather than assumed; it is empty for
-  # a behaviour-only change, which falls back to the feature name.
+  # THE OKF OVERVIEW'S SUBJECT. The Overview step selects a `## Aggregate:` section BY
+  # NAME, so it needs the aggregate, which is not always the feature: a feature that is
+  # one capability over a shared aggregate (PatientRegistration over Patient) has no
+  # section of its own name. delta_aggregates is what the change's own model delta
+  # declares; it is empty for a behaviour-only change, which falls back to the aggregate
+  # the feature answers for (feature-aggregates — the spec's Acts-on line).
   delta_aggregates: ""
   overview_scope: ""
   overview_section_ok: "false"
@@ -211,7 +212,7 @@ workflow:
     action: verify_context
     require_non_empty: feature_dir
     on_empty: stop
-    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the aggregate, e.g. Order), then re-run finalize-delta."
+    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the feature, e.g. Order or PatientRegistration), then re-run finalize-delta."
 
   - id: verify_spec
     action: verify_context
@@ -700,16 +701,15 @@ workflow:
   #     the context has no model: there would be nothing in context to distil, and a
   #     query with no source invents one. Best-effort; an empty answer is a no-op.
   # WHICH AGGREGATE SECTION(S) THIS CHANGE ACTUALLY TOUCHED, read off the model delta's
-  # own `## Aggregate:` headings rather than assumed from the feature name. The kit's
-  # working assumption is feature == aggregate, and it holds today — but the Overview step
-  # below is the one place that assumption is LOAD-BEARING rather than cosmetic: it selects
-  # a section by name, and a feature whose name is not an aggregate name selects nothing,
-  # producing an empty answer that the writer then declines. Driving it off the delta's
-  # declared aggregates makes the common case exact and the uncommon case visible.
+  # own `## Aggregate:` headings rather than assumed from the feature name. The Overview
+  # step below selects a section by name, and a feature whose name is not an aggregate
+  # name — one capability over a shared aggregate — selects nothing, producing an empty
+  # answer that the writer then declines. Driving it off the delta's declared aggregates
+  # makes a model change exact.
   #
   # A BEHAVIOUR-ONLY CHANGE HAS NO MODEL DELTA, so this reports none and the step falls
-  # back to the feature name — which is correct, not a degradation: there is no model
-  # change to distil and the concept's existing Overview stands.
+  # back to the aggregate the feature answers for — which is correct, not a degradation:
+  # there is no model change to distil and the concept's existing Overview stands.
   - id: cr_aggregates
     action: execute_script
     on_error: continue        # informational — a missing model delta is the ordinary case
@@ -720,9 +720,19 @@ workflow:
       - { name: delta_aggregates,     from: "$.aggregates_csv" }
       - { name: delta_aggregate_list, from: "$.aggregates" }
 
+  # The fallback subject: the aggregate this feature answers for, which is the feature
+  # itself on a 1:1 slice and the shared aggregate on a capability over one.
+  - id: feature_aggregates
+    action: execute_script
+    script: { ref: xref }
+    subcommand: feature-aggregates
+    args: ["--feature-dir", "{{feature_dir}}"]
+    outputs:
+      - { name: owned_csv, from: "$.owned_csv" }
+
   - id: overview_scope_feature
     action: set
-    vars: { overview_scope: "{{feature}}" }
+    vars: { overview_scope: "{{owned_csv}}" }
   - id: overview_scope_delta
     condition: "{{delta_aggregates}} != "
     action: set
@@ -823,4 +833,4 @@ outputs:
   model_merged: "{{delta_model_exists}}"      # true ⇒ domain-model.md was the second target of this merge.
                                               # false = a behaviour-only change: the spec merge was the
                                               # whole merge, not a half of one.
-  next: "Delta MERGED into spec.md, and into the context's domain-model.md one aggregate section at a time where the change carried a model delta (model_merged={{delta_model_exists}} — false means a behaviour-only change, so the spec merge was the whole merge). The lane plans were NOT touched — they are DERIVED from these two masters, so backend-plan.md / frontend-plan.md now stand BEHIND the spec and model at their last authored content. That drift starts here and lasts until /appweaver plan main re-derives them, carrying the recorded decisions (DA-n) and workarounds (WA-n) forward and rewriting what the spec and model no longer support. analyze-plan is not what closes it and cannot repair it while this change is open: with a change open it runs READ-ONLY, reporting the drift into plan-analyze-report.md without rewriting either plan. The full gate — check, repair, stop — comes back once the last change is closed, so the order is close-delta, then plan main, then analyze-plan. OKF edges reconciled ({{xref_edge_count}} dep(s)), {{downstream_count}} downstream slice(s) fenced (gate: {{gate_decision}}). The concept Overview was distilled for aggregate(s) `{{overview_scope}}` — taken from what this change's model delta DECLARES it touched, not assumed from the feature name (empty on a behaviour-only change, which falls back to the feature). section_found={{overview_section_ok}}, written={{overview_written}}{{overview_reason}} — written=false is normal for a behaviour-only change (nothing to distil, the existing Overview stands), but section_found=false means domain-model.md has no `## Aggregate:` section under that name and the concept's Overview was left as it was: check that the feature name matches the aggregate the model defines. Change {{active_change}} is STILL OPEN and the version is still {{version}}. Next: /appweaver analyze-slice — it now reads masters that carry this change, and a red result is still recoverable because nothing has been archived. Then /appweaver close-delta archives the change and bumps the version."
+  next: "Delta MERGED into spec.md, and into the context's domain-model.md one aggregate section at a time where the change carried a model delta (model_merged={{delta_model_exists}} — false means a behaviour-only change, so the spec merge was the whole merge). The lane plans were NOT touched — they are DERIVED from these two masters, so backend-plan.md / frontend-plan.md now stand BEHIND the spec and model at their last authored content. That drift starts here and lasts until /appweaver plan main re-derives them, carrying the recorded decisions (DA-n) and workarounds (WA-n) forward and rewriting what the spec and model no longer support. analyze-plan is not what closes it and cannot repair it while this change is open: with a change open it runs READ-ONLY, reporting the drift into plan-analyze-report.md without rewriting either plan. The full gate — check, repair, stop — comes back once the last change is closed, so the order is close-delta, then plan main, then analyze-plan. OKF edges reconciled ({{xref_edge_count}} dep(s)), {{downstream_count}} downstream slice(s) fenced (gate: {{gate_decision}}). The concept Overview was distilled for aggregate(s) `{{overview_scope}}` — taken from what this change's model delta DECLARES it touched, not assumed from the feature name (empty on a behaviour-only change, which falls back to the aggregate the feature answers for). section_found={{overview_section_ok}}, written={{overview_written}}{{overview_reason}} — written=false is normal for a behaviour-only change (nothing to distil, the existing Overview stands), but section_found=false means domain-model.md has no `## Aggregate:` section under that name and the concept's Overview was left as it was: check that the spec's Acts on aggregate(s) line names an aggregate the model defines. Change {{active_change}} is STILL OPEN and the version is still {{version}}. Next: /appweaver analyze-slice — it now reads masters that carry this change, and a red result is still recoverable because nothing has been archived. Then /appweaver close-delta archives the change and bumps the version."

package/assets/.appweaver/orchestrator/workflows/aw-spec-implement.orch.yaml

@@ -293,7 +293,7 @@ workflow:
     action: verify_context
     require_non_empty: feature_dir
     on_empty: stop
-    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the aggregate, e.g. Order), then re-run implement."
+    on_empty_message: "No active feature. Run /appweaver select-feature first (pick or create the feature, e.g. Order or PatientRegistration), then re-run implement."
 
   # The bounded context's DOMAIN MODEL — in every generating lane's payload as the authority
   # on what the plan's cited BR-nnn actually require and on the ubiquitous language, and the
@@ -309,6 +309,21 @@ workflow:
       - { name: domain_model,        from: "$.domain_model" }
       - { name: domain_model_exists, from: "$.domain_model_exists" }
 
+  # WHICH PART OF THAT MODEL IS THIS FEATURE'S. The model is filed by aggregate, the specs
+  # tree by feature, and the two names differ for a feature that is one capability over a
+  # shared aggregate (PatientRegistration over Patient) — reading the model by the
+  # feature's name finds no section there. Resolved from the spec's Acts-on line, then the
+  # boundary map, then the feature name, so a 1:1 feature resolves to exactly the section
+  # this workflow always read.
+  - id: feature_aggregates
+    action: execute_script
+    script: { ref: xref }
+    subcommand: feature-aggregates
+    args: ["--feature-dir", "{{feature_dir}}"]
+    outputs:
+      - { name: owned_csv,      from: "$.owned_csv" }
+      - { name: owned_sections, from: "$.owned_sections" }
+
   # 2. WHICH CHANGES ARE OPEN — the evidence is changes/<CR-id>/ on disk; a closed change
   #    has moved to changes/archive/. Any open change makes this run a DELTA run.
   #    `matched_label` resolves a CR id passed as the argument to the whole option string,
@@ -670,9 +685,9 @@ workflow:
       - THE MODEL IS READ, NEVER MINED FOR WORK. It describes the WHOLE bounded context,
         while this run builds one feature. Realise only what the PLAN calls for: an entity,
         event or invariant in the model that no plan element realises is a PLANNING gap —
-        surface it, do not implement it. `{{feature}}` is the aggregate this feature owns;
-        any other `## Aggregate:` section belongs to another slice, and you read it only to
-        honour a reference the plan makes, never to generate its code.
+        surface it, do not implement it. The section(s) this feature answers for are
+        {{owned_sections}}; any other `## Aggregate:` section you read only to honour a
+        reference the plan makes, never to generate its code.
       - BIND THE STACK: this lane is `{{be_lane_id}}` — {{be_title}}, language
         {{be_language}} ({{be_ecosystem}}), declared in .appweaver/stacks.json and compiled
         with `{{be_build}}`, tested with `{{be_test}}`. Generate in THAT language and
@@ -715,7 +730,14 @@ workflow:
       - Do NOT add behaviour the plan does not state, and do NOT omit any it does. If the
         plan looks wrong or incomplete, STOP and surface it (it is fixed in plan /
         analyze-plan) — never compensate from the spec or from memory.
-      - This aggregate OWNS its files; never regenerate a file another feature owns.
+      - SHARED AGGREGATE FILES ARE EXTENDED, NEVER REGENERATED. A feature is a capability
+        scope, and other features may act on the same aggregate: its root, entities,
+        value objects and repository are shared code. Where such a file already exists,
+        ADD only the members this plan needs and leave every existing member, signature
+        and test exactly as it is — another feature's code depends on them. Create a file
+        only when it does not exist yet. A file that serves only another feature (its
+        use-case, endpoint or handler) is not this feature's to touch; if this plan needs
+        one changed, STOP and surface it.
       - Where generated code depends on a plan Assumption (DA-n) or Workaround (WA-n), mark
         it with a comment citing that id so it is easy to revisit later.
     outputs:
@@ -1112,15 +1134,15 @@ workflow:
     schema: { overview: "<2-4 sentences of prose>" }
     mock: { overview: "" }
     task: |
-      Write the OKF knowledge-concept Overview for the aggregate `{{feature}}`. 2-4
-      sentences of PROSE:
+      Write the OKF knowledge-concept Overview for the feature `{{feature}}` — that is,
+      for the aggregate it answers for, {{owned_csv}}. 2-4 sentences of PROSE:
       - name the aggregate ROOT and what the aggregate IS;
       - state the INVARIANTS it guards (its BR-nnn — what they require, not their ids);
       - state its TRANSACTION BOUNDARY — what it OWNS inside the boundary vs what it only
         REFERENCES by id.
       The bounded context's domain-model.md is the source where it is in context: read
-      ONLY its `## Aggregate: {{feature}}` section — the other aggregates are other
-      slices' concepts. Where it is not in context, distil the same three things from
+      ONLY {{owned_sections}} — the other sections belong to other aggregates. Where more
+      than one is named, describe the FIRST. Where it is not in context, distil the same three things from
       backend-plan.md's domain section instead.
       Plain prose only: no headings, no bullets, no code fences, no file paths, and no
       restating of the dependency edges (those live in the Depends-On / Cross-References