aw-spec-cli 0.1.26 → 0.1.27

package/assets/.appweaver/orchestrator/workflows/_smoke.orch.yaml

@@ -5,13 +5,15 @@
 # Exercises every extended construct in one run: inputs, set (raw object),
 # execute_script (read-only subcommand), verify_context gates, ask
 # (non-interactive default), foreach + while loops + break, agent_query
-# (mock:), agent_author (mock content), build_context, include
-# (domain-select module), dispatch_hooks (empty).
+# (mock:), agent_author (mock content), build_context, agent_generate (the
+# mock writes SmokeGenerated.cs), agent_review (mock: pass when the files
+# exist), include (domain-select module), dispatch_hooks (empty).
 #
 # Run:
 #   python3 .appweaver/orchestrator/orchestrator.py \
 #     .appweaver/orchestrator/workflows/_smoke.orch.yaml --non-interactive --json
-# Expected: status ok, echo=hello, sum of foreach passes, smoke.md written.
+# Expected: status ok, echo=hello, sum of foreach passes, smoke.md and
+# SmokeGenerated.cs written, review_pass=true.
 # =============================================================================
 
 name: orch-smoke
@@ -138,6 +140,40 @@ workflow:
     action: verify_context
     required_files: ["{{out_dir}}/smoke.md"]
 
+  # agent_generate — the edit step: the agent writes the file itself and reports
+  # files[]. The mock names the file after the task's first `backtick` word and
+  # writes it under out_dir; a reported path not on disk is dropped before binding,
+  # so the non-empty gate proves the file was written.
+  - id: gen_file
+    action: agent_generate
+    tools: "Read,Write,Edit"
+    permission_mode: acceptEdits
+    task: |
+      Write exactly one file, {{out_dir}}/SmokeGenerated.cs, holding the single
+      line `SmokeGenerated` and nothing else. Write nothing outside {{out_dir}}.
+    outputs:
+      - { name: gen_files, from: "$.files" }
+  - id: gate_gen
+    action: verify_context
+    require_non_empty: gen_files
+    on_empty: stop
+    on_empty_message: "agent_generate wrote nothing, or files[] binding is broken"
+
+  # agent_review — read-only review of the files the generation reported; the
+  # mock passes when every reviewed file exists
+  - id: review_file
+    action: agent_review
+    review_of_var: gen_files
+    task: Check that the file holds the single line SmokeGenerated. Decide pass/fail.
+    outputs:
+      - { name: review_pass,   from: "$.pass" }
+      - { name: review_issues, from: "$.issues" }
+  - id: gate_review
+    action: verify_context
+    require_true: review_pass
+    on_false: stop
+    on_false_message: "agent_review result binding is broken"
+
   # F9: include — the shared domain-select module (read-only script + asks;
   # non-interactive: gate→continue, mode→all)
   - id: domain
@@ -156,5 +192,7 @@ outputs:
   mode: "{{mode}}"
   seen: "{{seen}}"
   q_items: "{{q_items}}"
+  generated: "{{gen_files}}"
+  review_pass: "{{review_pass}}"
   domain: "{{domain}}"
   note: "all engine constructs exercised"

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

@@ -141,7 +141,7 @@ workflow:
     on_false: stop
     on_false_message: >
       No .NET host/startup project found — nothing named Program.cs under `{{host_search}}`,
-      the source path the backend lane declares, nor elsewhere in this repository. Wiring a
+      the lane root folder the backend lane declares, nor elsewhere in this repository. Wiring a
       component means editing a host project's startup registration, so there has to be one
       to edit. If this is a .NET repository, scaffold it first with /appweaver foundation.
       If it is not — this lane's ecosystem is `{{host_eco}}` — then this catalogue's runbooks

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

@@ -37,7 +37,7 @@
 # active_version.json (v1.0) so the CR loop works immediately after.
 #
 # GOVERNANCE RECONCILE (the JIT contract, gap-fix #1) — ⏸ HELD, OFF BY DEFAULT.
-# onboard established the PROJECT constitution + guardrails/projects/<project>/ rule set
+# onboard established the PROJECT constitution + guardrails/<project>/ rule set
 # from the whole-repo SCAN, with per-feature specifics marked PROVISIONAL. The reconcile
 # block below carries this feature's real evidence (BR-/CN-/DC-/IC- ids, code coordinates)
 # INTO that scaffold — upgrading provisional → evidenced. It RECONCILES, never re-authors:
