@wildo-ai/framework-knowledge 1.1.1 → 1.1.2

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 (240) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +43 -2
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  6. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.loader.js +32 -0
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/framework-knowledge.schemas.d.ts +12 -0
  10. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  11. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +46 -0
  13. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +4 -4
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +3 -3
  18. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  19. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -3
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
  22. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -3
  24. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
  26. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -7
  28. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +0 -1
  30. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -3
  32. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +22 -1
  34. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +0 -3
  36. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
  38. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  39. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +4 -1
  40. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  41. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +4 -1
  42. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  43. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  44. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -13
  45. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +3 -4
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +3 -3
  49. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +2 -7
  51. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
  53. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +2 -7
  55. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
  57. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +54 -0
  59. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
  60. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
  61. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
  62. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +76 -0
  63. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
  64. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +92 -0
  65. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
  66. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +30 -0
  67. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
  68. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +29 -0
  69. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
  70. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -44
  71. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +4 -53
  73. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +31 -0
  75. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
  76. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +26 -0
  77. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
  78. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -7
  79. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +0 -1
  81. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  82. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -8
  83. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  85. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +2 -7
  87. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  88. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
  89. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  90. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -7
  91. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
  93. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +2 -7
  95. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +5 -3
  97. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -3
  99. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  101. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +4 -5
  103. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +25 -4
  105. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  106. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  107. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  108. package/dist/knowledge/manifest.json +8 -8
  109. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +51 -0
  110. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  111. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +27 -10
  112. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +8 -7
  113. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +6 -4
  114. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +4 -6
  115. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +5 -4
  116. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +4 -6
  117. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +0 -4
  118. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -6
  119. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +49 -22
  120. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +14 -6
  121. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +2 -4
  122. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +46 -1
  123. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +7 -3
  124. package/dist/knowledge/playbooks/refinement.document-facts/method.md +18 -4
  125. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -2
  126. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +2 -3
  127. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +8 -7
  128. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +3 -5
  129. package/dist/knowledge/playbooks/top_down.capability-map/method.md +0 -2
  130. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +4 -6
  131. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  132. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +100 -0
  133. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +117 -0
  134. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +86 -0
  135. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  136. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +41 -0
  137. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +21 -4
  138. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +14 -57
  139. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +76 -0
  140. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +42 -0
  141. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +3 -5
  142. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +3 -1
  143. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +3 -1
  144. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -5
  145. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +8 -4
  146. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +4 -6
  147. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +9 -7
  148. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +4 -6
  149. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +2 -2
  150. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +8 -7
  151. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +0 -2
  152. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +4 -6
  153. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
  154. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +8 -7
  155. package/dist/knowledge/references/companion.technical-doc.service.md +102 -2
  156. package/dist/knowledge/references/example.config.app-shell.full.md +0 -1
  157. package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
  158. package/dist/knowledge/references/platform.config.saas.md +1 -0
  159. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  160. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +25 -1
  161. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +45 -0
  162. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  163. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  164. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  165. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -0
  166. package/dist/knowledge/references/saas.models.data-mode-read-list.md +31 -4
  167. package/dist/knowledge/references/saas.models.engine-capabilities.md +26 -6
  168. package/dist/knowledge/references/saas.models.file-upload-grant.md +179 -0
  169. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  170. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  171. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +127 -0
  172. package/dist/knowledge/references/saas.models.provider-capabilities.md +4 -3
  173. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  174. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  175. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +11 -31
  176. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +32 -2
  177. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +29 -6
  178. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +20 -0
  179. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  180. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +6 -0
  181. package/dist/knowledge/references/zod.decorators.field-spec-params.md +31 -5
  182. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +43 -0
  183. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  184. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +15 -0
  185. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  186. package/dist/knowledge/registries/framework-topics.json +99 -1
  187. package/dist/knowledge/registries/playbooks.json +81 -8
  188. package/dist/knowledge/registries/source-tags.json +757 -588
  189. package/dist/knowledge/skills/INDEX.md +3 -3
  190. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +2 -1
  191. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +5 -1
  192. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +66 -37
  193. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +40 -7
  194. package/dist/knowledge/skills/config-app-shell/SKILL.md +25 -1
  195. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +25 -1
  196. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  197. package/dist/knowledge/skills/config-design-system/SKILL.md +23 -1
  198. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  199. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  200. package/dist/knowledge/skills/config-navigation/SKILL.md +75 -2
  201. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  202. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  203. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  204. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +149 -0
  205. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +114 -0
  206. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +133 -0
  207. package/dist/knowledge/skills/config-saas/SKILL.md +19 -2
  208. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +111 -0
  209. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +30 -9
  210. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +1 -0
  211. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +2 -1
  212. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  213. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -0
  214. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +20 -0
  215. package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
  216. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +20 -0
  217. package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
  218. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +104 -0
  219. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +13 -0
  220. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +71 -4
  221. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +89 -0
  222. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +22 -1
  223. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +192 -0
  224. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +28 -8
  225. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +15 -0
  226. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +6 -0
  227. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +89 -0
  228. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +43 -0
  229. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  230. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -1
  231. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
  232. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +20 -0
  233. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +31 -5
  234. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +22 -0
  235. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +45 -0
  236. package/dist/knowledge/topic-index.json +504 -156
  237. package/dist/tsconfig.build.tsbuildinfo +1 -1
  238. package/dist/tsconfig.tsbuildinfo +1 -1
  239. package/package.json +4 -4
  240. package/dist/esm/.builder.pid +0 -9
@@ -1,14 +1,10 @@
1
1
  {
2
2
  "ref": "bottom_up.build-decompose",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "bottom_up",
5
5
  "intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (labels / i18n, email templates, seeds) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / single-flight-lock / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. v1 scaffold methodology — a typed build-task-graph contract, a dependency-DAG solver, and a collection validator are a later depth phase, not here.",
6
6
  "functionalTopics": [],
7
7
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "bottom_up"
11
- },
12
8
  {
13
9
  "kind": "artifact_exists",
14
10
  "selector": {
@@ -31,6 +27,9 @@
31
27
  },
32
28
  {
33
29
  "family": "placement-plan"
30
+ },
31
+ {
32
+ "family": "vision-brief"
34
33
  }
35
34
  ],
36
35
  "outputs": [
@@ -42,7 +41,7 @@
42
41
  ],
43
42
  "stepOutputs": [],
