@wildo-ai/framework-knowledge 1.1.7 → 1.1.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (226) hide show
  1. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
  3. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
  5. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +29 -5
  6. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
  8. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
  9. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
  10. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
  11. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
  12. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +11 -1
  13. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  14. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  15. package/dist/esm/framework-knowledge.definitions.js +11 -1
  16. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  17. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  18. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  19. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
  21. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
  23. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -3
  25. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +59 -10
  27. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
  30. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  32. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +1 -1
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +5 -5
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
  41. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
  43. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
  45. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +85 -43
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +40 -0
  49. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
  50. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +41 -0
  51. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
  52. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +199 -0
  53. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
  54. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +201 -0
  55. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
  56. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +67 -0
  57. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
  58. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +76 -0
  59. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
  60. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
  61. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
  63. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
  65. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
  67. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
  69. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
  71. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
  73. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
  75. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
  77. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
  79. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
  81. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +36 -2
  83. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
  85. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
  87. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
  89. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
  91. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
  93. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +30 -17
  95. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  96. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  97. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  98. package/dist/knowledge/manifest.json +8 -8
  99. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
  100. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  101. package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
  102. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
  103. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  104. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  105. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +117 -28
  106. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +4 -4
  107. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +133 -59
  108. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  109. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
  110. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
  111. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
  112. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
  113. package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
  114. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +2 -2
  115. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  116. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  117. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +22 -6
  118. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -3
  119. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
  120. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +5 -2
  121. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  122. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  123. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  124. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +71 -37
  125. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
  126. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +105 -0
  127. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +55 -0
  128. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
  129. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
  130. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +78 -0
  131. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +63 -0
  132. package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
  133. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +65 -0
  134. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  135. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  136. package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
  137. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
  138. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
  139. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
  140. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
  141. package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
  142. package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
  143. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  144. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  145. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
  146. package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
  147. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
  148. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
  149. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +10 -0
  150. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +40 -17
  151. package/dist/knowledge/references/brand.name-choice.config.md +127 -0
  152. package/dist/knowledge/references/brand.name-screening.config.md +253 -0
  153. package/dist/knowledge/references/build-plan.task-graph.config.md +64 -11
  154. package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
  155. package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
  156. package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
  157. package/dist/knowledge/references/capability-composition.config.md +67 -4
  158. package/dist/knowledge/references/example.data-seeding.minimal.md +29 -1
  159. package/dist/knowledge/references/market.snapshot.validation.md +1 -1
  160. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
  161. package/dist/knowledge/references/saas.data-seeding.definition-input.md +6 -0
  162. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
  163. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
  164. package/dist/knowledge/references/saas.website.astro.label-loader.md +9 -0
  165. package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
  166. package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
  167. package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
  168. package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
  169. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  170. package/dist/knowledge/registries/framework-topics.json +38 -1
  171. package/dist/knowledge/registries/playbooks.json +68 -20
  172. package/dist/knowledge/registries/source-tags.json +748 -695
  173. package/dist/knowledge/rules/live-context-door.md +5 -2
  174. package/dist/knowledge/skills/INDEX.md +2 -1
  175. package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -1
  176. package/dist/knowledge/skills/brand-name-screening/SKILL.md +154 -0
  177. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +394 -0
  178. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +65 -0
  179. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +5 -2
  180. package/dist/knowledge/skills/config-saas/SKILL.md +31 -4
  181. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +14 -1
  182. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
  183. package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
  184. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
  185. package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
  186. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +11 -1
  187. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
  188. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
  189. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
  190. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -1
  191. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +11 -1
  192. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  193. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -1
  194. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
  195. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
  196. package/dist/knowledge/skills/module-relationships/SKILL.md +6 -4
  197. package/dist/knowledge/skills/seeding-authoring/SKILL.md +51 -3
  198. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +6 -0
  199. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
  200. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
  201. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -0
  202. package/dist/knowledge/skills/website-page-authoring/SKILL.md +84 -3
  203. package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
  204. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
  205. package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
  206. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
  207. package/dist/knowledge/skills/website-section-faq/SKILL.md +15 -0
  208. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
  209. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +15 -0
  210. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
  211. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +15 -0
  212. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
  213. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
  214. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
  215. package/dist/knowledge/skills/website-section-hero/SKILL.md +27 -9
  216. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
  217. package/dist/knowledge/skills/website-section-pricing/SKILL.md +15 -0
  218. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
  219. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +15 -0
  220. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
  221. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +1 -1
  222. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
  223. package/dist/knowledge/topic-index.json +169 -43
  224. package/dist/tsconfig.build.tsbuildinfo +1 -1
  225. package/dist/tsconfig.tsbuildinfo +1 -1
  226. package/package.json +4 -4
@@ -2,7 +2,7 @@
2
2
  "ref": "bottom_up.build-scale",
3
3
  "version": "0.1.0",
4
4
  "phase": "bottom_up",
5
- "intent": "Bottom-up build scale — the THIRD and final build-execution playbook, the pivot from dispatching ONE task safely (the single-flight dispatch contract) to running the build at SCALE: parallelism across several coding agents, the concurrency schedule, and interleaving the companion-owned generation steps concurrently with coding runs. Reads the approved build-plan (the ordered coding-agent task graph, each task carrying a target, ONE MetaWorkflow_FunctionalTopic, its skill(s), and prose prerequisite ordering) and the current journey state, and answers the SCALE questions the single-flight dispatch playbook deliberately left open: (1) derive the ready-SET (a wave / frontier of tasks whose prose prerequisites have ALL SUCCEEDED — not merely been attempted); (2) decide the parallelism degree (how many coding agents run at once) and the worktree-isolation model that keeps each concurrent run's change-set cleanly attributable; (3) schedule the waves respecting the DEPENDS_ON ordering the build-plan encodes; (4) interleave the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) concurrently with coding runs at the points their inputs exist — those steps run through their deterministic companion endpoints, NOT the coding-agent single-flight lock, so they genuinely overlap coding runs; (5) reconcile wave completion across the concurrent runs (all tasks in the frontier SUCCEEDED before the next wave opens) and apply onFailure across siblings + downstream. Then advance to the next wave and loop. Each parallel slot INVOKES the single-flight dispatch contract (the build-dispatch playbook, upstream — select-next / context-pack / one ACP prompt turn / change-set capture / verify-outside / record + onFailure); this playbook does NOT re-specify those per-task mechanics and does NOT re-decompose the plan (the build-decompose playbook owns the task graph) and authors no schemas / no code. IMPORTANT HONESTY: the companion runner HARD-ENFORCES single-flight today (a run plan carries at most ONE coding-agent task; a concurrent dispatch is refused; the workspace-mutation lock + the lock-free cursor + the missing run-outcome observation loop all assume one dispatch at a time). So this v1 scale METHOD is the DECLARATIVE TARGET a runner-serializer slice will realize — on the current runner the waves DEGRADE to sequential single-flight dispatch. And even the deterministic companion-generation steps, though they do not take the coding single-flight lock, cannot SAFELY overlap an active coding run today: the coding run's change-set is captured as a whole-worktree time-window diff, so a generation step writing files inside that window is misattributed to the coding run (the same whole-worktree pollution that forbids two concurrent coding agents) — so the generation steps also serialize outside an active coding-capture window today, and genuine concurrency (coding-parallel OR generation-overlap) both arrive only with the git worktree-per-agent isolation runner task. v1 scaffold: a multi-CODING_AGENT run-completion serializer, git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock are companion-runner mechanism filed as runner tasks, NOT built here; a priority/work-stealing scheduler and cost-optimal packing are a later depth phase.",
5
+ "intent": "Bottom-up build scale — the THIRD build-execution playbook: how the build runs at SCALE, as shipped. A run of a build-execution playbook starts a WAVE: up to the application's build parallelism of build-plan tasks at once (`wildo workbench parallelism`, 5 by default; 1 = one task at a time, the single-flight mode), in ONE shared worktree, as a rolling pool that refills each slot with whatever is ready when a run settles. This playbook declares the same CODING_AGENT executor as the build-dispatch playbook and runs through the same runtime branch, so both start the SAME wave; prefer build-dispatch to start a build, and read this one for the scale questions: (1) the ready-SET — tasks whose declared prerequisites have ALL SUCCEEDED, not merely been attempted, resolved by the host from the declared refs and git; (2) the width — the build parallelism, the person's setting, never chosen by the method; (3) the isolation model — none by decision: the runs share the worktree, only a task being built twice at once is prevented, and overlap is RECORDED on each run (`concurrency`, `interferenceSuspected`); (4) the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) — run through their companion endpoints at their input-ready point, inline while live coding runs continue, at most once per wave; (5) the wave's end — bounded at four dispatches per slot per call, it drains its live runs, commits what their own accepts left as ONE change naming every run it carries, re-runs ALONE each completed task whose product a sibling overwrote, and applies keep_and_flag across siblings + dependents. Each slot runs the per-task dispatch contract of the build-dispatch playbook; this playbook does NOT re-specify it, does NOT re-decompose the plan (the build-decompose playbook owns the task graph), and authors no schemas / no code. A priority / work-stealing scheduler, cost-optimal packing and a revert_changeset failure path are later phases.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -19,7 +19,7 @@
19
19
  "outputs": [],
20
20
  "stepOutputs": [],