@@ -55,7 +55,7 @@
 #
 # Adopt does NOT generate code and does NOT modify source — writes land under
 # specs/<Context>/<Feature>/, in the context's specs/<Context>/domain-model.md, and in the
-# aggregate's OKF concept; the constitution halves and guardrails/projects/<project>/ are
+# aggregate's OKF concept; the constitution halves and guardrails/<project>/ are
 # written only when the reconcile block below is enabled.
 # Fidelity checks spec/design ↔ CODE; the Adopt review is REPORTED for out-of-band
 # closure — it blocks only on structural failures (unmapped code / fabricated spec/design).
@@ -111,7 +111,7 @@ scripts:
 # Sticky standards seed = the UNIVERSAL always-on rule only (ai-rules). The TECHNICAL/
 # architecture set for the reversed DESIGN step (mirrors aw-spec-design) is no longer
 # hardcoded here — it is now CONFIGURATION, loaded per-command from
-# guardrails/projects/<project>/tech-rule-bindings.md under "## /aw-spec-adopt" by the
+# guardrails/<project>/tech-rule-bindings.md under "## /aw-spec-adopt" by the
 # tech-select module (see the tech_select step below). The reversed SPEC step runs
 # include_standards:false and takes its domain frame from constitution.domain.md via
 # build_context — so design never sees a domain rule file (rule partition preserved); the
@@ -335,7 +335,7 @@ workflow:
     on_false_message: "No concept for the aggregate '{{aggregate_primary}}' — the one feature '{{feature_name}}' acts on — in the onboard bundle under {{bundle_dir}}. If its bounded context has not been onboarded, run /appweaver onboard <Context> first; {{bundle_dir}}/aggregates/index.md lists each aggregate with the features that act on it. If '{{feature_name}}' is a NEW feature (no existing code), do NOT adopt it — author it through the forward pipeline (/appweaver specify → plan → implement), which onboard already made brownfield-ready."
 
   # Governance prerequisite: the reverse steps below are authored AGAINST the project
-  # onboard established (the constitution halves + guardrails/projects/<project>/ rule set).
+  # onboard established (the constitution halves + guardrails/<project>/ rule set).
   # Resolve the active domain now and require its rule map to exist — without it there is
   # no code-derived rule set for tech_select to load, no domain frame for the reversed
   # spec, and nothing for the reconcile block to upgrade when it is enabled. Reconciling
@@ -363,10 +363,10 @@ workflow:
     action: verify_context
     require_true: rulemap_exists
     on_false: stop
-    on_false_message: "No active governance for adopt to work against — run /appweaver onboard first. onboard establishes the PROJECT constitution + guardrails/projects/<project>/ rule set (provisional-from-scan) and activates it. Reversing '{{feature_name}}' without that scaffold would author the spec and design against no code-derived rules at all, and leave them with no governance home."
+    on_false_message: "No active governance for adopt to work against — run /appweaver onboard first. onboard establishes the PROJECT constitution + guardrails/<project>/ rule set (provisional-from-scan) and activates it. Reversing '{{feature_name}}' without that scaffold would author the spec and design against no code-derived rules at all, and leave them with no governance home."
 
   # TECHNICAL rule files → sticky standards (configuration, not hardcoded). tech-select
-  # reads guardrails/projects/<project>/tech-rule-bindings.md under "## /aw-spec-adopt" and
+  # reads guardrails/<project>/tech-rule-bindings.md under "## /aw-spec-adopt" and
   # loads that reference set into the sticky standards for reverse_plan
   # (include_standards:true) — the reversed SPEC and MODEL steps turn it off
   # (include_standards:false), keeping them free of architecture (rule partition). No domain
@@ -1119,7 +1119,7 @@ workflow:
   # ═══════════ GOVERNANCE RECONCILE — upgrade onboard's PROVISIONAL scaffold ═══
   # ⏸ HELD 2026-07-29: every step in this block is gated on `reconcile_governance`
   #   (default "false"), so adopt currently does NOT touch the constitution halves
-  #   or the guardrails/projects/<project>/ rule set — onboard's provisional scaffold
+  #   or the guardrails/<project>/ rule set — onboard's provisional scaffold
   #   is left as-is. Flip the var to "true" (workflow vars) to restore the behaviour.
   # Now that this feature is reversed to a TRUSTWORTHY spec (real BR-/CN-/DC-/IC- ids)
   # + design (real code coordinates), reconcile that evidence INTO the governance
@@ -1145,7 +1145,7 @@ workflow:
       - { path: "{{spec_file}}" }                                          # the feature's real BR-/CN-/DC-/IC-
       - { path: "{{backend_plan}}" }
       - { path: "{{feature_dir}}/source-map.md" }
