aw-spec-cli 0.1.26 → 0.1.28

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."

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

@@ -81,5 +81,5 @@ workflow:
 outputs:
   feature_dir: "{{feature_dir}}"
   deployed: "{{configured}}"
-  note: "Set .appweaver/deploy.json {\"command\": \"...\"} to enable an actual deploy; add smoke/rollback via before_deploy/after_deploy hooks."
+  note: 'Set .appweaver/deploy.json {"command": "..."} to enable an actual deploy; add smoke/rollback via before_deploy/after_deploy hooks.'
   next: "done"