44
43
  "method": {
45
- "guidance": "# Build Decompose — Domain Plan → Ordered Coding-Agent Task Graph (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 per-resource stage order, and the\n> task-shape convention below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The *analytical\n> depth* of build planning (a typed task-graph contract, a dependency-DAG solver with\n> transitive ordering, a collection validator, cost/effort estimation) is intentionally\n> shallow here and is deepened in a later phase; do not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first build-execution playbook** — the pivot from **planning the\ndomain** (the domain-plan: modules, per-module resource inventory, relationship\nintents) to **decomposing the build** (the ordered set of buildable tasks). It runs\nin the **bottom-up phase**, after the domain plan exists (`artifact_exists\ndomain-plan`). You are not re-opening domain questions here — you are turning an\n*approved* domain plan into the *ordered work that builds it*.\n\nDownstream of this playbook, two further playbooks consume your output: the\n**dispatch-orchestration** playbook single-flight-dispatches each task through the\ncoding-agent contract, and the **scale** playbook parallelises and interleaves the\ncompanion generation steps. **You author neither of those concerns** — see the\nboundary section below.\n\n## What this playbook does\n\nYou are the **build planner**. This playbook reads the approved domain plan and the\ndefinition set and drafts the **build plan**: the answer to *\"what ordered sequence\nof coding-agent tasks turns this domain plan into a running app?\"* You produce **one\nartifact**: the **build-plan** family — an **ordered task graph**, each task bound\nonto the **7-topic functional taxonomy** and the **app-knowledge skill catalog**.\n\nThis is a **decomposition pass**. You name tasks, their target, their topic, their\nskill(s), and their ordering intent. You do **not** dispatch any task, capture any\nchange-set, author any schema, or generate any code — that is the job of the\ndownstream dispatch / scale playbooks and the coding agents they run.\n\n## Read state first — what you read, the one artifact you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before decomposing\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the domain plan is present and\n approved, and check whether a `build-plan` already exists from an earlier run\n (refine it, do not re-author — see below).\n2. Read the approved domain plan and the definition set. **Load-bearing** (these drive\n the decomposition): the **domain-plan** (`domain-plan` — the module decomposition +\n each module's `mainResources` / `supportingResources` inventory) and the\n **relationship drafts** (inside the domain-plan value — the inter-resource relationship\n intents, each with two ends + cardinality intent + ownership direction).\n **Contextual** (they shape ordering and task briefs, not the core decomposition):\n the **roadmap** (`roadmap` — the release phasing, so MVP-critical modules are\n sequenced before later ones) and the **requirements** + **feature-drafts** (the\n prose contracts each task's brief points the coding agent at).\n\n// TODO CLI COMMAND: wildo context journey-status\n// (read current journey scope + approved domain plan + any existing build plan)\n// TODO CLI COMMAND: wildo context domain-plan\n// (read the module decomposition + per-module resource inventory to decompose)\n\nYou **read** `domain-plan` (incl. its relationship drafts) + `roadmap` + `requirements` +\n`feature-drafts`; you **write** the `build-plan` family.\n\n3. Read the **current application workspace** section supplied with this brief (the real\n module ids and each resource's present schema fields). It is BINDING, in both directions:\n - Every task's `moduleRef` MUST be one of the listed module ids, exactly — a module id\n the workspace does not carry is an invented address the dispatcher cannot route.\n - A resource the workspace already lists exists as a **compose-born starter skeleton**\n (registered, typechecking, carrying the fields shown). Its stage tasks are\n **enrichment** tasks: their objective states what domain content to ADD or CHANGE.\n An objective that asks to \"create\" or \"scaffold\" such a resource describes work that\n is already done, and the dispatched coding run will correctly change nothing.\n\n## The two ordering axes\n\nEvery task you emit is placed on **two ordering axes**. They are **distinct** — the\nper-resource sequence deliberately *spans* topics and is not monotonic on the topic\nchain — so keep them separate and satisfy both:\n\n1. **The topic dependency edges** (across the whole app — from the taxonomy's\n `Depends On`): `configure_application_foundation` → `model_domain_graph` →\n `define_interaction_semantics` → app-level `shape_user_experience` →\n `extend_application` → `connect_runtime_and_external_capabilities` →\n `assemble_verify_and_iterate`. You author neither the foundation nor the final\n assemble/verify — you decompose the middle bands (Topics 2–6). Topic 1 IS a sibling\n playbook (`bottom_up.foundation`). **Topic 7 currently has no playbook at all**\n (issue #147): its producer was removed with the verification/digest demolition and\n has not been replaced. You still emit no Topic 7 task, for a structural reason rather\n than a delegation — see the verify/quality-gate exclusion below. The edges you must respect: an\n operation task after the resources it acts on; an **app-level** view / navigation\n task after the interaction semantics and resources it composes; an extension after\n the UX it extends; an integration after the resources it connects.\n2. **The per-resource inner stage order** (within one resource):\n **schema → config → ui-behavior → spec.** This is a *dependency* sequence (each\n stage needs the prior artifact) and it deliberately **crosses topics**: schema +\n config are `model_domain_graph`, ui-behavior is `shape_user_experience`, and the\n spec is the `model_domain_graph` documentation capstone authored last. Two\n consequences to get right:\n - A resource's **own** ui-behavior (its field displays / forms) depends only on\n that resource's schema + config — so it may be ordered **before** cross-resource\n operations. That is **not** a topic-chain violation; only *app-level* UX\n (views / navigation composing multiple resources or operations) waits on the\n interaction-semantics band.\n - The **spec** task is a documentation capstone: order it **after** the stages it\n documents (schema, config, ui-behavior), regardless of its `model_domain_graph`\n topic binding. Its topic says *what* it documents; its ordering says *after what*.\n\n**Sequencing tiebreaker — MVP first.** The two axes constrain *relative* order but leave\nfreedom in which module to build first. Break that tie with the **roadmap** — but note the\nroadmap is requirement-addressed, not module-addressed: a phase delivers\n`deliversRequirementRefs` / `deliversSuccessCriterionRefs`, not modules. So trace each\nmodule's requirements to the earliest roadmap phase that delivers them, then sequence the\nmodules whose requirements land in an earlier phase (NOW / MVP) before those whose\nrequirements land later (NEXT / LATER), so a partial build is a coherent MVP slice rather\nthan a scattered half of every module. This is a soft ordering preference, not a hard\nprerequisite — never let it override the two hard axes above.\n\n## Step 1 — Emit the module + resource tasks (the domain-graph band)\n\nWalk the domain plan module by module. For each **module**, first check whether the\n**foundation step** (a sibling playbook) already scaffolded its slice — it normally has,\nbecause foundation materialises every module in the domain plan. Emit a module task only\nwhere that is not guaranteed; then, for each **resource** in that module's inventory,\nemit the ordered per-resource stage tasks:\n\n| Task | Functional topic | Skill (the HOW) |\n|---|---|---|\n| **(only when needed)** Ensure module `<id>` slice exists + is registered across runtimes — **normally already done by the foundation step**; emit this only for a module the foundation step did NOT establish (e.g. one added to the plan after foundation ran). Idempotent, never a blind re-scaffold | `model_domain_graph` | `resource-add-module` + `module-registration` |\n| Resource `<name>` — domain schema (fields, enums, structural decorators). **Workspace-aware**: when the resource already exists as a compose-born starter (see the workspace section), the objective names the DOMAIN content to add to it; only a resource the workspace does not list gets a skeleton-creation objective | `model_domain_graph` | `resource-add-resource` (skeleton, only when the resource does not exist yet) + `resource-schema-authoring` (the persisted shape) |\n| Resource `<name>` — config (registry presence, core operation verbs, access / role scope — but NOT cross-resource relationships, which are the dedicated Step 2 tasks) | `model_domain_graph` | `resource-config-wiring` |\n| Resource `<name>` — ui-behavior (field displays / forms / enum chrome — the resource's own UX) | `shape_user_experience` | `resource-ui-behavior` |\n| Resource `<name>` — spec (canonical business semantics — the per-resource documentation capstone) | `model_domain_graph` | `spec-resource-update` |\n\n> **Two things this table is careful about.** (a) **`ui-behavior` is `shape_user_experience`,\n> not interaction semantics** — a resource's field-display / form chrome is UX (Topic 4's\n> \"resource displays / forms\"); the resource's *operations* (custom verbs, access, scope) are a\n> SEPARATE interaction-semantics band, Step 3. (b) The **`spec` task is a documentation\n> capstone**: it documents the resource's fields (domain), operations (interaction), and frontend\n> (UX), so its single topic binding is `model_domain_graph` (the spec's canonical role is business\n> semantics), but its *ordering* is \"after the stages it documents\", not a topic-chain position —\n> see the ordering axes below. (c) **Module scaffolding + registration is the foundation\n> step's job** (a sibling playbook that materialises every domain-plan module). Do NOT emit a\n> module-scaffold or module-registration task for a module foundation already established — that\n> double-counts foundation. The build loop's domain-graph band is per-**resource**; only ensure a\n> module slice where foundation genuinely did not (e.g. a module added to the plan after\n> foundation ran).\n\nRules for a buildable domain-graph band:\n\n- **Cover every module and every resource** in the inventory (both `mainResources`\n and `supportingResources`). A module or resource with no task is a coverage GAP (the\n build would not produce it).\n- **Not every resource needs every stage.** A `mainResource` (the entity the module is\n about) typically earns the full schema → config → ui-behavior → spec sequence. A\n `supportingResource` may not: a pure junction / lookup entity needs schema + config\n but no ui-behavior (it has no first-class UX surface). Emit the stages the resource\n genuinely needs, and say why a stage is omitted — do NOT pad every supporting\n resource with a UX task it will never use.\n- **Respect the per-resource stage order** (schema → config → ui-behavior → spec) as\n prose prerequisite references on each task (\"depends on: resource `<name>` — schema\").\n- **State objectives against workspace reality.** A task for a resource the workspace\n section already lists says what to ENRICH (\"author the deal-pipeline stage enum and\n amount/close-date fields the domain plan declares on `deals`\"), never \"create the\n `deals` resource\" — that file exists and a creation objective dispatches a no-op.\n `moduleRef` values come from the workspace section verbatim.\n- **Do not author fields or schemas here.** The task *names* the resource and its\n stage and points the coding agent at the skill; *what* fields the resource carries\n is resolved by the coding agent at dispatch time, from the domain plan + the skill.\n If you catch yourself writing a field list, stop — that is the coding agent's job.\n (Naming the domain CONCERN a stage must cover — \"the pipeline stages\", \"the follow-up\n reminder date\" — is objective-writing, not field authoring; listing concrete\n field-by-field types would be.)\n\n## Step 1b — Emit the shell-placement tasks (when a placement plan exists)\n\nThe **placement plan** decides WHERE every settings destination, resource operation\nand view sits in the shell, and why. It runs before you — it depends on the domain\nplan, not on your output, which is what keeps the two from forming a cycle. You do\nnot re-decide any of it; you turn it into buildable work.\n\nEmit **one task per SURFACE the plan actually places something on**, never one per\ndecision — the config files are per-surface, so a task per decision would have N\ntasks editing one file:\n\n| Task | Functional topic | Skill (the HOW) |\n|---|---|---|\n| Author the `<surface>` placement config from the accepted placement plan | `shape_user_experience` | `settings-placement-authoring` |\n\nRules:\n\n- **Target kind is `SHELL_PLACEMENT`, carrying the surface.** Not\n `COMPANION_GENERATION_STEP` — that kind is \"never a coding-agent run\" and this is\n one. The host derives the mutation scope from the kind, so borrowing a neighbour's\n gives the task the wrong permissions.\n- **A surface the plan places nothing on gets no task.** An empty settings rail is\n not something to author.\n- **Order after the resources and views a surface references.** Placing a resource's\n LIST in the sidebar before that resource exists is a task that cannot verify.\n- **Carry the decision, not the config.** The task names the surface and points at\n the skill; which category a destination lands in and in what order is IN the plan,\n read by the coding agent at dispatch. Do not restate placements in the objective.\n- **No placement plan? Emit nothing here and say so.** Do not invent placement — a\n guessed arrangement is exactly what the plan exists to replace, and it would be\n invisible to the reader who assumes a placement task came from a decision.\n\n## Step 2 — Emit the relationship-wiring tasks\n\nFor each **relationship-draft**, emit one wiring task:\n\n| Task | Functional topic | Skill (the HOW) |\n|---|---|---|\n| Wire relationship `<A> <-> <B>` (`<cardinality>`, `<owner>` holds the ref) | `model_domain_graph` | `module-relationships` |\n\nRules:\n\n- **This is the single home for cross-resource relationships.** A relationship is wired\n ONCE, here, by the `module-relationships` skill (which coordinates the FK across the\n owner's schema + config, the target's relationship map, and both specs coherently). Do\n NOT also wire it inside the per-resource config task in Step 1 — that config task\n establishes the resource's registry presence and core verbs, not its cross-resource\n FKs. Emitting the relationship in both places double-counts the work.\n- **Order after both endpoints' schema tasks.** A relationship-wiring task references\n two resources; both must have a schema task ordered before it (a relationship wired\n before an endpoint exists is a GAP).\n- **Carry the intent, not the resolution.** The task states the two ends, the\n cardinality intent, and the ownership direction from the relationship-draft. The\n cardinality-to-FK-holder resolution (discriminator / conditional relationships, the\n physical FK placement) is the `module-relationships` skill's job **at dispatch\n time**, not decided here.\n\n## Step 3 — Emit the interaction, UX, extension, and integration tasks\n\nOnce the domain graph is decomposed, emit the tasks for the later topic bands, drawn\nfrom the requirements + feature-drafts. Bind each task to **one** functional topic and\nto the skill(s) that carry its HOW, resolved from the **skills router**\n(`.claude/skills/INDEX.md` in the app — the catalog index that routes a task to its\nskill folder). Do **not** guess a skill name; route through the index.\n\n- **`define_interaction_semantics`** — custom operations, lifecycle behaviour, access /\n role / scope rules, rate limits — interaction beyond the default resource verbs.\n- **`shape_user_experience`** — app-level composite views, navigation, layouts, the app\n shell, design-system application, charts (the cross-resource UX; a resource's own\n field-display ui-behavior was already emitted in Step 1).\n- **`extend_application`** — custom UI components / widgets, custom implementation\n logic, PDF templates / renderers, workers / minions and other auxiliary execution\n surfaces (the controlled extension points where the declarative model is not enough).\n- **`connect_runtime_and_external_capabilities`** — providers, external connectors,\n billing wiring, email / notification wiring, storage, infra / environment config.\n\n(Seed authoring and the label / email generation are companion-owned generation steps —\nsee Step 4 — not coding-agent extension tasks.)\n\nRules:\n\n- **Every task names a real topic + a real skill.** A task with an invented topic or a\n skill folder that does not exist is a GAP (the dispatch playbook would have nothing\n to run). Route through the skills index; do not invent.\n- **Respect the topic dependency edges.** An operation task after the resources it acts\n on; an app-level view / navigation task after the interaction semantics **and** every\n resource it composes; an extension after the UX it extends; an integration after the\n resources it connects. (A resource's own field-display ui-behavior was already emitted\n in Step 1 and needs only that resource's schema/config — see the ordering axes.)\n- **Draw tasks from the definition set, not a blank page.** A UX or operation task\n earns its existence from a requirement or feature-draft; a task justified by nothing\n in the definition set is a CONCERN (speculative work).\n\n## Step 4 — Interleave the companion-owned generation steps\n\nSome build steps are **companion-owned deterministic generation**, not coding-agent\nwork. Emit these as tasks too — `target.kind: COMPANION_GENERATION_STEP` with\n`generationStepRef` set to the EXACT step slug below (the companion executes only this\nclosed vocabulary; any other slug refuses at dispatch) — and **order them after the\nsurfaces whose output they consume**:\n\n- **`i18n-labels`** — label generation + translation to every enabled locale. Order it\n after the resources / ui-behavior / views whose labels it generates.\n- **`email-templates`** — email template + label generation and label translation.\n Order it after the notification/email surfaces it renders.\n\nSeed generation joins this vocabulary when its companion pipeline exists. Until then,\ndo **not** author a seeds generation step — an unknown `generationStepRef` refuses at\ndispatch instead of parking the build.\n\nYou **place** these steps in the order; you do **not** design how they run\nconcurrently with coding-agent tasks (that interleaving-at-scale concern is the scale\nplaybook's job — see the boundary below).\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not re-decompose modules or resources\n whose tasks are already correct. Only add a task, re-order where a prerequisite\n changed, or add/correct a relationship-wiring task where the domain plan genuinely\n changed.\n- **Reuse existing task refs.** A task that already exists keeps its ref — never mint a\n second ref for the same unit of work.\n- **Never orphan an ordering reference.** A task's prerequisite reference must name a\n task that is actually in the plan. If you remove or rename a task, follow it into\n every prerequisite reference.\n\n## Quality gate — `build-plan-coherent` (declarative at scaffold depth)\n\nThe build plan is checked against the `build-plan-coherent` **reviewer checklist** (see the end of this method):\nseven invariants (module + resource coverage, task well-formedness, per-resource stage\norder, topic dependency order, relationship coverage, companion-generation interleave,\nand decomposition-depth boundary discipline), each marked PASS / CONCERN / GAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the build plan today is the\ncreator's `approve_result` review of the produced task graph. There is intentionally\n**no deterministic gate**: no typed build-task-graph contract or collection validator\nexists at this phase (see the boundary below).\n\n## Scaffold-depth boundary (deferred to a later depth phase, or owned by a sibling)\n\nKeep this playbook at decomposition depth. Explicitly **out of scope here**:\n\n- **Dispatch execution.** You do NOT dispatch any task, spawn any coding agent, build a\n context pack, or run the coding-agent contract. That is the **dispatch-orchestration**\n playbook, downstream of this decomposition.\n- **Workspace-mutation safety.** Single-flight locking, clean-worktree preconditions,\n change-set capture (git baseline / diff), and the failure-policy revert/flag mechanics\n are the dispatch playbook's concern — NOT modelled here. A task that describes *how* it\n is captured or locked is out of this playbook's depth.\n- **Verify / quality-gate mechanics.** Running typecheck, validators, tests, or reviewer\n agents *around* a dispatched task is the dispatch playbook's verify step — you do not model it.\n The app-wide assemble / verify phase (Topic 7) you also do not emit, and the reason is\n STRUCTURAL rather than delegation: a build-plan task's `target.kind` is one of `MODULE`,\n `RESOURCE_STAGE`, `RELATIONSHIP` or `COMPANION_GENERATION_STEP`, and none of them can express\n \"verify the assembled application\". There is no vocabulary for it, so a task claiming to do it\n would be a task no executor could run.\n **Do not read that as \"a sibling playbook covers it\" — none does today** (issue #147). Per-task\n verification exists; app-wide verification does not. You decompose Topics 2–6 only.\n- **Multi-agent scale + interleaving.** Parallelising tasks across multiple coding\n agents, and interleaving the companion generation steps concurrently with coding-agent\n runs, is the **scale** playbook. You produce a linear-enough ordered graph with prose\n prerequisite intent; you do NOT solve the concurrency schedule.\n- **Schema / field authoring + code generation.** You name resources and stages; you do\n NOT author fields, enums, decorators, Zod schemas, or any code, and you do NOT resolve\n a cardinality intent into a concrete FK. That is the coding agent at dispatch time.\n- **A typed build-task-graph contract + a collection validator.** The `build-plan`\n family has **no schemaRef** because the framework ships no `_core` build-task-graph\n shape, and it has no deterministic gate because no task-graph validator exists. A typed\n task contract, a dependency-DAG solver, and a module-set coverage validator are all a\n filed depth-phase item — do **NOT** reshape `_core` here.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\ndecomposition depth — depth is a dedicated later pass, and dispatch/scale are sibling\nplaybooks.\n\n## What you emit\n\nOne artifact for this journey:\n\n- The **build-plan** at `specifications/src/build-plan/index.ts` — an ordered task\n graph: the per-resource (schema / config / ui-behavior / spec) tasks, the\n relationship-wiring tasks, the interaction / UX / extension / integration tasks, any\n module-ensure tasks foundation did not cover, and the interleaved companion-generation\n steps — each carrying its target, its one functional topic, its skill(s), and its prose\n ordering intent.\n\nThe creator reviews the result (approval posture `approve_result`) before it is accepted\nas the journey's build plan, which the dispatch-orchestration and scale playbooks then\nturn into dispatched, verified coding-agent runs.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,\n and confirm the approved domain plan is in place to decompose the build from.\n- `.claude/skills/resource-add-module/SKILL.md` — the module-scaffolding vocabulary, for\n the conditional ensure-module task (only where the foundation step did not establish the\n module slice).\n- `.claude/skills/resource-add-resource/SKILL.md` — the resource vocabulary (the\n resource-skeleton task in the schema stage).\n- `.claude/skills/resource-schema-authoring/SKILL.md` — the schema stage (first\n per-resource task).\n- `.claude/skills/resource-config-wiring/SKILL.md` — the config stage (second\n per-resource task).\n- `.claude/skills/resource-ui-behavior/SKILL.md` — the ui-behavior stage (third\n per-resource task).\n- `.claude/skills/spec-resource-update/SKILL.md` — the spec stage (fourth per-resource\n task).\n- `.claude/skills/module-relationships/SKILL.md` — the relationship-wiring task's HOW\n (cardinality-to-FK-holder resolution, at dispatch time — named here, not performed).\n- `.claude/skills/module-registration/SKILL.md` — the cross-runtime module-registration\n task's HOW.\n- `.claude/skills/INDEX.md` — the skills router: consult it to bind each interaction /\n UX / extension / integration task to its real skill folder from the full catalog. Do\n not invent skill names; route through the index.\n\n## Reviewer checklist — `build-plan-coherent`\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 drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess seven invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. Do NOT flag the absence of a seeds step — seed generation has no companion pipeline yet and must not be authored. (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (single-flight locking, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)\n",
44
+ "guidance": "# Build Decompose — Domain Plan → Ordered Coding-Agent Task Graph (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 per-resource stage order, and the\n> task-shape convention below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The *analytical\n> depth* of build planning (a typed task-graph contract, a dependency-DAG solver with\n> transitive ordering, a collection validator, cost/effort estimation) is intentionally\n> shallow here and is deepened in a later phase; do not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first build-execution playbook** — the pivot from **planning the\ndomain** (the domain-plan: modules, per-module resource inventory, relationship\nintents) to **decomposing the build** (the ordered set of buildable tasks). It runs\nin the **bottom-up phase**, after the domain plan exists (`artifact_exists\ndomain-plan`). You are not re-opening domain questions here — you are turning an\n*approved* domain plan into the *ordered work that builds it*.\n\nDownstream of this playbook, two further playbooks consume your output: the\n**dispatch-orchestration** playbook single-flight-dispatches each task through the\ncoding-agent contract, and the **scale** playbook parallelises and interleaves the\ncompanion generation steps. **You author neither of those concerns** — see the\nboundary section below.\n\n## What this playbook does\n\nYou are the **build planner**. This playbook reads the approved domain plan and the\ndefinition set and drafts the **build plan**: the answer to *\"what ordered sequence\nof coding-agent tasks turns this domain plan into a running app?\"* You produce **one\nartifact**: the **build-plan** family — an **ordered task graph**, each task bound\nonto the **7-topic functional taxonomy** and the **app-knowledge skill catalog**.\n\nThis is a **decomposition pass**. You name tasks, their target, their topic, their\nskill(s), and their ordering intent. You do **not** dispatch any task, capture any\nchange-set, author any schema, or generate any code — that is the job of the\ndownstream dispatch / scale playbooks and the coding agents they run.\n\n## Read state first — what you read, the one artifact you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before decomposing\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the domain plan is present and\n approved, and check whether a `build-plan` already exists from an earlier run\n (refine it, do not re-author — see below).\n2. Read the approved domain plan and the definition set. **Load-bearing** (these drive\n the decomposition): the **domain-plan** (`domain-plan` — the module decomposition +\n each module's `mainResources` / `supportingResources` inventory) and the\n **relationship drafts** (inside the domain-plan value — the inter-resource relationship\n intents, each with two ends + cardinality intent + ownership direction).\n **Contextual** (they shape ordering and task briefs, not the core decomposition):\n the **roadmap** (`roadmap` — the release phasing, so MVP-critical modules are\n sequenced before later ones) and the **requirements** + **feature-drafts** (the\n prose contracts each task's brief points the coding agent at).\n\n(Both are already in your brief: the domain plan renders under \"# Accepted application truth\", and\nthe real module/resource state arrives as the declared `workspace_truth` context section of your brief. There is no command to\nrun in this mode.)\n\nYou **read** `domain-plan` (incl. its relationship drafts) + `roadmap` + `requirements` +\n`feature-drafts`; you **write** the `build-plan` family.\n\n3. Read the **current application workspace** section supplied with this brief (the real\n module ids and each resource's present schema fields). It is BINDING, in both directions:\n - Every task's `moduleRef` MUST be one of the listed module ids, exactly — a module id\n the workspace does not carry is an invented address the dispatcher cannot route.\n - A resource the workspace already lists exists as a **compose-born starter skeleton**\n (registered, typechecking, carrying the fields shown). Its stage tasks are\n **enrichment** tasks: their objective states what domain content to ADD or CHANGE.\n An objective that asks to \"create\" or \"scaffold\" such a resource describes work that\n is already done, and the dispatched coding run will correctly change nothing.\n\n## The two ordering axes\n\nEvery task you emit is placed on **two ordering axes**. They are **distinct** — the\nper-resource sequence deliberately *spans* topics and is not monotonic on the topic\nchain — so keep them separate and satisfy both:\n\n1. **The topic dependency edges** (across the whole app — from the taxonomy's\n `Depends On`): `configure_application_foundation` → `model_domain_graph` →\n `define_interaction_semantics` → app-level `shape_user_experience` →\n `extend_application` → `connect_runtime_and_external_capabilities` →\n `assemble_verify_and_iterate`. You author neither the foundation nor the final\n assemble/verify — you decompose the middle bands (Topics 2–6). Topic 1 IS a sibling\n playbook (`bottom_up.foundation`), and Topic 7 IS one again\n (`bottom_up.assemble-verify`, rebuilt under issue #147 after its producer was removed\n with the verification/digest demolition). You still emit no Topic 7 task, and the reason\n is structural rather than a delegation: `BuildPlanTaskTargetKind` has no verification\n member, so app-wide verification cannot be expressed as a build-plan task at all — see\n the verify/quality-gate exclusion below. The edges you must respect: an\n operation task after the resources it acts on; an **app-level** view / navigation\n task after the interaction semantics and resources it composes; an extension after\n the UX it extends; an integration after the resources it connects.\n2. **The per-resource inner stage order** (within one resource):\n **schema → config → ui-behavior → spec.** This is a *dependency* sequence (each\n stage needs the prior artifact) and it deliberately **crosses topics**: schema +\n config are `model_domain_graph`, ui-behavior is `shape_user_experience`, and the\n spec is the `model_domain_graph` documentation capstone authored last. Two\n consequences to get right:\n - A resource's **own** ui-behavior (its field displays / forms) depends only on\n that resource's schema + config — so it may be ordered **before** cross-resource\n operations. That is **not** a topic-chain violation; only *app-level* UX\n (views / navigation composing multiple resources or operations) waits on the\n interaction-semantics band.\n - The **spec** task is a documentation capstone: order it **after** the stages it\n documents (schema, config, ui-behavior), regardless of its `model_domain_graph`\n topic binding. Its topic says *what* it documents; its ordering says *after what*.\n\n**Sequencing tiebreaker — MVP first.** The two axes constrain *relative* order but leave\nfreedom in which module to build first. Break that tie with the **roadmap** — but note the\nroadmap is requirement-addressed, not module-addressed: a phase delivers\n`deliversRequirementRefs` / `deliversSuccessCriterionRefs`, not modules. So trace each\nmodule's requirements to the earliest roadmap phase that delivers them, then sequence the\nmodules whose requirements land in an earlier phase (NOW / MVP) before those whose\nrequirements land later (NEXT / LATER), so a partial build is a coherent MVP slice rather\nthan a scattered half of every module. This is a soft ordering preference, not a hard\nprerequisite — never let it override the two hard axes above.\n\n## Step 1 — Emit the module + resource tasks (the domain-graph band)\n\nWalk the domain plan module by module. For each **module**, first check whether the\n**foundation step** (a sibling playbook) already scaffolded its slice — it normally has,\nbecause foundation materialises every module in the domain plan. Emit a module task only\nwhere that is not guaranteed; then, for each **resource** in that module's inventory,\nemit the ordered per-resource stage tasks:\n\n| Task | Functional topic | Skill (the HOW) |\n|---|---|---|\n| **(only when needed)** Ensure module `<id>` slice exists + is registered across runtimes — **normally already done by the foundation step**; emit this only for a module the foundation step did NOT establish (e.g. one added to the plan after foundation ran). Idempotent, never a blind re-scaffold | `model_domain_graph` | `resource-add-module` + `module-registration` |\n| Resource `<name>` — domain schema (fields, enums, structural decorators). **Workspace-aware**: when the resource already exists as a compose-born starter (see the workspace section), the objective names the DOMAIN content to add to it; only a resource the workspace does not list gets a skeleton-creation objective | `model_domain_graph` | `resource-add-resource` (skeleton, only when the resource does not exist yet) + `resource-schema-authoring` (the persisted shape) |\n| Resource `<name>` — config (registry presence, core operation verbs, access / role scope — but NOT cross-resource relationships, which are the dedicated Step 2 tasks) | `model_domain_graph` | `resource-config-wiring` |\n| Resource `<name>` — ui-behavior (field displays / forms / enum chrome — the resource's own UX) | `shape_user_experience` | `resource-ui-behavior` |\n| Resource `<name>` — spec (canonical business semantics — the per-resource documentation capstone) | `model_domain_graph` | `spec-resource-update` |\n\n> **Two things this table is careful about.** (a) **`ui-behavior` is `shape_user_experience`,\n> not interaction semantics** — a resource's field-display / form chrome is UX (Topic 4's\n> \"resource displays / forms\"); the resource's *operations* (custom verbs, access, scope) are a\n> SEPARATE interaction-semantics band, Step 3. (b) The **`spec` task is a documentation\n> capstone**: it documents the resource's fields (domain), operations (interaction), and frontend\n> (UX), so its single topic binding is `model_domain_graph` (the spec's canonical role is business\n> semantics), but its *ordering* is \"after the stages it documents\", not a topic-chain position —\n> see the ordering axes below. (c) **Module scaffolding + registration is the foundation\n> step's job** (a sibling playbook that materialises every domain-plan module). Do NOT emit a\n> module-scaffold or module-registration task for a module foundation already established — that\n> double-counts foundation. The build loop's domain-graph band is per-**resource**; only ensure a\n> module slice where foundation genuinely did not (e.g. a module added to the plan after\n> foundation ran).\n\nRules for a buildable domain-graph band:\n\n- **Cover every module and every resource** in the inventory (both `mainResources`\n and `supportingResources`). A module or resource with no task is a coverage GAP (the\n build would not produce it).\n- **Not every resource needs every stage.** A `mainResource` (the entity the module is\n about) typically earns the full schema → config → ui-behavior → spec sequence. A\n `supportingResource` may not: a pure junction / lookup entity needs schema + config\n but no ui-behavior (it has no first-class UX surface). Emit the stages the resource\n genuinely needs, and say why a stage is omitted — do NOT pad every supporting\n resource with a UX task it will never use.\n- **Respect the per-resource stage order** (schema → config → ui-behavior → spec) as\n prose prerequisite references on each task (\"depends on: resource `<name>` — schema\").\n- **State objectives against workspace reality.** A task for a resource the workspace\n section already lists says what to ENRICH (\"author the deal-pipeline stage enum and\n amount/close-date fields the domain plan declares on `deals`\"), never \"create the\n `deals` resource\" — that file exists and a creation objective dispatches a no-op.\n `moduleRef` values come from the workspace section verbatim.\n- **Do not author fields or schemas here.** The task *names* the resource and its\n stage and points the coding agent at the skill; *what* fields the resource carries\n is resolved by the coding agent at dispatch time, from the domain plan + the skill.\n If you catch yourself writing a field list, stop — that is the coding agent's job.\n (Naming the domain CONCERN a stage must cover — \"the pipeline stages\", \"the follow-up\n reminder date\" — is objective-writing, not field authoring; listing concrete\n field-by-field types would be.)\n\n## Step 1b — Emit the shell-placement tasks (when a placement plan exists)\n\nThe **placement plan** decides WHERE every settings destination, resource operation\nand view sits in the shell, and why. It runs before you — it depends on the domain\nplan, not on your output, which is what keeps the two from forming a cycle. You do\nnot re-decide any of it; you turn it into buildable work.\n\nEmit **one task per SURFACE the plan actually places something on**, never one per\ndecision — the config files are per-surface, so a task per decision would have N\ntasks editing one file:\n\n| Task | Functional topic | Skill (the HOW) |\n|---|---|---|\n| Author the `<surface>` placement config from the accepted placement plan | `shape_user_experience` | `settings-placement-authoring` |\n\nRules:\n\n- **Target kind is `SHELL_PLACEMENT`, carrying the surface.** Not\n `COMPANION_GENERATION_STEP` — that kind is \"never a coding-agent run\" and this is\n one. The host derives the mutation scope from the kind, so borrowing a neighbour's\n gives the task the wrong permissions.\n- **A surface the plan places nothing on gets no task.** An empty settings rail is\n not something to author.\n- **Order after the resources and views a surface references.** Placing a resource's\n LIST in the sidebar before that resource exists is a task that cannot verify.\n- **Carry the decision, not the config.** The task names the surface and points at\n the skill; which category a destination lands in and in what order is IN the plan,\n read by the coding agent at dispatch. Do not restate placements in the objective.\n- **No placement plan? Emit nothing here and say so.** Do not invent placement — a\n guessed arrangement is exactly what the plan exists to replace, and it would be\n invisible to the reader who assumes a placement task came from a decision.\n\n## Step 2 — Emit the relationship-wiring tasks\n\nFor each **relationship-draft**, emit one wiring task:\n\n| Task | Functional topic | Skill (the HOW) |\n|---|---|---|\n| Wire relationship `<A> <-> <B>` (`<cardinality>`, `<owner>` holds the ref) | `model_domain_graph` | `module-relationships` |\n\nRules:\n\n- **This is the single home for cross-resource relationships.** A relationship is wired\n ONCE, here, by the `module-relationships` skill (which coordinates the FK across the\n owner's schema + config, the target's relationship map, and both specs coherently). Do\n NOT also wire it inside the per-resource config task in Step 1 — that config task\n establishes the resource's registry presence and core verbs, not its cross-resource\n FKs. Emitting the relationship in both places double-counts the work.\n- **Order after both endpoints' schema tasks.** A relationship-wiring task references\n two resources; both must have a schema task ordered before it (a relationship wired\n before an endpoint exists is a GAP).\n- **Carry the intent, not the resolution.** The task states the two ends, the\n cardinality intent, and the ownership direction from the relationship-draft. The\n cardinality-to-FK-holder resolution (discriminator / conditional relationships, the\n physical FK placement) is the `module-relationships` skill's job **at dispatch\n time**, not decided here.\n\n## Step 3 — Emit the interaction, UX, extension, and integration tasks\n\nOnce the domain graph is decomposed, emit the tasks for the later topic bands, drawn\nfrom the requirements + feature-drafts. Bind each task to **one** functional topic and\nto the skill(s) that carry its HOW, resolved from the **skills router**\n(`.claude/skills/INDEX.md` in the app — the catalog index that routes a task to its\nskill folder). Do **not** guess a skill name; route through the index.\n\n- **`define_interaction_semantics`** — custom operations, lifecycle behaviour, access /\n role / scope rules, rate limits — interaction beyond the default resource verbs.\n- **`shape_user_experience`** — app-level composite views, navigation, layouts, the app\n shell, design-system application, charts (the cross-resource UX; a resource's own\n field-display ui-behavior was already emitted in Step 1).\n- **`extend_application`** — custom UI components / widgets, custom implementation\n logic, PDF templates / renderers, workers / minions and other auxiliary execution\n surfaces (the controlled extension points where the declarative model is not enough).\n- **`connect_runtime_and_external_capabilities`** — providers, external connectors,\n billing wiring, email / notification wiring, storage, infra / environment config.\n\n## Posture constraints are work, not commentary\n\nThe vision family's compliance posture and constraints are INPUT on equal footing with the\nrequirements: an obligation the posture states — a retention/erasure rule over customer data, a\nterminal-access (cookie/telemetry) posture, an operational-vs-marketing email distinction — needs a\ntask that lands it, serving the nfr it substantiates. Do not compress a posture into an adjective\ninside another task's objective (\"GDPR-appropriate handling\"): an adjective is not schedulable,\nreviewable or landable. If the posture states an obligation and no task expresses it, the\ndecomposition is incomplete.\n\n(Seed authoring and the label / email generation are companion-owned generation steps —\nsee Step 4 — not coding-agent extension tasks.)\n\nRules:\n\n- **Every task names a real topic + a real skill.** A task with an invented topic or a\n skill folder that does not exist is a GAP (the dispatch playbook would have nothing\n to run). Route through the declared `skill_catalog` context section of your brief; do not invent.\n- **Respect the topic dependency edges.** An operation task after the resources it acts\n on; an app-level view / navigation task after the interaction semantics **and** every\n resource it composes; an extension after the UX it extends; an integration after the\n resources it connects. (A resource's own field-display ui-behavior was already emitted\n in Step 1 and needs only that resource's schema/config — see the ordering axes.)\n- **Draw tasks from the definition set, not a blank page.** A UX or operation task\n earns its existence from a requirement or feature-draft; a task justified by nothing\n in the definition set is a CONCERN (speculative work).\n\n## Step 4 — Interleave the companion-owned generation steps\n\nSome build steps are **companion-owned deterministic generation**, not coding-agent\nwork. Emit these as tasks too — `target.kind: COMPANION_GENERATION_STEP` with\n`generationStepRef` set to the EXACT step slug below (the companion executes only this\nclosed vocabulary; any other slug refuses at dispatch) — and **order them after the\nsurfaces whose output they consume**:\n\n- **`i18n-labels`** — label generation + translation to every enabled locale. Order it\n after the resources / ui-behavior / views whose labels it generates.\n- **`email-templates`** — email template + label generation and label translation.\n Order it after the notification/email surfaces it renders.\n- **`logo`** — the brand mark: an expert panel derives creative directions, marks are\n generated, a vision judge scores them, and the winner is promoted into the\n specifications brand SSOT. Order it after the brand brief exists; it depends on no\n code surface, so it may run early and in parallel with resource work. Author it at\n most once — an application has one accepted mark, and the step skips itself without\n calling a model when one is already accepted.\n\nSeed generation joins this vocabulary when its companion pipeline exists. Until then,\ndo **not** author a seeds generation step — an unknown `generationStepRef` refuses at\ndispatch instead of parking the build.\n\nYou **place** these steps in the order; you do **not** design how they run\nconcurrently with coding-agent tasks (that interleaving-at-scale concern is the scale\nplaybook's job — see the boundary below).\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not re-decompose modules or resources\n whose tasks are already correct. Only add a task, re-order where a prerequisite\n changed, or add/correct a relationship-wiring task where the domain plan genuinely\n changed.\n- **Reuse existing task refs.** A task that already exists keeps its ref — never mint a\n second ref for the same unit of work.\n- **Never orphan an ordering reference.** A task's prerequisite reference must name a\n task that is actually in the plan. If you remove or rename a task, follow it into\n every prerequisite reference.\n\n## Quality gate — `build-plan-coherent` (declarative at scaffold depth)\n\nThe build plan is checked against the `build-plan-coherent` **reviewer checklist** (see the end of this method):\nseven invariants (module + resource coverage, task well-formedness, per-resource stage\norder, topic dependency order, relationship coverage, companion-generation interleave,\nand decomposition-depth boundary discipline), each marked PASS / CONCERN / GAP.\n\nThis checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the build plan today is the\ncreator's `approve_result` review of the produced task graph. There is intentionally\n**no deterministic gate**: no typed build-task-graph contract or collection validator\nexists at this phase (see the boundary below).\n\n## Scaffold-depth boundary (deferred to a later depth phase, or owned by a sibling)\n\nKeep this playbook at decomposition depth. Explicitly **out of scope here**:\n\n- **Dispatch execution.** You do NOT dispatch any task, spawn any coding agent, build a\n context pack, or run the coding-agent contract. That is the **dispatch-orchestration**\n playbook, downstream of this decomposition.\n- **Workspace-mutation safety.** Single-flight locking, clean-worktree preconditions,\n change-set capture (git baseline / diff), and the failure-policy revert/flag mechanics\n are the dispatch playbook's concern — NOT modelled here. A task that describes *how* it\n is captured or locked is out of this playbook's depth.\n- **Verify / quality-gate mechanics.** Running typecheck, validators, tests, or reviewer\n agents *around* a dispatched task is the dispatch playbook's verify step — you do not model it.\n The app-wide assemble / verify phase (Topic 7) you also do not emit, and the reason is\n STRUCTURAL rather than delegation: a build-plan task's `target.kind` is one of `MODULE`,\n `RESOURCE_STAGE`, `RELATIONSHIP` or `COMPANION_GENERATION_STEP`, and none of them can express\n \"verify the assembled application\". There is no vocabulary for it, so a task claiming to do it\n would be a task no executor could run.\n **Do not read that as \"a sibling playbook covers it\" — none does today** (issue #147). Per-task\n verification exists; app-wide verification does not. You decompose Topics 2–6 only.\n- **Multi-agent scale + interleaving.** Parallelising tasks across multiple coding\n agents, and interleaving the companion generation steps concurrently with coding-agent\n runs, is the **scale** playbook. You produce a linear-enough ordered graph with prose\n prerequisite intent; you do NOT solve the concurrency schedule.\n- **Schema / field authoring + code generation.** You name resources and stages; you do\n NOT author fields, enums, decorators, Zod schemas, or any code, and you do NOT resolve\n a cardinality intent into a concrete FK. That is the coding agent at dispatch time.\n- **A typed build-task-graph contract + a collection validator.** The `build-plan`\n family has **no schemaRef** because the framework ships no `_core` build-task-graph\n shape, and it has no deterministic gate because no task-graph validator exists. A typed\n task contract, a dependency-DAG solver, and a module-set coverage validator are all a\n filed depth-phase item — do **NOT** reshape `_core` here.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\ndecomposition depth — depth is a dedicated later pass, and dispatch/scale are sibling\nplaybooks.\n\n## What you emit\n\nOne artifact for this journey:\n\n- The **build-plan** at `specifications/src/build-plan/index.ts` — an ordered task\n graph: the per-resource (schema / config / ui-behavior / spec) tasks, the\n relationship-wiring tasks, the interaction / UX / extension / integration tasks, any\n module-ensure tasks foundation did not cover, and the interleaved companion-generation\n steps — each carrying its target, its one functional topic, its skill(s), and its prose\n ordering intent.\n\nThe creator reviews the result (approval posture `approve_result`) before it is accepted\nas the journey's build plan, which the dispatch-orchestration and scale playbooks then\nturn into dispatched, verified coding-agent runs.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,\n and confirm the approved domain plan is in place to decompose the build from.\n- `.claude/skills/resource-add-module/SKILL.md` — the module-scaffolding vocabulary, for\n the conditional ensure-module task (only where the foundation step did not establish the\n module slice).\n- `.claude/skills/resource-add-resource/SKILL.md` — the resource vocabulary (the\n resource-skeleton task in the schema stage).\n- `.claude/skills/resource-schema-authoring/SKILL.md` — the schema stage (first\n per-resource task).\n- `.claude/skills/resource-config-wiring/SKILL.md` — the config stage (second\n per-resource task).\n- `.claude/skills/resource-ui-behavior/SKILL.md` — the ui-behavior stage (third\n per-resource task).\n- `.claude/skills/spec-resource-update/SKILL.md` — the spec stage (fourth per-resource\n task).\n- `.claude/skills/module-relationships/SKILL.md` — the relationship-wiring task's HOW\n (cardinality-to-FK-holder resolution, at dispatch time — named here, not performed).\n- `.claude/skills/module-registration/SKILL.md` — the cross-runtime module-registration\n task's HOW.\n- `.claude/skills/INDEX.md` — the skills router: consult it to bind each interaction /\n UX / extension / integration task to its real skill folder from the full catalog. Do\n not invent skill names; route through the index.\n\n## Reviewer checklist — `build-plan-coherent`\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 drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess seven invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. Do NOT flag the absence of a seeds step — seed generation has no companion pipeline yet and must not be authored. (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (single-flight locking, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)\n",
46
45
  "skillRefs": [
47
46
  "journey-status",
48
47
  "resource-add-module",
@@ -58,7 +57,9 @@
58
57
  "workspace_truth",
59
58
  "skill_catalog"
60
59
  ],
61
- "suspendsForClarification": false
60
+ "suspendsForClarification": false,
61
+ "briefAdequacyGate": false,
62
+ "briefAdequacyExcludedSources": []
62
63
  },