-      - { path: "guardrails/projects/{{gov_domain}}/domain-rule-bindings.md", optional: true }
+      - { path: "guardrails/{{gov_domain}}/domain-rule-bindings.md", optional: true }
       - { path: .appweaver/RULE-PARTITION.md }                                       # the rule-partition authority (which command reads what)
   - id: reconcile_pack
     condition: "{{reconcile_governance}} == true"   # HELD — governance reconcile paused (see vars)
@@ -1153,12 +1153,12 @@ workflow:
     tools: "Read,Write,Edit"
     permission_mode: acceptEdits
     task: |
-      RECONCILE the domain rule-file set in guardrails/projects/{{gov_domain}}/domain/ with the
+      RECONCILE the domain rule-file set in guardrails/{{gov_domain}}/domain/ with the
       newly-adopted feature '{{feature_name}}'. onboard authored these rule files from the
       whole-repo scan with per-feature specifics marked `PROVISIONAL — reconciled at
       adopt`. READ this feature's reversed spec.md + backend-plan.md + source-map.md (in
       context — the real evidence) and the EXISTING rule files under
-      guardrails/projects/{{gov_domain}}/.
+      guardrails/{{gov_domain}}/.
 
       RECONCILE, do NOT re-author:
       - UPGRADE the provisional entries this feature now evidences: replace a
@@ -1174,7 +1174,7 @@ workflow:
       - Preserve the RULE PARTITION in domain-rule-bindings.md (constitution / specify / gate get
         the domain files; design / implement get None). Keep each file's frontmatter and
         note in `generated_by` that adopt reconciled '{{feature_name}}'.
-      Write ONLY inside guardrails/projects/{{gov_domain}}/. Report the files changed/added.
+      Write ONLY inside guardrails/{{gov_domain}}/. Report the files changed/added.
     outputs:
       - { name: pack_reconciled, from: "$.files" }
 
@@ -1250,7 +1250,7 @@ workflow:
       - { path: "{{constitution_domain_file}}" }
       - { path: "{{constitution_technical_file}}" }
       - { path: "{{spec_file}}" }
-      - { path: "guardrails/projects/{{gov_domain}}/domain-rule-bindings.md", optional: true }
+      - { path: "guardrails/{{gov_domain}}/domain-rule-bindings.md", optional: true }
   - id: reconcile_domain
     condition: "{{reconcile_governance}} == true"   # HELD — governance reconcile paused (see vars)
     action: agent_author
@@ -1351,4 +1351,4 @@ outputs:
   composed_file: "{{composed_file}}"
   technical_reconcile_ok: "{{technical_ok}}"
   domain_reconcile_ok: "{{domain_ok}}"