21
21
  "method": {
22
- "guidance": "# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and a deliberately honest one.** It is a\n> working first cut of the *scale* orchestration — derive a wave of ready tasks,\n> run several coding agents in parallel under an isolation model, interleave the\n> deterministic companion-generation steps, and reconcile wave completion. But\n> the companion runner **hard-enforces single-flight today**: it refuses a run\n> plan with more than one coding-agent task, refuses a second dispatch while one\n> is active, holds one workspace-mutation lock per run, and has no run-outcome\n> reconciler. So the concurrency described below is the **declarative target** a\n> runner-serializer slice will realize. **On the current runner the waves\n> degrade to sequential single-flight dispatch** — read the \"What the runner\n> actually does today\" section before you assume anything ran in parallel. Do\n> not overclaim concurrency the runner cannot do.\n\n## Where you are in the journey\n\nThis is the **third and final build-execution playbook** — the pivot from\n**dispatching one task safely** (the build-dispatch playbook's single-flight\ncontract) to **running the build at scale**. It runs in the **bottom-up phase**,\nafter the build plan exists (`artifact_exists build-plan`) and the foundation\nstep has authored the app's config and skeleton. You\nare not re-opening the decomposition here, and you are not re-specifying how one\ntask dispatches — you are deciding **how many** tasks run **concurrently** and\n**safely**, in **what order**, with the companion-generation steps interleaved.\n\nUpstream: the **build-decompose** playbook produced the ordered task graph you\nschedule; the **build-dispatch** playbook defined how ONE task dispatches\nsafely — you **invoke that contract per parallel slot**, you do not re-author\nit. **You author neither of those concerns** — see the boundary section.\n\n## What this playbook does\n\nYou are the **scale orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, across the *whole* build: *\"which set\nof tasks is ready to run now, how many run at once and on what isolation, when\ndo the deterministic generation steps run, and when has a wave actually\nfinished?\"* You do **not** produce a new journey artifact — the observable\nresult of the build is the per-task change-sets + task statuses the runner\nrecords on the task rows (the build-dispatch playbook's mechanism), not a\nschedule artifact authored here (see \"What you emit\"). You do **not** decompose\nthe plan, re-specify the per-task dispatch mechanics, author any schema, or\nwrite any code.\n\n## The scale contract — you sequence waves, the dispatch playbook runs each slot\n\nMost of the *per-task* mechanism is **not yours**: selecting one task,\ncomposing its context pack, running one prompt turn against the coding agent over\nthe Agent Client Protocol (answering its permission requests within the declared\nceiling), capturing the change-set, running the verify hook, holding the\nsingle-flight lock, applying the host's actual execution limits — all of that is the **build-dispatch** contract, which each\nparallel slot invokes. Your method here is the **declarative concurrency\nrecipe** the runner (or a future runner-serializer) interprets: *which set* of\ntasks is ready, *how many* run at once, *how* they are isolated, *when* the\ndeterministic generation steps interleave, and *when* a wave is done. Do not\nhand-drive git, do not compose a dispatch prompt, do not re-implement the\nsingle-flight capture — invoke the dispatch contract per slot and let it own\nthose.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the schedule by one\nwave* (and, on today's single-flight runner, by one task within that wave).\nBefore scheduling anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the **build plan** is\n present and approved and the **foundation** ran. For each build-plan task,\n read its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify),\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run\n or a failed verify), or **in-flight**. This full state — not just \"has a\n change-set\" — is what the wave derivation keys on (under `keep_and_flag` a\n *failed* task also has a captured change-set, so presence of a change-set\n alone never means \"done\").\n2. Read the approved **build plan** (`build-plan` — the ordered task graph, with\n each task's prose prerequisite references). It is your work list.\n\n That there is an application to dispatch into is answered by the committed\n `./wildo.saas.config.ts` and skeleton, not by a journey artifact. (A\n `foundation-manifest` played that role until 2026-08-25 and was retired with the\n app-creation verification/digest aspect.) The honest limitation the foundation step\n carries still applies: on-disk skeleton materialization depends on greenfield\n bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale\n contract runs against an existing workspace.\n\n// Operator status: `wildo context journey` (eligibility board + runs in flight); per-task landed\n// state is read from git by the runner.\n\nYou **read** `build-plan`; you **write** no journey\nartifact — the runner records each dispatched task's change-set + status on its\nrow.\n\n## Step 1 — Derive the ready-set (the wave / frontier)\n\nWalk the build plan and compute the **frontier**: the set of tasks that are\n**not yet dispatched** (or previously-**failed** tasks cleared for retry) and\nwhose prose prerequisites have **all SUCCEEDED**. That set is the next **wave**.\n\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task\n enters the frontier only when every task it depends on is\n dispatched-and-succeeded (verify passed). A prerequisite that is\n dispatched-and-**failed** (its change-set flagged for triage under\n `keep_and_flag`), still **in-flight**, or un-run does **not** satisfy the\n dependency — its dependents stay **out of the frontier** until it succeeds.\n This is the U13b readiness discipline, lifted to a set: do not open a wave on\n a schema whose run has not verified.\n- **The wave respects the build-plan ordering.** The build-decompose playbook\n encoded the DEPENDS_ON edges (the per-resource stage order schema → config →\n ui-behavior → spec, the cross-topic edges, relationship-after-endpoints); the\n frontier is exactly the tasks with no unsatisfied edge remaining. You do not\n re-derive or re-order those edges — you read them and compute the ready-set.\n- **An empty frontier is a terminal state.** If no task is ready — every task\n has succeeded, or the only undispatched tasks are blocked behind an\n unresolved failure — the build is done (or blocked on a flagged failure):\n report it and stop. An empty build plan is the same.\n\n## Step 2 — Decide the parallelism degree + the worktree-isolation model\n\nFor the frontier, decide **how many** coding agents run at once and **on what\nisolation**. This is the core scale decision, and it is bounded by a hard\nsafety constraint, not just throughput:\n\n- **Change-set attribution requires isolation.** The dispatch contract captures\n each run's change-set by diffing the worktree around the run and attributing\n every file as `RUN_EXCLUSIVE`, `APPEARED_DURING_RUN`, or\n `BASELINE_DIRTY_AMBIGUOUS`. **Two coding agents mutating the SAME worktree\n concurrently make every touched file `BASELINE_DIRTY_AMBIGUOUS`** — each run\n looks like it started against a tree the other was dirtying — which\n **destroys per-run attribution**. So real parallelism needs one of:\n - **git worktree-per-agent isolation** — each concurrent coding agent runs in\n its own git worktree (a disjoint checkout of the same repo), so each run's\n change-set is captured against a tree only it mutates; the worktrees are\n reconciled/merged after the wave. This is the general answer.\n - **module / resource partitioning** — schedule concurrent agents only onto\n tasks whose targets touch **disjoint file sets** (different modules /\n resources), so even on one shared worktree no two runs collide. This is the\n cheaper answer when the frontier naturally partitions by module.\n - **or keep coding single-flight** and only parallelise the deterministic\n companion-generation steps (Step 3), which are not coding-locked.\n- **Pick the degree deliberately, not maximally.** At scaffold depth prefer a\n small degree (or a module partition) over max fan-out — cost-optimal packing,\n a priority / work-stealing scheduler, and backoff are a later depth phase, not\n this scaffold. State the isolation model you chose; a wave with degree > 1 and\n **no** isolation answer is unsafe (the reviewer rubric flags it as a GAP).\n\n## Step 3 — Interleave the deterministic companion-generation steps\n\nThe build plan carries **companion-owned generation steps** — labels / i18n,\nemail templates, seeds — as tasks. These are **deterministic companion\nendpoints**, not coding-agent dispatches: they do **not** contend for the\ncoding single-flight lock. It is tempting to conclude they can freely run\n*alongside* a coding run — but there is a subtlety that makes that unsafe on\ntoday's runner, see the caveat below.\n\n- **Run each generation step at its input-ready point.** A labels/i18n step runs\n after the resources it labels exist; an email step after its templates'\n definition surfaces exist; a seed step after the resources it seeds exist.\n Schedule each at its input-ready point in the wave sequence — do not block a\n coding wave on them and do not run them before their inputs exist. (The\n *ordering* is what matters here; the *concurrency* is deferred — see the\n caveat.)\n- **Route them to their deterministic endpoint, not the coding lane.** Do not\n dispatch a coding agent for a labels/email/seed step — it has a deterministic\n companion generator. Treating a generation step as a coding dispatch is scope\n creep the reviewer flags.\n- **CAVEAT — no attribution-safe overlap with an active coding run today.** The\n coding run's change-set is captured as a **whole-worktree time-window diff**\n (every tracked-dirty + untracked file in the window). So a generation step\n writing label / email / seed files **while a coding dispatch is capturing** is\n misattributed to that coding run — its files show up as the coding run's own\n edits. This is the *same* whole-worktree pollution that forbids two concurrent\n coding agents (Step 2), and it applies identically to coding + generation. So\n on today's runner the generation steps must **also** be serialized to run\n **outside** an active coding-capture window (i.e. between coding runs). Genuine\n overlap — generation alongside coding, and coding alongside coding — both\n arrive only with git worktree-per-agent isolation (the runner task in Step 5's\n gap note). Until then, keep the input-ready *ordering* and serialize.\n\n// The trigger is `wildo creation run <playbookRef>` (or `/wildo:run` from a Claude Code session),\n// which reaches the companion's run route with the local token attached. Each coding slot invokes the\n// single-flight dispatch contract; each generation step runs its deterministic endpoint.\n\n## Step 4 — Check the actual host authorization boundary\n\nA coding dispatch writes the application workspace. Read its selected task, readiness,\nmutation scope and the configured coding host's authorization policy before invoking it.\nThe single-flight mutation lock still applies to the current shared workspace.\n\nThe playbook's `approval` declaration and the journey autonomy presets express policy\nintent. The current playbook runner does not interpret them as pre-dispatch gates,\nautomatic authorization, or a GUIDED/YOLO mapping. A declared `approve_before` does\nnot create a pending Authority Request, and no authority workflow exists to create one —\nnever invent one from an enum.\n\nLikewise, do not infer enforced per-playbook or per-journey run ceilings from declared\nbudget fields. Respect the limits actually reported by the execution host. Inspect the\nrecorded changes and verification result after each task; no preset commits or accepts them.\n\n## Step 5 — Reconcile wave completion, then advance\n\nA wave is done only when **every task in the frontier reached a terminal\nSUCCEEDED outcome** (change-set captured + verify passed) or is explicitly held\nas a blocked / flagged failure. Only then does the next frontier open (Step 1).\n\n- **Do not open the next wave on an unfinished one.** Advancing while a wave's\n tasks are still in-flight, or with an unreconciled failure, risks a downstream\n task building on an unfinished prerequisite. Reconcile first.\n- **Failure disposition across siblings + downstream** — this playbook's\n declared `onFailure` describes **`keep_and_flag`**; the current host retains changes for review. A failed/timed-out task keeps its captured\n change-set flagged for human triage (never silently reverted, never an\n un-recorded half-applied state). Its already-dispatched **siblings** in the\n same wave are left to complete; its **dependents** in later waves stay\n **blocked** (Step 1) until it is triaged and re-dispatched successfully.\n Triage is a human decision: keep + fix forward, unwind the flagged change-set\n by hand, or re-dispatch once the blocker is resolved. This playbook does not\n auto-retry a failed task (automated retry / backoff is a deferred build-loop\n resilience concern).\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a\n> failed run's edits is a *mutating* git op, deliberately **outside** the\n> read-only change-set carve-out the dispatch lane observes. So `keep_and_flag`\n> is both the correct F-5 workspace-safety posture and the behavior the runner\n> enforces today; a `revert_changeset` path is a deliberate later boundary.\n\nThen **loop**: on the next run, the build plan's task records reflect the just-completed\nwave's outcomes (`wildo build tasks`), and you derive the next frontier (Step 1). Close a\nsignificant stretch of the build with a progress summary — which waves ran, which\nchange-sets landed, what verify said, which generation steps interleaved, and\nany failed task left flagged for triage.\n\n## What the runner actually does today (do not overclaim)\n\nBe honest with the creator about the gap between this method and the runner:\n\n- **The runner enforces single-flight.** It refuses a run plan carrying more\n than one coding-agent task, refuses a second dispatch while one is active, and\n holds one workspace-mutation lock per background run. So a wave with\n parallelism degree > 1 is **not** realizable on today's runner — the wave\n **degrades to sequential single-flight dispatch** (repeated invocation of the\n build-dispatch contract, one task at a time, in frontier order). The frontier\n math, the readiness discipline, and the reconciliation are all still correct\n and useful sequentially — you just do not get concurrency yet.\n- **No overlap is attribution-safe today — not even a companion-generation\n step.** The generation endpoints are not coding-locked, but the coding\n change-set capture is a whole-worktree time-window diff, so a generation step\n writing files while a coding dispatch is capturing is misattributed to that\n run (Step 3's caveat). So the generation steps **also** serialize outside an\n active coding-capture window: their input-ready *ordering* holds, only the\n *concurrency* is deferred. Safe overlap of generation-with-coding, and\n coding-with-coding, both require git worktree-per-agent isolation.\n- **The concurrency this method describes is the declarative target** for a\n runner-serializer slice (multi-coding-agent run-completion serialization,\n git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock)\n — filed as runner tasks, **not** built by this scaffold playbook. Until they\n land, run the waves sequentially and do not claim a parallel run (or a\n generation-alongside-coding overlap) happened when it did not.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **scale-orchestration depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order\n the graph, or add tasks — the **build-decompose** playbook owns the task\n graph. You read it and schedule from it.\n- **The per-task dispatch contract.** You do NOT re-specify single-flight\n locking, context-pack composition, change-set capture, or the verify hook —\n the **build-dispatch** playbook owns \"how ONE task dispatches safely\", and\n each parallel slot **invokes** that contract. If you catch yourself describing\n how a single task captures its change-set, stop — that is the dispatch\n playbook.\n- **The runner-serializer mechanism.** The multi-coding-agent serializer, git\n worktree-per-agent provisioning, the run-outcome reconciler, and the cursor\n lock are **companion-runner mechanism**, filed as runner tasks — this\n declarative method does not build them.\n- **A priority / work-stealing scheduler + cost-optimal packing.** Deciding an\n optimal task ordering within a band, work-stealing across idle slots, backoff,\n and cost-optimal packing are a later depth phase — the v1 scaffold picks a\n small parallelism degree (or a module partition) and a simple frontier order.\n- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the v1\n disposition.\n- **Auto-executed reviewer checklist.** The scale-soundness checklist ships\n **declarative** — the deterministic typecheck gate runs automatically; nothing\n executes the checklist prose (rubric-only judge gates were retired at the\n flexible-intelligence hard cut). Do not assume it auto-ran.\n- **Schema / field authoring + code generation.** The **coding agents** author\n fields, schemas, ui-behavior, and code at dispatch time — never the\n orchestrator.\n\nIf you find yourself designing how ONE task dispatches safely rather than how\nMANY tasks are scheduled + reconciled, stop — that is the build-dispatch\nplaybook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable\nresult of the build — each task's **change-set** (files touched, attributed,\nsummarized) and **status** — is materialized by the runner on the dispatched\ntask rows (the build-dispatch playbook's mechanism), not authored here. A\nseparate schedule / wave-log artifact family is deliberately not added: the task\nrows already *are* the dispatch record and a second home for the same record\nwould drift (a typed wave-schedule / run-ledger contract is a filed later-phase\nitem). Use the configured host's actual authorization boundary and review its\nrecorded changes and verification outcomes. The approval declaration alone does\nnot authorize or gate dispatch.\n\n## References\n\n- A playbook's declared `approval` and failure policy gate nothing on a leaf run; they are read only\n at a composite lane's boundary, where they frame a decision for the person and revert nothing.\n\n## Reviewer checklist — `scale-schedule-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the SCALE orchestration ran the build soundly — the trust-but-verify reviewer pass over how MANY tasks were scheduled, parallelised, and reconciled, WITHOUT straying into how ONE task dispatches (that is the build-dispatch playbook's rubric) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task dispatched in a wave had ALL its prose prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP (the build stage ran against a missing prerequisite). A prerequisite whose run FAILED (its change-set flagged under keep_and_flag) does NOT satisfy the dependency — its dependents must stay blocked, and dispatching them anyway is a GAP. (2) PARALLELISM SAFETY / ATTRIBUTION — the concurrent coding runs in a wave were isolated so each run's change-set is cleanly attributable (files RUN_EXCLUSIVE / APPEARED_DURING_RUN per run), via git worktree-per-agent isolation OR a module/resource partition that puts every concurrent agent on a DISJOINT file set. Two concurrent coding agents mutating the SAME worktree — which makes every touched file BASELINE_DIRTY_AMBIGUOUS and destroys per-run attribution — is a GAP (the single-flight floor was bypassed without an isolation answer). Note the honest floor: the runner enforces single-flight today, so on the current runner a 'wave' degrades to SEQUENTIAL single-flight dispatch and this invariant reads whether the METHOD declared a sound isolation model, not whether concurrency actually ran. (3) COMPANION-GENERATION INTERLEAVE — the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) ran through their deterministic companion endpoints AFTER the resources / modules whose output they consume existed, at the right point in the schedule order; a generation step ordered before its inputs exist, or a missing generation step for authored surfaces, is a CONCERN; treating a deterministic generation step as a coding-agent dispatch (dispatching an agent for it) is a CONCERN. Note the honest floor: the generation steps do NOT take the coding single-flight lock, but the coding change-set capture is a whole-worktree time-window diff, so a generation step writing files WHILE a coding dispatch is capturing is misattributed to that coding run — so on today's runner the generation steps also serialize outside an active coding-capture window, and this invariant reads whether they ran at the right point in the ORDER, not whether they truly overlapped a coding run (safe overlap needs worktree isolation). (4) WAVE-COMPLETION RECONCILIATION — the next wave opened only after every task in the current frontier reached a terminal SUCCEEDED outcome (or was explicitly held as a blocked / flagged failure); advancing the schedule while a wave's tasks were still in-flight or with an unreconciled failure is a GAP (a downstream task could build on an unfinished prerequisite). (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task in a wave kept its captured change-set flagged for human triage (keep_and_flag), its already-dispatched siblings in the same wave were left to complete, and its DEPENDENTS in later waves stayed blocked until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the orchestration stays at SCALE depth: it derives ready-sets, schedules waves, sets the parallelism + isolation model, interleaves the companion-generation steps, and reconciles completion. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT re-specify the per-task dispatch mechanics (single-flight lock / context-pack / change-set capture / verify — the build-dispatch playbook owns those; the scale orchestrator INVOKES that contract per slot), and does NOT itself author schemas / fields / code (the coding agents do that at dispatch time). Evidence of re-decomposition, re-authoring the single-task dispatch contract, or the orchestrator authoring code itself is a CONCERN (scope creep out of the scale lane). (The checklist is declarative: nothing executes it; the current host's deterministic checks apply; the approval enum alone adds no gate.)\n",
22
+ "guidance": "# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **The build already runs at scale, and this playbook describes how.** A run of\n> a build-execution playbook starts a **wave**: up to N build-plan tasks at once\n> in the application's one worktree, N being the application's **build\n> parallelism** (`wildo workbench parallelism`, 5 unless the person set it). This\n> playbook and the build-dispatch playbook declare the same executor and run\n> through the same runtime branch, so they start the SAME wave. Prefer the\n> build-dispatch playbook to start a build; read this one for how a wave is\n> scheduled, how wide it is, and how it is reconciled. With a build parallelism\n> of `1` the lane dispatches one task at a time (the single-flight mode).\n\n## Where you are in the journey\n\nThis is the **third build-execution playbook**. It runs in the **bottom-up\nphase**, after the build plan exists (`artifact_exists build-plan`) and the\nfoundation step has authored the app's config and skeleton. You are not\nre-opening the decomposition here, and you are not re-specifying how one task\ndispatches — you are reading **how many** tasks run **concurrently**, in **what\norder**, with the companion-generation steps interleaved, and how the wave\n**ends**.\n\nUpstream: the **build-decompose** playbook produced the ordered task graph the\nwave schedules; the **build-dispatch** playbook defines the per-task contract\nevery slot runs (context pack, one ACP prompt turn, change-set capture, verify\noutside the agent, record + `onFailure`). **You author neither of those\nconcerns** — see the boundary section.\n\n## What this playbook does\n\nYou are the **scale reader**. Across the *whole* build you answer: *\"which tasks\nare ready now, how many run at once, when do the deterministic generation steps\nrun, and when has a wave actually finished?\"* You do **not** produce a journey\nartifact — the observable result of the build is the per-task change-sets and\ntask statuses the runner records on the task rows (see \"What you emit\"). You do\n**not** decompose the plan, re-specify the per-task dispatch mechanics, author\nany schema, or write any code.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the build by one\nwave*. Before reasoning about a wave:\n\n1. Read the current journey state and scope from what this run is given — the\n loaded specifications and the workspace sections of your brief — and do not\n re-derive it. Confirm the **build plan** is present and approved and the\n **foundation** ran. For each build-plan task, read its dispatch state from\n its task row (`wildo build tasks`) — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify),\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run\n or a failed verify), or **in-flight**. Under `keep_and_flag` a *failed* task\n also has a captured change-set, so the presence of a change-set alone never\n means \"done\".\n2. Read the approved **build plan** (`build-plan` — the ordered task graph, with\n each task's declared prerequisite references). It is the work list.\n\n That there is an application to dispatch into is answered by the committed\n `./wildo.saas.config.ts` and skeleton, not by a journey artifact.\n\n// Operator status: `wildo context journey` (eligibility board + runs in flight); per-task landed\n// state is read from git by the runner.\n\nYou **read** `build-plan`; you **write** no journey artifact.\n\n## Step 1 — The ready-set (the frontier)\n\nA task is **ready** when it is not yet dispatched (or a previously-**failed**\ntask cleared for retry), it is not already running, and every prerequisite it\ndeclares has **SUCCEEDED** — not merely been attempted. A prerequisite that is\ndispatched-and-failed, in-flight, or un-run does **not** satisfy the dependency.\nThe runner resolves this from the declared prerequisite refs and from git; it is\nnever inferred from prose, and you do not re-order the edges the build-decompose\nplaybook encoded.\n\nThe wave is a **rolling pool**, not a fixed batch: when a run settles, its slot\nis refilled with whatever is ready THEN, so a task that just landed unlocks its\ndependents within the same wave. An empty frontier with no run live ends the\nwave; if every task has landed the build is done (and the wave reports whether\nthe application assembles), and if the only remaining tasks are stuck the wave\nnames them and why.\n\n## Step 2 — The width and the isolation model, as shipped\n\n- **The width is the build parallelism.** `wildo workbench parallelism` shows it\n and sets it, from `1` to a safety ceiling; the default is 5. The runner reads it\n at the start of every wave, so a change needs no restart. Each slot is a live\n coding agent spending on its own, so the width is the person's decision, not\n the method's: do not propose a different degree as part of a run.\n- **The runs share ONE worktree, by decision.** Concurrent agents editing the same\n tree reconcile fine in practice, so the lane does not isolate them (no\n worktree per agent, no partition by module). It prevents only a task being\n built twice at once. Everything else is DETECTED and REPAIRED (Step 4).\n- **Attribution is recorded, not guaranteed.** Each run still captures its\n change-set and attributes every file (`RUN_EXCLUSIVE`, `APPEARED_DURING_RUN`,\n `BASELINE_DIRTY_AMBIGUOUS`). In a wave, files a sibling also touched are\n expected to come out ambiguous; the run's `concurrency` entry names the runs\n that overlapped it and the paths both touched, which is what a reviewer reads\n to settle authorship.\n- **One wave is bounded.** A call takes at most four tasks per slot and then\n stops taking new ones, waits for its live runs, and returns. The next run of a\n build-execution playbook continues from where the build stands.\n- **One wave at a time.** The companion refuses a second wave while one runs —\n submitted, running, or in its end-of-wave commit and repair — because a second\n wave would double the width and write while the first one repairs.\n\n## Step 3 — The deterministic companion-generation steps\n\nThe build plan carries **companion-owned generation steps** — labels / i18n,\nemail templates, seeds — as tasks. They run through their **deterministic\ncompanion endpoint**, never a coding agent.\n\n- **They run at their input-ready point**, like any task: a labels step after the\n resources it labels exist, a seed step after the resources it seeds exist. Their\n readiness is declared in the plan the same way.\n- **In a wave they run in their turn while the coding runs already started keep\n going.** The runner runs a ready generation step inline as it fills the wave;\n it does not wait for the live coding runs to settle first. A generation step's\n files that land inside a coding run's capture window are recorded as overlap on\n that run, and the end-of-wave repair commits them with the rest.\n- **Each generation step runs at most once per wave.** If its landing is still unmet\n afterwards, the wave stops taking tasks rather than re-select it forever; the\n next wave tries again, and a step that never lands is a stuck task to report.\n\n// The trigger is `wildo build run` from a console (or `/wildo:build` in a Claude Code session),\n// which starts a wave through the build-dispatch playbook; `wildo creation run <playbookRef>`\n// starts one through this playbook or that one alike.\n\n## Step 4 — How a wave ends: reconcile, repair, advance\n\nA wave stops taking tasks for one of four reasons — nothing ready, its per-call\ncap, a generation step it already ran, or a refused admission — and it always\ndrains the runs already live before it ends.\n\n- **The repair, once nothing is writing.** The runner commits what the runs' own\n accepts left in the tree as ONE change naming every run whose writes it may\n carry, failed runs included (a failed run's files sit in the same tree). Then\n each run that COMPLETED but whose declared product a sibling overwrote is\n re-armed and re-run ALONE, so nothing can overwrite the second attempt; the\n number of such re-runs per task is bounded, after which the task waits for a\n person. Each repair is on the wave's result and on the task's record\n (`interference`).\n- **Failure disposition across siblings + downstream** — `keep_and_flag`. A\n failed or timed-out run keeps its captured change-set flagged for human triage\n (never silently reverted). Its siblings in the same wave run to completion. Its\n **dependents** stay out of every frontier until it is triaged and re-dispatched\n successfully. This playbook does not auto-retry a failure that was the task's\n own; only a suspected interference is re-run.\n- **Advance.** On the next run, the task records reflect the wave's outcomes\n (`wildo build tasks`), and the next wave selects from what is ready now. Close a\n significant stretch of the build with a progress summary — which waves ran,\n which change-sets landed, what verify said, which runs overlapped or were\n repaired, and any task left flagged for triage.\n\n> **Why keep_and_flag, not revert_changeset.** Reverting a failed run's edits is\n> a *mutating* git op, deliberately **outside** the read-only change-set\n> carve-out the dispatch lane observes; with a shared worktree it would also\n> reach a sibling's files. A `revert_changeset` path is a deliberate later\n> boundary.\n\n## Step 5 — Check the actual host authorization boundary\n\nA coding dispatch writes the application workspace. Each run is confined to its\nown task's mutation scope by the configured coding host's authorization policy;\nnothing confines it from its siblings, which is what Steps 2 and 4 are about.\n\nThe playbook's `approval` declaration and the journey autonomy presets express\npolicy intent. The current playbook runner does not interpret them as\npre-dispatch gates, automatic authorization, or a GUIDED/YOLO mapping. A declared\n`approve_before` does not create a pending Authority Request — never invent one\nfrom an enum. Do not infer enforced run ceilings from declared budget fields;\nrespect the limits actually reported by the execution host.\n\n## Boundary (owned by a sibling, or deferred to a later phase)\n\nExplicitly **out of scope here**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order\n the graph, or add tasks — the **build-decompose** playbook owns the task graph.\n- **The per-task dispatch contract.** You do NOT re-specify context-pack\n composition, change-set capture, or the verify hook — the **build-dispatch**\n playbook owns \"how one task dispatches safely\", and every slot runs it.\n- **Choosing the width or a different isolation model.** The width is the\n application's build parallelism, set by the person; the shared worktree with\n detection and repair is the lane's decision. A priority / work-stealing\n scheduler and cost-optimal packing are a later depth phase.\n- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the\n disposition.\n- **Schema / field authoring + code generation.** The **coding agents** author\n fields, schemas, ui-behavior, and code at dispatch time — never the\n orchestrator.\n\n## What you emit\n\n**No journey artifact.** The observable result of the build — each task's\n**change-set** and **status**, plus each run's overlap and repair record — is\nmaterialized by the runner on the task rows and on the wave's result, not\nauthored here. A separate wave-log artifact family is deliberately not added:\nthe task rows already *are* the dispatch record, and a second home for it would\ndrift.\n\n## References\n\n- A playbook's declared `approval` and failure policy gate nothing on a leaf run; they are read only\n at a composite lane's boundary, where they frame a decision for the person and revert nothing.\n\n## Reviewer checklist — `scale-schedule-sound`\n\nCreator-facing review guidance (the generic rubric-only gate kind was retired at the flexible-intelligence hard cut; nothing executes this checklist):\n\nJudge whether a WAVE ran the build soundly — how MANY tasks were scheduled, run concurrently, and reconciled, WITHOUT straying into how ONE task dispatches (the build-dispatch playbook's checklist) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task the wave dispatched had ALL its declared prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP. (2) WIDTH — the wave ran no more coding runs at once than the application's build parallelism; more is a GAP, and a width chosen by the method rather than by the person's setting is a CONCERN. (3) OVERLAP ACCOUNTED FOR — the runs shared one worktree by design, so overlap is expected; each run that overlapped another carries a `concurrency` record naming the runs and paths, and a change-set dominated by BASELINE_DIRTY_AMBIGUOUS files is resolved against that record. An overlap the reviewer cannot account for from the records is a CONCERN; a run accepted as clean while its record says `interferenceSuspected` is a GAP. (4) REPAIR — after the runs settled, the wave's end-of-run commit names the runs whose writes it carries, and every completed run whose product a sibling overwrote was re-run alone (or is shown waiting for a person once its re-runs were spent); a lost product with no repair and no record is a GAP. (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task kept its captured change-set flagged for human triage (keep_and_flag), its siblings in the wave were left to complete, and its DEPENDENTS stayed out of later frontiers until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP. (6) GENERATION STEPS + BOUNDARY — the deterministic companion-generation steps ran through their companion endpoints at their input-ready point, at most once per wave, and never as a coding-agent dispatch (a CONCERN otherwise); the orchestration did not re-decompose the plan, re-specify the per-task contract, or author code itself (a CONCERN otherwise).\n",
23
23
  "skillRefs": [],
24
24
  "skillBodyRefs": [],
25
25
  "contextSources": [],
@@ -34,13 +34,20 @@ DECLARE:
34
34
  |---|---|---|
35
35
  | `add-website` | the market declares an inbound web channel (organic or paid search, content, owned or paid social); else a brand brief has landed; else the business model declares pricing plans | `market-snapshot.channels`, `brand-brief`, `business-model.plans` |
36
36
  | `add-technical-doc` | a targeted ICP (CORE or EXPANSION) is a legal entity; else a non-functional requirement declares PORTABILITY | `market-snapshot.icps`, `requirements.nonFunctional` |
37
- | `add-locale` | a website is composed and the application configuration serves more than one language — one locale per language beyond the primary | `appPreferences.languages` in the application configuration (a host fact: no family declares languages, and the configuration already does) |
37
+ | `add-locale` | a website is composed and either the market targets a country whose languages the configuration does not serve (one locale for each such country's first listed language) or the configuration serves more than one language (one locale per language beyond the primary) — the decision names its `locales` | `market-snapshot.icps` geographies (CORE and EXPANSION), and `appPreferences.languages` in the application configuration (a host fact: no family declares languages, and the configuration already does) |
38
38
 
39
39
  Where no typed declaration can decide a scenario, the record says **DECLINED with the basis
40
40
  `NO_DECLARATION_DECIDES_IT` and names the declaration that would decide it** — a field for
41
41
  somebody to add, never a question for somebody to answer. Today the only such case is `add-locale`
42
42
  when a website is composed but the host could not read the configuration's languages.
43
43
 
44
+ Each basis justifies exactly ONE disposition (`COMPOSITION_BASIS_DISPOSITION`): a declaration that
45
+ was read and implies nothing is `NO_DECLARATION_IMPLIES_IT`, never a NEED basis with a DECLINED
46
+ verdict. A market whose countries the configuration cannot address is never declined in silence:
47
+ with a website it makes `add-locale` NEEDED on `MARKET_TARGETS_UNSERVED_LANGUAGES`, naming each
48
+ language, and with or without one the coherence report names the gap as a contradiction, so the
49
+ configuration's own `enabledLanguages` can follow.
50
+
44
51
  Scenarios another step applies are recorded as **OWNED_BY_ANOTHER_STEP**, naming the owner, so
45
52
  the record stays total without claiming the application lacks them:
46
53
 
@@ -42,7 +42,7 @@
42
42
  ],
43
43
  "stepOutputs": [],
44
44
  "method": {
45
- "guidance": "# Capability Composition — Which Scenarios This Application Needs\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nThe framework ships one composition scenario per folder under `templates/saas/scenarios/`. Two of\nthem — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The\nothers give an application a marketing website, a documentation portal, a cron minion, a worker, a\nprovider, a file-picker provider, a second website locale, another deployment environment or the\noptional 3D layout, and until this step existed nothing in the journey decided whether an\napplication needed any of them: they were reachable only by a person running `wildo compose`.\n\nThis step records that decision as the `capability-composition` family: **one decision per\nscenario the framework ships**, each with a disposition, the closed basis it was derived from,\nand a one-sentence detail naming the declaring entries.\n\n## It is derived, never asked\n\nNothing here is an interview. Every decision is read off what the application's own families\nDECLARE:\n\n| scenario | NEEDED when | read from |\n|---|---|---|\n| `add-website` | the market declares an inbound web channel (organic or paid search, content, owned or paid social); else a brand brief has landed; else the business model declares pricing plans | `market-snapshot.channels`, `brand-brief`, `business-model.plans` |\n| `add-technical-doc` | a targeted ICP (CORE or EXPANSION) is a legal entity; else a non-functional requirement declares PORTABILITY | `market-snapshot.icps`, `requirements.nonFunctional` |\n| `add-locale` | a website is composed and the application configuration serves more than one language — one locale per language beyond the primary | `appPreferences.languages` in the application configuration (a host fact: no family declares languages, and the configuration already does) |\n\nWhere no typed declaration can decide a scenario, the record says **DECLINED with the basis\n`NO_DECLARATION_DECIDES_IT` and names the declaration that would decide it** — a field for\nsomebody to add, never a question for somebody to answer. Today the only such case is `add-locale`\nwhen a website is composed but the host could not read the configuration's languages.\n\nScenarios another step applies are recorded as **OWNED_BY_ANOTHER_STEP**, naming the owner, so\nthe record stays total without claiming the application lacks them:\n\n| scenario | owner |\n|---|---|\n| `add-module`, `add-resource` | `bottom_up.foundation` — the domain composition |\n| `add-minion`, `add-worker-node`, `add-worker-rust` | `bottom_up.foundation` — one per surface the integration plan declares |\n| `add-custom-operation`, `add-website-section`, `add-marketing-page`, `add-file-picker-provider` | the build tasks that produce those artifacts (`bottom_up.build-decompose`) |\n| `add-provider` | the foundation's provider decision |\n| `add-environment` | the operator, at deployment (`wildo compose add-environment`) |\n| `add-3d-layout` | the operator's opt-in (`wildo compose add-3d-layout`): nothing a product declares decides a rendering style, so the journey never adopts the optional 3D layout |\n\n## Where it lands, and who reads it\n\nThe family lands at `specifications/src/capability-composition/index.ts` and is wired onto the\n`capabilityComposition` companion-exports slot. `bottom_up.foundation` reads it there: the NEEDED\nscenarios are applied after the domain scenarios, with the application's own host facts (slug,\ndisplay name, public domain from its infrastructure environments, its port block), and the\nfoundation record names **every scenario applied and every scenario declined with the declaration\neach came from**. A package that already exists (`website/`, `technical-doc/`) is left alone and\nreported as already composed.\n\n## Read state first\n\nA composition landed before the market, the brand or the business model exists declines what\nnothing yet implies, and says so in each decision's detail. That is the honest first record, not a\nmistake: derived staleness marks the composition stale when any input family lands or changes, and\nre-running this step refines it. Nothing is re-asked because nothing was asked.\n\n## What you emit\n\n- The **capability-composition** at `specifications/src/capability-composition/index.ts` —\n one decision per scenario, total over the scenarios the framework ships.\n\n## Verification\n\n- The record is total: `validateCapabilityComposition` reports `SCENARIO_NOT_DECIDED` for any\n scenario the framework ships that the record never decided about, and\n `DISPOSITION_BASIS_MISMATCH` for a disposition whose basis contradicts it.\n- `rg -n \"disposition: CompositionDisposition.NEEDED\" specifications/src/capability-composition/index.ts`\n lists what the foundation will apply.\n\n## References — named by REF, because nothing here opens a file\n\nThis step is RUNNER-OWNED: the composition is derived by a function, and no model reads this method\nat all. The two skills are named by ref rather than by path for the same reason the tool-less\nplaybooks are (#1435) — a path is an instruction nothing can follow:\n\n- `config-saas` — the SaaS-config surface the applied scenarios append to\n (`applicationExtraServices`, the workspace members), which is what the foundation executor writes.\n",
45
+ "guidance": "# Capability Composition — Which Scenarios This Application Needs\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nThe framework ships one composition scenario per folder under `templates/saas/scenarios/`. Two of\nthem — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The\nothers give an application a marketing website, a documentation portal, a cron minion, a worker, a\nprovider, a file-picker provider, a second website locale, another deployment environment or the\noptional 3D layout, and until this step existed nothing in the journey decided whether an\napplication needed any of them: they were reachable only by a person running `wildo compose`.\n\nThis step records that decision as the `capability-composition` family: **one decision per\nscenario the framework ships**, each with a disposition, the closed basis it was derived from,\nand a one-sentence detail naming the declaring entries.\n\n## It is derived, never asked\n\nNothing here is an interview. Every decision is read off what the application's own families\nDECLARE:\n\n| scenario | NEEDED when | read from |\n|---|---|---|\n| `add-website` | the market declares an inbound web channel (organic or paid search, content, owned or paid social); else a brand brief has landed; else the business model declares pricing plans | `market-snapshot.channels`, `brand-brief`, `business-model.plans` |\n| `add-technical-doc` | a targeted ICP (CORE or EXPANSION) is a legal entity; else a non-functional requirement declares PORTABILITY | `market-snapshot.icps`, `requirements.nonFunctional` |\n| `add-locale` | a website is composed and either the market targets a country whose languages the configuration does not serve (one locale for each such country's first listed language) or the configuration serves more than one language (one locale per language beyond the primary) — the decision names its `locales` | `market-snapshot.icps` geographies (CORE and EXPANSION), and `appPreferences.languages` in the application configuration (a host fact: no family declares languages, and the configuration already does) |\n\nWhere no typed declaration can decide a scenario, the record says **DECLINED with the basis\n`NO_DECLARATION_DECIDES_IT` and names the declaration that would decide it** — a field for\nsomebody to add, never a question for somebody to answer. Today the only such case is `add-locale`\nwhen a website is composed but the host could not read the configuration's languages.\n\nEach basis justifies exactly ONE disposition (`COMPOSITION_BASIS_DISPOSITION`): a declaration that\nwas read and implies nothing is `NO_DECLARATION_IMPLIES_IT`, never a NEED basis with a DECLINED\nverdict. A market whose countries the configuration cannot address is never declined in silence:\nwith a website it makes `add-locale` NEEDED on `MARKET_TARGETS_UNSERVED_LANGUAGES`, naming each\nlanguage, and with or without one the coherence report names the gap as a contradiction, so the\nconfiguration's own `enabledLanguages` can follow.\n\nScenarios another step applies are recorded as **OWNED_BY_ANOTHER_STEP**, naming the owner, so\nthe record stays total without claiming the application lacks them:\n\n| scenario | owner |\n|---|---|\n| `add-module`, `add-resource` | `bottom_up.foundation` — the domain composition |\n| `add-minion`, `add-worker-node`, `add-worker-rust` | `bottom_up.foundation` — one per surface the integration plan declares |\n| `add-custom-operation`, `add-website-section`, `add-marketing-page`, `add-file-picker-provider` | the build tasks that produce those artifacts (`bottom_up.build-decompose`) |\n| `add-provider` | the foundation's provider decision |\n| `add-environment` | the operator, at deployment (`wildo compose add-environment`) |\n| `add-3d-layout` | the operator's opt-in (`wildo compose add-3d-layout`): nothing a product declares decides a rendering style, so the journey never adopts the optional 3D layout |\n\n## Where it lands, and who reads it\n\nThe family lands at `specifications/src/capability-composition/index.ts` and is wired onto the\n`capabilityComposition` companion-exports slot. `bottom_up.foundation` reads it there: the NEEDED\nscenarios are applied after the domain scenarios, with the application's own host facts (slug,\ndisplay name, public domain from its infrastructure environments, its port block), and the\nfoundation record names **every scenario applied and every scenario declined with the declaration\neach came from**. A package that already exists (`website/`, `technical-doc/`) is left alone and\nreported as already composed.\n\n## Read state first\n\nA composition landed before the market, the brand or the business model exists declines what\nnothing yet implies, and says so in each decision's detail. That is the honest first record, not a\nmistake: derived staleness marks the composition stale when any input family lands or changes, and\nre-running this step refines it. Nothing is re-asked because nothing was asked.\n\n## What you emit\n\n- The **capability-composition** at `specifications/src/capability-composition/index.ts` —\n one decision per scenario, total over the scenarios the framework ships.\n\n## Verification\n\n- The record is total: `validateCapabilityComposition` reports `SCENARIO_NOT_DECIDED` for any\n scenario the framework ships that the record never decided about, and\n `DISPOSITION_BASIS_MISMATCH` for a disposition whose basis contradicts it.\n- `rg -n \"disposition: CompositionDisposition.NEEDED\" specifications/src/capability-composition/index.ts`\n lists what the foundation will apply.\n\n## References — named by REF, because nothing here opens a file\n\nThis step is RUNNER-OWNED: the composition is derived by a function, and no model reads this method\nat all. The two skills are named by ref rather than by path for the same reason the tool-less\nplaybooks are (#1435) — a path is an instruction nothing can follow:\n\n- `config-saas` — the SaaS-config surface the applied scenarios append to\n (`applicationExtraServices`, the workspace members), which is what the foundation executor writes.\n",
46
46
  "skillRefs": [
47
47
  "config-saas"
48
48
  ],
@@ -48,8 +48,9 @@ already offers the three that follow it.
48
48
 
49
49
  ## Selecting the next children
50
50
 
51
- - **Missing beats present.** A plan or a placement already on record is not
52
- re-derived unless what it was derived from has been re-derived in this run.
51
+ - **Missing beats present.** A plan or a placement already on record whose inputs
52
+ have not changed since it landed is not offered at all. Every option is marked
53
+ FIRST RUN, or REFRESH with the input that moved.
53
54
  - **The runner-owned steps run once.** The foundation and the personas land nothing
54
55
  the runtime marks delivered, so they stay eligible; the round history is the record
55
56
  that they ran. Do not spend a round on either a second time.
@@ -2,7 +2,7 @@
2
2
  "ref": "bottom_up.conception",
3
3
  "version": "0.1.2",
4
4
  "phase": "bottom_up",
5
- "intent": "Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you: a family already on record is not re-derived unless the plan it was derived from has been re-derived in this run. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane's closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.",
5
+ "intent": "Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane's closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_valid",
@@ -66,7 +66,7 @@
66
66
  "outputs": [],
67
67
  "stepOutputs": [],
68
68
  "method": {
69
- "guidance": "# The Conception Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that CONCEIVE the\napplication's structure — the domain plan, the panels' staffing, the foundation, the\nplacement plan — and it ends on the placement plan, which is the lane's closing decision.\n\n## The children, and why the order is not written here\n\n- **`bottom_up.domain-plan`** — modules, resources and relationships, from the\n requirements and the market. Asks the creator one question (tenancy) and may suspend\n mid-run on a clarification.\n- **`top_down.expert-personas`** — derives and accepts the expert charters the panels\n convene. Runner-owned, lands no family, never re-derives a committed charter, reports\n a role whose inputs have not landed as waiting.\n- **`bottom_up.capability-composition`** — which composition scenarios the\n application needs (a website, a technical-doc portal, workers, minions). Its record\n is what the foundation applies.\n- **`bottom_up.foundation`** — composes the application from the domain plan: the\n configuration, the module and resource slices, the environments. Runner-owned,\n idempotent (a byte-identical target is a skip; a collision refuses), asks the creator\n three questions.\n- **`bottom_up.experience-plan`**, **`bottom_up.website-plan`**,\n **`bottom_up.documentation-plan`** — what each surface the composition declared\n CONTAINS. Conception rather than build: the decomposer reads all three, so a surface\n planned after decomposition is one the build plan has no task for. An application that\n declared no website simply has no website plan, and nothing waits for one.\n- **`bottom_up.placement-plan`** — where every module lands in the application shell,\n decided by a panel (an information architect and a design-system guardian) over three\n candidates.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. The plan needs the requirements and the\nmarket; the personas need the vision and the market; the foundation and the placement\nneed the plan. Re-run the lane on an application whose plan exists and the first round\nalready offers the three that follow it.\n\n## Selecting the next children\n\n- **Missing beats present.** A plan or a placement already on record is not\n re-derived unless what it was derived from has been re-derived in this run.\n- **The runner-owned steps run once.** The foundation and the personas land nothing\n the runtime marks delivered, so they stay eligible; the round history is the record\n that they ran. Do not spend a round on either a second time.\n- **Independent children share a round.** The personas and the foundation both need\n only the plan and can run beside each other.\n- **A child waiting on the creator is not offered** — an unanswered interview, or a\n suspended clarification. Run everything else, and stop when nothing eligible advances\n the conception.\n\n## Composing an objective for a child\n\nFor the domain plan, name the requirements the plan must route and the market ICPs it\nserves. For a re-derivation, name what placement or the build reported the plan could\nnot route — that is the whole objective. For placement, name the modules the plan\ndeclares and the audiences that reach them.\n\n## When the build sends the application back\n\nThe root re-opens this lane when the build lane's decomposer finds the conception unbuildable\n(`conception-buildable` GAP, #1638). The round history names the criterion, and the objective you\nare given carries the decomposer's reason. Revise the leaf that owns the faulted element, which is\nusually the domain plan: a module, resource or relationship no build target can express, or a\nreference another family makes to something the plan does not declare. A composition surface no\nplan realises belongs to the surface plan it names. Do not re-derive the whole conception: the\nleaves the fault does not touch are still right, and re-deriving them makes the build re-plan work\nthat was sound.\n\n## When to stop\n\nStop when the placement plan is on record AND every surface the capability composition\ndecided is planned: the placement plan is the decision this lane ends on, but it depends\nonly on the domain plan, so it can land while the composition's surfaces are still\nunplanned. A website or documentation portal the composition marks NEEDED, with no\nwebsite plan or documentation plan on record, is a surface the build decomposition will\nemit no task for — and nothing downstream says so. Offer its plan before stopping. The\ncoherence report names the gap as `composition-surface-not-planned`.\n\nStop also when nothing eligible advances the conception — the plan suspended on a\nclarification, or an interview is unanswered — and say which.\n\n## What the creator reviews\n\nThe domain plan and the placement plan, exactly as each leaf's own review guide says;\nthe composed application in the working tree, through `git status`; and the accepted\ncharters. The decision this lane ends on: the conception is accepted, or returned to\nthe domain plan with what could not be routed.\n",
69
+ "guidance": "# The Conception Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that CONCEIVE the\napplication's structure — the domain plan, the panels' staffing, the foundation, the\nplacement plan — and it ends on the placement plan, which is the lane's closing decision.\n\n## The children, and why the order is not written here\n\n- **`bottom_up.domain-plan`** — modules, resources and relationships, from the\n requirements and the market. Asks the creator one question (tenancy) and may suspend\n mid-run on a clarification.\n- **`top_down.expert-personas`** — derives and accepts the expert charters the panels\n convene. Runner-owned, lands no family, never re-derives a committed charter, reports\n a role whose inputs have not landed as waiting.\n- **`bottom_up.capability-composition`** — which composition scenarios the\n application needs (a website, a technical-doc portal, workers, minions). Its record\n is what the foundation applies.\n- **`bottom_up.foundation`** — composes the application from the domain plan: the\n configuration, the module and resource slices, the environments. Runner-owned,\n idempotent (a byte-identical target is a skip; a collision refuses), asks the creator\n three questions.\n- **`bottom_up.experience-plan`**, **`bottom_up.website-plan`**,\n **`bottom_up.documentation-plan`** — what each surface the composition declared\n CONTAINS. Conception rather than build: the decomposer reads all three, so a surface\n planned after decomposition is one the build plan has no task for. An application that\n declared no website simply has no website plan, and nothing waits for one.\n- **`bottom_up.placement-plan`** — where every module lands in the application shell,\n decided by a panel (an information architect and a design-system guardian) over three\n candidates.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. The plan needs the requirements and the\nmarket; the personas need the vision and the market; the foundation and the placement\nneed the plan. Re-run the lane on an application whose plan exists and the first round\nalready offers the three that follow it.\n\n## Selecting the next children\n\n- **Missing beats present.** A plan or a placement already on record whose inputs\n have not changed since it landed is not offered at all. Every option is marked\n FIRST RUN, or REFRESH with the input that moved.\n- **The runner-owned steps run once.** The foundation and the personas land nothing\n the runtime marks delivered, so they stay eligible; the round history is the record\n that they ran. Do not spend a round on either a second time.\n- **Independent children share a round.** The personas and the foundation both need\n only the plan and can run beside each other.\n- **A child waiting on the creator is not offered** — an unanswered interview, or a\n suspended clarification. Run everything else, and stop when nothing eligible advances\n the conception.\n\n## Composing an objective for a child\n\nFor the domain plan, name the requirements the plan must route and the market ICPs it\nserves. For a re-derivation, name what placement or the build reported the plan could\nnot route — that is the whole objective. For placement, name the modules the plan\ndeclares and the audiences that reach them.\n\n## When the build sends the application back\n\nThe root re-opens this lane when the build lane's decomposer finds the conception unbuildable\n(`conception-buildable` GAP, #1638). The round history names the criterion, and the objective you\nare given carries the decomposer's reason. Revise the leaf that owns the faulted element, which is\nusually the domain plan: a module, resource or relationship no build target can express, or a\nreference another family makes to something the plan does not declare. A composition surface no\nplan realises belongs to the surface plan it names. Do not re-derive the whole conception: the\nleaves the fault does not touch are still right, and re-deriving them makes the build re-plan work\nthat was sound.\n\n## When to stop\n\nStop when the placement plan is on record AND every surface the capability composition\ndecided is planned: the placement plan is the decision this lane ends on, but it depends\nonly on the domain plan, so it can land while the composition's surfaces are still\nunplanned. A website or documentation portal the composition marks NEEDED, with no\nwebsite plan or documentation plan on record, is a surface the build decomposition will\nemit no task for — and nothing downstream says so. Offer its plan before stopping. The\ncoherence report names the gap as `composition-surface-not-planned`.\n\nStop also when nothing eligible advances the conception — the plan suspended on a\nclarification, or an interview is unanswered — and say which.\n\n## What the creator reviews\n\nThe domain plan and the placement plan, exactly as each leaf's own review guide says;\nthe composed application in the working tree, through `git status`; and the accepted\ncharters. The decision this lane ends on: the conception is accepted, or returned to\nthe domain plan with what could not be routed.\n",
70
70
  "skillRefs": [],
71
71
  "skillBodyRefs": [],
72
72
  "contextSources": [],
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1}],"instruction":"Determine whether the output remains at planning depth: modules, resource inventories and relationship intents only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The output is usable but contains limited premature implementation detail.","GAP":"The output materially crosses into schema, foreign-key or implementation authoring.","INDETERMINATE":"The staged evidence cannot establish the output depth boundary.","PASS":"The output remains within the declared planning-depth boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-feature-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1}],"instruction":"Determine whether every feature draft and benefit-delivering feature is realizable by the proposed module capabilities and resource inventories. Do not infer a home from naming similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All features have homes, but one or more mappings are weak or insufficiently explained.","GAP":"At least one feature or benefit-delivering capability has no resolvable domain home.","INDETERMINATE":"The staged evidence cannot establish complete feature coverage.","PASS":"Every feature and benefit-delivering capability has a resolvable domain home."}},{"criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1}],"instruction":"Assess whether main resources form each module semantic center, supporting resources remain genuinely supporting, and ownership boundaries are plausible. Deterministic uniqueness has already passed and must not be reinterpreted.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The inventories are usable but one or more main/supporting classifications are questionable.","GAP":"At least one inventory materially contradicts its declared module capability.","INDETERMINATE":"The staged evidence cannot establish plausible module inventories.","PASS":"Each module inventory has a plausible semantic center and supporting boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-module-justification","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1}],"instruction":"Determine whether every proposed module is justified by accepted requirements or features and represents one coherent business capability. Flag speculative or mixed-purpose modules.","schemaVersion":1,"verdictGuidance":{"CONCERN":"One or more modules are weakly justified or combine boundaries that should be reconsidered.","GAP":"At least one module is speculative or materially incoherent with the definition set.","INDETERMINATE":"The staged evidence cannot establish why every module exists.","PASS":"Every proposed module is justified and capability-coherent."}},{"criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1}],"instruction":"Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Do not resolve them into physical foreign keys.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The relationships are structurally valid but one or more semantic intents need refinement.","GAP":"At least one necessary relationship is missing or one declared relationship is materially incoherent.","INDETERMINATE":"The staged evidence cannot establish semantic relationship integrity.","PASS":"The relationship intents coherently connect the proposed resource inventory."}},{"criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory. Treat a requirement without a resolvable module home as a material gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete but one or more requirement-to-module links are weak or indirect.","GAP":"At least one current-horizon functional requirement has no resolvable module home.","INDETERMINATE":"The staged evidence cannot establish complete requirement coverage.","PASS":"Every current-horizon functional requirement has a coherent module and resource home."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/domain-plan-output-set-result","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.domain-plan"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1}],"instruction":"Determine whether the output remains at planning depth: modules, resource inventories and relationship intents only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The output is usable but contains limited premature implementation detail.","GAP":"The output materially crosses into schema, foreign-key or implementation authoring.","INDETERMINATE":"The staged evidence cannot establish the output depth boundary.","PASS":"The output remains within the declared planning-depth boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-feature-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1}],"instruction":"Determine whether every feature draft and benefit-delivering feature is realizable by the proposed module capabilities and resource inventories. Do not infer a home from naming similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All features have homes, but one or more mappings are weak or insufficiently explained.","GAP":"At least one feature or benefit-delivering capability has no resolvable domain home.","INDETERMINATE":"The staged evidence cannot establish complete feature coverage.","PASS":"Every feature and benefit-delivering capability has a resolvable domain home."}},{"criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1}],"instruction":"Assess whether main resources form each module semantic center, supporting resources remain genuinely supporting, and ownership boundaries are plausible. Deterministic uniqueness has already passed and must not be reinterpreted.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The inventories are usable but one or more main/supporting classifications are questionable.","GAP":"At least one inventory materially contradicts its declared module capability.","INDETERMINATE":"The staged evidence cannot establish plausible module inventories.","PASS":"Each module inventory has a plausible semantic center and supporting boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-module-justification","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1}],"instruction":"Determine whether every proposed module is justified by accepted requirements or features and represents one coherent business capability. Flag speculative or mixed-purpose modules.","schemaVersion":1,"verdictGuidance":{"CONCERN":"One or more modules are weakly justified or combine boundaries that should be reconsidered.","GAP":"At least one module is speculative or materially incoherent with the definition set.","INDETERMINATE":"The staged evidence cannot establish why every module exists.","PASS":"Every proposed module is justified and capability-coherent."}},{"criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1}],"instruction":"Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Read every cardinality from the source resource to the target resource (how many sources to how many targets): an edge from the resource holding the reference to the resource it references, where many holders share one referenced row, is many-to-one and is correct. Deterministic validation has already refused a one-sided cardinality whose \"one\" end holds the reference; do not re-report that. Do not resolve the intents into physical foreign keys.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The relationships are structurally valid but one or more semantic intents need refinement.","GAP":"At least one necessary relationship is missing or one declared relationship is materially incoherent.","INDETERMINATE":"The staged evidence cannot establish semantic relationship integrity.","PASS":"The relationship intents coherently connect the proposed resource inventory."}},{"criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory. Treat a requirement without a resolvable module home as a material gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete but one or more requirement-to-module links are weak or indirect.","GAP":"At least one current-horizon functional requirement has no resolvable module home.","INDETERMINATE":"The staged evidence cannot establish complete requirement coverage.","PASS":"Every current-horizon functional requirement has a coherent module and resource home."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/domain-plan-output-set-result","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.domain-plan"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-domain-plan-output-set","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/domain-plan-boundary-discipline","application-creation:evidence-requirement/domain-plan-feature-coverage","application-creation:evidence-requirement/domain-plan-inventory-plausibility","application-creation:evidence-requirement/domain-plan-module-justification","application-creation:evidence-requirement/domain-plan-relationship-integrity","application-creation:evidence-requirement/domain-plan-requirement-coverage"],"requirementRef":"application-creation:authority-requirement/domain-plan-output-set-result","requirementVersion":1,"riskClassRef":"application-creation:risk/domain-plan-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/domain-plan-output-set-result","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/domain-plan-output-set-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/domain-plan-output-set-result","policyVersion":1},"decisionPointRef":"application-creation:decision-point/domain-plan-output-set-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/domain-plan-output-set-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/domain-plan-output-set-result","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/domain-plan-output-set-structurally-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/domain-plan-accepted-landing","triggerRefs":["application-creation:trigger/domain-plan-output-set-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/domain-plan-boundary-discipline","application-creation:evidence-requirement/domain-plan-feature-coverage","application-creation:evidence-requirement/domain-plan-inventory-plausibility","application-creation:evidence-requirement/domain-plan-module-justification","application-creation:evidence-requirement/domain-plan-relationship-integrity","application-creation:evidence-requirement/domain-plan-requirement-coverage"],"hardFloorRef":"application-creation:hard-floor/domain-plan-output-set-structurally-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/domain-plan-output-set-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/domain-plan-output-set-result","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1}],"instruction":"Determine whether the output remains at planning depth: modules, resource inventories and relationship intents only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The output is usable but contains limited premature implementation detail.","GAP":"The output materially crosses into schema, foreign-key or implementation authoring.","INDETERMINATE":"The staged evidence cannot establish the output depth boundary.","PASS":"The output remains within the declared planning-depth boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-feature-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1}],"instruction":"Determine whether every feature draft and benefit-delivering feature is realizable by the proposed module capabilities and resource inventories. Do not infer a home from naming similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All features have homes, but one or more mappings are weak or insufficiently explained.","GAP":"At least one feature or benefit-delivering capability has no resolvable domain home.","INDETERMINATE":"The staged evidence cannot establish complete feature coverage.","PASS":"Every feature and benefit-delivering capability has a resolvable domain home."}},{"criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1}],"instruction":"Assess whether main resources form each module semantic center, supporting resources remain genuinely supporting, and ownership boundaries are plausible. Deterministic uniqueness has already passed and must not be reinterpreted.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The inventories are usable but one or more main/supporting classifications are questionable.","GAP":"At least one inventory materially contradicts its declared module capability.","INDETERMINATE":"The staged evidence cannot establish plausible module inventories.","PASS":"Each module inventory has a plausible semantic center and supporting boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-module-justification","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1}],"instruction":"Determine whether every proposed module is justified by accepted requirements or features and represents one coherent business capability. Flag speculative or mixed-purpose modules.","schemaVersion":1,"verdictGuidance":{"CONCERN":"One or more modules are weakly justified or combine boundaries that should be reconsidered.","GAP":"At least one module is speculative or materially incoherent with the definition set.","INDETERMINATE":"The staged evidence cannot establish why every module exists.","PASS":"Every proposed module is justified and capability-coherent."}},{"criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1}],"instruction":"Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Do not resolve them into physical foreign keys.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The relationships are structurally valid but one or more semantic intents need refinement.","GAP":"At least one necessary relationship is missing or one declared relationship is materially incoherent.","INDETERMINATE":"The staged evidence cannot establish semantic relationship integrity.","PASS":"The relationship intents coherently connect the proposed resource inventory."}},{"criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory. Treat a requirement without a resolvable module home as a material gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete but one or more requirement-to-module links are weak or indirect.","GAP":"At least one current-horizon functional requirement has no resolvable module home.","INDETERMINATE":"The staged evidence cannot establish complete requirement coverage.","PASS":"Every current-horizon functional requirement has a coherent module and resource home."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/domain-plan-output-set-result","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.domain-plan"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/domain-plan-output-set-result","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-feature-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-module-justification","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-domain-plan-output-set","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/domain-plan-boundary-discipline","application-creation:evidence-requirement/domain-plan-feature-coverage","application-creation:evidence-requirement/domain-plan-inventory-plausibility","application-creation:evidence-requirement/domain-plan-module-justification","application-creation:evidence-requirement/domain-plan-relationship-integrity","application-creation:evidence-requirement/domain-plan-requirement-coverage"],"requirementRef":"application-creation:authority-requirement/domain-plan-output-set-result","requirementVersion":1,"riskClassRef":"application-creation:risk/domain-plan-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/domain-plan-output-set-result","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/domain-plan-output-set-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/domain-plan-output-set-result","policyVersion":1},"decisionPointRef":"application-creation:decision-point/domain-plan-output-set-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/domain-plan-output-set-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/domain-plan-output-set-result","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/domain-plan-output-set-structurally-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/domain-plan-accepted-landing","triggerRefs":["application-creation:trigger/domain-plan-output-set-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/domain-plan-boundary-discipline","application-creation:evidence-requirement/domain-plan-feature-coverage","application-creation:evidence-requirement/domain-plan-inventory-plausibility","application-creation:evidence-requirement/domain-plan-module-justification","application-creation:evidence-requirement/domain-plan-relationship-integrity","application-creation:evidence-requirement/domain-plan-requirement-coverage"],"hardFloorRef":"application-creation:hard-floor/domain-plan-output-set-structurally-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/domain-plan-output-set-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/domain-plan-output-set-result","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-domain-plan-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1}],"instruction":"Determine whether the output remains at planning depth: modules, resource inventories and relationship intents only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The output is usable but contains limited premature implementation detail.","GAP":"The output materially crosses into schema, foreign-key or implementation authoring.","INDETERMINATE":"The staged evidence cannot establish the output depth boundary.","PASS":"The output remains within the declared planning-depth boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-feature-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1}],"instruction":"Determine whether every feature draft and benefit-delivering feature is realizable by the proposed module capabilities and resource inventories. Do not infer a home from naming similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All features have homes, but one or more mappings are weak or insufficiently explained.","GAP":"At least one feature or benefit-delivering capability has no resolvable domain home.","INDETERMINATE":"The staged evidence cannot establish complete feature coverage.","PASS":"Every feature and benefit-delivering capability has a resolvable domain home."}},{"criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1}],"instruction":"Assess whether main resources form each module semantic center, supporting resources remain genuinely supporting, and ownership boundaries are plausible. Deterministic uniqueness has already passed and must not be reinterpreted.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The inventories are usable but one or more main/supporting classifications are questionable.","GAP":"At least one inventory materially contradicts its declared module capability.","INDETERMINATE":"The staged evidence cannot establish plausible module inventories.","PASS":"Each module inventory has a plausible semantic center and supporting boundary."}},{"criterionRef":"application-creation:criterion/domain-plan-module-justification","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1}],"instruction":"Determine whether every proposed module is justified by accepted requirements or features and represents one coherent business capability. Flag speculative or mixed-purpose modules.","schemaVersion":1,"verdictGuidance":{"CONCERN":"One or more modules are weakly justified or combine boundaries that should be reconsidered.","GAP":"At least one module is speculative or materially incoherent with the definition set.","INDETERMINATE":"The staged evidence cannot establish why every module exists.","PASS":"Every proposed module is justified and capability-coherent."}},{"criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1}],"instruction":"Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Read every cardinality from the source resource to the target resource (how many sources to how many targets): an edge from the resource holding the reference to the resource it references, where many holders share one referenced row, is many-to-one and is correct. Deterministic validation has already refused a one-sided cardinality whose \"one\" end holds the reference; do not re-report that. Do not resolve the intents into physical foreign keys.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The relationships are structurally valid but one or more semantic intents need refinement.","GAP":"At least one necessary relationship is missing or one declared relationship is materially incoherent.","INDETERMINATE":"The staged evidence cannot establish semantic relationship integrity.","PASS":"The relationship intents coherently connect the proposed resource inventory."}},{"criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory. Treat a requirement without a resolvable module home as a material gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete but one or more requirement-to-module links are weak or indirect.","GAP":"At least one current-horizon functional requirement has no resolvable module home.","INDETERMINATE":"The staged evidence cannot establish complete requirement coverage.","PASS":"Every current-horizon functional requirement has a coherent module and resource home."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/domain-plan-output-set-result","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.domain-plan"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/domain-plan-output-set-result","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-boundary-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-boundary-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-feature-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-feature-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-inventory-plausibility","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-inventory-plausibility","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-module-justification","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-module-justification","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-relationship-integrity","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-relationship-integrity","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/complete-domain-plan-definition-context-and-exact-output-set","criterionRef":"application-creation:criterion/domain-plan-requirement-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-accepted-heads-and-domain-plan-action-result","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/domain-plan-requirement-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:evidence-subject/domain-plan-definition-context-and-staged-output-set"}],"schemaVersion":1}
@@ -51,8 +51,9 @@ what resources live in each, and how do those resources relate?"* You produce
51
51
  **inside** each module draft because an inventory is inherently *per module*.