63
64
  "executor": "companion_agent",
64
65
  "approval": "approve_result",
@@ -292,8 +292,9 @@ Before dispatching anything:
292
292
  depends on greenfield bring-up tooling (deferred). The dispatch contract is real and
293
293
  runs against an **existing** app skeleton — the dogfood app already has one.
294
294
 
295
- // TODO CLI COMMAND: wildo journey status
296
- // (read current journey scope + the approved build plan + which tasks already dispatched)
295
+ // Operator status: `wildo context journey` (phase + board + runs in flight). Which tasks already
296
+ // landed is read from GIT by the runner itself — a task is landed when every file it produces is
297
+ // committed clean.
297
298
 
298
299
  You **read** `build-plan`; you **write** no journey artifact
299
300
  — the runner records the change-set + task status on the dispatched task's row.
@@ -421,8 +422,9 @@ dispatch contract for you (you do not hand-assemble any of it):
421
422
  dirty-at-dispatch is the NORMAL state (parallel sessions), so the capture
422
423
  *attributes* rather than assuming the run had the tree to itself.
423
424
 
424
- // TODO CLI COMMAND: wildo journey run <playbookRef>
425
- // (trigger the dispatch; the runner composes the context pack + runs one ACP prompt turn + captures the change-set)
425
+ // The trigger is the companion's run route (`POST /api/companion/playbooks/<ref>/run`, via the
426
+ // workbench or HTTP) — there is no CLI trigger yet. The runner composes the typed context pack,
427
+ // runs one ACP prompt turn, and captures the change-set.
426
428
 