-  next: "Adopted {{feature_name}} (spec.md + backend-plan.md + source-map.md, v1.0) and wrote {{aggregate_sections}} — the model section(s) for the aggregate(s) it acts on, resolved from the {{aggregate_source}} — in the bounded context `{{context}}`'s shared {{domain_model}}. The spec cites BR-nnn by id, the model carries their text, so this slice is checkable by the same gates as a greenfield one and analyze-plan's check 4 now has a model to check against. A section another feature over the same aggregate wrote first was EXTENDED, never duplicated; every other section is untouched. COMPLETED the OKF concept of {{aggregate_primary}} (deepened + linked the deep artifacts; {{xref_edge_count}} cross-slice edge(s) recorded). UI HALF: ui_lane={{ui_lane}} — where it is true this slice also has frontend-plan.md, reversed from the {{ui_count}} UI file(s) the feature map attributes to it; where it is false the repo declared no frontend lane, or this aggregate owns no part of its surface, and a service-only adoption is the correct outcome rather than a gap. In the second case, where a frontend lane IS declared, the feature records lanes=[backend] in its active_version.json (feature_lanes shows it), so plan and the analyze gates treat the frontend lane as absent for THIS feature; run `aw-spec-actions feature-lanes --clear` if it later gains a UI. The SHARED UI surface (app shell, layout, design system) belongs to no slice and stays in {{bundle_dir}}/architecture/frontend.md. NOTE — governance reconcile is currently HELD (reconcile_governance=false): this run did NOT modify the constitution halves or the guardrails/projects/{{gov_domain}}/ rule set, so they keep onboard's provisional scaffold. Close any items in {{feature_dir}}/adopt-review-report.md out of band. The slice is now a NORMAL feature: refine via /appweaver analyze-plan, then drive every change through the CR delta loop (/appweaver specify → plan → analyze-plan-delta → implement → build → analyze-slice-delta → finalize-delta → analyze-slice → close-delta). If a change edits untested legacy behaviour with blast radius, characterize just that surface first (optional on-touch fence). To restore governance reconcile, set reconcile_governance to \"true\" in the workflow vars."
+  next: "Adopted {{feature_name}} (spec.md + backend-plan.md + source-map.md, v1.0) and wrote {{aggregate_sections}} — the model section(s) for the aggregate(s) it acts on, resolved from the {{aggregate_source}} — in the bounded context `{{context}}`'s shared {{domain_model}}. The spec cites BR-nnn by id, the model carries their text, so this slice is checkable by the same gates as a greenfield one and analyze-plan's check 4 now has a model to check against. A section another feature over the same aggregate wrote first was EXTENDED, never duplicated; every other section is untouched. COMPLETED the OKF concept of {{aggregate_primary}} (deepened + linked the deep artifacts; {{xref_edge_count}} cross-slice edge(s) recorded). UI HALF: ui_lane={{ui_lane}} — where it is true this slice also has frontend-plan.md, reversed from the {{ui_count}} UI file(s) the feature map attributes to it; where it is false the repo declared no frontend lane, or this aggregate owns no part of its surface, and a service-only adoption is the correct outcome rather than a gap. In the second case, where a frontend lane IS declared, the feature records lanes=[backend] in its active_version.json (feature_lanes shows it), so plan and the analyze gates treat the frontend lane as absent for THIS feature; run `aw-spec-actions feature-lanes --clear` if it later gains a UI. The SHARED UI surface (app shell, layout, design system) belongs to no slice and stays in {{bundle_dir}}/architecture/frontend.md. NOTE — governance reconcile is currently HELD (reconcile_governance=false): this run did NOT modify the constitution halves or the guardrails/{{gov_domain}}/ rule set, so they keep onboard's provisional scaffold. Close any items in {{feature_dir}}/adopt-review-report.md out of band. The slice is now a NORMAL feature: refine via /appweaver analyze-plan, then drive every change through the CR delta loop (/appweaver specify → plan → analyze-plan-delta → implement → build → analyze-slice-delta → finalize-delta → analyze-slice → close-delta). If a change edits untested legacy behaviour with blast radius, characterize just that surface first (optional on-touch fence). To restore governance reconcile, set reconcile_governance to \"true\" in the workflow vars."

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

@@ -158,7 +158,7 @@ workflow:
     with: { command: aw-spec-analyze-slice }
 
   # 1. WHICH LANES EXIST. Declaration only — this gate reads code, it does not write it, so
-  #    it has no reason to require a source path on disk.
+  #    it has no reason to require a lane root folder on disk.
   - id: lane_resolve
     action: execute_script
     on_error: continue
@@ -448,7 +448,7 @@ workflow:
       the pre-existing slice.
 
       CHECK 7 — PLACEMENT. Every file this change added or edited sits under the lane that
-      owns it: this lane's production code under its source path `{{be_source_path}}`, its
+      owns it: this lane's production code under its lane root folder `{{be_source_path}}`, its
       tests under its test path `{{be_test_path}}`. A service-lane element written into the
       frontend lane's subtree — or outside every lane's paths — is a HIGH `placement` gap.
       One edit outside them is allowed: registering a test project this change created in
@@ -542,7 +542,7 @@ workflow:
       gap. Judge it only over what this change touched.
 
       CHECK 7 — PLACEMENT. Every file this change added or edited sits under this lane's
-      source path, `{{fe_source_path}}`, or — for a test — its test path, `{{fe_test_path}}`.
+      lane root folder, `{{fe_source_path}}`, or — for a test — its test path, `{{fe_test_path}}`.
       A file written into the service lane's subtree is a HIGH `placement` gap — a gap in the
       service surface is a contract delta raised back to that lane, never a client-side edit
       to it. The one edit allowed outside them is the test setup this change had to create,

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

@@ -85,7 +85,7 @@ scripts:
 
 # No hardcoded technical standards seed. The technical rule files the code/conformance
 # passes check against (testing + coding-standards) are now CONFIGURATION, loaded per-