52
52
  2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship
53
53
  intents**: for each durable association between two inventoried resources, the
54
- two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-many),
55
- and the **ownership direction** (which resource holds the reference). These are
54
+ two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-one /
55
+ many-to-many, read from source to target), and the **ownership direction**
56
+ (which resource holds the reference). These are
56
57
  typed conceptual drafts — a relationship is not a module, so it earns its own
57
58
  family, and the build loop consumes it when it wires FK fields.
58
59
 
@@ -149,14 +150,29 @@ the relationship drafts (inside the domain-plan value) stating:
149
150
  - **The two ends** — the two resources that relate (both must be inventoried in
150
151
  some module's inventory from Step 2; a relationship to an un-inventoried resource
151
152
  is a coverage GAP).
152
- - **The cardinality intent** — one-to-one, one-to-many, or many-to-many. This is an
153
- *intent*, in prose; you are not resolving it into a foreign-key placement here.
153
+ - **The cardinality intent** — one-to-one, one-to-many, many-to-one, or
154
+ many-to-many, **always read from the source to the target**: *how many sources*
155
+ to *how many targets*. "Each `task` belongs to one `project`, a project has many
156
+ tasks", authored with `task` as the source and `project` as the target, is
157
+ **many-to-one**. The same association authored with `project` as the source is
158
+ **one-to-many**. This is an *intent*; you are not resolving it into a foreign-key
159
+ placement here.
154
160
  - **The ownership direction** — which resource conceptually **holds** the reference