427
429
  ## Step 4 — Verify OUTSIDE the coding agent
428
430
 
@@ -5,10 +5,6 @@
5
5
  "intent": "Bottom-up build dispatch — the SECOND build-execution playbook, the pivot from DECOMPOSING the build (the build-plan task graph) to DISPATCHING it: turning one ordered task into an actually-run, verified coding-agent run under the D4 dispatch contract. Reads the approved TYPED build-plan (`BuildPlanTaskGraph` — each task carries a closed target kind, ONE MetaWorkflow_FunctionalTopic, its skill refs, and DECLARED prerequisite task refs) and the current journey state, selects the NEXT READY task (`selectReadyBuildPlanTasks`: every declared prerequisite has landed — resolved by the host, never inferred from prose; SINGLE-FLIGHT — exactly ONE workspace-mutating run at a time), and dispatches exactly that typed task: (1) the runner builds the context pack (task brief + the task's skill pointers + the relevant journey/definition artifacts + introspected app reality + repo paths); (2) it runs ONE prompt turn against the coding agent over the Agent Client Protocol, in a session rooted at the app workspace (cwd = app root, so CLAUDE.md / .claude skills load naturally), answering the agent's permission requests within the execution profile's declared ceiling and refusing anything above it or outside the task's mutation scope; (3) it captures the change-set around the run (git baseline/post-run worktree snapshots → per-file attribution → a structured GitChangeSetCapture recorded on the task row); (4) it runs the VERIFY gate OUTSIDE the coding agent (a deterministic typecheck the runner maps onto the dispatch verification hook — pnpm exec tsc --noEmit — the trust-but-verify floor); (5) it records the result + applies the onFailure disposition (keep_and_flag: a failed/timed-out run keeps its captured change-set flagged for human triage, never a silent half-applied state). Then loop to the next ready task. This playbook PRODUCES the per-task dispatch contract + execution semantics; it authors no schemas and generates no code (the coding agent does that at dispatch time). It does NOT decompose the plan (that is the build-decompose playbook, upstream — it owns the task graph) and does NOT solve multi-agent SCALE — parallelism across several coding agents, the concurrency schedule, and interleaving the companion generation steps at scale are the downstream scale playbook. v1 scaffold: the single-flight dispatch contract; multi-agent parallelism, a run-completion serializer, and a revert_changeset failure path are later phases (revert is a MUTATING git op outside the read-only change-set carve-out, deliberately deferred).",
6
6
  "functionalTopics": [],