-# command from guardrails/projects/<project>/tech-rule-bindings.md under "## /aw-spec-analyze-slice"
+# command from guardrails/<project>/tech-rule-bindings.md under "## /aw-spec-analyze-slice"
 # by the tech-select module (see the tech_select step below). The DOMAIN gate overlays are
 # still loaded separately, as before (resolve_gate_overlays → load_gate_overlays). This gate
 # does not reference constitution.technical.md. The seed below is behaviour-only — the kit's
@@ -149,7 +149,7 @@ vars:
 workflow:
 
   # 0. TECHNICAL rule files → sticky standards (configuration, not hardcoded).
-  #    tech-select reads guardrails/projects/<project>/tech-rule-bindings.md under
+  #    tech-select reads guardrails/<project>/tech-rule-bindings.md under
   #    "## /aw-spec-analyze-slice" and loads that set (testing + coding-standards) into
   #    the sticky standards the conformance query reads (include_standards: true). The
   #    DOMAIN gate overlays are loaded separately below. No blocking gate: an unconfigured
@@ -559,7 +559,7 @@ workflow:
         mock: { ok: true, unbound: [], notes: [] }
         task: |
           WOULD THIS SLICE RUN? Check the service lane's composition against its code.
-          The lane is `{{be_lane_id}}` and its source path is `{{be_source_path}}`; the
+          The lane is `{{be_lane_id}}` and its lane root folder is `{{be_source_path}}`; the
           backend plan is in context, and its §2.1 Ports, §4.1 Persistence and §4.3 Wiring
           say what has to be bound.
 

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

@@ -26,7 +26,7 @@
 # compiled by its own build command, so what this stage needs is a declaration to compile
 # from, not a particular kind of one; requiring the service lane blocked a frontend-only
 # project that `plan` and `implement` both accept. The rest of the gate is unchanged: no
-# lane declared, a lane with no source path, a source path that is not on disk, and two
+# lane declared, a lane with no lane root folder, a lane root folder that is not on disk, and two
 # lanes claiming overlapping subtrees all still stop the run.
 #
 # Launch:  /appweaver build [strategy]
@@ -48,7 +48,7 @@ scripts:
 
 # Sticky standards seed = the UNIVERSAL always-on rule only (ai-rules). The technical
 # rule files (the compile/fix reference set) are CONFIGURATION, loaded per-command from
-# guardrails/projects/<project>/tech-rule-bindings.md by the tech-select module (see the
+# guardrails/<project>/tech-rule-bindings.md by the tech-select module (see the
 # tech_select step below). Technical rules ONLY — build loads no domain rules and does
 # not reference constitution.technical.md. A required file that is missing is reported
 # at assembly time (`[system] MISSING (required)`), an `optional:` one is skipped.
@@ -61,7 +61,7 @@ vars:
 workflow:
 
   # Rule files → sticky standards: TECHNICAL only, via tech-select, read from
-  # guardrails/projects/<project>/tech-rule-bindings.md under "## /aw-spec-build".
+  # guardrails/<project>/tech-rule-bindings.md under "## /aw-spec-build".
   # NO domain-select here — see the header: build repairs compile errors, a purely
   # technical job, and the domain never reaches this stage anyway (specify is its sole
   # carrier; build reads code and design intent, not spec).
@@ -90,7 +90,7 @@ workflow:
   # project compiles the one it has, whichever kind that is. A frontend-only project is a
   # legal project: `plan` and `implement` both accept one, so refusing it here stopped it
   # at the first stage that had no reason to care. Passing no required kind leaves every
-  # other check armed — no lane declared at all, a lane with no source path, a source path
+  # other check armed — no lane declared at all, a lane with no lane root folder, a lane root folder
   # that is not on disk, and two lanes claiming overlapping subtrees.
   - id: lane_gate
     action: include

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

@@ -58,7 +58,7 @@ scripts:
 # Sticky standards seed = the UNIVERSAL always-on rule only (ai-rules). The FRAMEWORK /
 # test-generation set (same as implement/analyze-slice — HOW to write + place tests) is no
 # longer hardcoded here — it is now CONFIGURATION, loaded per-command from
-# guardrails/projects/<project>/tech-rule-bindings.md under "## /aw-spec-characterize" by the
+# guardrails/<project>/tech-rule-bindings.md under "## /aw-spec-characterize" by the
 # tech-select module (see the tech_select step below). No domain files: the behaviour to
 # fence comes from the CODE + the adopted spec/design/source-map (constitution.technical.md
 # is referred to directly as context), not from domain rules — the tech map lists only
@@ -79,7 +79,7 @@ vars:
 workflow:
 
   # 0. TECHNICAL rule files → sticky standards (configuration, not hardcoded). tech-select