155
161
  (e.g. "a `task` belongs to a `project`" → the `task` end holds the reference).
156
162
  This is the *intent* the build loop needs; it does **not** decide the physical FK
157
163
  holder (that resolution — FK holder from cardinality, discriminator relationships,
158
164
  conditional relationships — is the `module-relationships` skill's job at build
159
165
  time, **not** here).
166
+ - **The two must agree.** In a one-to-many or many-to-one association the **many**
167
+ side holds the reference, so many-to-one goes with *source holds the reference*
168
+ and one-to-many with *target holds the reference*. Deterministic validation
169
+ refuses the other two combinations. Only one-to-one and many-to-many leave the
170
+ holder to you. The simplest habit: make the resource that carries the reference
171
+ the **source**, and the edge is many-to-one.
172
+ - **Make the rationale say the same thing as the labels.** The relationship
173
+ judge reads the rationale against the cardinality, so "each customer has one
174
+ country context, many customers share one" belongs on a many-to-one edge from
175
+ customer to country context.
160
176
 
161
177
  The `module-relationships` skill carries the technical HOW of realising a
162
178
  relationship (FK fields, cardinality-to-FK-holder resolution, conditional /
@@ -232,8 +248,8 @@ Two artifacts for this journey:
232
248
  module carrying its purpose, business capability, primary actors, and its
233
249
  `mainResources` / `supportingResources` inventory.
234
250
  - The **relationship drafts** inside the landed `specifications/src/domain-plan/` value
235
- — the inter-resource relationship intents (two ends + cardinality intent +
236
- ownership direction) between inventoried resources.
251
+ — the inter-resource relationship intents (two ends + cardinality intent read
252
+ source → target + ownership direction) between inventoried resources.
237
253
 
238
254
  After deterministic validation and semantic PASS, the runtime creates a distinct
239
255
  result-bound Authority Request for the exact staged output-set digest. The local
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "bottom_up.domain-plan",
3
- "version": "0.2.1",
3
+ "version": "0.3.0",
4
4
  "phase": "bottom_up",
5
5
  "intent": "Turn the approved definition set into one atomic, planning-depth domain output set: module decomposition with per-module resource inventory plus typed inter-resource relationship intents. The output remains staged until deterministic validation, semantic evaluation and distinct result authority complete.",
6
6
  "preconditions": [
@@ -47,7 +47,7 @@
47
47
  ],
48
48
  "stepOutputs": [],
49
49
  "method": {
50
- "guidance": "# Domain Plan — Definition Set → Modules + Resources + Relationships (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The decomposition heuristic, the resource-inventory convention, and\n> the relationship-intent shape below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of domain modelling (a full ERD, a\n> cardinality-to-FK solver and full domain-graph validation) is intentionally\n> shallow here and is deepened in a later phase; do\n> not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first bottom-up playbook** — the pivot from **product definition**\n(top-down: vision, market, requirements, roadmap, business model) to **project\ndefinition** (bottom-up: the app's modules, resources, and how they relate). It\nruns **only after** the exact\n`top_down-to-bottom_up.bootstrap-non-regulated@0.1.0` route has produced a\ndurable `top_down → bottom_up` transition-commit fact. That fact proves the\nroute-bound readiness, semantic decision, Authority Request/Decision and phase\neffect chain; it is not an arbitrary approval flag. The separate\n`phase_is bottom_up` predicate checks the current phase projection. You are not\nre-opening product questions here — you are turning the currently accepted\nproduct definition into the *shape of the software that delivers it*.\n\n## What this playbook does\n\nYou are the **domain architect**. This playbook reads the approved definition set\nand drafts the **domain plan**: the answer to *\"what modules does this app have,\nwhat resources live in each, and how do those resources relate?\"* You produce\n**two artifacts**:\n\n1. The **domain-plan** family — the **module decomposition** with a **per-module\n resource inventory**, authored as a collection of **ModuleBusinessSemantics\n drafts** (one per proposed module). Each module draft states its purpose, its\n business capability, its primary actors, and its resource inventory\n (`mainResources` — the semantic center of the module; `supportingResources` —\n resources that support without being the center). The resource inventory lives\n **inside** each module draft because an inventory is inherently *per module*.\n2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship\n intents**: for each durable association between two inventoried resources, the\n two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-many),\n and the **ownership direction** (which resource holds the reference). These are\n typed conceptual drafts — a relationship is not a module, so it earns its own\n family, and the build loop consumes it when it wires FK fields.\n\nThis is a **planning pass**. You name modules, the resources inside them, and how\nthey relate. You do **not** author schemas, resolve a cardinality intent into a\nconcrete foreign-key field, or generate any code — that is the **bottom-up build\nloop's** job, downstream of this plan.\n\n## Read state first — the definition set you read, the two artifacts you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting\nanything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the top-down set is present\n and approved, and check whether a `domain-plan` already\n exist from an earlier run (refine them, do not re-author — see below).\n2. Read the approved definition set. **Load-bearing** (these drive the\n decomposition): the **requirements** (`requirements` family — the functional and\n non-functional requirements the domain must satisfy), the capability-mapped\n **MarketSnapshot** (`market-snapshot` — the benefits wired to their delivering\n features, so you know what capability each feature carries), and the\n **feature-drafts** (the prose capability contracts — what each delivering\n feature actually is). **Contextual** (they shape emphasis, not the core\n decomposition): the **roadmap** (`roadmap` — the release phasing, so you can see\n which modules are MVP-critical vs later) and the **VisionSnapshot**\n (`vision-brief` — the product framing and differentiation).\n\n\nYou **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +\n`vision-brief`; you **write** the `domain-plan` families.\n\n## Step 1 — Derive the modules (the decomposition)\n\nA **module** is a bounded slice of the app that delivers a coherent business\ncapability. Derive modules by **clustering** the definition set, not by guessing:\n\n1. **Cluster requirements and features by capability.** Group the functional\n requirements and the feature-drafts that serve one coherent capability (e.g.\n \"everything about authoring and tracking tasks\", \"everything about billing and\n plans\"). Each tight cluster is a candidate module. A feature-draft and the\n requirements it realises usually land in the same module.\n2. **Name each module and state its semantics.** For each candidate module author a\n `ModuleBusinessSemantics` draft: a `relatedModuleId` (the id the module registry\n will use — it must be **distinct across all module drafts**; two modules sharing\n an id silently collide, since the registry addresses modules by id), a `purpose`\n (why the module exists, in plain language), a\n `businessCapability` (the capability it delivers), the `primaryActors` (the\n human/business actors that interact with it), and — optionally — a\n `businessDomain` (the larger bounded-context label) and `integrationSurfaces`\n (named surfaces the module participates in).\n3. **Keep modules justified.** Every module must earn its existence from\n requirements or features in the definition set. Do **not** invent a module the\n definition set does not call for — a speculative module is a coherence CONCERN\n (see the quality gate). Conversely, if a requirement or feature has no home\n module, you are missing a module (a coverage GAP).\n\nThe `resource-add-module` skill carries the module-scaffolding vocabulary (what a\nmodule is across the project layout); read it to keep module boundaries idiomatic.\n\n## Step 2 — Inventory the resources per module\n\nFor each module, list the **resources** (persisted entity types) it owns. The\ninventory is **two lists on the module draft**:\n\n- **`mainResources`** — the resources that form the semantic **center** of the\n module (the entities the module is *about*: a `tasks` module's `task`).\n- **`supportingResources`** — resources that **support** the module's capability\n without being its center (lookup tables, join/junction entities, per-entity\n settings). A resource that is the center of the module belongs in `mainResources`,\n not here.\n\nRules for a plausible inventory:\n\n- **Derive resources from the requirements + feature-drafts**, not from a blank\n page: a requirement that says \"users can label tasks\" implies a `task` resource\n and (probably) a `label` resource. The `resource-add-resource` skill carries the\n vocabulary for what a resource is; read it to keep the inventory idiomatic.\n- **Each resource is inventoried in exactly one module** as its `mainResource`. A\n resource that is genuinely shared across modules is a signal you either have the\n module boundary wrong or you need a relationship (Step 3), not the same main\n resource duplicated in two modules.\n- **Do not author fields or schemas here.** The inventory names the resource and\n says which module owns it. What fields the resource carries, its enums, its\n decorators — all of that is the **build loop's** job. If you catch yourself\n writing a field list, stop: that is out of this playbook's depth.\n\n## Step 3 — Draft the inter-resource relationships\n\nOnce the resources are inventoried, capture how they **relate**. For each durable\nassociation between two inventoried resources, author a **relationship draft** in\nthe relationship drafts (inside the domain-plan value) stating:\n\n- **The two ends** — the two resources that relate (both must be inventoried in\n some module's inventory from Step 2; a relationship to an un-inventoried resource\n is a coverage GAP).\n- **The cardinality intent** — one-to-one, one-to-many, or many-to-many. This is an\n *intent*, in prose; you are not resolving it into a foreign-key placement here.\n- **The ownership direction** — which resource conceptually **holds** the reference\n (e.g. \"a `task` belongs to a `project`\" → the `task` end holds the reference).\n This is the *intent* the build loop needs; it does **not** decide the physical FK\n holder (that resolution — FK holder from cardinality, discriminator relationships,\n conditional relationships — is the `module-relationships` skill's job at build\n time, **not** here).\n\nThe `module-relationships` skill carries the technical HOW of realising a\nrelationship (FK fields, cardinality-to-FK-holder resolution, conditional /\ndiscriminator relationships). Read it to keep your relationship *intents* aligned\nwith what the build loop can actually wire — but do **not** perform that wiring in\nthis planning pass.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not rename or re-decompose modules\n that are already correct. Only add a module, move a resource to a different\n module, or add/correct a relationship where the plan genuinely changed.\n- **Reuse existing module ids.** A module that already exists keeps its\n `relatedModuleId` — never mint a second id for the same module. Likewise, keep a\n resource's name stable across runs.\n- **Never orphan a relationship.** A relationship draft must name two resources\n that are actually inventoried in Step 2. If you move or rename a resource, follow\n it into every relationship draft that references it.\n\n## Executable semantic evaluation — `domain-plan-output-set-result`\n\nThe staged output set first passes deterministic structural validation: exact\nmodule/resource identities, typed relationship ends, unique ownership, and the\natomic manifest must all be valid. That is a non-bypassable eligibility floor,\nnot a semantic quality opinion.\n\nThe companion then executes the playbook's structured semantic Treatment over\nthe exact staged output-set artifact. Its six criteria remain distinct:\nrequirement coverage, feature coverage, module justification, inventory\nplausibility, relationship integrity, and planning-depth boundary discipline.\nEach criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the\nworst-verdict aggregation policy determines the Decision Rule consequence.\n\nA semantic PASS does **not** accept or publish the candidate. It transitions the\nresult Decision Point to `AUTHORITY_REQUIRED`; an explicit operator authority\ndecision is a separate later boundary. CONCERN or GAP requests revision,\nINDETERMINATE requests evidence, and evaluator or hard-floor failure blocks\nclosed. The evaluation path never mutates accepted specification heads.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **Schema / field authoring.** The inventory names resources and their owning\n module; it does **not** author fields, enums, decorators, or Zod schemas. That is\n the build loop. If you catch yourself writing a field list, stop.\n- **Cardinality-to-FK resolution.** A relationship draft states a cardinality\n *intent* and an ownership *intent* in prose. Resolving that into a physical\n foreign-key holder, a discriminator relationship, or a conditional relationship is\n the `module-relationships` skill's job **at build time**, not here.\n- **A full ERD / domain-graph solver.** Phases-of-a-graph, transitive dependency\n ordering, normalization analysis, and diagram generation are a later-phase\n concern. You draft modules, an inventory, and relationship intents — not a solved\n entity-relationship diagram.\n- **A full domain-graph solver.** The framework now ships a typed conceptual\n relationship-draft contract and deterministic structural validation for the\n atomic output set. It deliberately does not solve physical FK placement,\n normalization, graph execution order, discriminator relationships, or\n conditional relationships; those remain build-depth concerns.\n- **Code generation / module registration.** Scaffolding the module folders,\n registering the module across runtimes, generating resource files — all of that is\n the bottom-up build loop, downstream of this plan.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n- The **domain-plan** under `specifications/src/domain-plan/` — a\n collection of `ModuleBusinessSemantics` drafts: the module decomposition, each\n module carrying its purpose, business capability, primary actors, and its\n `mainResources` / `supportingResources` inventory.\n- The **relationship drafts** inside the landed `specifications/src/domain-plan/` value\n — the inter-resource relationship intents (two ends + cardinality intent +\n ownership direction) between inventoried resources.\n\nAfter deterministic validation and semantic PASS, the runtime creates a distinct\nresult-bound Authority Request for the exact staged output-set digest. The local\noperator's explicit interface response settles that request; transition authority\ncannot substitute for it. Only then may the atomic specification-family mutation\naccept both files together for consumption by the bottom-up build loop.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `resource-add-module` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `resource-add-resource` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `module-relationships` — the technical HOW of realising a\n relationship (FK fields, cardinality-to-FK-holder resolution, conditional /\n discriminator relationships) — consulted so relationship *intents* align with what\n the build loop can wire, NOT performed in this planning pass.\n",
50
+ "guidance": "# Domain Plan — Definition Set → Modules + Resources + Relationships (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The decomposition heuristic, the resource-inventory convention, and\n> the relationship-intent shape below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of domain modelling (a full ERD, a\n> cardinality-to-FK solver and full domain-graph validation) is intentionally\n> shallow here and is deepened in a later phase; do\n> not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first bottom-up playbook** — the pivot from **product definition**\n(top-down: vision, market, requirements, roadmap, business model) to **project\ndefinition** (bottom-up: the app's modules, resources, and how they relate). It\nruns **only after** the exact\n`top_down-to-bottom_up.bootstrap-non-regulated@0.1.0` route has produced a\ndurable `top_down → bottom_up` transition-commit fact. That fact proves the\nroute-bound readiness, semantic decision, Authority Request/Decision and phase\neffect chain; it is not an arbitrary approval flag. The separate\n`phase_is bottom_up` predicate checks the current phase projection. You are not\nre-opening product questions here — you are turning the currently accepted\nproduct definition into the *shape of the software that delivers it*.\n\n## What this playbook does\n\nYou are the **domain architect**. This playbook reads the approved definition set\nand drafts the **domain plan**: the answer to *\"what modules does this app have,\nwhat resources live in each, and how do those resources relate?\"* You produce\n**two artifacts**:\n\n1. The **domain-plan** family — the **module decomposition** with a **per-module\n resource inventory**, authored as a collection of **ModuleBusinessSemantics\n drafts** (one per proposed module). Each module draft states its purpose, its\n business capability, its primary actors, and its resource inventory\n (`mainResources` — the semantic center of the module; `supportingResources` —\n resources that support without being the center). The resource inventory lives\n **inside** each module draft because an inventory is inherently *per module*.\n2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship\n intents**: for each durable association between two inventoried resources, the\n two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-one /\n many-to-many, read from source to target), and the **ownership direction**\n (which resource holds the reference). These are\n typed conceptual drafts — a relationship is not a module, so it earns its own\n family, and the build loop consumes it when it wires FK fields.\n\nThis is a **planning pass**. You name modules, the resources inside them, and how\nthey relate. You do **not** author schemas, resolve a cardinality intent into a\nconcrete foreign-key field, or generate any code — that is the **bottom-up build\nloop's** job, downstream of this plan.\n\n## Read state first — the definition set you read, the two artifacts you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting\nanything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the top-down set is present\n and approved, and check whether a `domain-plan` already\n exist from an earlier run (refine them, do not re-author — see below).\n2. Read the approved definition set. **Load-bearing** (these drive the\n decomposition): the **requirements** (`requirements` family — the functional and\n non-functional requirements the domain must satisfy), the capability-mapped\n **MarketSnapshot** (`market-snapshot` — the benefits wired to their delivering\n features, so you know what capability each feature carries), and the\n **feature-drafts** (the prose capability contracts — what each delivering\n feature actually is). **Contextual** (they shape emphasis, not the core\n decomposition): the **roadmap** (`roadmap` — the release phasing, so you can see\n which modules are MVP-critical vs later) and the **VisionSnapshot**\n (`vision-brief` — the product framing and differentiation).\n\n\nYou **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +\n`vision-brief`; you **write** the `domain-plan` families.\n\n## Step 1 — Derive the modules (the decomposition)\n\nA **module** is a bounded slice of the app that delivers a coherent business\ncapability. Derive modules by **clustering** the definition set, not by guessing:\n\n1. **Cluster requirements and features by capability.** Group the functional\n requirements and the feature-drafts that serve one coherent capability (e.g.\n \"everything about authoring and tracking tasks\", \"everything about billing and\n plans\"). Each tight cluster is a candidate module. A feature-draft and the\n requirements it realises usually land in the same module.\n2. **Name each module and state its semantics.** For each candidate module author a\n `ModuleBusinessSemantics` draft: a `relatedModuleId` (the id the module registry\n will use — it must be **distinct across all module drafts**; two modules sharing\n an id silently collide, since the registry addresses modules by id), a `purpose`\n (why the module exists, in plain language), a\n `businessCapability` (the capability it delivers), the `primaryActors` (the\n human/business actors that interact with it), and — optionally — a\n `businessDomain` (the larger bounded-context label) and `integrationSurfaces`\n (named surfaces the module participates in).\n3. **Keep modules justified.** Every module must earn its existence from\n requirements or features in the definition set. Do **not** invent a module the\n definition set does not call for — a speculative module is a coherence CONCERN\n (see the quality gate). Conversely, if a requirement or feature has no home\n module, you are missing a module (a coverage GAP).\n\nThe `resource-add-module` skill carries the module-scaffolding vocabulary (what a\nmodule is across the project layout); read it to keep module boundaries idiomatic.\n\n## Step 2 — Inventory the resources per module\n\nFor each module, list the **resources** (persisted entity types) it owns. The\ninventory is **two lists on the module draft**:\n\n- **`mainResources`** — the resources that form the semantic **center** of the\n module (the entities the module is *about*: a `tasks` module's `task`).\n- **`supportingResources`** — resources that **support** the module's capability\n without being its center (lookup tables, join/junction entities, per-entity\n settings). A resource that is the center of the module belongs in `mainResources`,\n not here.\n\nRules for a plausible inventory:\n\n- **Derive resources from the requirements + feature-drafts**, not from a blank\n page: a requirement that says \"users can label tasks\" implies a `task` resource\n and (probably) a `label` resource. The `resource-add-resource` skill carries the\n vocabulary for what a resource is; read it to keep the inventory idiomatic.\n- **Each resource is inventoried in exactly one module** as its `mainResource`. A\n resource that is genuinely shared across modules is a signal you either have the\n module boundary wrong or you need a relationship (Step 3), not the same main\n resource duplicated in two modules.\n- **Do not author fields or schemas here.** The inventory names the resource and\n says which module owns it. What fields the resource carries, its enums, its\n decorators — all of that is the **build loop's** job. If you catch yourself\n writing a field list, stop: that is out of this playbook's depth.\n\n## Step 3 — Draft the inter-resource relationships\n\nOnce the resources are inventoried, capture how they **relate**. For each durable\nassociation between two inventoried resources, author a **relationship draft** in\nthe relationship drafts (inside the domain-plan value) stating:\n\n- **The two ends** — the two resources that relate (both must be inventoried in\n some module's inventory from Step 2; a relationship to an un-inventoried resource\n is a coverage GAP).\n- **The cardinality intent** — one-to-one, one-to-many, many-to-one, or\n many-to-many, **always read from the source to the target**: *how many sources*\n to *how many targets*. \"Each `task` belongs to one `project`, a project has many\n tasks\", authored with `task` as the source and `project` as the target, is\n **many-to-one**. The same association authored with `project` as the source is\n **one-to-many**. This is an *intent*; you are not resolving it into a foreign-key\n placement here.\n- **The ownership direction** — which resource conceptually **holds** the reference\n (e.g. \"a `task` belongs to a `project`\" → the `task` end holds the reference).\n This is the *intent* the build loop needs; it does **not** decide the physical FK\n holder (that resolution — FK holder from cardinality, discriminator relationships,\n conditional relationships — is the `module-relationships` skill's job at build\n time, **not** here).\n- **The two must agree.** In a one-to-many or many-to-one association the **many**\n side holds the reference, so many-to-one goes with *source holds the reference*\n and one-to-many with *target holds the reference*. Deterministic validation\n refuses the other two combinations. Only one-to-one and many-to-many leave the\n holder to you. The simplest habit: make the resource that carries the reference\n the **source**, and the edge is many-to-one.\n- **Make the rationale say the same thing as the labels.** The relationship\n judge reads the rationale against the cardinality, so \"each customer has one\n country context, many customers share one\" belongs on a many-to-one edge from\n customer to country context.\n\nThe `module-relationships` skill carries the technical HOW of realising a\nrelationship (FK fields, cardinality-to-FK-holder resolution, conditional /\ndiscriminator relationships). Read it to keep your relationship *intents* aligned\nwith what the build loop can actually wire — but do **not** perform that wiring in\nthis planning pass.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not rename or re-decompose modules\n that are already correct. Only add a module, move a resource to a different\n module, or add/correct a relationship where the plan genuinely changed.\n- **Reuse existing module ids.** A module that already exists keeps its\n `relatedModuleId` — never mint a second id for the same module. Likewise, keep a\n resource's name stable across runs.\n- **Never orphan a relationship.** A relationship draft must name two resources\n that are actually inventoried in Step 2. If you move or rename a resource, follow\n it into every relationship draft that references it.\n\n## Executable semantic evaluation — `domain-plan-output-set-result`\n\nThe staged output set first passes deterministic structural validation: exact\nmodule/resource identities, typed relationship ends, unique ownership, and the\natomic manifest must all be valid. That is a non-bypassable eligibility floor,\nnot a semantic quality opinion.\n\nThe companion then executes the playbook's structured semantic Treatment over\nthe exact staged output-set artifact. Its six criteria remain distinct:\nrequirement coverage, feature coverage, module justification, inventory\nplausibility, relationship integrity, and planning-depth boundary discipline.\nEach criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the\nworst-verdict aggregation policy determines the Decision Rule consequence.\n\nA semantic PASS does **not** accept or publish the candidate. It transitions the\nresult Decision Point to `AUTHORITY_REQUIRED`; an explicit operator authority\ndecision is a separate later boundary. CONCERN or GAP requests revision,\nINDETERMINATE requests evidence, and evaluator or hard-floor failure blocks\nclosed. The evaluation path never mutates accepted specification heads.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **Schema / field authoring.** The inventory names resources and their owning\n module; it does **not** author fields, enums, decorators, or Zod schemas. That is\n the build loop. If you catch yourself writing a field list, stop.\n- **Cardinality-to-FK resolution.** A relationship draft states a cardinality\n *intent* and an ownership *intent* in prose. Resolving that into a physical\n foreign-key holder, a discriminator relationship, or a conditional relationship is\n the `module-relationships` skill's job **at build time**, not here.\n- **A full ERD / domain-graph solver.** Phases-of-a-graph, transitive dependency\n ordering, normalization analysis, and diagram generation are a later-phase\n concern. You draft modules, an inventory, and relationship intents — not a solved\n entity-relationship diagram.\n- **A full domain-graph solver.** The framework now ships a typed conceptual\n relationship-draft contract and deterministic structural validation for the\n atomic output set. It deliberately does not solve physical FK placement,\n normalization, graph execution order, discriminator relationships, or\n conditional relationships; those remain build-depth concerns.\n- **Code generation / module registration.** Scaffolding the module folders,\n registering the module across runtimes, generating resource files — all of that is\n the bottom-up build loop, downstream of this plan.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n- The **domain-plan** under `specifications/src/domain-plan/` — a\n collection of `ModuleBusinessSemantics` drafts: the module decomposition, each\n module carrying its purpose, business capability, primary actors, and its\n `mainResources` / `supportingResources` inventory.\n- The **relationship drafts** inside the landed `specifications/src/domain-plan/` value\n — the inter-resource relationship intents (two ends + cardinality intent read\n source → target + ownership direction) between inventoried resources.\n\nAfter deterministic validation and semantic PASS, the runtime creates a distinct\nresult-bound Authority Request for the exact staged output-set digest. The local\noperator's explicit interface response settles that request; transition authority\ncannot substitute for it. Only then may the atomic specification-family mutation\naccept both files together for consumption by the bottom-up build loop.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `resource-add-module` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `resource-add-resource` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `module-relationships` — the technical HOW of realising a\n relationship (FK fields, cardinality-to-FK-holder resolution, conditional /\n discriminator relationships) — consulted so relationship *intents* align with what\n the build loop can wire, NOT performed in this planning pass.\n",
51
51
  "skillRefs": [
52
52
  "resource-add-module",
53
53
  "resource-add-resource",
@@ -63,7 +63,8 @@
63
63
  "options": [
64
64
  "organizations",
65
65
  "users"
66
- ]
66
+ ],
67
+ "depth": "essential"
67
68
  }
68
69
  ]