7
7
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "bottom_up"
11
- },
12
8
  {
13
9
  "kind": "artifact_exists",
14
10
  "selector": {
@@ -24,7 +20,7 @@
24
20
  "outputs": [],
25
21
  "stepOutputs": [],
26
22
  "method": {
27
- "guidance": "# Build Dispatch — One Build-Plan Task → One Verified Coding-Agent Run (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 of the\n> *single-flight* dispatch contract — dispatch exactly ONE build-plan task at a\n> time, capture its change-set, verify it outside the coding agent, record it, and\n> apply the failure disposition. The context-pack shape, the verify gate, and the\n> failure-handling below are deliberately explicit so they can be tuned against real\n> runs. Multi-agent parallelism, a concurrency scheduler, a run-completion\n> serializer, and a `revert_changeset` failure path are a **later phase** — do not\n> build them here (see the boundary section).\n\n## Where you are in the journey\n\nThis is the **second build-execution playbook** — the pivot from **decomposing the\nbuild** (the build-plan: the ordered coding-agent task graph) to **dispatching it**\n(turning one ordered task into an actually-run, verified coding-agent run). It runs\nin the **bottom-up phase**, after the build plan exists (`artifact_exists\nbuild-plan`) and the foundation step has authored the app's config and skeleton.\nYou are not re-opening the decomposition\nhere — you are turning one *approved, ordered* task into a *dispatched, verified*\nchange to the application.\n\nUpstream, the **build-decompose** playbook produced the ordered task graph you\nconsume; downstream, the **scale** playbook generalises this single-flight contract\nto many concurrent coding agents and interleaves the companion generation steps.\n**You author neither of those concerns** — see the boundary section.\n\n## The typed task you dispatch\n\nThe build plan is a typed family (`BuildPlanTaskGraph`): dispatch selects ONE\nREADY task (all declared prerequisite task refs have landed) and hands the\ncoding host exactly that task's `objective`, `target`, `functionalTopic` and\n`skillRefs`. The host derives the physical allowed/prohibited paths and the\nfixed verification from the target kind; nothing in the task — and nothing in\nthis method prose — authors a path, a command, a prompt or a runtime control.\n\n## Import Origins\n\n- `@wildo-ai/saas-specifications`\n\n## Source Excerpts\n\n### Origin Package: `@wildo-ai/saas-specifications`\n\n```typescript\n *\n * Versioning for the build-plan task-graph payload format itself. `V1` —\n * initial shape (one ordered `tasks` collection with typed targets and\n * declared prerequisites). The shape grows additively across versions; the\n * `version` field is the explicit marker for consumers that branch on era.\n */\nexport enum BuildPlanTaskGraphVersion {\n V1 = 'v1',\n}\n\n/** Stable prefix every build-plan task ref carries; the trusted runtime stamps it, a provider supplies only the slug. */\nexport const BUILD_PLAN_TASK_REF_PREFIX = 'build-task-';\n\n/**\n * WHAT a build task builds — a closed vocabulary, because the host derives\n * the physical mutation scope and verification policy from the target kind\n * and the model must never author those powers through free text.\n */\nexport enum BuildPlanTaskTargetKind {\n /** A whole application module (its shared-lib registration, backend module and frontend module skeletons). */\n MODULE = 'MODULE',\n /** One build stage of one resource: schema → config → ui-behavior → spec. */\n RESOURCE_STAGE = 'RESOURCE_STAGE',\n /** One relationship between two resources. */\n RELATIONSHIP = 'RELATIONSHIP',\n /** A companion-owned deterministic generation step (labels, seeds, emails…) interleaved by the build loop, never a coding-agent run. */\n COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',\n /**\n * Authoring one SHELL SURFACE's placement configuration from the accepted\n * placement plan — the settings rail, the sidebar, the user menu or the\n * command palette.\n *\n * Its own kind rather than a reuse of the neighbours, because none of them is\n * true of it: it is not a MODULE or a RESOURCE_STAGE (it is application-wide\n * and belongs to no resource), not a RELATIONSHIP, and emphatically not a\n * COMPANION_GENERATION_STEP — that kind is documented as \"never a coding-agent\n * run\" and writing `settings-hub.config.ts` is exactly a coding-agent run.\n * Borrowing one would hand the host the wrong mutation scope and the wrong\n * verification, which is what the closed vocabulary exists to prevent.\n */\n SHELL_PLACEMENT = 'SHELL_PLACEMENT',\n}\n\n/** The per-resource build stages, in their fixed order. */\nexport enum BuildPlanResourceStage {\n SCHEMA = 'SCHEMA',\n CONFIG = 'CONFIG',\n UI_BEHAVIOR = 'UI_BEHAVIOR',\n SPEC = 'SPEC',\n}\n\nconst SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n/**\n * A skill ref is the skill's FOLDER id in the app-knowledge catalog, which is\n * also its `SKILL.md` frontmatter `name` — one id, kebab-case. The host refuses\n * any skill name outside `[a-z0-9-]+`, so a ref that does not match this shape\n * can never resolve to an installed skill.\n */\nconst SkillRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\nconst NonEmptyStringSchema = z.string().trim().min(1);\n\nexport const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),\n moduleRef: SlugSchema,\n resourceRef: SlugSchema,\n stage: z.enum(BuildPlanResourceStage),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),\n moduleRef: SlugSchema,\n relationshipRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),\n /** The companion generation step this task runs (e.g. labels, seeds); resolved by the companion, never by a coding agent. */\n generationStepRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.SHELL_PLACEMENT),\n /**\n * Which shell surface this task authors — the placement family's OWN\n * `PlacementSurface`, deliberately not a build-plan copy of it.\n *\n * A copy was written first and was a defect, caught by probing the landing\n * renderer rather than by any test: `PlacementAddress` discriminates on\n * `surface` with `z.literal(...)` per option, so only the VALUES survive into\n * the schema, and the renderer resolves a discriminator by matching that value\n * SET against the exported enums. Two enums with identical values made the\n * match ambiguous, the renderer correctly refused to guess an owner, and the\n * address discriminator became unnameable — a landed placement plan would have\n * emitted `surface: \"SETTINGS_HUB\"` as a bare string instead of\n * `PlacementSurface.SETTINGS_HUB`. One concept, one named source.\n */\n surface: z.enum(PlacementSurface),\n }),\n]);\nexport type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;\n\n/**\n * One ordered build task. It names WHAT to build and WHY; it never carries\n * HOW (no paths, commands, prompts, cwd, model, profile). The host resolves\n * the physical allowed/prohibited paths and the fixed verification from the\n * target kind, and the installed skills from `skillRefs` against the app\n * knowledge catalog.\n *\n * Dependency readiness is DECLARED as prerequisite task refs and RESOLVED by\n * the host (a prerequisite is satisfied when its task has landed), never a\n * solved DAG the model must get right.\n */\nexport const BuildPlanTaskSchema = z.strictObject({\n /** `build-task-<slug>`, stamped by the trusted runtime. */\n taskRef: z.string().regex(new RegExp(`^${BUILD_PLAN_TASK_REF_PREFIX}[a-z0-9]+(?:-[a-z0-9]+)*$`)),\n /** One sentence of intent: what this task delivers. */\n objective: NonEmptyStringSchema,\n target: BuildPlanTaskTargetSchema,\n /**\n * Exactly ONE functional topic this task belongs to.\n *\n * **It does NOT drive ordering** — this said \"drives cross-app ordering\" until 2026-08-30 and\n * nothing ever ordered by it. Sequencing is `prerequisiteTaskRefs`, resolved by the host, and it\n * is the only thing that decides what may run next.\n *\n * What it DOES: the dispatch host stamps it into the coding-agent's task payload beside\n * `skillRefs`, so the agent is told which phase of building the application this task belongs to.\n * That is context an LLM reads, not a value the runtime branches on — the distinction matters,\n * because a reader who believes it orders will look here for a scheduling bug that lives in the\n * prerequisite graph. See issue #124.\n */\n functionalTopic: z.enum(MetaWorkflow_FunctionalTopic),\n /** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */\n skillRefs: z.array(SkillRefSchema).min(1),\n /** Task refs that must have landed first; resolved by the host, not solved by the model. */\n prerequisiteTaskRefs: z.array(z.string()).default([]),\n /** Requirement / roadmap refs this task serves (traceability only; never scope authority). */\n servesRefs: z.array(NonEmptyStringSchema).default([]),\n});\nexport type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;\n\n/**\n * THE build-plan payload — a **single aggregate per product**: the ORDERED\n * task graph that turns the accepted domain plan into buildable units.\n *\n * **Artifact-family id: `build-plan`.** This schema is the shape of the\n * journey artifact selected by `MetaWorkflow_ArtifactSelector.family ===\n * 'build-plan'` (the `family` vocabulary stays an open string owned by the\n * selector surface; this note is the single place tying the SHAPE to the\n * NAME). Produced by the build-decompose playbook, consumed one task at a\n * time by build-dispatch (single-flight coding dispatch) and by the scale\n * playbook.\n *\n * Invariants enforced here: unique task refs; every prerequisite names a task\n * in this graph; no self-prerequisite. Cycle detection and ordering\n * soundness are the deterministic validator's job (`validateBuildPlanTaskGraph`).\n */\nexport const BuildPlanTaskGraphSchema = z.object({\n version: z.enum(BuildPlanTaskGraphVersion).default(BuildPlanTaskGraphVersion.V1),\n /**\n * At least one task, at the SCHEMA — not merely as a validator warning. The first live playbook-loop\n * run (2026-08-24) proved why: build-decompose answered `tasks: []`, which was schema-valid, passed\n * `_core` validation as a mere warning, and LANDED — overwriting a completed 3-task plan with a\n * vacuous artifact. Decomposing to zero tasks is a refusal (\"nothing to decompose\"), never an\n * artifact: an empty plan carries no information a reader could act on, and the file it replaces\n * does. Same vacuity class already closed on the requirements family (`functional: min(1)`).\n */\n tasks: z.array(BuildPlanTaskSchema).min(1),\n}).superRefine((graph, context) => {\n const refs = new Set<string>();\n graph.tasks.forEach((task, index) => {\n if (refs.has(task.taskRef)) {\n context.addIssue({ code: 'custom', message: `duplicate build task ref \"${task.taskRef}\"`, path: ['tasks', index, 'taskRef'] });\n }\n refs.add(task.taskRef);\n });\n graph.tasks.forEach((task, index) => {\n task.prerequisiteTaskRefs.forEach((prerequisite, prerequisiteIndex) => {\n if (prerequisite === task.taskRef) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" cannot be its own prerequisite`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n } else if (!refs.has(prerequisite)) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" names an unknown prerequisite \"${prerequisite}\"`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n }\n });\n });\n});\nexport type BuildPlanTaskGraph = z.infer<typeof BuildPlanTaskGraphSchema>;\n```\n\n## What this playbook does\n\nYou are the **dispatch orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, for *one* task at a time: *\"dispatch this\ntask safely, verify it, and record what happened.\"* You do **not** produce a new\njourney artifact — the dispatch's observable result (the change-set + the task\nstatus) is materialized by the runner on the task row, not authored here (see \"What\nyou emit\"). You do **not** decompose the plan, author any schema, or write any code\n— the coding agent writes the code at dispatch time; the plan is the\nbuild-decompose playbook's; scale is the scale playbook's.\n\n## The dispatch contract — the runner owns the mechanism, you sequence it\n\nMost of the D4 dispatch contract is **runner mechanism**, not prose you re-implement:\nthe runner composes the context pack, opens a coding session with the agent over the\nAgent Client Protocol and sends one prompt turn, answers the agent's permission\nrequests within the declared ceiling, captures the change-set, runs the verify hook,\nholds the single-flight lock, and enforces the budget floor. Your method here is the **declarative recipe** the runner interprets —\n*which* task to dispatch next, *when* it is authorized, and *how* its outcome is\njudged. Do not hand-compose a dispatch prompt or drive git yourself; let the runner\nown composition and change-set capture.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the loop by one task*.\nBefore dispatching anything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the **build plan** is present\n and approved, and confirm the **foundation** ran. For each build-plan task,\n determine its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify), or\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run or a\n failed verify). This tri-state matters: under `keep_and_flag` a **failed** task\n *also* has a captured change-set, so \"has a change-set\" alone does NOT mean the\n task is done — read the task's terminal status + verify outcome, not just the\n presence of a change-set.\n2. Read the approved **build plan** (`build-plan` — the ordered task graph). It is your\n work list.\n\n Evidence that the foundation ran is `./wildo.saas.config.ts` itself, committed: the\n app either has a config and a skeleton or it does not, and git answers that without a\n journey artifact standing in for it. (A `foundation-manifest` family was that stand-in\n until 2026-08-25; it was retired with the app-creation verification/digest aspect, and\n this playbook no longer gates on it.) The honest limitation inherited from the\n foundation step still applies: at scaffold depth the on-disk skeleton *materialization*\n depends on greenfield bring-up tooling (deferred). The dispatch contract is real and\n runs against an **existing** app skeleton — the dogfood app already has one.\n\n// TODO CLI COMMAND: wildo journey status\n// (read current journey scope + the approved build plan + which tasks already dispatched)\n\nYou **read** `build-plan`; you **write** no journey artifact\n— the runner records the change-set + task status on the dispatched task's row.\n\n## Precondition — the application must establish the agent's role, or dispatch stalls\n\nCheck this before the first dispatch of an application's life. It costs one look and it is the\ndifference between a working lane and one that burns model time producing nothing.\n\n**The application needs a root `CLAUDE.md` stating that a task dispatched by its dev companion is\nlegitimate work.** Without it the agent is right to refuse, and refusing is what it does.\n\nThe reason is structural rather than a matter of tone. A dispatched task reaches the agent as an\nordinary prompt — a user turn carrying an objective, a mutation scope and skill refs. Nothing in\nthat turn proves where it came from. So the agent is being handed conversational content that\ntells it to write files into a repository, which is indistinguishable from the thing every\ncareful agent is supposed to decline, and the more trustworthy the agent the more reliably it\ndeclines. Measured on a real application with no such file: two dispatched runs stalled, one\nanswering *\"content that arrives as conversational input doesn't get to reassign what I am\"*.\n\nThe failure does not look like a missing file. It looks like an agent that deliberates well,\nidentifies exactly which files it would author, explains its reasoning, asks a human to confirm,\nand ends its turn — `end_turn`, no error, no denial, an empty change set, and a bill for the\ntokens. Read as \"the agent chose not to work\", which invites prompt-tuning that cannot fix it.\n\n`wildo init` scaffolds this file. An application created before that, or one whose `CLAUDE.md`\ncovers only its own conventions, needs the section added. What it must establish:\n\n- the task is **selected by the host** from the accepted build plan, not composed by a caller;\n- it is **confined before it arrives** — the host answers every permission request against the\n declared mutation scope and refuses paths outside it, so the agent need not police itself;\n- it is **reversible** — every write is an uncommitted working edit, and a human commits.\n\nTwo smaller things belong in the same section, because both were observed costing a run:\n\n- **Say what `allowedPathPrefixes` are relative to.** The agent receives bare prefixes such as\n `shared-lib/src/modules/<module>/` with no root, and cannot verify its own confinement against\n them. One sentence naming the application root removes the ambiguity.\n- **Do not name a task so it reads as a fixture.** An agent that concludes it is looking at a\n smoke test will say so and stop. Name the task after the product change it makes.\n\n## Step 1 — Select the next dispatchable task (single-flight)\n\nWalk the build plan in its authored order and pick the **first** task that is not\nyet dispatched (or a previously-**failed** task cleared for retry — see Step 5) and\nwhose prose prerequisites have all **succeeded**. Dispatch **exactly one** such task\nper run. If **no** task is ready — every task has already succeeded, or the only\nundispatched tasks are blocked behind a still-unresolved failure — there is nothing\nto dispatch: report the loop as done (or blocked on the failed task) and stop. An\nempty build plan is the same: nothing to dispatch, stop.\n\n- **Single-flight — one workspace-mutating run at a time.** The dispatch lane holds\n ONE workspace-mutation lock for the whole background run; a run plan carries **at\n most one** coding-agent task, and a second concurrent dispatch is refused. This is\n a hard runner floor, not a suggestion — do not try to dispatch two tasks in one\n run to \"go faster\". Batching across many agents is the scale playbook's job.\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task is ready\n only when every task it depends on is dispatched-and-succeeded (verify passed).\n A prerequisite that is dispatched-and-**failed** (its change-set is flagged for\n triage under `keep_and_flag`) does **not** satisfy the dependency — its dependents\n stay **blocked** until the failure is triaged and the prerequisite re-dispatched\n successfully. Do not build a config on a schema whose run failed. Never dispatch a\n task before the stage it depends on (a config before its schema, a spec before its\n ui-behavior — the build-decompose playbook ordered these).\n- **Companion-generation steps are not coding-agent dispatches.** A build-plan task\n marked as a companion-owned generation step (labels / i18n, email templates,\n seeds) runs through its deterministic companion endpoint, not the coding-agent\n dispatch lane. Route it there; do not dispatch a coding agent for it. Interleaving\n those steps *concurrently* with coding runs at scale is the scale playbook's job —\n here you simply run the ready one in its turn.\n\n## Step 2 — Authorize the mutating run (approve_before)\n\nA coding-agent dispatch **mutates the application workspace** — the highest-stakes\naction in the journey. This playbook's approval posture is `approve_before`: the run\nis authorized **before** it touches the tree. Settle the exact pending Authority\nRequest through the `journey-approve` interface-relay workflow; never start the\ndispatch on your own judgment.\n\n- Under the **GUIDED** autonomy preset the gate is verbatim; under **YOLO_LIGHT** it\n downgrades to a post-hoc result review; under **YOLO** it is auto (the\n non-bypassable **budget floor** — per-playbook and per-journey run/wall-time\n ceilings — is the guardrail no preset can lift).\n- **v1 gate granularity (be honest about the floor's reach).** The approval gate is\n currently **playbook-scoped for the journey**, not scoped to a single dispatch: the\n first authorization of this dispatch playbook admits the subsequent dispatches of it\n too (bounded by the run-count budget floor), rather than re-prompting per task. So\n `approve_before` here means \"the creator authorizes the **dispatch loop** before any\n task mutates the workspace\" — a real pre-mutation floor. A per-run, single-use gate\n is a deferred runner posture; until it lands, the budget ceiling + the per-task\n change-set capture + the verify gate are what bound the authorized loop.\n- The floor still hard-gates regardless of preset: once the dispatch playbook's run\n ceiling is reached, further dispatches are **refused** — that refusal is the\n correct outcome; report it, do not work around it.\n\n## Step 3 — Dispatch the task through the coding-agent contract\n\nTrigger the run through the `journey-run` skill. The runner then performs the D4\ndispatch contract for you (you do not hand-assemble any of it):\n\n1. **Context pack** — the runner composes the prompt: the task brief, the task's\n skill pointers (`Read .claude/skills/<skillRef>/SKILL.md first` — the per-task\n HOW-skills the build plan named on this task), the relevant journey / definition\n artifacts, an introspected app-reality block, and the repo paths.\n2. **Session and one prompt turn** — the runner starts the agent over the Agent\n Client Protocol and opens a session rooted at the app workspace (cwd = the\n application root, so `./CLAUDE.md`, the sub-`CLAUDE.md`s, and the `.claude/` rules\n and skills load naturally), then sends the task as a single prompt turn. It is a\n session rather than a one-shot process, which is what makes the next three things\n possible at all:\n - **Permissions are answered, not assumed.** The agent asks before each action it\n considers privileged; the runner answers within the execution profile's declared\n ceiling and refuses anything above it, or anything touching a path outside the\n task's mutation scope. Refusals are counted on the task row, so a run that was\n held back is distinguishable from a run that had nothing to do.\n - **The turn can be cancelled.** Cancellation asks the agent to stop and waits, so\n the run terminalises with its change-set intact instead of being killed — an\n operator who stops a run still needs to know what it had already written.\n - **Usage is reported.** Tokens and cost come back from the run itself rather than\n being unavailable, which is what lets the budget floor mean anything.\n3. **Change-set capture** — the runner captures a git worktree snapshot before and\n after the run and attributes each touched file (the run's own edit vs. an\n already-dirty parallel-session file vs. a file that appeared during the run),\n recording a structured change-set on the task row. On the dogfood tree,\n dirty-at-dispatch is the NORMAL state (parallel sessions), so the capture\n *attributes* rather than assuming the run had the tree to itself.\n\n// TODO CLI COMMAND: wildo journey run <playbookRef>\n// (trigger the dispatch; the runner composes the context pack + runs one ACP prompt turn + captures the change-set)\n\n## Step 4 — Verify OUTSIDE the coding agent\n\nTrust, but verify. The verify gate runs **outside** the coding agent, after the run,\nso the agent cannot mark its own homework:\n\n- **`dispatch-typecheck` (deterministic — the auto-run trust floor).** The runner\n maps this `deterministic_validator` gate (`validatorRef: typecheck`) onto the\n dispatch verification hook and runs a typecheck (`pnpm exec tsc --noEmit`) over the\n application workspace after the run, **outside** the coding agent. This is a\n **real, wired** gate — it actually executes and its result is recorded on the task\n row. A run whose typecheck fails is a failed run (apply the failure disposition in\n Step 5). At scaffold depth the gate is a **workspace-wide** typecheck (one static\n gate for every dispatch of this playbook); narrowing it to the specific package a\n given task touched — a per-task `typecheck:<pkgDir>` or a `vitest:<path>` targeted\n at the task's tests — is a later refinement, since a static playbook gate cannot\n vary per task.\n- **`dispatch-outcome-sound` (declarative reviewer checklist).** The six-invariant\n reviewer checklist (task accomplished, change-set scoped to the task, verify ran +\n passed, attribution clean, failure disposition correct, boundary discipline)\n is the *trust-but-verify reviewer* pass. It is **declarative** — the creator's\n review checklist; the compiled build-dispatch Evaluation Treatment is what the\n runtime judges with, and the deterministic typecheck above is what runs\n automatically.\n\n## Step 5 — Record the result and apply the failure disposition\n\nThe runner records the change-set + the task's terminal status on the task row. On a\n**failed or timed-out** run, this playbook's `onFailure` is **`keep_and_flag`**: the\ncaptured change-set is **kept and flagged for human triage** — never silently\nreverted, and never left as an un-recorded half-applied state. The change-set capture\n*is* the flag: it attributes exactly which files the run touched, so a human can\nreview, keep, or unwind them.\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a failed\n> run's edits is a *mutating* git operation, deliberately **outside** the read-only\n> change-set carve-out the dispatch lane observes (the runner *observes* git —\n> baseline/post-run snapshots — but stage/commit/revert stay a human/CLI concern).\n> So `keep_and_flag` is both the correct F-5 workspace-safety posture (no silent\n> half-applied state) and the behavior the runner actually enforces today. Wiring a\n> `revert_changeset` path is a deliberate later boundary decision, not a gap this\n> playbook papers over.\n\nOn a **succeeded** run (change-set captured + verify passed), the task is done and\nits dependents become eligible. On a **failed** run, the task is **not** done — it is\nflagged for human triage, and its dependents stay blocked (Step 1) until it is\ntriaged and cleared for re-dispatch. Triage is a human decision: keep + fix forward,\nunwind the flagged change-set by hand, or re-dispatch the task once its blocker is\nresolved. This playbook does not auto-retry a failed task — automated retry / backoff\nis a deferred build-loop-resilience concern, and human triage is the v1 disposition;\nhere the loop simply surfaces the failure and stops advancing that dependency chain.\n\nThen **loop**: on the next run of this playbook, `journey-status` reflects the\njust-dispatched task's outcome, and you select the next ready task (Step 1). Close a\nsignificant stretch of dispatches with a `journey-report` summary — what was\nproduced, which change-sets landed, what verify said, and any failed task left\nflagged for triage.\n\n## Refine, don't re-dispatch\n\n- **Never re-dispatch a SUCCEEDED task.** A task that is dispatched-and-succeeded\n (change-set captured + verify passed) is done — advance to the next ready task, do\n not re-run it because the plan was re-opened elsewhere. A dispatched-and-**failed**\n task is a different case: it is re-dispatchable once triaged (Step 5) — a captured\n change-set alone does not make a task \"finished\".\n- **Follow the plan's order.** If the build plan was refined upstream (a task added,\n an ordering corrected), respect the new order on the next selection — do not cache\n a stale work list across runs.\n- **A budget refusal is a real stop.** When the run ceiling is hit, stop dispatching\n and report what remains; do not do the coding work out-of-band to \"finish the\n build\" — that makes the journey's task history a lie.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **single-flight dispatch depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order the\n graph, or add tasks — the **build-decompose** playbook owns the task graph. You\n read it and dispatch from it.\n- **Multi-agent scale + interleaving.** Running MANY coding agents concurrently, a\n concurrency scheduler, a run-completion serializer, and interleaving the companion\n generation steps *concurrently* with coding runs is the **scale** playbook. You\n dispatch **one** task at a time under the single-flight lock; you do NOT design the\n concurrency schedule.\n- **A `revert_changeset` failure path.** Undoing a failed run's edits is a mutating\n git op outside the read-only change-set carve-out — deferred. `keep_and_flag` (keep\n + flag the captured change-set for triage) is the v1 disposition.\n- **Auto-executed reviewer checklist.** The checklist ships **declarative** —\n the deterministic typecheck gate runs automatically and the compiled Evaluation\n Treatment is the judged protocol; nothing executes the checklist prose. Do not\n assume it auto-ran.\n- **Schema / field authoring + code generation.** You dispatch a task; the **coding\n agent** authors the fields, schemas, ui-behavior, and code at dispatch time. If you\n catch yourself writing application code or a resource schema here, stop — that is\n the dispatched agent's job, not the orchestrator's.\n\nIf you find yourself designing how MANY agents run concurrently rather than how ONE\ntask dispatches safely, stop — that is the scale playbook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable result\nof a dispatch — the **change-set** (files touched, attributed, summarized) and the\n**task status** — is materialized by the runner on the dispatched task's row, not\nauthored by this playbook. That is deliberately not duplicated into a separate\njourney artifact family: the task row already *is* the dispatch record, and a second\nhome for the same record would drift.\n\nThe creator authorizes each dispatch (approval posture `approve_before`) before it\nmutates the workspace, and reviews the recorded change-set + verify outcome after —\none verified task at a time, until the build plan is fully dispatched.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state,\n scope, and budget; confirm the build plan is approved and the foundation ran, and\n see which tasks already dispatched.\n- `.claude/skills/journey-approve/SKILL.md` — relay the exact pre-dispatch Authority Request\n gate decision that authorizes the workspace-mutating dispatch (never self-approve).\n- `.claude/skills/journey-run/SKILL.md` — trigger the dispatch and monitor it; the\n runner composes the context pack, runs one prompt turn against the coding agent in\n the app workspace, captures the change-set, and runs the verify hook.\n- `.claude/skills/journey-report/SKILL.md` — summarize a stretch of dispatches:\n what was produced, which change-sets landed, and what the verify gates said.\n\n## Reviewer checklist — `dispatch-outcome-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, and with repository-specific wording made application-neutral):\n\nJudge whether ONE dispatched build-plan task ran soundly under the D4 dispatch contract — the trust-but-verify reviewer pass OUTSIDE the coding agent. Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) TASK ACCOMPLISHED — the change-set the run produced actually implements the dispatched task's target + stage (e.g. a schema task added the persisted shape; a ui-behavior task added field displays); a run whose change-set does not advance the task's stated target is a GAP (the dispatch produced nothing useful), and an empty change-set on a task that should have authored files is a GAP. (2) CHANGE-SET SCOPED TO THE TASK — the files touched belong to the task's target (its module / resource / stage) and the app workspace; edits sprawling into unrelated modules, Wildo package source outside the application workspace, or files no build-plan task owns are a CONCERN (scope creep the reviewer must flag). On the dogfood tree, files attributed BASELINE_DIRTY_AMBIGUOUS (already dirty at dispatch baseline — a parallel session, not this run) are review-required and must NOT be counted against the run. (3) VERIFY RAN + PASSED — the deterministic verify gate (typecheck) ran OUTSIDE the coding agent after the run and passed; a run recorded as succeeded whose typecheck the reviewer cannot confirm passed is a CONCERN, and a run whose typecheck FAILED but was recorded succeeded is a GAP. (4) ATTRIBUTION CLEAN (the single-flight signal) — the run's edits are cleanly attributable to it in the captured change-set (files classed RUN_EXCLUSIVE or APPEARED_DURING_RUN), consistent with the single-flight lock having held for this dispatch. A change-set the capture could NOT cleanly attribute to the run — dominated by BASELINE_DIRTY_AMBIGUOUS overlap, or captured across a HEAD that moved mid-run — is a CONCERN the reviewer must resolve by hand before accepting the run, not a clean pass (single-flight is a hard runner floor, so this invariant reads the attribution the run actually recorded rather than re-proving the lock). (5) FAILURE DISPOSITION CORRECT — a failed/timed-out run's captured change-set is KEPT + FLAGGED for human triage (keep_and_flag), never silently reverted nor silently left as an un-recorded half-applied state; a failed run with no recorded change-set flag is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the dispatch stays at single-task depth: it dispatches ONE task, captures + verifies + records it, and applies onFailure. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT run MANY coding agents concurrently / design a concurrency scheduler / interleave the companion generation steps at scale (the scale playbook), and does NOT itself author schemas / fields / code (the coding agent does that at dispatch time). Evidence of re-decomposition, multi-agent scale orchestration, or the dispatcher authoring code itself is a CONCERN (scope creep out of the single-flight dispatch lane). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)\n",
23
+ "guidance": "# Build Dispatch — One Build-Plan Task → One Verified Coding-Agent Run (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 of the\n> *single-flight* dispatch contract — dispatch exactly ONE build-plan task at a\n> time, capture its change-set, verify it outside the coding agent, record it, and\n> apply the failure disposition. The context-pack shape, the verify gate, and the\n> failure-handling below are deliberately explicit so they can be tuned against real\n> runs. Multi-agent parallelism, a concurrency scheduler, a run-completion\n> serializer, and a `revert_changeset` failure path are a **later phase** — do not\n> build them here (see the boundary section).\n\n## Where you are in the journey\n\nThis is the **second build-execution playbook** — the pivot from **decomposing the\nbuild** (the build-plan: the ordered coding-agent task graph) to **dispatching it**\n(turning one ordered task into an actually-run, verified coding-agent run). It runs\nin the **bottom-up phase**, after the build plan exists (`artifact_exists\nbuild-plan`) and the foundation step has authored the app's config and skeleton.\nYou are not re-opening the decomposition\nhere — you are turning one *approved, ordered* task into a *dispatched, verified*\nchange to the application.\n\nUpstream, the **build-decompose** playbook produced the ordered task graph you\nconsume; downstream, the **scale** playbook generalises this single-flight contract\nto many concurrent coding agents and interleaves the companion generation steps.\n**You author neither of those concerns** — see the boundary section.\n\n## The typed task you dispatch\n\nThe build plan is a typed family (`BuildPlanTaskGraph`): dispatch selects ONE\nREADY task (all declared prerequisite task refs have landed) and hands the\ncoding host exactly that task's `objective`, `target`, `functionalTopic` and\n`skillRefs`. The host derives the physical allowed/prohibited paths and the\nfixed verification from the target kind; nothing in the task — and nothing in\nthis method prose — authors a path, a command, a prompt or a runtime control.\n\n## Import Origins\n\n- `@wildo-ai/saas-specifications`\n\n## Source Excerpts\n\n### Origin Package: `@wildo-ai/saas-specifications`\n\n```typescript\n *\n * Versioning for the build-plan task-graph payload format itself. `V1` —\n * initial shape (one ordered `tasks` collection with typed targets and\n * declared prerequisites). The shape grows additively across versions; the\n * `version` field is the explicit marker for consumers that branch on era.\n */\nexport enum BuildPlanTaskGraphVersion {\n V1 = 'v1',\n}\n\n/** Stable prefix every build-plan task ref carries; the trusted runtime stamps it, a provider supplies only the slug. */\nexport const BUILD_PLAN_TASK_REF_PREFIX = 'build-task-';\n\n/**\n * WHAT a build task builds — a closed vocabulary, because the host derives\n * the physical mutation scope and verification policy from the target kind\n * and the model must never author those powers through free text.\n */\nexport enum BuildPlanTaskTargetKind {\n /** A whole application module (its shared-lib registration, backend module and frontend module skeletons). */\n MODULE = 'MODULE',\n /** One build stage of one resource: schema → config → ui-behavior → spec. */\n RESOURCE_STAGE = 'RESOURCE_STAGE',\n /** One relationship between two resources. */\n RELATIONSHIP = 'RELATIONSHIP',\n /** A companion-owned deterministic generation step (labels, seeds, emails…) interleaved by the build loop, never a coding-agent run. */\n COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',\n /**\n * Authoring one SHELL SURFACE's placement configuration from the accepted\n * placement plan — the settings rail, the sidebar, the user menu or the\n * command palette.\n *\n * Its own kind rather than a reuse of the neighbours, because none of them is\n * true of it: it is not a MODULE or a RESOURCE_STAGE (it is application-wide\n * and belongs to no resource), not a RELATIONSHIP, and emphatically not a\n * COMPANION_GENERATION_STEP — that kind is documented as \"never a coding-agent\n * run\" and writing `settings-hub.config.ts` is exactly a coding-agent run.\n * Borrowing one would hand the host the wrong mutation scope and the wrong\n * verification, which is what the closed vocabulary exists to prevent.\n */\n SHELL_PLACEMENT = 'SHELL_PLACEMENT',\n}\n\n/** The per-resource build stages, in their fixed order. */\nexport enum BuildPlanResourceStage {\n SCHEMA = 'SCHEMA',\n CONFIG = 'CONFIG',\n UI_BEHAVIOR = 'UI_BEHAVIOR',\n SPEC = 'SPEC',\n}\n\nconst SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n/**\n * A skill ref is the skill's FOLDER id in the app-knowledge catalog, which is\n * also its `SKILL.md` frontmatter `name` — one id, kebab-case. The host refuses\n * any skill name outside `[a-z0-9-]+`, so a ref that does not match this shape\n * can never resolve to an installed skill.\n */\nconst SkillRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\nconst NonEmptyStringSchema = z.string().trim().min(1);\n\nexport const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),\n moduleRef: SlugSchema,\n resourceRef: SlugSchema,\n stage: z.enum(BuildPlanResourceStage),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),\n moduleRef: SlugSchema,\n relationshipRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),\n /** The companion generation step this task runs (e.g. labels, seeds); resolved by the companion, never by a coding agent. */\n generationStepRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.SHELL_PLACEMENT),\n /**\n * Which shell surface this task authors — the placement family's OWN\n * `PlacementSurface`, deliberately not a build-plan copy of it.\n *\n * A copy was written first and was a defect, caught by probing the landing\n * renderer rather than by any test: `PlacementAddress` discriminates on\n * `surface` with `z.literal(...)` per option, so only the VALUES survive into\n * the schema, and the renderer resolves a discriminator by matching that value\n * SET against the exported enums. Two enums with identical values made the\n * match ambiguous, the renderer correctly refused to guess an owner, and the\n * address discriminator became unnameable — a landed placement plan would have\n * emitted `surface: \"SETTINGS_HUB\"` as a bare string instead of\n * `PlacementSurface.SETTINGS_HUB`. One concept, one named source.\n */\n surface: z.enum(PlacementSurface),\n }),\n]);\nexport type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;\n\n/**\n * One ordered build task. It names WHAT to build and WHY; it never carries\n * HOW (no paths, commands, prompts, cwd, model, profile). The host resolves\n * the physical allowed/prohibited paths and the fixed verification from the\n * target kind, and the installed skills from `skillRefs` against the app\n * knowledge catalog.\n *\n * Dependency readiness is DECLARED as prerequisite task refs and RESOLVED by\n * the host (a prerequisite is satisfied when its task has landed), never a\n * solved DAG the model must get right.\n */\nexport const BuildPlanTaskSchema = z.strictObject({\n /** `build-task-<slug>`, stamped by the trusted runtime. */\n taskRef: z.string().regex(new RegExp(`^${BUILD_PLAN_TASK_REF_PREFIX}[a-z0-9]+(?:-[a-z0-9]+)*$`)),\n /** One sentence of intent: what this task delivers. */\n objective: NonEmptyStringSchema,\n target: BuildPlanTaskTargetSchema,\n /**\n * Exactly ONE functional topic this task belongs to.\n *\n * **It does NOT drive ordering** — this said \"drives cross-app ordering\" until 2026-08-30 and\n * nothing ever ordered by it. Sequencing is `prerequisiteTaskRefs`, resolved by the host, and it\n * is the only thing that decides what may run next.\n *\n * What it DOES: the dispatch host stamps it into the coding-agent's task payload beside\n * `skillRefs`, so the agent is told which phase of building the application this task belongs to.\n * That is context an LLM reads, not a value the runtime branches on — the distinction matters,\n * because a reader who believes it orders will look here for a scheduling bug that lives in the\n * prerequisite graph. See issue #124.\n */\n functionalTopic: z.enum(MetaWorkflow_FunctionalTopic),\n /** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */\n skillRefs: z.array(SkillRefSchema).min(1),\n /** Task refs that must have landed first; resolved by the host, not solved by the model. */\n prerequisiteTaskRefs: z.array(z.string()).default([]),\n /** Requirement / roadmap refs this task serves (traceability only; never scope authority). */\n servesRefs: z.array(NonEmptyStringSchema).default([]),\n});\nexport type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;\n\n/**\n * THE build-plan payload — a **single aggregate per product**: the ORDERED\n * task graph that turns the accepted domain plan into buildable units.\n *\n * **Artifact-family id: `build-plan`.** This schema is the shape of the\n * journey artifact selected by `MetaWorkflow_ArtifactSelector.family ===\n * 'build-plan'` (the `family` vocabulary stays an open string owned by the\n * selector surface; this note is the single place tying the SHAPE to the\n * NAME). Produced by the build-decompose playbook, consumed one task at a\n * time by build-dispatch (single-flight coding dispatch) and by the scale\n * playbook.\n *\n * Invariants enforced here: unique task refs; every prerequisite names a task\n * in this graph; no self-prerequisite. Cycle detection and ordering\n * soundness are the deterministic validator's job (`validateBuildPlanTaskGraph`).\n */\nexport const BuildPlanTaskGraphSchema = z.object({\n version: z.enum(BuildPlanTaskGraphVersion).default(BuildPlanTaskGraphVersion.V1),\n /**\n * At least one task, at the SCHEMA — not merely as a validator warning. The first live playbook-loop\n * run (2026-08-24) proved why: build-decompose answered `tasks: []`, which was schema-valid, passed\n * `_core` validation as a mere warning, and LANDED — overwriting a completed 3-task plan with a\n * vacuous artifact. Decomposing to zero tasks is a refusal (\"nothing to decompose\"), never an\n * artifact: an empty plan carries no information a reader could act on, and the file it replaces\n * does. Same vacuity class already closed on the requirements family (`functional: min(1)`).\n */\n tasks: z.array(BuildPlanTaskSchema).min(1),\n}).superRefine((graph, context) => {\n const refs = new Set<string>();\n graph.tasks.forEach((task, index) => {\n if (refs.has(task.taskRef)) {\n context.addIssue({ code: 'custom', message: `duplicate build task ref \"${task.taskRef}\"`, path: ['tasks', index, 'taskRef'] });\n }\n refs.add(task.taskRef);\n });\n graph.tasks.forEach((task, index) => {\n task.prerequisiteTaskRefs.forEach((prerequisite, prerequisiteIndex) => {\n if (prerequisite === task.taskRef) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" cannot be its own prerequisite`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n } else if (!refs.has(prerequisite)) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" names an unknown prerequisite \"${prerequisite}\"`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n }\n });\n });\n});\nexport type BuildPlanTaskGraph = z.infer<typeof BuildPlanTaskGraphSchema>;\n```\n\n## What this playbook does\n\nYou are the **dispatch orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, for *one* task at a time: *\"dispatch this\ntask safely, verify it, and record what happened.\"* You do **not** produce a new\njourney artifact — the dispatch's observable result (the change-set + the task\nstatus) is materialized by the runner on the task row, not authored here (see \"What\nyou emit\"). You do **not** decompose the plan, author any schema, or write any code\n— the coding agent writes the code at dispatch time; the plan is the\nbuild-decompose playbook's; scale is the scale playbook's.\n\n## The dispatch contract — the runner owns the mechanism, you sequence it\n\nMost of the D4 dispatch contract is **runner mechanism**, not prose you re-implement:\nthe runner composes the context pack, opens a coding session with the agent over the\nAgent Client Protocol and sends one prompt turn, answers the agent's permission\nrequests within the declared ceiling, captures the change-set, runs the verify hook,\nholds the single-flight lock, and enforces the budget floor. Your method here is the **declarative recipe** the runner interprets —\n*which* task to dispatch next, *when* it is authorized, and *how* its outcome is\njudged. Do not hand-compose a dispatch prompt or drive git yourself; let the runner\nown composition and change-set capture.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the loop by one task*.\nBefore dispatching anything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the **build plan** is present\n and approved, and confirm the **foundation** ran. For each build-plan task,\n determine its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify), or\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run or a\n failed verify). This tri-state matters: under `keep_and_flag` a **failed** task\n *also* has a captured change-set, so \"has a change-set\" alone does NOT mean the\n task is done — read the task's terminal status + verify outcome, not just the\n presence of a change-set.\n2. Read the approved **build plan** (`build-plan` — the ordered task graph). It is your\n work list.\n\n Evidence that the foundation ran is `./wildo.saas.config.ts` itself, committed: the\n app either has a config and a skeleton or it does not, and git answers that without a\n journey artifact standing in for it. (A `foundation-manifest` family was that stand-in\n until 2026-08-25; it was retired with the app-creation verification/digest aspect, and\n this playbook no longer gates on it.) The honest limitation inherited from the\n foundation step still applies: at scaffold depth the on-disk skeleton *materialization*\n depends on greenfield bring-up tooling (deferred). The dispatch contract is real and\n runs against an **existing** app skeleton — the dogfood app already has one.\n\n// Operator status: `wildo context journey` (phase + board + runs in flight). Which tasks already\n// landed is read from GIT by the runner itself — a task is landed when every file it produces is\n// committed clean.\n\nYou **read** `build-plan`; you **write** no journey artifact\n— the runner records the change-set + task status on the dispatched task's row.\n\n## Precondition — the application must establish the agent's role, or dispatch stalls\n\nCheck this before the first dispatch of an application's life. It costs one look and it is the\ndifference between a working lane and one that burns model time producing nothing.\n\n**The application needs a root `CLAUDE.md` stating that a task dispatched by its dev companion is\nlegitimate work.** Without it the agent is right to refuse, and refusing is what it does.\n\nThe reason is structural rather than a matter of tone. A dispatched task reaches the agent as an\nordinary prompt — a user turn carrying an objective, a mutation scope and skill refs. Nothing in\nthat turn proves where it came from. So the agent is being handed conversational content that\ntells it to write files into a repository, which is indistinguishable from the thing every\ncareful agent is supposed to decline, and the more trustworthy the agent the more reliably it\ndeclines. Measured on a real application with no such file: two dispatched runs stalled, one\nanswering *\"content that arrives as conversational input doesn't get to reassign what I am\"*.\n\nThe failure does not look like a missing file. It looks like an agent that deliberates well,\nidentifies exactly which files it would author, explains its reasoning, asks a human to confirm,\nand ends its turn — `end_turn`, no error, no denial, an empty change set, and a bill for the\ntokens. Read as \"the agent chose not to work\", which invites prompt-tuning that cannot fix it.\n\n`wildo init` scaffolds this file. An application created before that, or one whose `CLAUDE.md`\ncovers only its own conventions, needs the section added. What it must establish:\n\n- the task is **selected by the host** from the accepted build plan, not composed by a caller;\n- it is **confined before it arrives** — the host answers every permission request against the\n declared mutation scope and refuses paths outside it, so the agent need not police itself;\n- it is **reversible** — every write is an uncommitted working edit, and a human commits.\n\nTwo smaller things belong in the same section, because both were observed costing a run:\n\n- **Say what `allowedPathPrefixes` are relative to.** The agent receives bare prefixes such as\n `shared-lib/src/modules/<module>/` with no root, and cannot verify its own confinement against\n them. One sentence naming the application root removes the ambiguity.\n- **Do not name a task so it reads as a fixture.** An agent that concludes it is looking at a\n smoke test will say so and stop. Name the task after the product change it makes.\n\n## Step 1 — Select the next dispatchable task (single-flight)\n\nWalk the build plan in its authored order and pick the **first** task that is not\nyet dispatched (or a previously-**failed** task cleared for retry — see Step 5) and\nwhose prose prerequisites have all **succeeded**. Dispatch **exactly one** such task\nper run. If **no** task is ready — every task has already succeeded, or the only\nundispatched tasks are blocked behind a still-unresolved failure — there is nothing\nto dispatch: report the loop as done (or blocked on the failed task) and stop. An\nempty build plan is the same: nothing to dispatch, stop.\n\n- **Single-flight — one workspace-mutating run at a time.** The dispatch lane holds\n ONE workspace-mutation lock for the whole background run; a run plan carries **at\n most one** coding-agent task, and a second concurrent dispatch is refused. This is\n a hard runner floor, not a suggestion — do not try to dispatch two tasks in one\n run to \"go faster\". Batching across many agents is the scale playbook's job.\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task is ready\n only when every task it depends on is dispatched-and-succeeded (verify passed).\n A prerequisite that is dispatched-and-**failed** (its change-set is flagged for\n triage under `keep_and_flag`) does **not** satisfy the dependency — its dependents\n stay **blocked** until the failure is triaged and the prerequisite re-dispatched\n successfully. Do not build a config on a schema whose run failed. Never dispatch a\n task before the stage it depends on (a config before its schema, a spec before its\n ui-behavior — the build-decompose playbook ordered these).\n- **Companion-generation steps are not coding-agent dispatches.** A build-plan task\n marked as a companion-owned generation step (labels / i18n, email templates,\n seeds) runs through its deterministic companion endpoint, not the coding-agent\n dispatch lane. Route it there; do not dispatch a coding agent for it. Interleaving\n those steps *concurrently* with coding runs at scale is the scale playbook's job —\n here you simply run the ready one in its turn.\n\n## Step 2 — Authorize the mutating run (approve_before)\n\nA coding-agent dispatch **mutates the application workspace** — the highest-stakes\naction in the journey. This playbook's approval posture is `approve_before`: the run\nis authorized **before** it touches the tree. Settle the exact pending Authority\nRequest through the `journey-approve` interface-relay workflow; never start the\ndispatch on your own judgment.\n\n- Under the **GUIDED** autonomy preset the gate is verbatim; under **YOLO_LIGHT** it\n downgrades to a post-hoc result review; under **YOLO** it is auto (the\n non-bypassable **budget floor** — per-playbook and per-journey run/wall-time\n ceilings — is the guardrail no preset can lift).\n- **v1 gate granularity (be honest about the floor's reach).** The approval gate is\n currently **playbook-scoped for the journey**, not scoped to a single dispatch: the\n first authorization of this dispatch playbook admits the subsequent dispatches of it\n too (bounded by the run-count budget floor), rather than re-prompting per task. So\n `approve_before` here means \"the creator authorizes the **dispatch loop** before any\n task mutates the workspace\" — a real pre-mutation floor. A per-run, single-use gate\n is a deferred runner posture; until it lands, the budget ceiling + the per-task\n change-set capture + the verify gate are what bound the authorized loop.\n- The floor still hard-gates regardless of preset: once the dispatch playbook's run\n ceiling is reached, further dispatches are **refused** — that refusal is the\n correct outcome; report it, do not work around it.\n\n## Step 3 — Dispatch the task through the coding-agent contract\n\nTrigger the run through the `journey-run` skill. The runner then performs the D4\ndispatch contract for you (you do not hand-assemble any of it):\n\n1. **Context pack** — the runner composes the prompt: the task brief, the task's\n skill pointers (`Read .claude/skills/<skillRef>/SKILL.md first` — the per-task\n HOW-skills the build plan named on this task), the relevant journey / definition\n artifacts, an introspected app-reality block, and the repo paths.\n2. **Session and one prompt turn** — the runner starts the agent over the Agent\n Client Protocol and opens a session rooted at the app workspace (cwd = the\n application root, so `./CLAUDE.md`, the sub-`CLAUDE.md`s, and the `.claude/` rules\n and skills load naturally), then sends the task as a single prompt turn. It is a\n session rather than a one-shot process, which is what makes the next three things\n possible at all:\n - **Permissions are answered, not assumed.** The agent asks before each action it\n considers privileged; the runner answers within the execution profile's declared\n ceiling and refuses anything above it, or anything touching a path outside the\n task's mutation scope. Refusals are counted on the task row, so a run that was\n held back is distinguishable from a run that had nothing to do.\n - **The turn can be cancelled.** Cancellation asks the agent to stop and waits, so\n the run terminalises with its change-set intact instead of being killed — an\n operator who stops a run still needs to know what it had already written.\n - **Usage is reported.** Tokens and cost come back from the run itself rather than\n being unavailable, which is what lets the budget floor mean anything.\n3. **Change-set capture** — the runner captures a git worktree snapshot before and\n after the run and attributes each touched file (the run's own edit vs. an\n already-dirty parallel-session file vs. a file that appeared during the run),\n recording a structured change-set on the task row. On the dogfood tree,\n dirty-at-dispatch is the NORMAL state (parallel sessions), so the capture\n *attributes* rather than assuming the run had the tree to itself.\n\n// The trigger is the companion's run route (`POST /api/companion/playbooks/<ref>/run`, via the\n// workbench or HTTP) — there is no CLI trigger yet. The runner composes the typed context pack,\n// runs one ACP prompt turn, and captures the change-set.\n\n## Step 4 — Verify OUTSIDE the coding agent\n\nTrust, but verify. The verify gate runs **outside** the coding agent, after the run,\nso the agent cannot mark its own homework:\n\n- **`dispatch-typecheck` (deterministic — the auto-run trust floor).** The runner\n maps this `deterministic_validator` gate (`validatorRef: typecheck`) onto the\n dispatch verification hook and runs a typecheck (`pnpm exec tsc --noEmit`) over the\n application workspace after the run, **outside** the coding agent. This is a\n **real, wired** gate — it actually executes and its result is recorded on the task\n row. A run whose typecheck fails is a failed run (apply the failure disposition in\n Step 5). At scaffold depth the gate is a **workspace-wide** typecheck (one static\n gate for every dispatch of this playbook); narrowing it to the specific package a\n given task touched — a per-task `typecheck:<pkgDir>` or a `vitest:<path>` targeted\n at the task's tests — is a later refinement, since a static playbook gate cannot\n vary per task.\n- **`dispatch-outcome-sound` (declarative reviewer checklist).** The six-invariant\n reviewer checklist (task accomplished, change-set scoped to the task, verify ran +\n passed, attribution clean, failure disposition correct, boundary discipline)\n is the *trust-but-verify reviewer* pass. It is **declarative** — the creator's\n review checklist; the compiled build-dispatch Evaluation Treatment is what the\n runtime judges with, and the deterministic typecheck above is what runs\n automatically.\n\n## Step 5 — Record the result and apply the failure disposition\n\nThe runner records the change-set + the task's terminal status on the task row. On a\n**failed or timed-out** run, this playbook's `onFailure` is **`keep_and_flag`**: the\ncaptured change-set is **kept and flagged for human triage** — never silently\nreverted, and never left as an un-recorded half-applied state. The change-set capture\n*is* the flag: it attributes exactly which files the run touched, so a human can\nreview, keep, or unwind them.\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a failed\n> run's edits is a *mutating* git operation, deliberately **outside** the read-only\n> change-set carve-out the dispatch lane observes (the runner *observes* git —\n> baseline/post-run snapshots — but stage/commit/revert stay a human/CLI concern).\n> So `keep_and_flag` is both the correct F-5 workspace-safety posture (no silent\n> half-applied state) and the behavior the runner actually enforces today. Wiring a\n> `revert_changeset` path is a deliberate later boundary decision, not a gap this\n> playbook papers over.\n\nOn a **succeeded** run (change-set captured + verify passed), the task is done and\nits dependents become eligible. On a **failed** run, the task is **not** done — it is\nflagged for human triage, and its dependents stay blocked (Step 1) until it is\ntriaged and cleared for re-dispatch. Triage is a human decision: keep + fix forward,\nunwind the flagged change-set by hand, or re-dispatch the task once its blocker is\nresolved. This playbook does not auto-retry a failed task — automated retry / backoff\nis a deferred build-loop-resilience concern, and human triage is the v1 disposition;\nhere the loop simply surfaces the failure and stops advancing that dependency chain.\n\nThen **loop**: on the next run of this playbook, `journey-status` reflects the\njust-dispatched task's outcome, and you select the next ready task (Step 1). Close a\nsignificant stretch of dispatches with a `journey-report` summary — what was\nproduced, which change-sets landed, what verify said, and any failed task left\nflagged for triage.\n\n## Refine, don't re-dispatch\n\n- **Never re-dispatch a SUCCEEDED task.** A task that is dispatched-and-succeeded\n (change-set captured + verify passed) is done — advance to the next ready task, do\n not re-run it because the plan was re-opened elsewhere. A dispatched-and-**failed**\n task is a different case: it is re-dispatchable once triaged (Step 5) — a captured\n change-set alone does not make a task \"finished\".\n- **Follow the plan's order.** If the build plan was refined upstream (a task added,\n an ordering corrected), respect the new order on the next selection — do not cache\n a stale work list across runs.\n- **A budget refusal is a real stop.** When the run ceiling is hit, stop dispatching\n and report what remains; do not do the coding work out-of-band to \"finish the\n build\" — that makes the journey's task history a lie.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **single-flight dispatch depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order the\n graph, or add tasks — the **build-decompose** playbook owns the task graph. You\n read it and dispatch from it.\n- **Multi-agent scale + interleaving.** Running MANY coding agents concurrently, a\n concurrency scheduler, a run-completion serializer, and interleaving the companion\n generation steps *concurrently* with coding runs is the **scale** playbook. You\n dispatch **one** task at a time under the single-flight lock; you do NOT design the\n concurrency schedule.\n- **A `revert_changeset` failure path.** Undoing a failed run's edits is a mutating\n git op outside the read-only change-set carve-out — deferred. `keep_and_flag` (keep\n + flag the captured change-set for triage) is the v1 disposition.\n- **Auto-executed reviewer checklist.** The checklist ships **declarative** —\n the deterministic typecheck gate runs automatically and the compiled Evaluation\n Treatment is the judged protocol; nothing executes the checklist prose. Do not\n assume it auto-ran.\n- **Schema / field authoring + code generation.** You dispatch a task; the **coding\n agent** authors the fields, schemas, ui-behavior, and code at dispatch time. If you\n catch yourself writing application code or a resource schema here, stop — that is\n the dispatched agent's job, not the orchestrator's.\n\nIf you find yourself designing how MANY agents run concurrently rather than how ONE\ntask dispatches safely, stop — that is the scale playbook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable result\nof a dispatch — the **change-set** (files touched, attributed, summarized) and the\n**task status** — is materialized by the runner on the dispatched task's row, not\nauthored by this playbook. That is deliberately not duplicated into a separate\njourney artifact family: the task row already *is* the dispatch record, and a second\nhome for the same record would drift.\n\nThe creator authorizes each dispatch (approval posture `approve_before`) before it\nmutates the workspace, and reviews the recorded change-set + verify outcome after —\none verified task at a time, until the build plan is fully dispatched.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state,\n scope, and budget; confirm the build plan is approved and the foundation ran, and\n see which tasks already dispatched.\n- `.claude/skills/journey-approve/SKILL.md` — relay the exact pre-dispatch Authority Request\n gate decision that authorizes the workspace-mutating dispatch (never self-approve).\n- `.claude/skills/journey-run/SKILL.md` — trigger the dispatch and monitor it; the\n runner composes the context pack, runs one prompt turn against the coding agent in\n the app workspace, captures the change-set, and runs the verify hook.\n- `.claude/skills/journey-report/SKILL.md` — summarize a stretch of dispatches:\n what was produced, which change-sets landed, and what the verify gates said.\n\n## Reviewer checklist — `dispatch-outcome-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, and with repository-specific wording made application-neutral):\n\nJudge whether ONE dispatched build-plan task ran soundly under the D4 dispatch contract — the trust-but-verify reviewer pass OUTSIDE the coding agent. Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) TASK ACCOMPLISHED — the change-set the run produced actually implements the dispatched task's target + stage (e.g. a schema task added the persisted shape; a ui-behavior task added field displays); a run whose change-set does not advance the task's stated target is a GAP (the dispatch produced nothing useful), and an empty change-set on a task that should have authored files is a GAP. (2) CHANGE-SET SCOPED TO THE TASK — the files touched belong to the task's target (its module / resource / stage) and the app workspace; edits sprawling into unrelated modules, Wildo package source outside the application workspace, or files no build-plan task owns are a CONCERN (scope creep the reviewer must flag). On the dogfood tree, files attributed BASELINE_DIRTY_AMBIGUOUS (already dirty at dispatch baseline — a parallel session, not this run) are review-required and must NOT be counted against the run. (3) VERIFY RAN + PASSED — the deterministic verify gate (typecheck) ran OUTSIDE the coding agent after the run and passed; a run recorded as succeeded whose typecheck the reviewer cannot confirm passed is a CONCERN, and a run whose typecheck FAILED but was recorded succeeded is a GAP. (4) ATTRIBUTION CLEAN (the single-flight signal) — the run's edits are cleanly attributable to it in the captured change-set (files classed RUN_EXCLUSIVE or APPEARED_DURING_RUN), consistent with the single-flight lock having held for this dispatch. A change-set the capture could NOT cleanly attribute to the run — dominated by BASELINE_DIRTY_AMBIGUOUS overlap, or captured across a HEAD that moved mid-run — is a CONCERN the reviewer must resolve by hand before accepting the run, not a clean pass (single-flight is a hard runner floor, so this invariant reads the attribution the run actually recorded rather than re-proving the lock). (5) FAILURE DISPOSITION CORRECT — a failed/timed-out run's captured change-set is KEPT + FLAGGED for human triage (keep_and_flag), never silently reverted nor silently left as an un-recorded half-applied state; a failed run with no recorded change-set flag is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the dispatch stays at single-task depth: it dispatches ONE task, captures + verifies + records it, and applies onFailure. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT run MANY coding agents concurrently / design a concurrency scheduler / interleave the companion generation steps at scale (the scale playbook), and does NOT itself author schemas / fields / code (the coding agent does that at dispatch time). Evidence of re-decomposition, multi-agent scale orchestration, or the dispatcher authoring code itself is a CONCERN (scope creep out of the single-flight dispatch lane). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)\n",
28
24
  "skillRefs": [
29
25
  "journey-status",
30
26
  "journey-approve",
@@ -32,7 +28,9 @@
32
28
  "journey-report"
33
29
  ],