-  #    reads guardrails/projects/<project>/tech-rule-bindings.md under "## /aw-spec-characterize"
+  #    reads guardrails/<project>/tech-rule-bindings.md under "## /aw-spec-characterize"
   #    and loads that test-generation set into the sticky standards the agent_generate steps
   #    ALWAYS prepend. No domain rule file is loaded here — the tech map lists only technical
   #    files. No blocking gate: an unconfigured project soft-continues (the golden-master is

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

@@ -2,7 +2,7 @@
 # aw-spec-constitution (orchestrator) — create/update the SPLIT project constitution
 #
 # Authors up to THREE files. Each ratifies its own MAPPED rule set. The two maps live in
-# the ACTIVE PROJECT (guardrails/projects/<project>/); the files they list live in the
+# the ACTIVE PROJECT (guardrails/<project>/); the files they list live in the
 # shared corpora (guardrails/technology/<stack>/, guardrails/domain/<industry>/), except
 # the three the project's own team authors:
 #   .appweaver/memory/constitution.technical.md  ← "## /aw-spec-constitution" in
@@ -72,6 +72,13 @@
 # a bounded self-correction loop (max 3) — so the whole skill works under every
 # strategy (sdk/sdk-apply/spawn/agent), --checkpoint, or headless.
 #
+# THE DEFAULT SCOPE. On a project with no specs yet the run ends by creating the bounded
+# context MainContext and its feature CoreFeature (specs/MainContext/CoreFeature/) and
+# making both active, so a simple project goes from constitution straight to specify.
+# Any other state is left alone. A developer who wants other names runs
+# select-bounded-context and select-feature, which re-point both pointer files; the empty
+# default folders can then be deleted.
+#
 # NOT part of the per-feature pipeline. Project-level, run-once / amend-on-change.
 #
 # Launch:  /appweaver constitution [strategy] [principles or values…]
@@ -79,8 +86,8 @@
 # =============================================================================
 
 name: aw-spec-constitution