69
70
  },
@@ -68,17 +68,23 @@
68
68
  "sameDecisionAs": {
69
69
  "playbookRef": "bottom_up.domain-plan",
70
70
  "questionRef": "tenancy"
71
- }
71
+ },
72
+ "depth": "essential"
72
73
  },
73
74
  {
74
75
  "ref": "operating-entity",
75
76
  "question": "Which legal entity operates this service? Give the registered company name, its registered address, and the route a person uses to reach you about privacy (an email, a URL or a postal address). Answer only the parts you actually know today — anything you leave out is recorded as outstanding and nothing is blocked by it. Do NOT supply a placeholder or a plausible-looking value: a produced privacy notice quotes these as fact, and the address is what a person would use to serve a legal request on a real company.",
76
- "kind": "free_text"
77
+ "kind": "free_text",
78
+ "depth": "essential",
79
+ "whenUnknown": "ask",
80
+ "regulatedDomain": true
77
81
  },
78
82
  {
79
83
  "ref": "operating-jurisdictions",
80
84
  "question": "Which jurisdictions does this application operate in, and why does each one reach it — are you established there, do you sell there, or do you hold data about people there? Use country codes (`fr`, `us`), the supranational `eu`, or a subdivision (`us-ca`). Answer \"not decided\" if the market is genuinely unsettled; an absent answer is read as unanswered, never as \"nowhere\".",
81
- "kind": "free_text"
85
+ "kind": "free_text",
86
+ "depth": "essential",
87
+ "regulatedDomain": true
82
88
  },
83
89
  {
84
90
  "ref": "billing-provider",
@@ -87,7 +93,8 @@
87
93
  "options": [
88
94
  "stripe",
89
95
  "none"
90
- ]
96
+ ],
97
+ "depth": "detail"
91
98
  },
92
99
  {
93
100
  "ref": "sms-provider",
@@ -96,7 +103,8 @@
96
103
  "options": [
97
104
  "twilio",
98
105
  "none"
99
- ]
106
+ ],
107
+ "depth": "detail"
100
108
  }
101
109
  ]
102
110
  },