34
30
  "contextSources": [],
35
- "suspendsForClarification": false
31
+ "suspendsForClarification": false,
32
+ "briefAdequacyGate": false,
33
+ "briefAdequacyExcludedSources": []
36
34
  },
37
35
  "executor": "coding_agent",
38
36
  "approval": "approve_before",
@@ -96,8 +96,8 @@ Before scheduling anything:
96
96
  bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale
97
97
  contract runs against an existing workspace.
98
98
 
99
- // TODO CLI COMMAND: wildo journey status
100
- // (read journey scope + the approved build plan + every task's dispatch state)
99
+ // Operator status: `wildo context journey` (phase + board + runs in flight); per-task landed
100
+ // state is read from git by the runner.
101
101
 
102
102
  You **read** `build-plan`; you **write** no journey
103
103
  artifact — the runner records each dispatched task's change-set + status on its
@@ -189,8 +189,9 @@ today's runner, see the caveat below.
189
189
  arrive only with git worktree-per-agent isolation (the runner task in Step 5's
190
190
  gap note). Until then, keep the input-ready *ordering* and serialize.
191
191
 
192
- // TODO CLI COMMAND: wildo journey run <playbookRef>
193
- // (trigger the scheduled wave; each coding slot invokes the single-flight dispatch contract, each generation step runs its deterministic endpoint)
192
+ // The trigger is the companion's run route (`POST /api/companion/playbooks/<ref>/run`) — no CLI
193
+ // trigger yet. Each coding slot invokes the single-flight dispatch contract; each generation step
194
+ // runs its deterministic endpoint.
194
195
 
195
196
  ## Step 4 — Authorize the fan-out (approve_before)
196
197