-description: Create or update the split project constitution — constitution.technical.md (technology base) + constitution.ui.md (the frontend lane's base, only where a lane exists) + constitution.domain.md (active domain addenda), each version-bumped with a Sync Impact Report, then composed into constitution.md. Project-level, run-once/amend — not a per-feature phase.
-version: 2.5.0
+description: Create or update the split project constitution — constitution.technical.md (technology base) + constitution.ui.md (the frontend lane's base, only where a lane exists) + constitution.domain.md (active domain addenda), each version-bumped with a Sync Impact Report, then composed into constitution.md. On a project with no specs yet it also creates and activates the default bounded context MainContext and its feature CoreFeature. Project-level, run-once/amend — not a per-feature phase.
+version: 2.6.0
 agent_agnostic: true
 dialect: aw-spec.orchestrator/v1
 
@@ -97,7 +104,7 @@ scripts:
 
 # Sticky standards seed = the UNIVERSAL always-on rule only (ai-rules). The technology-
 # constitution base the TECHNICAL half ratifies is no longer hardcoded here — it is now
-# CONFIGURATION, loaded per-command from guardrails/projects/<project>/tech-rule-bindings.md
+# CONFIGURATION, loaded per-command from guardrails/<project>/tech-rule-bindings.md
 # under "## /aw-spec-constitution" by the tech-select module (see the tech_select step
 # below). tech_select runs BEFORE the technical half AND before domain-select, so the
 # technical author still sees only the technology base + ai-rules — NO domain file: the
@@ -112,6 +119,11 @@ vars:
   domain_ok: "false"      # domain-half validation-loop guard, flipped by constitution-verify
   ui_ok: "false"          # UI-half validation-loop guard, flipped by constitution-verify
   ui_lane: "false"        # set by the three-signal probe below; gates the whole UI block
+  default_context: "MainContext"   # the bounded context a project with no specs yet starts in
+  default_feature: "CoreFeature"   # the feature created inside it and made active
+  scope_created: "false"           # default-scope: whether this run created the pair
+  scope_skipped: ""                # default-scope: why it did not, when it did not
+  active_feature_dir: ""           # default-scope: the active feature after the step
 
 workflow:
 
@@ -121,7 +133,7 @@ workflow:
   #     what makes `(none)` in select-stack a real declaration rather than a shrug.
   #
   #     --allow-missing-root because nothing here reads the subtree: constitution
-  #     ratifies rules, and a greenfield project's source path does not exist until
+  #     ratifies rules, and a greenfield project's lane root folder does not exist until
   #     implement creates it. The on-disk check belongs to the phases that read code.
   - id: lane_model
     action: execute_script
@@ -179,7 +191,7 @@ workflow:
     vars: { svc_lane: "true", setup_tech_flag: "" }
 
   # 0. TECHNICAL rule files → sticky standards (configuration, not hardcoded). tech-select
-  #    reads guardrails/projects/<project>/tech-rule-bindings.md under "## /aw-spec-constitution"
+  #    reads guardrails/<project>/tech-rule-bindings.md under "## /aw-spec-constitution"
   #    and loads the technology-constitution base into the sticky standards the TECHNICAL
   #    half ratifies. Placed FIRST — before the technical half AND before domain-select — so
   #    the technical author sees only technical files: the seam that keeps it domain-free is
@@ -376,7 +388,7 @@ workflow:
     vars:
       ui_lane: "true"
       ui_stack: "{{fe_lane_profile}}"
-      ui_evidence: "lane '{{fe_lane_id}}' ({{fe_lane_profile}}) is declared in .appweaver/stacks.json, owning the source path {{fe_lane_root}}"
+      ui_evidence: "lane '{{fe_lane_id}}' ({{fe_lane_profile}}) is declared in .appweaver/stacks.json, owning the lane root folder {{fe_lane_root}}"
 
   # 9. A mapped UI rule set with no lane to govern. Not fatal and not a reason to
   #    author the half — the declaration decides that — but worth saying out loud,
@@ -405,8 +417,8 @@ workflow:
       No frontend lane in .appweaver/stacks.json — skipping the UI constitution half
       (constitution.ui.md is not created). This is the expected path for a backend-only
       project. To author it, run `/appweaver select-stack`, pick a UI stack and give
-      it a source path, then re-run `/appweaver constitution`. Mapping
-      `## /aw-spec-ui-constitution` in guardrails/projects/<project>/tech-rule-bindings.md
+      it a lane root folder, then re-run `/appweaver constitution`. Mapping
+      `## /aw-spec-ui-constitution` in guardrails/<project>/tech-rule-bindings.md
       supplies the rules that half ratifies, but no longer creates the lane on its own —
       a lane exists because the project declared it.
 
@@ -693,7 +705,41 @@ workflow:
       removed automatically. Delete that file by hand if the lane is gone for good and
       re-run; otherwise restore the lane's signal.
 
-  # 21. Post-execution hooks.
+  # 21. THE DEFAULT SCOPE. A project with no specs yet gets the bounded context named by
+  #     default_context and the feature named by default_feature inside it, both made
+  #     active, so /appweaver specify can run next with no select command in between.
+  #     default-scope acts only when specs/ holds no directory and no feature is active;
+  #     every other state is reported as skipped and left untouched, so amending the
+  #     constitution never moves the active feature and an onboarded brownfield tree is
+  #     never added to.
+  - id: default_scope
+    action: execute_script
+    script: { ref: actions }
+    subcommand: default-scope
+    args: ["--context", "{{default_context}}", "--feature", "{{default_feature}}"]
+    outputs:
+      - { name: scope_created,      from: "$.created" }
+      - { name: scope_skipped,      from: "$.skipped_reason" }
+      - { name: active_feature_dir, from: "$.feature_dir" }
+
+  # 21b. Say what was created and how to choose other names. The never-satisfiable
+  #      `equals` is the engine's announce-only idiom: the step is entered only when the
+  #      pair was created, and the comparison always misses, so the message is emitted
+  #      and the run continues.
+  - id: default_scope_notice
+    action: verify_context
+    condition: "{{scope_created}} == true"
+    require_value: scope_created
+    equals: "never"
+    on_mismatch: continue
+    on_mismatch_message: >
+      Created the default bounded context {{default_context}} and its feature
+      {{default_feature}} at {{active_feature_dir}}/ and made both active, so
+      /appweaver specify <what it does> can run next. To use your own names instead, run
+      /appweaver select-bounded-context <Name> and then /appweaver select-feature <Name>;
+      the empty default folders can then be deleted.
+
+  # 22. Post-execution hooks.
   - id: resolve_post_hooks
     action: execute_script
     script: { ref: actions }
@@ -723,5 +769,8 @@ outputs:
   ui_rule_files: "{{ui_rule_files}}"
   ui_validation_ok: "{{ui_ok}}"
   ui_validation_issues: "{{ui_issues}}"
-  note: "Split constitution authored, one half per LANE the project declared in .appweaver/stacks.json. service_lane / ui_lane report which lanes were found there, and the declaration is the ONLY signal read: a half is a lane's standing governance, so a lane declared `(none)` in select-stack gets no half AND no file. constitution.technical.md is the service lane's base (standing input to the SERVICE lane of plan + implement); constitution.ui.md is the UI lane's UX-* base (standing input to their FRONTEND lane); constitution.domain.md is the domain addenda (standing input to specify + a gate checklist), and it is always authored because domain is not a lane — it addends whichever halves exist. All are composed into constitution.md, which now tolerates an absent technical half: a UI-only project's domain half opens the roman-numeral sequence at I instead of continuing one, and numbering_checked reports false because that check has no subject rather than because it silently passed. Mapping ## /aw-spec-ui-constitution supplies the rules the UI half ratifies but no longer creates the lane on its own — a mapped rule set with no declared lane produces a warning naming both fixes. ui_lane false with ui_included true means a lane was retired after its half was authored: the file is left alone and the log says so, because a ratified governance file is never deleted automatically. If a validation_ok is false, the matching validation_issues lists what still needs a manual touch. See each half's Sync Impact Report for its version bump. Suggested commit: 'docs: amend split constitution'."
-  next: "/appweaver select-feature → specify. select-feature picks the feature to build and every stage from specify onward reads that active feature and stops without it; on a brownfield workspace pick the bounded context first with /appweaver select-bounded-context. From specify the greenfield sequence runs plan → analyze-plan → implement → build → analyze-slice → run → deploy. THE HALVES ARE LOADED PER CONCERN, not all at once — /appweaver specify loads constitution.domain.md; the SERVICE lane of plan + implement loads constitution.technical.md; their FRONTEND lane loads constitution.ui.md. Re-run /appweaver constitution to amend, including to pick up a lane declared or dropped after this run — re-run /appweaver select-stack first to change which lanes exist."
+  default_scope_created: "{{scope_created}}"
+  default_scope_skipped: "{{scope_skipped}}"
+  active_feature: "{{active_feature_dir}}"
+  note: "Split constitution authored, one half per LANE the project declared in .appweaver/stacks.json. service_lane / ui_lane report which lanes were found there, and the declaration is the ONLY signal read: a half is a lane's standing governance, so a lane declared `(none)` in select-stack gets no half AND no file. constitution.technical.md is the service lane's base (standing input to the SERVICE lane of plan + implement); constitution.ui.md is the UI lane's UX-* base (standing input to their FRONTEND lane); constitution.domain.md is the domain addenda (standing input to specify + a gate checklist), and it is always authored because domain is not a lane — it addends whichever halves exist. All are composed into constitution.md, which now tolerates an absent technical half: a UI-only project's domain half opens the roman-numeral sequence at I instead of continuing one, and numbering_checked reports false because that check has no subject rather than because it silently passed. Mapping ## /aw-spec-ui-constitution supplies the rules the UI half ratifies but no longer creates the lane on its own — a mapped rule set with no declared lane produces a warning naming both fixes. ui_lane false with ui_included true means a lane was retired after its half was authored: the file is left alone and the log says so, because a ratified governance file is never deleted automatically. If a validation_ok is false, the matching validation_issues lists what still needs a manual touch. See each half's Sync Impact Report for its version bump. DEFAULT SCOPE: on a project with no specs yet this run created the bounded context {{default_context}} and its feature {{default_feature}} and made both active (default_scope_created true); any other state is left untouched and default_scope_skipped says why. active_feature is the feature specify will write to. Suggested commit: 'docs: amend split constitution'."
+  next: "/appweaver specify <what the feature does> when active_feature is set — on a project with no specs yet that is the default {{default_context}}/{{default_feature}} this run created. To use your own names, run /appweaver select-bounded-context <Name> and then /appweaver select-feature <Name> first; the empty default folders can then be deleted. When no feature is active, run /appweaver select-feature first — every stage from specify onward reads the active feature and stops without it; if the repo uses bounded contexts, pick one with /appweaver select-bounded-context before it, since once any context exists select-feature refuses to run without one. From specify the greenfield sequence runs plan → analyze-plan → implement → build → analyze-slice → run → deploy. THE HALVES ARE LOADED PER CONCERN, not all at once — /appweaver specify loads constitution.domain.md; the SERVICE lane of plan + implement loads constitution.technical.md; their FRONTEND lane loads constitution.ui.md. Re-run /appweaver constitution to amend, including to pick up a lane declared or dropped after this run — re-run /appweaver select-stack first to change which lanes exist."