@wildo-ai/framework-knowledge 1.1.8 → 1.1.10

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 (480) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
  5. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
  7. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  8. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
  9. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  10. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
  11. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
  12. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
  14. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
  15. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +20 -4
  17. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  18. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  19. package/dist/esm/framework-knowledge.definitions.js +95 -5
  20. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  21. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  22. package/dist/esm/index.d.ts.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  24. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
  28. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +41 -3
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +175 -14
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  40. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
  43. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
  45. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +4 -2
  47. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +90 -13
  49. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
  51. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
  53. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
  55. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
  57. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  59. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  61. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
  63. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
  65. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  69. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  72. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
  74. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
  78. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +91 -43
  80. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +41 -0
  82. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +43 -0
  84. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
  85. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +200 -0
  86. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
  87. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +203 -0
  88. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
  89. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +81 -0
  90. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
  91. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +93 -0
  92. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
  93. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
  94. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  95. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
  96. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  97. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
  99. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
  101. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
  103. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
  105. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
  113. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  116. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
  117. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  118. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  121. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  123. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  124. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  125. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  126. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
  127. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  128. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
  129. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  130. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +71 -2
  131. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  132. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  133. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  134. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  135. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
  137. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  138. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
  139. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  140. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
  141. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  142. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
  143. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  144. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
  146. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +41 -17
  148. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  149. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  150. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  151. package/dist/knowledge/manifest.json +8 -8
  152. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
  153. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  154. package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
  155. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
  156. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  157. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  158. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +261 -34
  159. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
  160. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -59
  161. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  162. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
  163. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
  164. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
  165. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
  166. package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
  167. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
  168. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  169. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  170. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +129 -17
  171. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
  172. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
  173. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
  174. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
  175. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
  176. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  177. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
  178. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
  179. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
  180. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  181. package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
  182. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
  183. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  184. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  185. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  186. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  187. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +75 -37
  188. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
  189. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
  190. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -0
  191. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
  192. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
  193. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +99 -0
  194. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
  195. package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
  196. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -0
  197. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  198. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  199. package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
  200. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
  201. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  202. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  203. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
  204. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
  205. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
  206. package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
  207. package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
  208. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
  209. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  210. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  211. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  212. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  213. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  214. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
  215. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  216. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  217. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
  218. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  219. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  220. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  221. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  222. package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
  223. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
  224. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
  225. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +29 -0
  226. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
  227. package/dist/knowledge/references/brand.name-choice.config.md +144 -0
  228. package/dist/knowledge/references/brand.name-screening.config.md +308 -0
  229. package/dist/knowledge/references/build-plan.task-graph.config.md +119 -11
  230. package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
  231. package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
  232. package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
  233. package/dist/knowledge/references/capability-composition.config.md +67 -4
  234. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  235. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  236. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  237. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
  238. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  239. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
  240. package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
  241. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  242. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  243. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  244. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  245. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  246. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  247. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  248. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
  249. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  250. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  251. package/dist/knowledge/references/experience-plan.config.md +60 -7
  252. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  253. package/dist/knowledge/references/market.snapshot.validation.md +1 -1
  254. package/dist/knowledge/references/placement-plan.config.md +43 -0
  255. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  256. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  257. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  258. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  259. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  260. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  261. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  262. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  263. package/dist/knowledge/references/saas.backend.email.send.md +77 -0
  264. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  265. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
  266. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  267. package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
  268. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  269. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
  270. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
  271. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
  272. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
  273. package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
  274. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
  275. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
  276. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  277. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
  278. package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
  279. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
  280. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
  281. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
  282. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  283. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  284. package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
  285. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
  286. package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
  287. package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
  288. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  289. package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
  290. package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
  291. package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
  292. package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
  293. package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
  294. package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
  295. package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
  296. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  297. package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
  298. package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
  299. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  300. package/dist/knowledge/references/website-plan.config.md +26 -0
  301. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
  302. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
  303. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  304. package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
  305. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
  306. package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
  307. package/dist/knowledge/references/zod.factories.code.md +1 -0
  308. package/dist/knowledge/references/zod.factories.duration.md +1 -0
  309. package/dist/knowledge/references/zod.factories.money.md +1 -0
  310. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  311. package/dist/knowledge/registries/framework-topics.json +374 -1
  312. package/dist/knowledge/registries/playbooks.json +76 -28
  313. package/dist/knowledge/registries/source-tags.json +1513 -898
  314. package/dist/knowledge/rules/live-context-door.md +5 -2
  315. package/dist/knowledge/skills/INDEX.md +5 -2
  316. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  317. package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
  318. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  319. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  320. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  321. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
  322. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
  323. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  324. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
  325. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
  326. package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
  327. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
  328. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
  329. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
  330. package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
  331. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
  332. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
  333. package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
  334. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  335. package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
  336. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
  337. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
  338. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
  339. package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
  340. package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
  341. package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
  342. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  343. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
  344. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  345. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  346. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  347. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
  348. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
  349. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
  350. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
  351. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
  352. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
  353. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
  354. package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
  355. package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
  356. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
  357. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
  358. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
  359. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
  360. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  361. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  362. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  363. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  364. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  365. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
  366. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
  367. package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
  368. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
  369. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  370. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  371. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  372. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  373. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  374. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  375. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  376. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  377. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
  378. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
  379. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  380. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
  381. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  382. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
  383. package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
  384. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  385. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
  386. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
  387. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
  388. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
  389. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  390. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
  391. package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
  392. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
  393. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
  394. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
  395. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
  396. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
  397. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  398. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
  399. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
  400. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  401. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
  402. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
  403. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
  404. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
  405. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
  406. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  407. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
  408. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
  409. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
  410. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
  411. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  412. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  413. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  414. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
  415. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
  416. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
  417. package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
  418. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  419. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
  420. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  421. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
  422. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
  423. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
  424. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  425. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
  426. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  427. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
  428. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  429. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  430. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  431. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  432. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  433. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  434. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
  435. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  436. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  437. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
  438. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
  439. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
  440. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
  441. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
  442. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
  443. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
  444. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
  445. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
  446. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
  447. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
  448. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
  449. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
  450. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
  451. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
  452. package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
  453. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
  454. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
  455. package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
  456. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
  457. package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
  458. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
  459. package/dist/knowledge/skills/website-section-faq/SKILL.md +21 -1
  460. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
  461. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +21 -1
  462. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
  463. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +25 -2
  464. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
  465. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
  466. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
  467. package/dist/knowledge/skills/website-section-hero/SKILL.md +33 -10
  468. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
  469. package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
  470. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
  471. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +27 -2
  472. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
  473. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +16 -4
  474. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
  475. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
  476. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
  477. package/dist/knowledge/topic-index.json +1590 -292
  478. package/dist/tsconfig.build.tsbuildinfo +1 -1
  479. package/dist/tsconfig.tsbuildinfo +1 -1
  480. package/package.json +4 -4
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "bottom_up.build-decompose",
3
- "version": "0.4.0",
3
+ "version": "0.4.6",
4
4
  "phase": "bottom_up",
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 (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) 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. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.",
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 (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) 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 / lock or schedule runs / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -15,6 +15,44 @@
15
15
  "selector": {
16
16
  "family": "placement-plan"
17
17
  }
18
+ },
19
+ {
20
+ "kind": "artifact_expected",
21
+ "selector": {
22
+ "family": "experience-plan"
23
+ }
24
+ },
25
+ {
26
+ "kind": "artifact_expected",
27
+ "selector": {
28
+ "family": "integration-plan"
29
+ }
30
+ },
31
+ {
32
+ "kind": "artifact_expected",
33
+ "selector": {
34
+ "family": "website-plan"
35
+ },
36
+ "when": {
37
+ "selector": {
38
+ "family": "capability-composition"
39
+ },
40
+ "decision": "add-website",
41
+ "equals": "NEEDED"
42
+ }
43
+ },
44
+ {
45
+ "kind": "artifact_expected",
46
+ "selector": {
47
+ "family": "documentation-plan"
48
+ },
49
+ "when": {
50
+ "selector": {
51
+ "family": "capability-composition"
52
+ },
53
+ "decision": "add-technical-doc",
54
+ "equals": "NEEDED"
55
+ }
18
56
  }
19
57
  ],
20
58
  "inputs": [
@@ -63,12 +101,12 @@
63
101
  {
64
102
  "family": "build-plan",
65
103
  "schemaRef": "saas-specifications:BuildPlanTaskGraph",
66
- "description": "The build decomposition — an ORDERED set of coding-agent build tasks (a task graph) that turns the approved domain plan into a sequence of buildable units. Each task carries: a stable task ref, the target it builds (a module, a resource + one of its build stages, a relationship, a companion-generation step, a shell-surface placement config), WHAT IT PRODUCES (`produces` — the artifacts whose presence in the finished application proves the task landed; distinct from the target, which is a write scope several tasks may share), the ONE functional topic it belongs to (a real MetaWorkflow_FunctionalTopic value), the skill(s) that carry its technical HOW (real folders from the app-knowledge skill catalog, resolved via the skills router), and its ordering intent (which tasks must precede it — expressed as typed prerequisiteTaskRefs, which the host resolves for readiness). Author prerequisiteTaskRefs to express the actual dependencies, using these planning considerations: (a) the cross-app topic dependency edges (model_domain_graph before define_interaction_semantics before app-level shape_user_experience before extend_application before connect_runtime_and_external_capabilities; foundation and assemble/verify are owned by sibling playbooks) and (b) the per-resource stage sequence schema -> config -> ui-behavior -> spec — which deliberately CROSSES topics (ui-behavior is shape_user_experience; the spec is a model_domain_graph documentation capstone ordered last) and so is not monotonic on axis (a); a roadmap-driven MVP-first preference breaks ties within a band. TYPED since the flexible-intelligence Block 3: the `_core` build-task-graph contract (`BuildPlanTaskGraph` — `tasks[]` with a stable `taskRef`, a closed `BuildPlanTaskTargetKind` target (MODULE / RESOURCE_STAGE / RELATIONSHIP / COMPANION_GENERATION_STEP / SHELL_PLACEMENT / MODULE_FRONTEND / MODULE_BACKEND / APPLICATION_FRONTEND_CONFIG / WEBSITE / TECHNICAL_DOCUMENTATION / WORKER / MINION / PROVIDER_BINDING / BILLING_CATALOG), a `produces` list over the closed `BuildPlanTaskProductKind` vocabulary (the resource products — schema fields, registration, ui-behavior, specification, relationship, operation, composite / custom / chart view, PDF template; the application products — view, document, module, frontend configuration, custom component, milestone, guidance; and the runtime products — worker jobs, minion behaviours, provider binding, website page and section, documentation chapter, inbound channel handler; and the billing product the catalogue sells), exactly one `functionalTopic`, `skillRefs`, DECLARED `prerequisiteTaskRefs` the host resolves for readiness, and traceability `servesRefs`) is the family schema; the provider answers the strict `BuildPlanTaskGraphGeneration` shape and the trusted runtime stamps refs and version. The task never carries paths, commands, prompts or runtime controls — the dispatch host derives mutation scope and verification from the target kind. `validateBuildPlanTaskGraph` is the deterministic validator. A task's products must name something COMPOSITION DOES NOT ALREADY WRITE (the fields a schema gains, not its scaffolded file) and no two tasks may claim the same artifact — that is what makes landing decidable; a coding task declaring none is reported as `TASK_DECLARES_NO_PRODUCT`. If such a task has a COMPLETED durable run, the host advances past it but reports its ref in `unverifiableLandedTaskRefs`: it ran, but its output is not proven. Without that completed run it remains unlanded. Companion-generation tasks use their own landed conditions; migrations require the schema plan to be in sync. Product probes inspect committed files and named declarations, not runtime correctness. Two things are HARD FLOORS: a prerequisite cycle, and a resource stage that declares its predecessor stage in the SAME graph without depending on it — dispatch order comes solely from `prerequisiteTaskRefs`, so an undeclared stage edge lets the host author a resources-config for a schema that has not landed. A predecessor stage that is ABSENT from the plan is an authoring WARNING instead, because a plan may legitimately author one stage of a resource the tree already carries; the coherence reviewer checklist (`build-plan-coherent`, in the method) remains the semantic check and the creator's approve_result review the trust floor. Consumed by the bottom-up DISPATCH-ORCHESTRATION playbook (which single-flight-dispatches each task through the coding-agent contract) and the SCALE playbook (which parallelises + interleaves the companion generation steps) — both downstream of this decomposition."
104
+ "description": "The build decomposition — an ORDERED set of coding-agent build tasks (a task graph) that turns the approved domain plan into a sequence of buildable units. Each task carries: a stable task ref, the target it builds (a module, a resource + one of its build stages, a relationship, a companion-generation step, a shell-surface placement config), WHAT IT PRODUCES (`produces` — the artifacts whose presence in the finished application proves the task landed; distinct from the target, which is a write scope several tasks may share), the ONE functional topic it belongs to (a real MetaWorkflow_FunctionalTopic value), the skill(s) that carry its technical HOW (real folders from the app-knowledge skill catalog, resolved via the skills router), and its ordering intent (which tasks must precede it — expressed as typed prerequisiteTaskRefs, which the host resolves for readiness). Author prerequisiteTaskRefs to express the actual dependencies, using these planning considerations: (a) the cross-app topic dependency edges (model_domain_graph before define_interaction_semantics before app-level shape_user_experience before extend_application before connect_runtime_and_external_capabilities; foundation and assemble/verify are owned by sibling playbooks) and (b) the per-resource stage sequence schema -> config -> ui-behavior -> spec — which deliberately CROSSES topics (ui-behavior is shape_user_experience; the spec is a model_domain_graph documentation capstone ordered last) and so is not monotonic on axis (a); a roadmap-driven MVP-first preference breaks ties within a band. TYPED since the flexible-intelligence Block 3: the `_core` build-task-graph contract (`BuildPlanTaskGraph` — `tasks[]` with a stable `taskRef`, a closed `BuildPlanTaskTargetKind` target (MODULE / RESOURCE_STAGE / RELATIONSHIP / COMPANION_GENERATION_STEP / SHELL_PLACEMENT / MODULE_FRONTEND / MODULE_BACKEND / APPLICATION_FRONTEND_CONFIG / WEBSITE / TECHNICAL_DOCUMENTATION / WORKER / MINION / PROVIDER_BINDING / BILLING_CATALOG), a `produces` list over the closed `BuildPlanTaskProductKind` vocabulary (the resource products — schema fields, registration, ui-behavior, specification, relationship, operation, composite / custom / chart view, PDF template; the application products — view, document, module, frontend configuration, custom component, milestone, guidance; and the runtime products — worker jobs, minion behaviours, provider binding, website page and section, documentation chapter, inbound channel handler; and the billing product the catalogue sells), exactly one `functionalTopic`, `skillRefs`, DECLARED `prerequisiteTaskRefs` the host resolves for readiness, and traceability `servesRefs`) is the family schema; the provider answers the strict `BuildPlanTaskGraphGeneration` shape and the trusted runtime stamps refs and version. The task never carries paths, commands, prompts or runtime controls — the dispatch host derives mutation scope and verification from the target kind. `validateBuildPlanTaskGraph` is the deterministic validator. A task's products must name something COMPOSITION DOES NOT ALREADY WRITE (the fields a schema gains, not its scaffolded file) and no two tasks may claim the same artifact — that is what makes landing decidable; a coding task declaring none is reported as `TASK_DECLARES_NO_PRODUCT`. If such a task has a COMPLETED durable run, the host advances past it but reports its ref in `unverifiableLandedTaskRefs`: it ran, but its output is not proven. Without that completed run it remains unlanded. Companion-generation tasks use their own landed conditions; migrations require the schema plan to be in sync. Product probes inspect committed files and named declarations, not runtime correctness. Two things are HARD FLOORS: a prerequisite cycle, and a resource stage that declares its predecessor stage in the SAME graph without depending on it — dispatch order comes solely from `prerequisiteTaskRefs`, so an undeclared stage edge lets the host author a resources-config for a schema that has not landed. A predecessor stage that is ABSENT from the plan is an authoring WARNING instead, because a plan may legitimately author one stage of a resource the tree already carries; the coherence reviewer checklist (`build-plan-coherent`, in the method) remains the semantic check and the creator's approve_result review the trust floor. Consumed by the bottom-up DISPATCH-ORCHESTRATION playbook (which dispatches the tasks through the coding-agent contract in parallel waves, up to the application's build parallelism at once) and the SCALE playbook (which describes how those waves are scheduled, interleaved with the companion generation steps, and reconciled) — both downstream of this decomposition."
67
105
  }
68
106
  ],
69
107
  "stepOutputs": [],
70
108
  "method": {
71
- "guidance": "# Build Decompose — Domain Plan → Ordered Coding-Agent Task Graph \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\nThe output follows the existing `BuildPlanTaskGraph` contract. The host checks its\nshape and graph consistency, then uses `prerequisiteTaskRefs` to determine readiness.\nFunctional topics organize context; they do not create scheduling edges. Decompose\nthe work using the current contracts rather than designing a replacement planner.\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, **what each one\nproduces**, their topic, their skill(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 from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the 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`, and the **business model** for its pricing plans (the billing catalogue, Step 3);\nyou **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## Every task declares WHAT IT PRODUCES\n\nEach task carries `produces`: the artifacts the finished application will contain\n*because this task ran*. It is how the host answers **\"has this task landed?\"**, and\nit is not optional thinking: without declared products the host cannot probe the\nintended result. A COMPLETED durable run lets the loop advance, but the task remains\nexplicitly marked in `unverifiableLandedTaskRefs` as ran, not proven.\n\n**`target` and `produces` answer different questions, and a task needs both.**\n`target` is the WRITE SCOPE — which module tree this run may edit. Several tasks\nlegitimately share one. `produces` is the PRODUCT IDENTITY — what this task, and no\nother, is accountable for. Wonder CRM's plan proved they cannot be the same field:\nits pipeline-view task and its follow-through-operation task carry byte-identical\ntargets, so nothing derived from `target` could ever tell them apart, and 40 of its\n42 tasks were reported finished while none had run.\n\n**The one rule that makes a product real: name something the SCAFFOLD does not\nalready contain.** Every module, every resource file and every resource\nspecification is written by composition before any task exists. So \"the resource\nconfig file\" is not a product — it was there on day one. The VERBS it gains are.\nApply that test to every product you write.\n\n| product | you name | use it for |\n|---|---|---|\n| `RESOURCE_SCHEMA_FIELDS` | `resourceRef` + the `fieldRefs` the task adds | a schema stage. The FIELDS, never the file — the file is scaffolded. A `fieldRef` is the field's own IDENTIFIER as it will stand in the schema (`slug`, `archivedAt`, `completedAt`), never a description of what the fields express |\n| `RESOURCE_REGISTRATION` | `resourceRef` + the `operationRefs` it gains | a config stage |\n| `RESOURCE_UI_BEHAVIOR` | `resourceRef` | a ui-behavior stage — the one artifact composition never writes |\n| `RESOURCE_SPECIFICATION` | `resourceRef` + the `fieldRefs` it documents | a spec stage. The fields again: the spec file is scaffolded too |\n\n**A product ref is an ARTIFACT IDENTITY, not a concept.** Every `produces` entry is read back by a\nLANDING PROBE that searches the application's own source for that ref — in its plain, camelCase,\nPascalCase and SCREAMING_SNAKE spellings — and a task lands only when the probe finds it. So a ref\nnaming something that will never appear in the tree makes the task permanently unlandable, however\ncorrectly it is built.\n\nMeasured on the first end-to-end journey run (#1273): all sixteen schema tasks declared refs like\n`private-workspace-shape`, `membership-access-shape` and `one-sentence-rationale-shape` — eighteen\nrefs, not one of them a field. The schemas were authored correctly and committed; every task stayed\nunlanded, the loop guard then refused the whole band at task one, and the board read 9 of 94 while\nthe work was being done.\n\nName what a reader will find in the file. `slug`, `description`, `archivedAt` — not the idea they\nserve together. If you cannot name the fields yet, the task is not decomposed far enough to declare a\nproduct, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a placeholder concept.\n| `RESOURCE_RELATIONSHIP` | `relationshipRef` + `sourceResourceRef` + `targetResourceRef` | a relationship-wiring task. Both endpoints, because the scaffold already declares each resource's own edges |\n| `RESOURCE_OPERATION` | `resourceRef` + `operationRef` | a custom operation |\n| `APPLICATION_VIEW` | `viewRef` | an app-level view. With an experience plan, the `viewRef` is the plan's own (`view-…`), verbatim |\n| `APPLICATION_DOCUMENT` | `documentRef` | a governed document the engine catalog DEFINES — see the closed list below. Never a document you name yourself |\n| `APPLICATION_MODULE` | `moduleRef` | an ensure-module task. The REGISTRY entry, not the directory |\n| `APPLICATION_FRONTEND_CONFIG` | `configSurface` + the `declarationRefs` the file gains | composing ONE app-wide config file — `NAVIGATION`, `DESIGN_SYSTEM`, `APP_SHELL`, `GLOBAL_VIEWS`. The DECLARATIONS (a sidebar section ref, a zone, a token), never the file: `wildo init` writes all four |\n| `RESOURCE_COMPOSITE_VIEW` | `resourceRef` + `viewRef` | a composite view of one resource, bound in its ui-behavior's `compositeViews`. The plan's `viewRef`, verbatim |\n| `RESOURCE_CUSTOM_VIEW` | `resourceRef` + `viewRef` | a custom operation view or an execution view of one resource, bound in its ui-behavior. The plan's `viewRef`, verbatim — it is how the dispatch tells an execution view from a custom one |\n| `RESOURCE_CHART_VIEW` | `resourceRef` + `chartRef` | a chart view declared under the resource's `chartViews` |\n| `CUSTOM_COMPONENT` | `componentRef` | a custom frontend component, registered on the module's frontend index or in the engine registrations |\n| `APPLICATION_MILESTONE` | `milestoneRef` | a milestone the module declares — the experience plan's identifier, as a slug |\n| `APPLICATION_GUIDANCE` | `guidanceKind` + `guidanceRef` | an onboarding document or guidance flow the module declares — the experience plan's `kind` and ref |\n| `PDF_TEMPLATE` | `resourceRef` + `templateRef` | a PDF template BOUND to a resource's generated-file field (`generatedSummaryPdf`) |\n| `APPLICATION_WORKER` | `workerRef` + the `jobRefs` its entry file declares | a worker's behaviour. The JOBS, not the package: `add-worker-node` / `add-worker-rust` write the package |\n| `APPLICATION_MINION` | `minionRef` + the `behaviorRefs` its entry file declares | a minion's tick behaviour. Same rule: `add-minion` writes the package |\n| `PROVIDER_BINDING` | `providerRef` + `scope` (`BACKEND`, `COMPANION`, `FRONTEND_APP`, `WEBSITE`) | one provider declared in one runtime owner's scope — the SaaS config block, or the service's `provider-contributions.ts` |\n| `WEBSITE_PAGE` | `pageRef` | a marketing page, registered in `website-root.config.ts` by its manifest |\n| `WEBSITE_SECTION` | `pageRef` + `sectionRef` | one section of one page, declared in `<pageRef>.sections.tsx` |\n| `DOCUMENTATION_CHAPTER` | `chapterRef` | the chapter's authored body, keyed by its `chapterRef` in `specifications/src/technical-documentation/index.ts`, which `wildo docs publish` joins to the documentation plan and publishes under `/guides/<slug>` |\n| `APPLICATION_BILLING_PRODUCT` | `productKey` | one product of the application's billing catalogue, named by its catalogue `key` (a slug, e.g. `team`) — declared in `shared-lib/src/engine/product.ts` under the `BILLING_CATALOG` target. The KEY, never the file: `wildo init` writes the file with an empty catalogue |\n| `INBOUND_CHANNEL_HANDLER` | `channel` + the handler's `handlerRef` (`<moduleRef>.<purpose>`, e.g. `matters.mail-intake`) | the handler that decides what a message arriving on a channel the integration plan declared causes. Its file is `backend-api/src/modules/<moduleRef>/inbound/<handlerRef>.inbound-channel-handler.ts`, and it lands when the module's backend `index.ts` imports that file — which is how it is registered on `inboundHandlers` |\n\n**A GOVERNED DOCUMENT is chosen from a closed list, never invented.** There are six,\nand a `documentRef` names one of them in exactly this form:\n\n```\ndocument:public.privacy-notice document:governance.program-handbook\ndocument:public.service-terms document:governance.scope-system-description\n document:governance.roles-responsibilities\n document:governance.document-record-control\n```\n\nA document is drafted against a BLUEPRINT — the required sections, the required\nfacts, the claim guards — and the blueprint is what the catalog holds. A ref outside\nthis list resolves to no blueprint, so the only thing a coding agent could do is\nINVENT the document's structure, which its authoring skill forbids. The task is then\nunbuildable by any run, and the dispatcher skips it by name rather than spending an\nagent turn rediscovering that.\n\nThis is not a hypothetical constraint. A plan authored against the previous wording\nof the row above — \"a notice, a governance statement\" — declared\n`gdpr-data-handling-governance` and `terminal-access-governance`: two plausible\ngovernance statements, neither of which names anything. Both sat permanently ready,\nand the one that was dispatched spent a full turn establishing that the document does\nnot exist. **If the obligation you have in mind is not on this list, it belongs in a\ndocument that IS** — GDPR data-handling scope, retention and subject rights are\n`document:public.privacy-notice`'s subject matter — or it is not a build task at all.\n\n**A cross-resource FOREIGN KEY belongs to the RELATIONSHIP task, never to the schema\ntask of the resource that holds it.** The domain plan makes the FK derivable — an\n`ownershipIntent` of SOURCE_HOLDS_REFERENCE on `contact-company` says contact carries\n`companyId` — and that is exactly why the mistake is easy: the field is derivable, so\nit is tempting to declare it on the schema task that will contain it. Step 2 below\nmakes the relationship task the SINGLE home for cross-resource wiring, and the\n`module-relationships` skill coordinates that FK across the owner's schema and config.\nDeclaring it in both places attributes one artifact to two tasks — the ambiguity\n`produces` exists to remove, reintroduced through the field that removes it. A schema\ntask's products are the resource's OWN domain fields.\n\nTwo further rules the graph enforces, so authoring against them saves a rejection:\n\n- **No two tasks may claim the same artifact.** That is what makes landing decidable.\n Two tasks may both enrich one resource's schema — it is the FIELDS that must not\n overlap, so split by field, never by prose.\n- **A `COMPANION_GENERATION_STEP` declares NO products.** Its landing is the\n generation step's own condition, computed by the companion. A product declared\n beside one is refused.\n\nProducts stay SEMANTIC. You name a resource, a field, a relationship, a view — never\na path and never a command, exactly as with `target`. The host alone turns a product\ninto a question about the working tree.\n\nThe contract itself, so the vocabulary below is read from the source rather than\nfrom this prose:\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, email templates, logo or database migrations) 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 * THE NON-RESOURCE SURFACES (#1490). Until 2026-09-22 the five kinds above were the whole\n * vocabulary, and every one of them is about a resource or the shell placement of one. The\n * decompose method meanwhile told the planner to emit tasks for views, navigation, the design\n * system, custom components, PDF templates, workers, minions, providers, the website and the\n * documentation — surfaces the framework's own composition scenarios and 85 of its 111 skills\n * already build. A task for any of them had no kind to declare, so it either declared none\n * (landing as RAN-not-PROVEN forever) or borrowed `MODULE` with a product the module scope could\n * not prove. The members below are those surfaces, one per write scope the host can derive.\n */\n /**\n * The FRONTEND and SPECIFICATION layers of one module — its composite, custom and chart views,\n * its custom components and their specifications.\n *\n * Narrower than `MODULE` on purpose: a view task never touches `shared-lib` or `backend-api`, so\n * handing it the four-layer scope also hands it four typechecks and the FK sweep for a change\n * that can only break the frontend and the specifications package.\n */\n MODULE_FRONTEND = 'MODULE_FRONTEND',\n /**\n * The BACKEND layer of one module beside its shared-lib declarations — PDF templates and their\n * bindings, backend addons (services, controllers, flows-actors), email definitions.\n *\n * Shared-lib is in scope because a PDF template is bound to a resource FIELD the config declares\n * (`generatedSummaryPdf`), and a backend addon usually declares its contract there first.\n */\n MODULE_BACKEND = 'MODULE_BACKEND',\n /**\n * ONE application-wide frontend configuration surface — navigation, the design system, the app\n * shell's composition, the global views — named by {@link FrontendConfigSurface}.\n *\n * Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the\n * shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES\n * the surface itself (which sidebar sections exist, which transitions the primary zone uses,\n * which palette the product carries). Same file for `APP_SHELL`, different question.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /** The marketing website workspace (`website/`), composed by the `add-website` scenario. Pages and sections are its products. */\n WEBSITE = 'WEBSITE',\n /**\n * The technical-documentation workspace (`technical-doc/`) and the specification package's\n * `technical-documentation/` declarations that feed it. Its generated tree is never written by a\n * task: the companion publishes into it, and the coding policy prohibits it by prefix.\n */\n TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',\n /** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */\n WORKER = 'WORKER',\n /** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */\n MINION = 'MINION',\n /**\n * Declaring one provider in the application — the SaaS config's provider scopes, the backend\n * package dependency, the frontend provider module and its companion contribution.\n *\n * Application-wide by construction: a provider binding names no module, and the four files it\n * may touch are the same for every provider.\n */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /**\n * The application's BILLING CATALOGUE — the `ProductDefinition[]` in `shared-lib/src/engine/product.ts`\n * (and the product specifications that document it), which the backend syncs to the billing\n * provider and the public website reads for its pricing page (#1835).\n *\n * Its own kind because none of the others is true of it: the catalogue is application-wide (a plan\n * belongs to no module), it lives in the shared library's ENGINE module that no `MODULE_*` scope\n * reaches, and before it existed a journey-built application reached its website with an EMPTY\n * catalogue, so the website re-typed the business model's prices by hand.\n */\n BILLING_CATALOG = 'BILLING_CATALOG',\n}\n\n/**\n * WHICH application-wide frontend configuration surface a task composes — one file each, in\n * `frontend/src/config/`, and the coding policy resolves the member to that file exactly as\n * `SHELL_PLACEMENT` resolves a `PlacementSurface`.\n *\n * Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a\n * subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of\n * those live in one file. A configuration surface is WHICH FILE a composition task authors, and\n * navigation and the design system are not places anything is placed.\n */\nexport enum FrontendConfigSurface {\n /** `frontend/src/config/navigation.config.ts` — zones, transitions, overlay appearance. */\n NAVIGATION = 'NAVIGATION',\n /** `frontend/src/config/design-system.config.ts` — palette, typography, shell appearance from the brand's visual tone. */\n DESIGN_SYSTEM = 'DESIGN_SYSTEM',\n /** `frontend/src/config/app-shell.config.ts` — top bar, sidebar sections, quick switcher: the shell's COMPOSITION, not a placement into it. */\n APP_SHELL = 'APP_SHELL',\n /** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */\n GLOBAL_VIEWS = 'GLOBAL_VIEWS',\n}\n\n/**\n * The two shapes of guidance an application gives a person, and the file each is declared in.\n *\n * They are distinct because they are found differently: an onboarding DOCUMENT is embedded in a\n * screen (`EmbedOnboarding`) and is there whenever that screen is, while a guidance FLOW is started\n * by an event and shows once. Both are listed on the owning frontend module — `onboardingViews` and\n * `guidanceFlows`. Each kind has a CONVENTIONAL definitions file, which the authoring skill teaches\n * and a landing probe reads for the declared ref (alongside the module's `index.ts`, where a small\n * module may declare inline). A convention for generated applications: a hand-authored application\n * may keep its declarations elsewhere, and then simply is not probed by a build plan.\n */\nexport enum ApplicationGuidanceKind {\n /** `frontend/src/modules/<m>/app-level-views/onboarding-views.definitions.ts` — an embedded onboarding document. */\n ONBOARDING_DOCUMENT = 'ONBOARDING_DOCUMENT',\n /** `frontend/src/modules/<m>/app-level-views/guidance-flows.definitions.ts` — a triggered guidance flow. */\n GUIDANCE_FLOW = 'GUIDANCE_FLOW',\n}\n\n/**\n * The two worker runtimes the framework composes (`add-worker-node`, `add-worker-rust`). The\n * runtime decides the entry file a landing probe reads and whether a typecheck exists to run: a\n * Node worker is verified by its package typecheck, a Rust worker has no TypeScript to check and\n * the policy says so rather than inventing a command.\n *\n * Not the SaaS config's `WorkerRuntime`, which is a free-form `{ type, language }` pair an\n * application authors for deployment; this is the closed set a creation run can COMPOSE.\n */\nexport enum BuildPlanWorkerRuntime {\n NODE = 'NODE',\n RUST = 'RUST',\n}\n\n/**\n * WHERE a provider is bound — which runtime owner's scope its declaration lands in. Each member\n * is a different file, so a probe and a write grant both derive from it.\n *\n * Named after the SaaS config's own scope keys (`providers.scopes.backend`, `.companion`,\n * `.frontendServices.app`, `.frontendServices.website`), which the `add-provider` and\n * `add-file-picker-provider` scenarios write. Minion and worker scopes are deliberately absent:\n * a provider reaching a minion is declared on that minion's own `providers` block and belongs to\n * the {@link BuildPlanTaskTargetKind.MINION} task that builds it.\n */\nexport enum ProviderBindingScope {\n BACKEND = 'BACKEND',\n COMPANION = 'COMPANION',\n FRONTEND_APP = 'FRONTEND_APP',\n WEBSITE = 'WEBSITE',\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/**\n * The key of the domain-plan MODULE a task targets or produces (`deals`, `tasks-manager`). Same\n * slug grammar as the other keys, declared as its own schema because it names one thing — a\n * module — where the other slugs name resources, relationships, steps, workers and products.\n */\nconst ModuleRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n\n/**\n * The governed document a task produces, named as a COMPLIANCE-DOCUMENT CANDIDATE names it:\n * `document:<namespace>.<id>`, e.g. `document:public.privacy-notice`.\n *\n * **This field was `SlugSchema`, and a slug cannot name a governed document — so until 2026-09-16 no\n * build plan in any application could declare a document the engine catalog defines.** A slug forbids\n * the colon and the dot, the catalog's definitions are `document-definition:public.privacy-notice`,\n * and `selectAssuranceDocumentBlueprintForDocumentRef` joins the two namespaces by exact suffix — so\n * every authored `documentRef` resolved to NO blueprint, and a blueprint is what says which sections,\n * facts and claim guards the document owes. The two vocabularies were disjoint by construction.\n *\n * The cost is measured rather than theoretical. Wonder CRM's plan declares two such products\n * (`gdpr-data-handling-governance`, `terminal-access-governance`), neither of which names anything;\n * the first was dispatched, and its agent spent a full turn establishing — with a positive control —\n * that the document does not exist and could only be invented, which the authoring skill forbids.\n *\n * The bare slug is STILL ACCEPTED, and that is deliberate rather than tidiness left undone: tightening\n * this to the namespaced form alone would make every already-accepted plan carrying one fail to parse,\n * and a build plan that cannot be READ stops the whole lane — the gate\n * `application-creation-directive.md` forbids, for a task nobody can fix by re-running anything. A slug\n * simply resolves to no blueprint, so the dispatcher skips that task with a message naming the ref,\n * and the rest of the plan proceeds.\n */\nconst DocumentProductRefSchema = z.union([\n z.string().regex(/^document:[a-z0-9]+(?:-[a-z0-9]+)*\\.[a-z0-9]+(?:-[a-z0-9]+)*$/),\n SlugSchema,\n]);\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\n/**\n * WHAT a build task PRODUCES — the artifact whose presence in the application\n * proves the task is done.\n *\n * **This is not `target`, and the difference is the whole reason it exists.**\n * `target` is a WRITE SCOPE: the host turns it into the path prefixes a run may\n * mutate, and several tasks legitimately share one. `produces` is a PRODUCT\n * IDENTITY: it says which artifact this task, and no other, is accountable for.\n *\n * Measured 2026-09-10 on Wonder CRM (issue #597): `build-task-pipeline-view`\n * and `build-task-deal-follow-through-operation` carry BYTE-IDENTICAL targets\n * (`{ kind: MODULE, moduleRef: 'deals' }`), and 7 of that plan's 42 tasks share\n * 3 targets. Landing had been answered by narrowing the target to a module\n * DIRECTORY — which `wildo compose` commits on day one, and which cannot tell\n * two tasks apart even in principle. The loop reported 40 of 42 tasks landed\n * while no coding task had ever run, so `dispatch-next` skipped every one of\n * them and the phase-advance gate read a build that was all but complete.\n *\n * Like `target`, this stays SEMANTIC: a product names a resource, a field, a\n * relationship or a view — never a path, and never a command. The host owns the\n * translation from a product to the physical question it asks of the working\n * tree, exactly as it owns the translation from a target kind to path prefixes.\n * A model that could author the path could author its own mutation scope.\n */\nexport enum BuildPlanTaskProductKind {\n /**\n * Named fields on one resource's schema.\n *\n * The shape an ENRICHMENT task needs, and the reason a product cannot always\n * be \"a file\": every resource file already exists, written by the scaffold\n * with its self-described STARTER shape, so file presence answers nothing.\n * The FIELDS are what the task adds.\n */\n RESOURCE_SCHEMA_FIELDS = 'RESOURCE_SCHEMA_FIELDS',\n /**\n * One resource's declared operations — its registry presence, named by the verbs it gains.\n *\n * The VERBS, not the config file: `<r>.resources-config.ts` is written by the scaffold, so its\n * existence is satisfied before any task runs. That is the exact shape of the defect this\n * vocabulary replaces, and a kind that reproduced it would be worse than no kind at all.\n */\n RESOURCE_REGISTRATION = 'RESOURCE_REGISTRATION',\n /** One resource's frontend ui-behavior. */\n RESOURCE_UI_BEHAVIOR = 'RESOURCE_UI_BEHAVIOR',\n /**\n * One resource's specification, named by the fields it documents.\n *\n * The FIELDS, for the same reason as {@link RESOURCE_REGISTRATION}: every resource is scaffolded\n * with a `*.resource.specification.ts` documenting only the starter shape, so file existence\n * proves nothing about the task that was meant to enrich it.\n */\n RESOURCE_SPECIFICATION = 'RESOURCE_SPECIFICATION',\n /** One relationship edge between two resources, named by the domain plan's `relationshipRef`. */\n RESOURCE_RELATIONSHIP = 'RESOURCE_RELATIONSHIP',\n /** One named custom operation on one resource. */\n RESOURCE_OPERATION = 'RESOURCE_OPERATION',\n /** One named application-level view. */\n APPLICATION_VIEW = 'APPLICATION_VIEW',\n /** One named governed application document (a compliance notice, a governance statement). */\n APPLICATION_DOCUMENT = 'APPLICATION_DOCUMENT',\n /** One application module, registered across the layer registries under one module identity. */\n APPLICATION_MODULE = 'APPLICATION_MODULE',\n /*\n * THE NON-RESOURCE PRODUCTS (#1490). Each names an artifact of a surface the five target kinds\n * above `MODULE_FRONTEND` could not express, and each is probed by the host from committed bytes —\n * a declaration in the one file that registers it, never a directory a scenario already wrote.\n */\n /**\n * Named declarations in ONE application-wide frontend configuration file — a sidebar section\n * ref the app shell gains, a zone the navigation config declares, a token the design system sets.\n *\n * The DECLARATIONS, never the file: every `frontend/src/config/*.config.ts` is written by\n * `wildo init`, so its presence is true before any task runs. Same reasoning as\n * {@link RESOURCE_SCHEMA_FIELDS}, one level up.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /**\n * One composite view of one resource — the cross-resource surface a resource's ui-behavior\n * declares under `compositeViews`. Distinct from {@link APPLICATION_VIEW}, which is\n * application-level and owned by a module rather than a resource.\n */\n RESOURCE_COMPOSITE_VIEW = 'RESOURCE_COMPOSITE_VIEW',\n /** One custom operation or execution view of one resource, bound in its ui-behavior. */\n RESOURCE_CUSTOM_VIEW = 'RESOURCE_CUSTOM_VIEW',\n /** One chart view of one resource, declared under its ui-behavior's `chartViews`. */\n RESOURCE_CHART_VIEW = 'RESOURCE_CHART_VIEW',\n /** One custom frontend component, registered by `componentRef` in the module's or the engine's registrations. */\n CUSTOM_COMPONENT = 'CUSTOM_COMPONENT',\n /**\n * One milestone a module declares — the moment the application recognises and celebrates.\n *\n * Named by its identifier, which is what the module's `milestones.ts` declares\n * (`first-project-created` is spelled `FIRST_PROJECT_CREATED` there). The module FILE is not the\n * product: a module may carry milestones before this task runs, and only the identifier says this\n * one landed.\n */\n APPLICATION_MILESTONE = 'APPLICATION_MILESTONE',\n /** One onboarding document or guidance flow a module declares, named by its ref. */\n APPLICATION_GUIDANCE = 'APPLICATION_GUIDANCE',\n /** One PDF template bound to one resource's generated-file field. */\n PDF_TEMPLATE = 'PDF_TEMPLATE',\n /**\n * One worker's JOBS — the named handlers its entry file declares.\n *\n * The jobs, not the package: `add-worker-node` writes the package, so its directory proves\n * nothing. What a coding task adds is behaviour, and behaviour is a symbol in the entry file.\n */\n APPLICATION_WORKER = 'APPLICATION_WORKER',\n /** One minion's BEHAVIOURS — the named tick handlers its entry file declares. Same reasoning as the worker. */\n APPLICATION_MINION = 'APPLICATION_MINION',\n /** One provider declared in one runtime owner's scope. */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /**\n * One product of the application's billing catalogue — a plan, add-on or purchase the application\n * sells — named by its catalogue `key`, which the catalogue file declares (`key: 'team'`).\n *\n * The KEY, not the file: `wildo init` writes `product.ts` with an empty catalogue, so the file proves\n * nothing. Written from the accepted business model's pricing plans, with the plan's price as typed\n * money and the pricing-surface facts (recommended, price disclosure, availability) the plan implies.\n */\n APPLICATION_BILLING_PRODUCT = 'APPLICATION_BILLING_PRODUCT',\n /** One website page, registered in the website root config by its manifest. */\n WEBSITE_PAGE = 'WEBSITE_PAGE',\n /** One section of one website page, declared in that page's sections file. */\n WEBSITE_SECTION = 'WEBSITE_SECTION',\n /**\n * One authored documentation chapter — a consumer guide the specifications package declares\n * for the documentation portal to publish (#874's publication input).\n */\n DOCUMENTATION_CHAPTER = 'DOCUMENTATION_CHAPTER',\n /**\n * One inbound CHANNEL handler — the code that decides what a message arriving on a channel causes\n * (#1832). Named by the handler's `ref` (`matters.mail-intake`), which the handler file spells and whose\n * file NAME is derived from it, so the module index's import of that file is what proves the handler is\n * registered. Produced once per channel the integration plan declares (`inboundChannels`).\n */\n INBOUND_CHANNEL_HANDLER = 'INBOUND_CHANNEL_HANDLER',\n}\n\n/**\n * One artifact a task is accountable for. Closed by construction: a product the\n * host cannot ask a question about is a product that can never be shown to have\n * landed, so the vocabulary only grows alongside the resolver that answers it.\n */\nexport const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /**\n * At least one field, because a task that enriches a schema with nothing is\n * the vacuity this whole field exists to stop: it would land the moment the\n * scaffold existed, which is the defect being fixed.\n */\n fieldRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_REGISTRATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SPECIFICATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, fieldRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP).systemEnum('BuildPlanTaskProductKind'),\n relationshipRef: SlugSchema,\n /*\n * The two resources the edge relates, NAMED rather than parsed out of the ref.\n *\n * A ref is `<source>-<target>` by convention and that convention is not invertible:\n * `next-step-deal` splits as (`next`, `step-deal`) or (`next-step`, `deal`) and only the domain\n * plan knows which. The domain plan already carries both, so the plan passes them on instead of\n * making the host guess — a host that guesses wrong probes for a resource that does not exist\n * and reports the task permanently unlanded.\n */\n sourceResourceRef: SlugSchema,\n targetResourceRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_OPERATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_VIEW).systemEnum('BuildPlanTaskProductKind'), viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DOCUMENT).systemEnum('BuildPlanTaskProductKind'), documentRef: DocumentProductRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MODULE).systemEnum('BuildPlanTaskProductKind'), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG).systemEnum('BuildPlanTaskProductKind'),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n /** At least one, for the same vacuity reason as a schema's `fieldRefs`: the file exists on day one. */\n declarationRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CHART_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, chartRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.CUSTOM_COMPONENT).systemEnum('BuildPlanTaskProductKind'), componentRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MILESTONE).systemEnum('BuildPlanTaskProductKind'), milestoneRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_GUIDANCE).systemEnum('BuildPlanTaskProductKind'),\n /** Which definitions file carries it — a document and a flow live in different ones. */\n guidanceKind: z.enum(ApplicationGuidanceKind).systemEnum('ApplicationGuidanceKind'),\n guidanceRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PDF_TEMPLATE).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */\n templateRef: NonEmptyStringSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),\n providerRef: SlugSchema,\n scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER).systemEnum('BuildPlanTaskProductKind'),\n /** The channel the handler serves — one the integration plan declared. Email is the only declarable channel. */\n channel: z.literal(InboundChannelKind.EMAIL).systemEnum('InboundChannelKind'),\n /** The handler's `ref`, exactly as `inboundHandlerRef()` will accept it. */\n handlerRef: z.string().regex(INBOUND_HANDLER_REF_PATTERN),\n }),\n]);\nexport type BuildPlanTaskProduct = z.infer<typeof BuildPlanTaskProductSchema>;\n\n/**\n * Every artifact identity a product claims — one string per artifact, not one\n * per product, because a product may claim several.\n *\n * `RESOURCE_SCHEMA_FIELDS` is why this returns a list. Two tasks may both enrich\n * one resource's schema (a domain shape and a billing concern, say), and that is\n * legitimate; what must never overlap is the FIELDS. Comparing whole products\n * would refuse the legitimate pair, and comparing only the resource would let two\n * tasks claim one field and make landing ambiguous again.\n *\n * Derived from the product's own members rather than stored, and total over the\n * vocabulary, so a kind added tomorrow must state its identity here or fail to\n * compile — it cannot be silently treated as equal to its siblings.\n */\nexport function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): readonly string[] {\n switch (product.kind) {\n case BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_REGISTRATION:\n return product.operationRefs.map((operationRef) => `${product.kind}:${product.resourceRef}:${operationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_SPECIFICATION:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR:\n return [`${product.kind}:${product.resourceRef}`];\n case BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP:\n return [`${product.kind}:${product.relationshipRef}`];\n case BuildPlanTaskProductKind.RESOURCE_OPERATION:\n return [`${product.kind}:${product.resourceRef}:${product.operationRef}`];\n case BuildPlanTaskProductKind.APPLICATION_VIEW:\n return [`${product.kind}:${product.viewRef}`];\n case BuildPlanTaskProductKind.APPLICATION_DOCUMENT:\n /*\n * The ref AS AUTHORED, so a slug and a namespaced ref are different artifact identities even\n * where they mean the same document — the duplicate-artifact refusal cannot see two tasks\n * claiming one document if they spell it differently. Not normalisable: a slug carries no\n * namespace, so nothing can recover `public.` from `privacy-notice`. It costs nothing today\n * because a slug names no catalogued document at all, and the dispatcher skips such a task.\n */\n return [`${product.kind}:${product.documentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MODULE:\n return [`${product.kind}:${product.moduleRef}`];\n // One identity per DECLARATION, like schema fields: two tasks may compose one config file as\n // long as they declare different things in it.\n case BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG:\n return product.declarationRefs.map((declarationRef) => `${product.kind}:${product.configSurface}:${declarationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW:\n case BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.viewRef}`];\n case BuildPlanTaskProductKind.RESOURCE_CHART_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.chartRef}`];\n case BuildPlanTaskProductKind.CUSTOM_COMPONENT:\n return [`${product.kind}:${product.componentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MILESTONE:\n return [`${product.kind}:${product.milestoneRef}`];\n // The ref alone: a document and a flow sharing one ref is still one guidance identity, and the\n // runtime keys a person's saved state by it — two artifacts claiming it would collide there too.\n case BuildPlanTaskProductKind.APPLICATION_GUIDANCE:\n return [`${product.kind}:${product.guidanceRef}`];\n case BuildPlanTaskProductKind.PDF_TEMPLATE:\n return [`${product.kind}:${product.resourceRef}:${product.templateRef}`];\n case BuildPlanTaskProductKind.APPLICATION_WORKER:\n return product.jobRefs.map((jobRef) => `${product.kind}:${product.workerRef}:${jobRef}`);\n case BuildPlanTaskProductKind.APPLICATION_MINION:\n return product.behaviorRefs.map((behaviorRef) => `${product.kind}:${product.minionRef}:${behaviorRef}`);\n // The SCOPE is part of the identity: one provider bound on the backend and on the website is two artifacts.\n case BuildPlanTaskProductKind.PROVIDER_BINDING:\n return [`${product.kind}:${product.scope}:${product.providerRef}`];\n case BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT:\n return [`${product.kind}:${product.productKey}`];\n case BuildPlanTaskProductKind.WEBSITE_PAGE:\n return [`${product.kind}:${product.pageRef}`];\n case BuildPlanTaskProductKind.WEBSITE_SECTION:\n return [`${product.kind}:${product.pageRef}:${product.sectionRef}`];\n case BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER:\n return [`${product.kind}:${product.chapterRef}`];\n case BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER:\n return [`${product.kind}:${product.handlerRef}`];\n default: {\n const unhandled: never = product;\n throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);\n }\n }\n}\n\n/**\n * The skill every billing-catalogue task is authored with (#1835): the product-catalogue contract, the\n * money encoding (minor units), and the pricing-surface facts. The dispatch derives it from an\n * `APPLICATION_BILLING_PRODUCT` product whatever the decomposer wrote, so an agent writing the catalogue\n * the backend sells from is never without it.\n */\nexport const BILLING_CATALOG_SKILL_REF = 'configure-billing';\n\nexport const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),\n moduleRef: ModuleRefSchema,\n resourceRef: SlugSchema,\n stage: z.enum(BuildPlanResourceStage),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),\n moduleRef: ModuleRefSchema,\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. i18n-labels, email-templates); 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).systemEnum('PlacementSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_FRONTEND), moduleRef: ModuleRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_BACKEND), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_FRONTEND_CONFIG),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.WEBSITE) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.WORKER),\n /** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */\n workerRef: SlugSchema,\n runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.MINION),\n /** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */\n minionRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),\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 /**\n * One sentence of intent: what this task delivers.\n *\n * Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also\n * hold. A display decorator mutates the instance it is applied to, and the workbench gives those\n * refs a receding identifier look, which the objective sentence then took too.\n */\n objective: z.string().trim().min(1),\n target: BuildPlanTaskTargetSchema,\n /**\n * The artifacts this task is accountable for — what proves it done.\n *\n * Coding tasks should declare at least one product that composition did not already\n * write. A target is a shared mutation scope; its scaffolded file is not evidence\n * that this task's intended work exists. Products identify the output to probe.\n *\n * Empty declarations remain representable and produce the advisory\n * `TASK_DECLARES_NO_PRODUCT`. The host may advance after a COMPLETED durable run,\n * while naming the task in `unverifiableLandedTaskRefs`: it ran, but its output\n * cannot be proven from a product declaration. An unexecuted task is not landed.\n * This distinction avoids repeatedly dispatching the same unprovable task without\n * presenting execution history as evidence that the intended product is correct.\n *\n * The ONE hard exception is a `COMPANION_GENERATION_STEP`, which must declare NONE.\n * That kind already carries its own typed landed condition, owned by the\n * generation-step service — a set computed asynchronously (planner units x\n * enabled locales), and for the migration step a STATE rather than files. A\n * product declared beside it would be read by nothing, which is the inert\n * declaration this field exists to avoid. Enforced on the graph below, in both\n * directions.\n */\n produces: z.array(BuildPlanTaskProductSchema).default([]),\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).systemEnum('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 /**\n * What this task is accountable to — traceability only, NEVER scope authority.\n *\n * The vocabulary is the five aspects `BUILD_PLAN_FAMILY_ASPECTS` declares as targets: functional\n * and non-functional requirements, roadmap phases, and the vision's success criteria and\n * constraints. It reads \"Requirement / roadmap refs\" until 2026-09-11, and the last two were added\n * because the producer had been writing them all along (#629) — the generation contract asks for a\n * plain string list, so nothing here has ever refused a key.\n *\n * A key outside those five is not rejected and must not be: this is traceability a human or a\n * model wrote down, and dropping it loses the intent. The workbench renders such a key as visibly\n * unresolved instead, which is what makes a producer drift legible rather than silent.\n */\n servesRefs: z.array(NonEmptyStringSchema).default([]),\n /**\n * Who asked for this task DIRECTLY (#1608), rather than it being derived from the specifications: the\n * signed-in person who added it in conversation. STAMPED by the append, never authored: a value in\n * generated output is discarded. Absent on every task the decomposition derived.\n *\n * It is what keeps a requested task alive. Build decomposition refines the plan from the domain plan, and\n * a task nothing in the specifications justifies would read as unjustified and be dropped; a requested\n * task it leaves out is carried forward instead, keeping only the prerequisites the new plan still holds.\n */\n requestedBy: NonEmptyStringSchema.optional(),\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 /*\n * No two tasks claim the same artifact.\n *\n * This is what makes landing DECIDABLE, not a tidiness rule. If two tasks name\n * one product, the host cannot tell which of them a present artifact proves —\n * exactly the ambiguity that shared `target`s created, arriving through the\n * field that replaced them. Enforced here rather than left to the validator\n * because a graph that cannot answer \"has this task landed?\" is not a graph\n * the loop may run at all.\n */\n graph.tasks.forEach((task, index) => {\n const isGenerationStep = task.target.kind === BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP;\n if (isGenerationStep && task.produces.length > 0) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" is a companion generation step and must declare no products; its landing is the generation step's own condition`,\n path: ['tasks', index, 'produces'],\n });\n }\n });\n const productOwners = new Map<string, string>();\n graph.tasks.forEach((task, index) => {\n task.produces.forEach((product, productIndex) => {\n buildPlanTaskProductIdentities(product).forEach((identity) => {\n const owner = productOwners.get(identity);\n if (owner !== undefined) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" claims the same artifact as \"${owner}\" (${identity}); an artifact is produced by exactly one task`,\n path: ['tasks', index, 'produces', productIndex],\n });\n return;\n }\n productOwners.set(identity, task.taskRef);\n });\n });\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## 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) + `application-database-migrations` (**PostgreSQL applications only** — see below) |\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 (its read, form, summary and header surfaces and field chrome, each decided and stated — 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\n### The schema stage owes a migration on PostgreSQL\n\nThe workspace-truth section above ends with **\"Where this application STORES its data\"**, computed\nfrom the accepted schema plan and the authored store declaration. Read it, and follow what it says\nabout binding `application-database-migrations` to the schema stage.\n\nDo not try to find this out yourself. You have no shell and no file access: this method used to\ninstruct you to run `rg -n \"applicationDatabase\"`, which you could not do, and what you answered\ninstead was unanchored. If the section reports the store as UNKNOWN, say so in the plan and bind\nnothing — a wrong guess either way costs more than a stated gap.\n\n**Do not emit a separate coding task for the migration.** Generating one is deterministic work —\n`wildo db generate` writes it — so it is not a coding-agent objective at all. It is a\n`COMPANION_GENERATION_STEP`, and Step 4 below carries its slug.\n\nThe application-wide backstop is the assemble/verify playbook, whose check set includes\n`check:schema-plan-in-sync`. That gate catches a missed migration; it is not a licence to omit\nthe obligation here, because a build that fails at the capstone has already spent every task.\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) through\n `prerequisiteTaskRefs` naming the actual predecessor task refs.\n This is checked, and it is a REFUSAL rather than a note: dispatch order is computed\n from the declared prerequisites and from nothing else, so a config task that names a\n schema task in the same plan without depending on it may be dispatched first — the\n agent would author a resources-config for a schema that has not landed. Declaring\n the edge indirectly is fine (config → module → schema); leaving it out is not.\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\nAny task whose HOW includes **writing JSX for a bespoke surface** — a ui-behavior\nstage, a custom or composite view, an app-level screen — binds\n`frontend-component-catalog` alongside its own skill. It is what tells the coding\nagent which components the framework exports and how to spell their props; without\nit the agent builds the surface from raw `div`s and hand-written utility classes,\nbypassing the theme, the surface policy and the accessibility behaviour every\npreset carries. Do NOT bind it to a task that writes no markup (a schema stage, a\nconfig stage, a migration).\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- **Never invent an endpoint.** A relationship-draft whose source or target resource no\n module declares cannot be wired, and it is not yours to repair: emit no wiring task for\n it and do not add the resource to any task. The conception owns that fault, and the\n judge's `conception-buildable` verdict sends the application back to it. A plan that\n invents the resource to wire it hides the fault the conception needs to see.\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 catalog your brief\ncarries** — every installed skill's name and what it does, under \"Application-knowledge\nskills\". Every skill name you emit MUST appear there, spelled exactly. Do **not** guess a\nskill name and do not recall one: a name that is not in that list addresses no skill\nfolder, and the task bound to it cannot be dispatched.\n\n**Every surface below has its own target kind and its own product kind. Use them.**\nUntil 2026-09-22 only resources had a vocabulary, so a task for any of these surfaces\neither declared no product (and could never be proven landed) or borrowed `MODULE`\nwith a product its scope could not prove. A task that squeezes a website page into a\n`MODULE` target, or declares a view with no product, is the defect this vocabulary\nreplaced — the judge reports it as a gap.\n\n- **`define_interaction_semantics`** — custom operations, lifecycle behaviour, access /\n role / scope rules, rate limits — interaction beyond the default resource verbs.\n Target `RESOURCE_STAGE` (CONFIG), product `RESOURCE_OPERATION`. Skills: the Backend and\n Resources domains of the router (`backend-custom-operation`, `rate-limit-authoring`,\n `authorization-unit-narrowing`).\n- **`shape_user_experience`** — the cross-resource UX, and you do NOT decide it here. The\n **experience plan** (`bottom_up.experience-plan`) already did: which surfaces exist, what\n each is for, which presets it reuses, and how the shell, navigation, design system and\n global views are composed. Read it and emit:\n - one task per VIEW, target `MODULE_FRONTEND` on the view's own module, product matching\n its kind (`RESOURCE_COMPOSITE_VIEW`, `RESOURCE_CUSTOM_VIEW`, `RESOURCE_CHART_VIEW`,\n `APPLICATION_VIEW`, `CUSTOM_COMPONENT`; an execution view is a `RESOURCE_CUSTOM_VIEW`\n product, which is what its file is). A composite, custom or app-level view's product\n carries the plan's `viewRef` verbatim — a ref the plan does not carry is refused as\n dangling, and the dispatch looks the view up by it; a chart names its `chartRef` and a\n component its `componentRef`. Its skill is the one its view kind names (the dispatch\n derives it from the product and loads it first). Carry the view's `reusesComponentRefs` into the task's\n objective — the presets are the decision, and an objective that drops them hands the\n agent a blank surface;\n - one task per CONFIGURATION, target `APPLICATION_FRONTEND_CONFIG` with that surface,\n product `APPLICATION_FRONTEND_CONFIG` naming the surface's own `declarationRefs`, and\n its skill the one the surface names (`config-navigation`, `config-design-system`,\n `config-app-shell`; `views-app-level` for global views — derived at dispatch too).\n - one task per planned MILESTONE, target `MODULE_BACKEND` on the milestone's module,\n product `APPLICATION_MILESTONE` naming its `milestoneRef`, skill\n `milestones-and-celebrations` (`EXPERIENCE_MILESTONE_SKILL_REF`). It depends on the config stage of its\n `triggerResourceRef` — the operation that earns it must exist before it can be counted.\n Carry the planned moment into the objective;\n - one task per planned piece of GUIDANCE, target `MODULE_FRONTEND` on its module, product\n `APPLICATION_GUIDANCE` naming its `guidanceKind` (the plan's `kind`) and `guidanceRef`,\n skill `guidance-onboarding-authoring` (`EXPERIENCE_GUIDANCE_SKILL_REF`, the same for both\n kinds). It depends on the milestone tasks its `gatedByMilestoneRefs` name, and on the\n resources whose operations it responds to. Carry the planned purpose and gate into the\n objective — the gate is what makes it appear at the right moment. For an\n `ONBOARDING_DOCUMENT`, also carry its `hostViewRef` — the objective must say which view\n embeds it with `EmbedOnboarding` (a view of the document's own module, so inside the task's\n scope) — and depend on that view's task when the plan builds it:\n landing proves the document is declared, not that anything shows it.\n Do not choose any of these skills yourself: every map is total over its vocabulary, and the\n build dispatch DERIVES each task's skill from its product and loads it first, whatever the\n task declares. Declare the skill the product's kind names anyway (the view skill for a view,\n `config-<surface>` for a configuration), so the plan reads right; add a second only when the\n task genuinely needs one no map would give it. With no experience plan,\n emit nothing here — an improvised surface is the state this family replaced.\n (A placement DECIDED by the placement plan is Step 1b's `SHELL_PLACEMENT`, not this.)\n- **`extend_application`** — the controlled extension points where the declarative model\n is not enough:\n - a custom UI component / widget → target `MODULE_FRONTEND`, product `CUSTOM_COMPONENT`;\n skills `engine-component-registration`, `frontend-component-catalog`;\n - a PDF template / renderer → target `MODULE_BACKEND`, product `PDF_TEMPLATE`; skill\n `pdf-template-authoring`;\n - custom backend implementation logic → target `MODULE_BACKEND`, product the\n `RESOURCE_OPERATION` it serves; skill `backend-addon-wiring`;\n - workers and minions → you do NOT decide them here. The **integration plan**\n (`bottom_up.integration-plan`) already did: which surfaces run beside the backend, on\n which runtime, and exactly which resources a minion's tick may read and write. Read it\n and emit one task per WORKER (target `WORKER` with its `runtime`, product\n `APPLICATION_WORKER` naming its `jobRefs`, skill `worker-authoring` — both `NODE` and\n `RUST`, which is what `INTEGRATION_WORKER_SKILL_REF` holds) and one per MINION (target\n `MINION`, product `APPLICATION_MINION` naming its `behaviorRefs`, skill\n `minion-authoring`). Carry the minion's\n `readsResourceRefs` / `writesResourceRefs` into the task's objective: the whitelist\n starts DENY-ALL and an empty one keeps running, so an objective that drops them hands\n the agent a minion that looks healthy and touches nothing. The PACKAGE is composed by\n the foundation, one scenario per surface, so the task authors the BEHAVIOUR. With no\n integration plan, emit nothing here.\n - inbound channels → also decided by the **integration plan** (`inboundChannels`): work that\n ARRIVES — clients emailing documents to a matter, customers writing to a support address.\n Emit one task per declared channel: target `MODULE_BACKEND` in the module whose records the\n messages concern, product `INBOUND_CHANNEL_HANDLER` with the channel and a `handlerRef`\n (`<moduleRef>.<purpose>`), skill `inbound-channels` (the dispatch adds it whatever you write,\n so the agent is never without it). The channel's `purpose` is the task's objective, and its\n `servesRefs` are the task's. Make it depend on the tasks that register the resources the\n handler writes. The foundation already switched the receiving capability on; nothing here\n configures a provider.\n- **`connect_runtime_and_external_capabilities`** — providers and external connectors,\n and the **integration plan** decided these too: one task per PROVIDER BINDING it\n declares, target `PROVIDER_BINDING`, product `PROVIDER_BINDING` with the binding's own\n `scope`, and its skill taken from that scope through\n `INTEGRATION_PROVIDER_BINDING_SKILL_REF` — do not choose it yourself, the map is total\n over the scope vocabulary. The binding's `rationale` is the task's objective. Reach for\n `provider-operation-calls` and `configure-billing` as the task's further reading when the\n binding is one an application then CALLS. Environment and infra config are the\n foundation's, not a build task's.\n- **The billing catalogue** — target `BILLING_CATALOG`, and the **business model** decided it:\n its pricing plans are the products the application sells. Emit ONE task (the catalogue is one\n file, so two tasks would write over each other) producing one `APPLICATION_BILLING_PRODUCT` per\n plan, with a short `productKey` per plan (`free`, `team`, not the plan's `pricing-plan-…` ref),\n skill `configure-billing` (the dispatch adds it whatever you write), and `servesRefs` naming\n every plan it realises. Its objective carries what each plan decided, so the agent writes typed\n money rather than prose: the price and its billing period, whether it is per member or flat, and\n the three pricing-surface facts the plan implies — `isRecommended` for the plan the product is\n designed for (never because it sorts second), `priceDisclosure: STARTING_AT` when part of the\n price is not decided and `ON_REQUEST` when it is quoted, `availability: UPCOMING` when the plan\n is announced but the requirements do not yet build it. Order it after the module and resource\n tasks whose features the plans grant. The website's PRICING section task depends on it: the\n section reads this catalogue, so it must exist first. No business model, or one with no plans,\n emits nothing.\n- **The website** — target `WEBSITE`, and you do NOT decide its content here. The\n **website plan** (`bottom_up.website-plan`) already decided it: which pages, what each\n is for, and the sections that carry each page's argument in reading order. Read it and\n emit, in this order:\n - one `WEBSITE_PAGE` task per page (`produces: { kind: WEBSITE_PAGE, pageRef }`), skill\n `website-page-authoring`, its objective the page's own purpose. A page task authors the\n PAGE — route, bridge, component, manifest, registration and an EMPTY sections list —\n and never its sections: say so in the objective. On the first run that built a website\n the page tasks wrote every section themselves, so no section skill was ever applied;\n - one `WEBSITE_SECTION` task per section (`produces: { kind: WEBSITE_SECTION, pageRef,\n sectionRef }`), **with its page's task as a prerequisite** — a section is declared in\n its page's sections file, so the page must exist first — and its skill taken from the\n section's KIND through `WEBSITE_SECTION_SKILL_REF`: `HERO` → `website-section-hero`,\n `FEATURE_BENEFIT_SUMMARY` → `website-section-feature-benefit-summary`,\n `FEATURE_DETAIL` → `website-section-feature-detail`, `PRICING` →\n `website-section-pricing`, `SOCIAL_PROOF` → `website-section-social-proof`, `FAQ` →\n `website-section-faq`, `CTA` → `website-section-cta`, `FOOTER_CTA` →\n `website-section-footer-cta`, `CONTACT` → `website-section-contact`. Name it; the\n dispatch derives the same skill from the plan and puts it first whatever you wrote, so a\n wrong one is harmless but a right one keeps the plan readable.\n A plan whose disposition is `NOT_APPLICABLE`, or no plan at all, emits NOTHING here — the\n application has no `website/` workspace for a task to write in.\n- **Technical documentation** — target `TECHNICAL_DOCUMENTATION`, and you do not choose\n the chapters here either. The **documentation plan** (`bottom_up.documentation-plan`)\n decided them: read it and emit one task per chapter, product\n `DOCUMENTATION_CHAPTER` with its `chapterRef`, skill\n `application-consumer-documentation-authoring`, and an objective carrying the chapter's\n own purpose, audiences and the specifications it documents. A `NOT_APPLICABLE` plan, or\n none, emits nothing. The portal's generated tree is never written by a task — the\n target's own policy prohibits it, because the companion publishes there.\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(Label and 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 / milestones / guidance whose labels it\n generates — a milestone's title and a flow's words are generated from their declarations.\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. Author it only when the brand brief appears in your\n inputs (it is declared as a map: what the brand holds, not its content), and order\n it after that 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\n- **`database-migrations`** — `wildo db generate`: turns the drift the schema stages created into a\n committed migration, and advances the accepted plan with it. **PostgreSQL-backed applications\n ONLY** (`applicationDatabase: { engine: DatabaseEngine.POSTGRESQL }`); on MongoDB a collection\n appears on first write and this step must not be authored at all — it REFUSES on an application\n whose declared store is not PostgreSQL (or cannot be read), because generating there would author\n a table set nothing uses. A PostgreSQL application with no accepted plan yet is the opposite case:\n the step renders the whole model as the INITIAL migration and writes the baseline beside it, and\n the dispatch host derives that step itself when the plan omits it.\n\n Order it **after the schema stages whose drift it migrates** — practically, after the last\n resource's schema stage in the band. Author it ONCE: one step migrates all accumulated drift, and\n re-running it over a clean plan reports \"nothing to generate\" rather than writing an empty\n migration. It needs a BUILT `backend-api`, because the plan is computed by importing the compiled\n registry; it refuses on an unbuilt tree instead of authoring a migration for a model nobody has.\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## Validation and product review\n\n`BuildPlanTaskGraphGeneration` constrains the generated shape. The runtime normalizes\nit into `BuildPlanTaskGraph` and runs `validateBuildPlanTaskGraph`. Cycles and missing\nrequired prerequisite edges between stages present in the graph are hard failures;\na stage absent from the graph and a coding task without products produce warnings.\nSchema checks also reject unknown prerequisite refs and duplicate product ownership.\n\nThe `build-plan-coherent` checklist below complements those structural checks with\nproduct review: resource coverage, useful objectives, meaningful products and suitable\nmethods. Since 2026-09-22 it is also this playbook's compiled evaluation treatment: the\nADVISORY judge reads its invariants against the landed build plan and the domain plan\nafter every run, and its per-criterion verdicts reach the creator's review. A verdict is\na note, never a refusal. The method declares `approve_result`; neither shape validation,\nthe judge nor approval proves the application behavior that the plan intends to deliver.\n\n## Decomposition boundary\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`, `SHELL_PLACEMENT` 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 The `bottom_up.assemble-verify` method owns application-wide verification.\n Keep its work separate from the build targets decomposed here.\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 explicit\n `prerequisiteTaskRefs`; 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- **Framework contract design.** Use the existing `BuildPlanTaskGraph` schema and\n validator. This method authors an application plan; it does not reshape the\n framework's `_core` contracts or implement a new scheduling engine.\n\nKeep the output at decomposition depth. The dispatch and verification methods consume\nit and perform their own work; a task graph is not evidence that those runs succeeded.\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 (views,\n frontend configuration, components, PDF templates, workers, minions, provider bindings,\n website pages and sections, documentation chapters — each over its own target and\n product kind), any module-ensure tasks foundation did not cover, and the interleaved\n companion-generation steps — each carrying its target, **the artifacts it produces**,\n its one functional topic, its skill(s), and explicit `prerequisiteTaskRefs`.\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\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `resource-add-module` — the module-scaffolding vocabulary, for\n the conditional ensure-module task (only where the foundation step did not establish the\n module slice).\n- `resource-add-resource` — the resource vocabulary (the\n resource-skeleton task in the schema stage).\n- `resource-schema-authoring` — the schema stage (first\n per-resource task).\n- `resource-config-wiring` — the config stage (second\n per-resource task).\n- `resource-ui-behavior` — the ui-behavior stage (third\n per-resource task).\n- `spec-resource-update` — the spec stage (fourth per-resource\n task).\n- `module-relationships` — the relationship-wiring task's HOW\n (cardinality-to-FK-holder resolution, at dispatch time — named here, not performed).\n- `module-registration` — the cross-runtime module-registration\n task's HOW.\n- the skills CATALOG, which your brief carries as its own section — 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\nThese nine invariants are the criteria of this playbook's compiled evaluation treatment (`application-creation:evaluation-treatment/build-plan-coherent`, one criterion per invariant, invariants 2 and 2b sharing one), which the advisory judge runs after every landing. They are kept here as creator-facing review guidance too, so a reviewer and the judge read the same words:\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 nine 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. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product 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. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (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 whose two endpoints are resources the domain plan declares 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. A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) 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. The migration step follows the schema stages whose drift it migrates and is not authored for MongoDB. 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). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises) that the build would have to invent to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)\n",
109
+ "guidance": "# Build Decompose — Domain Plan → Ordered Coding-Agent Task Graph \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\nThe output follows the existing `BuildPlanTaskGraph` contract. The host checks its\nshape and graph consistency, then uses `prerequisiteTaskRefs` to determine readiness.\nFunctional topics organize context; they do not create scheduling edges. Decompose\nthe work using the current contracts rather than designing a replacement planner.\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 dispatches the tasks through the coding-agent\ncontract in parallel waves (up to the application's build parallelism at once), and the\n**scale** playbook describes how those waves are scheduled, interleaved with the\ncompanion generation steps, and reconciled. **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, **what each one\nproduces**, their topic, their skill(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 from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the 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`, and the **business model** for its pricing plans (the billing catalogue, Step 3);\nyou **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## Every task declares WHAT IT PRODUCES\n\nEach task carries `produces`: the artifacts the finished application will contain\n*because this task ran*. It is how the host answers **\"has this task landed?\"**, and\nit is not optional thinking: without declared products the host cannot probe the\nintended result. A COMPLETED durable run lets the loop advance, but the task remains\nexplicitly marked in `unverifiableLandedTaskRefs` as ran, not proven.\n\n**`target` and `produces` answer different questions, and a task needs both.**\n`target` is the WRITE SCOPE — which module tree this run may edit. Several tasks\nlegitimately share one. `produces` is the PRODUCT IDENTITY — what this task, and no\nother, is accountable for. Wonder CRM's plan proved they cannot be the same field:\nits pipeline-view task and its follow-through-operation task carry byte-identical\ntargets, so nothing derived from `target` could ever tell them apart, and 40 of its\n42 tasks were reported finished while none had run.\n\n**The one rule that makes a product real: name something the SCAFFOLD does not\nalready contain.** Every module, every resource file and every resource\nspecification is written by composition before any task exists. So \"the resource\nconfig file\" is not a product — it was there on day one. The VERBS it gains are.\nApply that test to every product you write.\n\n| product | you name | use it for |\n|---|---|---|\n| `RESOURCE_SCHEMA_FIELDS` | `resourceRef` + the `fieldRefs` the task adds | a schema stage. The FIELDS, never the file — the file is scaffolded. A `fieldRef` is the field's own IDENTIFIER as it will stand in the schema (`slug`, `archivedAt`, `completedAt`), never a description of what the fields express |\n| `RESOURCE_REGISTRATION` | `resourceRef` + the `operationRefs` it gains | a config stage |\n| `RESOURCE_UI_BEHAVIOR` | `resourceRef` | a ui-behavior stage — the one artifact composition never writes |\n| `RESOURCE_SPECIFICATION` | `resourceRef` + the `fieldRefs` it documents | a spec stage. The fields again: the spec file is scaffolded too |\n\n**A product ref is an ARTIFACT IDENTITY, not a concept.** Every `produces` entry is read back by a\nLANDING PROBE that searches the application's own source for that ref — in its plain, camelCase,\nPascalCase and SCREAMING_SNAKE spellings — and a task lands only when the probe finds it. So a ref\nnaming something that will never appear in the tree makes the task permanently unlandable, however\ncorrectly it is built.\n\nMeasured on the first end-to-end journey run (#1273): all sixteen schema tasks declared refs like\n`private-workspace-shape`, `membership-access-shape` and `one-sentence-rationale-shape` — eighteen\nrefs, not one of them a field. The schemas were authored correctly and committed; every task stayed\nunlanded, the loop guard then refused the whole band at task one, and the board read 9 of 94 while\nthe work was being done.\n\nName what a reader will find in the file. `slug`, `description`, `archivedAt` — not the idea they\nserve together. If you cannot name the fields yet, the task is not decomposed far enough to declare a\nproduct, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a placeholder concept.\n| `RESOURCE_RELATIONSHIP` | `relationshipRef` + `sourceResourceRef` + `targetResourceRef` | a relationship-wiring task. Both endpoints, because the scaffold already declares each resource's own edges |\n| `RESOURCE_OPERATION` | `resourceRef` + `operationRef` | a custom operation |\n| `APPLICATION_VIEW` | `viewRef` | an app-level view. With an experience plan, the `viewRef` is the plan's own (`view-…`), verbatim |\n| `APPLICATION_DOCUMENT` | `documentRef` | a governed document the engine catalog DEFINES — see the closed list below. Never a document you name yourself |\n| `APPLICATION_MODULE` | `moduleRef` | an ensure-module task. The REGISTRY entry, not the directory |\n| `APPLICATION_FRONTEND_CONFIG` | `configSurface` + the `declarationRefs` the file gains | composing ONE app-wide config file — `NAVIGATION`, `DESIGN_SYSTEM`, `APP_SHELL`, `GLOBAL_VIEWS`. The DECLARATIONS (a sidebar section ref, a zone, a token), never the file: `wildo init` writes all four |\n| `RESOURCE_COMPOSITE_VIEW` | `resourceRef` + `viewRef` | a composite view of one resource, bound in its ui-behavior's `compositeViews`. The plan's `viewRef`, verbatim |\n| `RESOURCE_CUSTOM_VIEW` | `resourceRef` + `viewRef` | a custom operation view or an execution view of one resource, bound in its ui-behavior. The plan's `viewRef`, verbatim — it is how the dispatch tells an execution view from a custom one |\n| `RESOURCE_CHART_VIEW` | `resourceRef` + `chartRef` | a chart view declared under the resource's `chartViews` |\n| `CUSTOM_COMPONENT` | `componentRef` | a custom frontend component, registered on the module's frontend index or in the engine registrations |\n| `APPLICATION_MILESTONE` | `milestoneRef` | a milestone the module declares — the experience plan's identifier, as a slug |\n| `APPLICATION_GUIDANCE` | `guidanceKind` + `guidanceRef` | an onboarding document or guidance flow the module declares — the experience plan's `kind` and ref |\n| `PDF_TEMPLATE` | `resourceRef` + `templateRef` | a PDF template BOUND to a resource's generated-file field (`generatedSummaryPdf`) |\n| `APPLICATION_WORKER` | `workerRef` + the `jobRefs` its entry file declares | a worker's behaviour. The JOBS, not the package: `add-worker-node` / `add-worker-rust` write the package |\n| `APPLICATION_MINION` | `minionRef` + the `behaviorRefs` its entry file declares | a minion's tick behaviour. Same rule: `add-minion` writes the package |\n| `PROVIDER_BINDING` | `providerRef` + `scope` (`BACKEND`, `COMPANION`, `FRONTEND_APP`, `WEBSITE`) | one provider declared in one runtime owner's scope — the SaaS config block, or the service's `provider-contributions.ts` |\n| `WEBSITE_PAGE` | `pageRef` | a marketing page, registered in `website-root.config.ts` by its manifest |\n| `WEBSITE_SECTION` | `pageRef` + `sectionRef` | one section of one page, declared in `<pageRef>.sections.tsx` |\n| `DOCUMENTATION_CHAPTER` | `chapterRef` | the chapter's authored body, keyed by its `chapterRef` in `specifications/src/technical-documentation/index.ts`, which `wildo docs publish` joins to the documentation plan and publishes under `/guides/<slug>` |\n| `APPLICATION_BILLING_PRODUCT` | `productKey` | one product of the application's billing catalogue, named by its catalogue `key` (a slug, e.g. `team`) — declared in `shared-lib/src/engine/product.ts` under the `BILLING_CATALOG` target. The KEY, never the file: `wildo init` writes the file with an empty catalogue |\n| `APPLICATION_ROLE` | `roleRef` | one role the application declares, named by its key in `CUSTOM_ROLES_CONFIGURATION` (upper snake case, e.g. `FIELD_TECHNICIAN`; never a core role such as `ORG_MEMBER`) — declared in `shared-lib/src/engine/roles.ts` under the `APPLICATION_ROLES` target. The NAME, never the file: `wildo init` writes the file with an empty table |\n| `APPLICATION_DATA_SEED` | `seedKey` + `resourceRef` + `content` (`REFERENCE` or `DEMONSTRATION`) | one data seed a module declares, named by its key (`<moduleRef>:<purpose>`, e.g. `crm:demo-customers`) — the file `backend-api/src/modules/<moduleRef>/seeds/<seedKey with : as .>.seed.ts`, registered by the module. A `DEMONSTRATION` seed lands only once it declares the environments it runs in, without production |\n| `INBOUND_CHANNEL_HANDLER` | `channel` + the handler's `handlerRef` (`<moduleRef>.<purpose>`, e.g. `matters.mail-intake`) | the handler that decides what a message arriving on a channel the integration plan declared causes. Its file is `backend-api/src/modules/<moduleRef>/inbound/<handlerRef>.inbound-channel-handler.ts`, and it lands when the module's backend `index.ts` imports that file — which is how it is registered on `inboundHandlers` |\n\n**A GOVERNED DOCUMENT is chosen from a closed list, never invented.** There are six,\nand a `documentRef` names one of them in exactly this form:\n\n```\ndocument:public.privacy-notice document:governance.program-handbook\ndocument:public.service-terms document:governance.scope-system-description\n document:governance.roles-responsibilities\n document:governance.document-record-control\n```\n\nA document is drafted against a BLUEPRINT — the required sections, the required\nfacts, the claim guards — and the blueprint is what the catalog holds. A ref outside\nthis list resolves to no blueprint, so the only thing a coding agent could do is\nINVENT the document's structure, which its authoring skill forbids. The task is then\nunbuildable by any run, and the dispatcher skips it by name rather than spending an\nagent turn rediscovering that.\n\nThis is not a hypothetical constraint. A plan authored against the previous wording\nof the row above — \"a notice, a governance statement\" — declared\n`gdpr-data-handling-governance` and `terminal-access-governance`: two plausible\ngovernance statements, neither of which names anything. Both sat permanently ready,\nand the one that was dispatched spent a full turn establishing that the document does\nnot exist. **If the obligation you have in mind is not on this list, it belongs in a\ndocument that IS** — GDPR data-handling scope, retention and subject rights are\n`document:public.privacy-notice`'s subject matter — or it is not a build task at all.\n\n**A cross-resource FOREIGN KEY belongs to the RELATIONSHIP task, never to the schema\ntask of the resource that holds it.** The domain plan makes the FK derivable — an\n`ownershipIntent` of SOURCE_HOLDS_REFERENCE on `contact-company` says contact carries\n`companyId` — and that is exactly why the mistake is easy: the field is derivable, so\nit is tempting to declare it on the schema task that will contain it. Step 2 below\nmakes the relationship task the SINGLE home for cross-resource wiring, and the\n`module-relationships` skill coordinates that FK across the owner's schema and config.\nDeclaring it in both places attributes one artifact to two tasks — the ambiguity\n`produces` exists to remove, reintroduced through the field that removes it. A schema\ntask's products are the resource's OWN domain fields.\n\nTwo further rules the graph enforces, so authoring against them saves a rejection:\n\n- **No two tasks may claim the same artifact.** That is what makes landing decidable.\n Two tasks may both enrich one resource's schema — it is the FIELDS that must not\n overlap, so split by field, never by prose.\n- **A `COMPANION_GENERATION_STEP` declares NO products.** Its landing is the\n generation step's own condition, computed by the companion. A product declared\n beside one is refused.\n\nProducts stay SEMANTIC. You name a resource, a field, a relationship, a view — never\na path and never a command, exactly as with `target`. The host alone turns a product\ninto a question about the working tree.\n\nThe contract itself, so the vocabulary below is read from the source rather than\nfrom this prose:\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, email templates, logo or database migrations) 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 * THE NON-RESOURCE SURFACES (#1490). Until 2026-09-22 the five kinds above were the whole\n * vocabulary, and every one of them is about a resource or the shell placement of one. The\n * decompose method meanwhile told the planner to emit tasks for views, navigation, the design\n * system, custom components, PDF templates, workers, minions, providers, the website and the\n * documentation — surfaces the framework's own composition scenarios and 85 of its 111 skills\n * already build. A task for any of them had no kind to declare, so it either declared none\n * (landing as RAN-not-PROVEN forever) or borrowed `MODULE` with a product the module scope could\n * not prove. The members below are those surfaces, one per write scope the host can derive.\n */\n /**\n * The FRONTEND and SPECIFICATION layers of one module — its composite, custom and chart views,\n * its custom components and their specifications.\n *\n * Narrower than `MODULE` on purpose: a view task never touches `shared-lib` or `backend-api`, so\n * handing it the four-layer scope also hands it four typechecks and the FK sweep for a change\n * that can only break the frontend and the specifications package.\n */\n MODULE_FRONTEND = 'MODULE_FRONTEND',\n /**\n * The BACKEND layer of one module beside its shared-lib declarations — PDF templates and their\n * bindings, backend addons (services, controllers, flows-actors), email definitions.\n *\n * Shared-lib is in scope because a PDF template is bound to a resource FIELD the config declares\n * (`generatedSummaryPdf`), and a backend addon usually declares its contract there first.\n */\n MODULE_BACKEND = 'MODULE_BACKEND',\n /**\n * ONE application-wide frontend configuration surface — navigation, the design system, the app\n * shell's composition, the global views — named by {@link FrontendConfigSurface}.\n *\n * Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the\n * shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES\n * the surface itself (which sidebar sections exist, which transitions the primary zone uses,\n * which palette the product carries). Same file for `APP_SHELL`, different question.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /** The marketing website workspace (`website/`), composed by the `add-website` scenario. Pages and sections are its products. */\n WEBSITE = 'WEBSITE',\n /**\n * The technical-documentation workspace (`technical-doc/`) and the specification package's\n * `technical-documentation/` declarations that feed it. Its generated tree is never written by a\n * task: the companion publishes into it, and the coding policy prohibits it by prefix.\n */\n TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',\n /** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */\n WORKER = 'WORKER',\n /** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */\n MINION = 'MINION',\n /**\n * Declaring one provider in the application — the SaaS config's provider scopes, the backend\n * package dependency, the frontend provider module and its companion contribution.\n *\n * Application-wide by construction: a provider binding names no module, and the four files it\n * may touch are the same for every provider.\n */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /**\n * The application's BILLING CATALOGUE — the `ProductDefinition[]` in `shared-lib/src/engine/product.ts`\n * (and the product specifications that document it), which the backend syncs to the billing\n * provider and the public website reads for its pricing page (#1835).\n *\n * Its own kind because none of the others is true of it: the catalogue is application-wide (a plan\n * belongs to no module), it lives in the shared library's ENGINE module that no `MODULE_*` scope\n * reaches, and before it existed a journey-built application reached its website with an EMPTY\n * catalogue, so the website re-typed the business model's prices by hand.\n */\n BILLING_CATALOG = 'BILLING_CATALOG',\n /**\n * The application's own ROLES — `CUSTOM_ROLES_CONFIGURATION` in `shared-lib/src/engine/roles.ts`, the\n * organization types that offer them (`availableOrgRoles` in `wildo.saas.config.ts`), their\n * specifications, and the `roles` of the operations they unlock (#2490).\n *\n * Its own kind because none of the others reaches it: the role table is application-wide and lives in\n * the shared library's ENGINE module. Before it existed a requirement naming user groups (\"office and\n * field users see different things\") had no task able to declare a role, so app-creation-test-005\n * modelled roles as an access-role RESOURCE that nothing reads.\n */\n APPLICATION_ROLES = 'APPLICATION_ROLES',\n}\n\n/**\n * WHICH application-wide frontend configuration surface a task composes — one file each, in\n * `frontend/src/config/`, and the coding policy resolves the member to that file exactly as\n * `SHELL_PLACEMENT` resolves a `PlacementSurface`.\n *\n * Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a\n * subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of\n * those live in one file. A configuration surface is WHICH FILE a composition task authors, and\n * navigation and the design system are not places anything is placed.\n */\nexport enum FrontendConfigSurface {\n /** `frontend/src/config/navigation.config.ts` — zones, transitions, overlay appearance. */\n NAVIGATION = 'NAVIGATION',\n /** `frontend/src/config/design-system.config.ts` — palette, typography, shell appearance from the brand's visual tone. */\n DESIGN_SYSTEM = 'DESIGN_SYSTEM',\n /** `frontend/src/config/app-shell.config.ts` — top bar, sidebar sections, quick switcher: the shell's COMPOSITION, not a placement into it. */\n APP_SHELL = 'APP_SHELL',\n /** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */\n GLOBAL_VIEWS = 'GLOBAL_VIEWS',\n}\n\n/**\n * The two shapes of guidance an application gives a person, and the file each is declared in.\n *\n * They are distinct because they are found differently: an onboarding DOCUMENT is embedded in a\n * screen (`EmbedOnboarding`) and is there whenever that screen is, while a guidance FLOW is started\n * by an event and shows once. Both are listed on the owning frontend module — `onboardingViews` and\n * `guidanceFlows`. Each kind has a CONVENTIONAL definitions file, which the authoring skill teaches\n * and a landing probe reads for the declared ref (alongside the module's `index.ts`, where a small\n * module may declare inline). A convention for generated applications: a hand-authored application\n * may keep its declarations elsewhere, and then simply is not probed by a build plan.\n */\nexport enum ApplicationGuidanceKind {\n /** `frontend/src/modules/<m>/app-level-views/onboarding-views.definitions.ts` — an embedded onboarding document. */\n ONBOARDING_DOCUMENT = 'ONBOARDING_DOCUMENT',\n /** `frontend/src/modules/<m>/app-level-views/guidance-flows.definitions.ts` — a triggered guidance flow. */\n GUIDANCE_FLOW = 'GUIDANCE_FLOW',\n}\n\n/**\n * The two worker runtimes the framework composes (`add-worker-node`, `add-worker-rust`). The\n * runtime decides the entry file a landing probe reads and whether a typecheck exists to run: a\n * Node worker is verified by its package typecheck, a Rust worker has no TypeScript to check and\n * the policy says so rather than inventing a command.\n *\n * Not the SaaS config's `WorkerRuntime`, which is a free-form `{ type, language }` pair an\n * application authors for deployment; this is the closed set a creation run can COMPOSE.\n */\nexport enum BuildPlanWorkerRuntime {\n NODE = 'NODE',\n RUST = 'RUST',\n}\n\n/**\n * WHERE a provider is bound — which runtime owner's scope its declaration lands in. Each member\n * is a different file, so a probe and a write grant both derive from it.\n *\n * Named after the SaaS config's own scope keys (`providers.scopes.backend`, `.companion`,\n * `.frontendServices.app`, `.frontendServices.website`), which the `add-provider` and\n * `add-file-picker-provider` scenarios write. Minion and worker scopes are deliberately absent:\n * a provider reaching a minion is declared on that minion's own `providers` block and belongs to\n * the {@link BuildPlanTaskTargetKind.MINION} task that builds it.\n */\nexport enum ProviderBindingScope {\n BACKEND = 'BACKEND',\n COMPANION = 'COMPANION',\n FRONTEND_APP = 'FRONTEND_APP',\n WEBSITE = 'WEBSITE',\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/**\n * The key of the domain-plan MODULE a task targets or produces (`deals`, `tasks-manager`). Same\n * slug grammar as the other keys, declared as its own schema because it names one thing — a\n * module — where the other slugs name resources, relationships, steps, workers and products.\n */\nconst ModuleRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n\n/**\n * The governed document a task produces, named as a COMPLIANCE-DOCUMENT CANDIDATE names it:\n * `document:<namespace>.<id>`, e.g. `document:public.privacy-notice`.\n *\n * **This field was `SlugSchema`, and a slug cannot name a governed document — so until 2026-09-16 no\n * build plan in any application could declare a document the engine catalog defines.** A slug forbids\n * the colon and the dot, the catalog's definitions are `document-definition:public.privacy-notice`,\n * and `selectAssuranceDocumentBlueprintForDocumentRef` joins the two namespaces by exact suffix — so\n * every authored `documentRef` resolved to NO blueprint, and a blueprint is what says which sections,\n * facts and claim guards the document owes. The two vocabularies were disjoint by construction.\n *\n * The cost is measured rather than theoretical. Wonder CRM's plan declares two such products\n * (`gdpr-data-handling-governance`, `terminal-access-governance`), neither of which names anything;\n * the first was dispatched, and its agent spent a full turn establishing — with a positive control —\n * that the document does not exist and could only be invented, which the authoring skill forbids.\n *\n * The bare slug is STILL ACCEPTED, and that is deliberate rather than tidiness left undone: tightening\n * this to the namespaced form alone would make every already-accepted plan carrying one fail to parse,\n * and a build plan that cannot be READ stops the whole lane — the gate\n * `application-creation-directive.md` forbids, for a task nobody can fix by re-running anything. A slug\n * simply resolves to no blueprint, so the dispatcher skips that task with a message naming the ref,\n * and the rest of the plan proceeds.\n */\nconst DocumentProductRefSchema = z.union([\n z.string().regex(/^document:[a-z0-9]+(?:-[a-z0-9]+)*\\.[a-z0-9]+(?:-[a-z0-9]+)*$/),\n SlugSchema,\n]);\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\n/**\n * WHAT a build task PRODUCES — the artifact whose presence in the application\n * proves the task is done.\n *\n * **This is not `target`, and the difference is the whole reason it exists.**\n * `target` is a WRITE SCOPE: the host turns it into the path prefixes a run may\n * mutate, and several tasks legitimately share one. `produces` is a PRODUCT\n * IDENTITY: it says which artifact this task, and no other, is accountable for.\n *\n * Measured 2026-09-10 on Wonder CRM (issue #597): `build-task-pipeline-view`\n * and `build-task-deal-follow-through-operation` carry BYTE-IDENTICAL targets\n * (`{ kind: MODULE, moduleRef: 'deals' }`), and 7 of that plan's 42 tasks share\n * 3 targets. Landing had been answered by narrowing the target to a module\n * DIRECTORY — which `wildo compose` commits on day one, and which cannot tell\n * two tasks apart even in principle. The loop reported 40 of 42 tasks landed\n * while no coding task had ever run, so `dispatch-next` skipped every one of\n * them and the phase-advance gate read a build that was all but complete.\n *\n * Like `target`, this stays SEMANTIC: a product names a resource, a field, a\n * relationship or a view — never a path, and never a command. The host owns the\n * translation from a product to the physical question it asks of the working\n * tree, exactly as it owns the translation from a target kind to path prefixes.\n * A model that could author the path could author its own mutation scope.\n */\nexport enum BuildPlanTaskProductKind {\n /**\n * Named fields on one resource's schema.\n *\n * The shape an ENRICHMENT task needs, and the reason a product cannot always\n * be \"a file\": every resource file already exists, written by the scaffold\n * with its self-described STARTER shape, so file presence answers nothing.\n * The FIELDS are what the task adds.\n */\n RESOURCE_SCHEMA_FIELDS = 'RESOURCE_SCHEMA_FIELDS',\n /**\n * One resource's declared operations — its registry presence, named by the verbs it gains.\n *\n * The VERBS, not the config file: `<r>.resources-config.ts` is written by the scaffold, so its\n * existence is satisfied before any task runs. That is the exact shape of the defect this\n * vocabulary replaces, and a kind that reproduced it would be worse than no kind at all.\n */\n RESOURCE_REGISTRATION = 'RESOURCE_REGISTRATION',\n /** One resource's frontend ui-behavior. */\n RESOURCE_UI_BEHAVIOR = 'RESOURCE_UI_BEHAVIOR',\n /**\n * One resource's specification, named by the fields it documents.\n *\n * The FIELDS, for the same reason as {@link RESOURCE_REGISTRATION}: every resource is scaffolded\n * with a `*.resource.specification.ts` documenting only the starter shape, so file existence\n * proves nothing about the task that was meant to enrich it.\n */\n RESOURCE_SPECIFICATION = 'RESOURCE_SPECIFICATION',\n /** One relationship edge between two resources, named by the domain plan's `relationshipRef`. */\n RESOURCE_RELATIONSHIP = 'RESOURCE_RELATIONSHIP',\n /** One named custom operation on one resource. */\n RESOURCE_OPERATION = 'RESOURCE_OPERATION',\n /** One named application-level view. */\n APPLICATION_VIEW = 'APPLICATION_VIEW',\n /** One named governed application document (a compliance notice, a governance statement). */\n APPLICATION_DOCUMENT = 'APPLICATION_DOCUMENT',\n /** One application module, registered across the layer registries under one module identity. */\n APPLICATION_MODULE = 'APPLICATION_MODULE',\n /*\n * THE NON-RESOURCE PRODUCTS (#1490). Each names an artifact of a surface the five target kinds\n * above `MODULE_FRONTEND` could not express, and each is probed by the host from committed bytes —\n * a declaration in the one file that registers it, never a directory a scenario already wrote.\n */\n /**\n * Named declarations in ONE application-wide frontend configuration file — a sidebar section\n * ref the app shell gains, a zone the navigation config declares, a token the design system sets.\n *\n * The DECLARATIONS, never the file: every `frontend/src/config/*.config.ts` is written by\n * `wildo init`, so its presence is true before any task runs. Same reasoning as\n * {@link RESOURCE_SCHEMA_FIELDS}, one level up.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /**\n * One composite view of one resource — the cross-resource surface a resource's ui-behavior\n * declares under `compositeViews`. Distinct from {@link APPLICATION_VIEW}, which is\n * application-level and owned by a module rather than a resource.\n */\n RESOURCE_COMPOSITE_VIEW = 'RESOURCE_COMPOSITE_VIEW',\n /** One custom operation or execution view of one resource, bound in its ui-behavior. */\n RESOURCE_CUSTOM_VIEW = 'RESOURCE_CUSTOM_VIEW',\n /** One chart view of one resource, declared under its ui-behavior's `chartViews`. */\n RESOURCE_CHART_VIEW = 'RESOURCE_CHART_VIEW',\n /** One custom frontend component, registered by `componentRef` in the module's or the engine's registrations. */\n CUSTOM_COMPONENT = 'CUSTOM_COMPONENT',\n /**\n * One milestone a module declares — the moment the application recognises and celebrates.\n *\n * Named by its identifier, which is what the module's `milestones.ts` declares\n * (`first-project-created` is spelled `FIRST_PROJECT_CREATED` there). The module FILE is not the\n * product: a module may carry milestones before this task runs, and only the identifier says this\n * one landed.\n */\n APPLICATION_MILESTONE = 'APPLICATION_MILESTONE',\n /** One onboarding document or guidance flow a module declares, named by its ref. */\n APPLICATION_GUIDANCE = 'APPLICATION_GUIDANCE',\n /** One PDF template bound to one resource's generated-file field. */\n PDF_TEMPLATE = 'PDF_TEMPLATE',\n /**\n * One worker's JOBS — the named handlers its entry file declares.\n *\n * The jobs, not the package: `add-worker-node` writes the package, so its directory proves\n * nothing. What a coding task adds is behaviour, and behaviour is a symbol in the entry file.\n */\n APPLICATION_WORKER = 'APPLICATION_WORKER',\n /** One minion's BEHAVIOURS — the named tick handlers its entry file declares. Same reasoning as the worker. */\n APPLICATION_MINION = 'APPLICATION_MINION',\n /** One provider declared in one runtime owner's scope. */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /**\n * One product of the application's billing catalogue — a plan, add-on or purchase the application\n * sells — named by its catalogue `key`, which the catalogue file declares (`key: 'team'`).\n *\n * The KEY, not the file: `wildo init` writes `product.ts` with an empty catalogue, so the file proves\n * nothing. Written from the accepted business model's pricing plans, with the plan's price as typed\n * money and the pricing-surface facts (recommended, price disclosure, availability) the plan implies.\n */\n APPLICATION_BILLING_PRODUCT = 'APPLICATION_BILLING_PRODUCT',\n /**\n * One data seed a module declares — rows the application creates for itself, named by the seed's\n * `seedKey` (`crm:demo-customers`).\n *\n * The seed is its own file, `backend-api/src/modules/<module>/seeds/<seedKey with ':' as '.'>.seed.ts`,\n * and it lands only once the module registers it — a seed file nothing imports never runs. Its\n * {@link BuildPlanDataSeedContent} says whether it is REFERENCE data the application needs everywhere\n * or DEMONSTRATION data that must never reach production.\n */\n APPLICATION_DATA_SEED = 'APPLICATION_DATA_SEED',\n /** One website page, registered in the website root config by its manifest. */\n WEBSITE_PAGE = 'WEBSITE_PAGE',\n /** One section of one website page, declared in that page's sections file. */\n WEBSITE_SECTION = 'WEBSITE_SECTION',\n /**\n * One authored documentation chapter — a consumer guide the specifications package declares\n * for the documentation portal to publish (#874's publication input).\n */\n DOCUMENTATION_CHAPTER = 'DOCUMENTATION_CHAPTER',\n /**\n * One inbound CHANNEL handler — the code that decides what a message arriving on a channel causes\n * (#1832). Named by the handler's `ref` (`matters.mail-intake`), which the handler file spells and whose\n * file NAME is derived from it, so the module index's import of that file is what proves the handler is\n * registered. Produced once per channel the integration plan declares (`inboundChannels`).\n */\n INBOUND_CHANNEL_HANDLER = 'INBOUND_CHANNEL_HANDLER',\n /**\n * One role the application declares, named by its role name (`FIELD_TECHNICIAN`), which is its key in\n * `CUSTOM_ROLES_CONFIGURATION`. The NAME, not the file: `wildo init` writes `roles.ts` with an empty\n * table, so the file proves nothing (#2490).\n */\n APPLICATION_ROLE = 'APPLICATION_ROLE',\n}\n\n\n/**\n * What a data seed's rows ARE, which decides where they may exist.\n *\n * - `REFERENCE` — rows the application needs to work wherever it runs: a closed list, a default\n * record, a system template. Every environment, production included.\n * - `DEMONSTRATION` — sample rows that make a freshly created application look lived-in (customers,\n * projects, a few records per list). They must never sit beside real rows, so the seed declares\n * `allowedApplicationEnvironments` without `production`, and the task lands only once it does.\n */\nexport enum BuildPlanDataSeedContent {\n REFERENCE = 'REFERENCE',\n DEMONSTRATION = 'DEMONSTRATION',\n}\n\n/**\n * A data seed's key: kebab-case segments joined by `:` (`crm:demo-customers`), the convention a\n * `DataSeedDefinition` documents. Constrained here because the seed's FILE is derived from it.\n */\n/**\n * An application role's name, as `CUSTOM_ROLES_CONFIGURATION` keys it: upper snake case (`FIELD_TECHNICIAN`).\n * A core role (`ORG_MEMBER`, `APP_ADMIN_SUPER_ADMIN`) is not something an application declares, so the\n * product refuses one: a plan naming it would claim to create a role the engine already owns.\n */\nexport const APPLICATION_ROLE_NAME_PATTERN: RegExp = /^[A-Z][A-Z0-9]*(?:_[A-Z0-9]+)*$/;\nconst CORE_ROLE_NAMES: ReadonlySet<string> = new Set<string>([...Object.values(CORE_APP_ROLES), ...Object.values(CORE_ORG_ROLES)]);\n\nexport const DATA_SEED_KEY_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*(?::[a-z0-9]+(?:-[a-z0-9]+)*)*$/;\n\n/**\n * One artifact a task is accountable for. Closed by construction: a product the\n * host cannot ask a question about is a product that can never be shown to have\n * landed, so the vocabulary only grows alongside the resolver that answers it.\n */\nexport const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /**\n * At least one field, because a task that enriches a schema with nothing is\n * the vacuity this whole field exists to stop: it would land the moment the\n * scaffold existed, which is the defect being fixed.\n */\n fieldRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_REGISTRATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SPECIFICATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, fieldRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP).systemEnum('BuildPlanTaskProductKind'),\n relationshipRef: SlugSchema,\n /*\n * The two resources the edge relates, NAMED rather than parsed out of the ref.\n *\n * A ref is `<source>-<target>` by convention and that convention is not invertible:\n * `next-step-deal` splits as (`next`, `step-deal`) or (`next-step`, `deal`) and only the domain\n * plan knows which. The domain plan already carries both, so the plan passes them on instead of\n * making the host guess — a host that guesses wrong probes for a resource that does not exist\n * and reports the task permanently unlanded.\n */\n sourceResourceRef: SlugSchema,\n targetResourceRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_OPERATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_VIEW).systemEnum('BuildPlanTaskProductKind'), viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DOCUMENT).systemEnum('BuildPlanTaskProductKind'), documentRef: DocumentProductRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MODULE).systemEnum('BuildPlanTaskProductKind'), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG).systemEnum('BuildPlanTaskProductKind'),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n /** At least one, for the same vacuity reason as a schema's `fieldRefs`: the file exists on day one. */\n declarationRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CHART_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, chartRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.CUSTOM_COMPONENT).systemEnum('BuildPlanTaskProductKind'), componentRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MILESTONE).systemEnum('BuildPlanTaskProductKind'), milestoneRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_GUIDANCE).systemEnum('BuildPlanTaskProductKind'),\n /** Which definitions file carries it — a document and a flow live in different ones. */\n guidanceKind: z.enum(ApplicationGuidanceKind).systemEnum('ApplicationGuidanceKind'),\n guidanceRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PDF_TEMPLATE).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */\n templateRef: NonEmptyStringSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),\n providerRef: SlugSchema,\n scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_ROLE).systemEnum('BuildPlanTaskProductKind'),\n roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).refine((roleRef) => !CORE_ROLE_NAMES.has(roleRef), {\n message: 'A core role is the engine\\'s; an application role needs a name of its own.',\n }),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DATA_SEED).systemEnum('BuildPlanTaskProductKind'),\n seedKey: z.string().regex(DATA_SEED_KEY_PATTERN),\n /** The resource whose rows the seed writes — the `resourceType` it declares. */\n resourceRef: SlugSchema,\n content: z.enum(BuildPlanDataSeedContent).systemEnum('BuildPlanDataSeedContent'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER).systemEnum('BuildPlanTaskProductKind'),\n /** The channel the handler serves — one the integration plan declared. Email is the only declarable channel. */\n channel: z.literal(InboundChannelKind.EMAIL).systemEnum('InboundChannelKind'),\n /** The handler's `ref`, exactly as `inboundHandlerRef()` will accept it. */\n handlerRef: z.string().regex(INBOUND_HANDLER_REF_PATTERN),\n }),\n]);\nexport type BuildPlanTaskProduct = z.infer<typeof BuildPlanTaskProductSchema>;\n\n/**\n * Every artifact identity a product claims — one string per artifact, not one\n * per product, because a product may claim several.\n *\n * `RESOURCE_SCHEMA_FIELDS` is why this returns a list. Two tasks may both enrich\n * one resource's schema (a domain shape and a billing concern, say), and that is\n * legitimate; what must never overlap is the FIELDS. Comparing whole products\n * would refuse the legitimate pair, and comparing only the resource would let two\n * tasks claim one field and make landing ambiguous again.\n *\n * Derived from the product's own members rather than stored, and total over the\n * vocabulary, so a kind added tomorrow must state its identity here or fail to\n * compile — it cannot be silently treated as equal to its siblings.\n */\nexport function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): readonly string[] {\n switch (product.kind) {\n case BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_REGISTRATION:\n return product.operationRefs.map((operationRef) => `${product.kind}:${product.resourceRef}:${operationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_SPECIFICATION:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR:\n return [`${product.kind}:${product.resourceRef}`];\n case BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP:\n return [`${product.kind}:${product.relationshipRef}`];\n case BuildPlanTaskProductKind.RESOURCE_OPERATION:\n return [`${product.kind}:${product.resourceRef}:${product.operationRef}`];\n case BuildPlanTaskProductKind.APPLICATION_VIEW:\n return [`${product.kind}:${product.viewRef}`];\n case BuildPlanTaskProductKind.APPLICATION_DOCUMENT:\n /*\n * The ref AS AUTHORED, so a slug and a namespaced ref are different artifact identities even\n * where they mean the same document — the duplicate-artifact refusal cannot see two tasks\n * claiming one document if they spell it differently. Not normalisable: a slug carries no\n * namespace, so nothing can recover `public.` from `privacy-notice`. It costs nothing today\n * because a slug names no catalogued document at all, and the dispatcher skips such a task.\n */\n return [`${product.kind}:${product.documentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MODULE:\n return [`${product.kind}:${product.moduleRef}`];\n // One identity per DECLARATION, like schema fields: two tasks may compose one config file as\n // long as they declare different things in it.\n case BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG:\n return product.declarationRefs.map((declarationRef) => `${product.kind}:${product.configSurface}:${declarationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW:\n case BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.viewRef}`];\n case BuildPlanTaskProductKind.RESOURCE_CHART_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.chartRef}`];\n case BuildPlanTaskProductKind.CUSTOM_COMPONENT:\n return [`${product.kind}:${product.componentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MILESTONE:\n return [`${product.kind}:${product.milestoneRef}`];\n // The ref alone: a document and a flow sharing one ref is still one guidance identity, and the\n // runtime keys a person's saved state by it — two artifacts claiming it would collide there too.\n case BuildPlanTaskProductKind.APPLICATION_GUIDANCE:\n return [`${product.kind}:${product.guidanceRef}`];\n case BuildPlanTaskProductKind.PDF_TEMPLATE:\n return [`${product.kind}:${product.resourceRef}:${product.templateRef}`];\n case BuildPlanTaskProductKind.APPLICATION_WORKER:\n return product.jobRefs.map((jobRef) => `${product.kind}:${product.workerRef}:${jobRef}`);\n case BuildPlanTaskProductKind.APPLICATION_MINION:\n return product.behaviorRefs.map((behaviorRef) => `${product.kind}:${product.minionRef}:${behaviorRef}`);\n // The SCOPE is part of the identity: one provider bound on the backend and on the website is two artifacts.\n case BuildPlanTaskProductKind.PROVIDER_BINDING:\n return [`${product.kind}:${product.scope}:${product.providerRef}`];\n case BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT:\n return [`${product.kind}:${product.productKey}`];\n case BuildPlanTaskProductKind.APPLICATION_ROLE:\n return [`${product.kind}:${product.roleRef}`];\n // The key alone: two seeds may write one resource, and the key is what the seed run ledger tracks.\n case BuildPlanTaskProductKind.APPLICATION_DATA_SEED:\n return [`${product.kind}:${product.seedKey}`];\n case BuildPlanTaskProductKind.WEBSITE_PAGE:\n return [`${product.kind}:${product.pageRef}`];\n case BuildPlanTaskProductKind.WEBSITE_SECTION:\n return [`${product.kind}:${product.pageRef}:${product.sectionRef}`];\n case BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER:\n return [`${product.kind}:${product.chapterRef}`];\n case BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER:\n return [`${product.kind}:${product.handlerRef}`];\n default: {\n const unhandled: never = product;\n throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);\n }\n }\n}\n\n/**\n * The skill every billing-catalogue task is authored with (#1835): the product-catalogue contract, the\n * money encoding (minor units), and the pricing-surface facts. The dispatch derives it from an\n * `APPLICATION_BILLING_PRODUCT` product whatever the decomposer wrote, so an agent writing the catalogue\n * the backend sells from is never without it.\n */\nexport const BILLING_CATALOG_SKILL_REF = 'configure-billing';\n\n/**\n * The skill every application-roles task is authored with (#2490): the role table, the organization\n * types that offer a role, and the operation roles that make it matter. The dispatch derives it from an\n * `APPLICATION_ROLE` product whatever the decomposer wrote.\n */\nexport const APPLICATION_ROLES_SKILL_REF = 'application-roles-authoring';\n\n/**\n * The skill every data-seed task is authored with (#2234): levels, modes, business keys, and the\n * environment restriction that keeps demonstration rows out of production. The dispatch derives it from\n * an `APPLICATION_DATA_SEED` product whatever the decomposer wrote.\n */\nexport const DATA_SEED_SKILL_REF = 'seeding-authoring';\n\n/**\n * The skill every PDF-template task is authored with (#2495): the template contract, the file field it fills, and\n * where the generated file is stored. The dispatch derives it from a `PDF_TEMPLATE` product whatever the decomposer\n * wrote.\n */\nexport const PDF_TEMPLATE_SKILL_REF = 'pdf-template-authoring';\n\n/**\n * The skill a resource CONFIG task carries when the resource DECLARES personal data (#2495): its retention binding\n * lives in that configuration file, and storage limitation is a duty about personal data. The dispatch reads the\n * declaration from the resource's schema (the engine's personal-data markers), whatever the decomposer wrote.\n */\nexport const RESOURCE_RETENTION_SKILL_REF = 'resource-retention-binding';\n\nexport const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),\n moduleRef: ModuleRefSchema,\n resourceRef: SlugSchema,\n stage: z.enum(BuildPlanResourceStage),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),\n moduleRef: ModuleRefSchema,\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. i18n-labels, email-templates); 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).systemEnum('PlacementSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_FRONTEND), moduleRef: ModuleRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_BACKEND), moduleRef: ModuleRefSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_FRONTEND_CONFIG),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.WEBSITE) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.WORKER),\n /** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */\n workerRef: SlugSchema,\n runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.MINION),\n /** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */\n minionRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_ROLES) }),\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 /**\n * One sentence of intent: what this task delivers.\n *\n * Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also\n * hold. A display decorator mutates the instance it is applied to, and the workbench gives those\n * refs a receding identifier look, which the objective sentence then took too.\n */\n objective: z.string().trim().min(1),\n target: BuildPlanTaskTargetSchema,\n /**\n * The artifacts this task is accountable for — what proves it done.\n *\n * Coding tasks should declare at least one product that composition did not already\n * write. A target is a shared mutation scope; its scaffolded file is not evidence\n * that this task's intended work exists. Products identify the output to probe.\n *\n * Empty declarations remain representable and produce the advisory\n * `TASK_DECLARES_NO_PRODUCT`. The host may advance after a COMPLETED durable run,\n * while naming the task in `unverifiableLandedTaskRefs`: it ran, but its output\n * cannot be proven from a product declaration. An unexecuted task is not landed.\n * This distinction avoids repeatedly dispatching the same unprovable task without\n * presenting execution history as evidence that the intended product is correct.\n *\n * The ONE hard exception is a `COMPANION_GENERATION_STEP`, which must declare NONE.\n * That kind already carries its own typed landed condition, owned by the\n * generation-step service — a set computed asynchronously (planner units x\n * enabled locales), and for the migration step a STATE rather than files. A\n * product declared beside it would be read by nothing, which is the inert\n * declaration this field exists to avoid. Enforced on the graph below, in both\n * directions.\n */\n produces: z.array(BuildPlanTaskProductSchema).default([]),\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).systemEnum('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 /**\n * What this task is accountable to — traceability only, NEVER scope authority.\n *\n * The vocabulary is the target aspects `BUILD_PLAN_FAMILY_ASPECTS` declares for this edge:\n * functional and non-functional requirements, roadmap phases, the vision's success criteria and\n * constraints, drafted features, pricing plans, and the brand's name, logo direction and visual\n * tone. Each target after the first three was added because a producer had already been writing\n * it (#629, #1433, #1835, #2221). A companion generation step serves what it consumes: the `logo`\n * step serves the brand's logo direction and name.\n *\n * This schema accepts any non-empty string. Generation does not: the edge is DECLARED, so a key\n * that resolves to no element of a target family (when that family has landed) is a dangling\n * reference. The model is told so on retry, and the landing refuses it. That is why widening the\n * vocabulary to what producers genuinely mean matters: a true link the vocabulary does not name\n * fails generation. The workbench renders a key outside the vocabulary as visibly unresolved.\n */\n servesRefs: z.array(NonEmptyStringSchema).default([]),\n /**\n * Who asked for this task DIRECTLY (#1608), rather than it being derived from the specifications: the\n * signed-in person who added it in conversation. STAMPED by the append, never authored: a value in\n * generated output is discarded. Absent on every task the decomposition derived.\n *\n * It is what keeps a requested task alive. Build decomposition refines the plan from the domain plan, and\n * a task nothing in the specifications justifies would read as unjustified and be dropped; a requested\n * task it leaves out is carried forward instead, keeping only the prerequisites the new plan still holds.\n */\n requestedBy: NonEmptyStringSchema.optional(),\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 by\n * build-dispatch (and build-scale, which runs the same branch): ready tasks\n * are dispatched in parallel waves of up to the application's build\n * parallelism (`wildo workbench parallelism`, 5 by default; 1 = one at a\n * time).\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 /*\n * No two tasks claim the same artifact.\n *\n * This is what makes landing DECIDABLE, not a tidiness rule. If two tasks name\n * one product, the host cannot tell which of them a present artifact proves —\n * exactly the ambiguity that shared `target`s created, arriving through the\n * field that replaced them. Enforced here rather than left to the validator\n * because a graph that cannot answer \"has this task landed?\" is not a graph\n * the loop may run at all.\n */\n graph.tasks.forEach((task, index) => {\n const isGenerationStep = task.target.kind === BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP;\n if (isGenerationStep && task.produces.length > 0) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" is a companion generation step and must declare no products; its landing is the generation step's own condition`,\n path: ['tasks', index, 'produces'],\n });\n }\n });\n const productOwners = new Map<string, string>();\n graph.tasks.forEach((task, index) => {\n task.produces.forEach((product, productIndex) => {\n buildPlanTaskProductIdentities(product).forEach((identity) => {\n const owner = productOwners.get(identity);\n if (owner !== undefined) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" claims the same artifact as \"${owner}\" (${identity}); an artifact is produced by exactly one task`,\n path: ['tasks', index, 'produces', productIndex],\n });\n return;\n }\n productOwners.set(identity, task.taskRef);\n });\n });\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## 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) + `application-database-migrations` (**PostgreSQL applications only** — see below) |\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` (plus `resource-retention-binding` when the resource declares personal data — the dispatch adds it whatever you write) |\n| Resource `<name>` — ui-behavior (its read, form, summary and header surfaces and field chrome, each decided and stated — 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\n### The schema stage owes a migration on PostgreSQL\n\nThe workspace-truth section above ends with **\"Where this application STORES its data\"**, computed\nfrom the accepted schema plan and the authored store declaration. Read it, and follow what it says\nabout binding `application-database-migrations` to the schema stage.\n\nDo not try to find this out yourself. You have no shell and no file access: this method used to\ninstruct you to run `rg -n \"applicationDatabase\"`, which you could not do, and what you answered\ninstead was unanchored. If the section reports the store as UNKNOWN, say so in the plan and bind\nnothing — a wrong guess either way costs more than a stated gap.\n\n**Do not emit a separate coding task for the migration.** Generating one is deterministic work —\n`wildo db generate` writes it — so it is not a coding-agent objective at all. It is a\n`COMPANION_GENERATION_STEP`, and Step 4 below carries its slug.\n\nThe application-wide backstop is the assemble/verify playbook, whose check set includes\n`check:schema-plan-in-sync`. That gate catches a missed migration; it is not a licence to omit\nthe obligation here, because a build that fails at the capstone has already spent every task.\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) through\n `prerequisiteTaskRefs` naming the actual predecessor task refs.\n This is checked, and it is a REFUSAL rather than a note: dispatch order is computed\n from the declared prerequisites and from nothing else, so a config task that names a\n schema task in the same plan without depending on it may be dispatched first — the\n agent would author a resources-config for a schema that has not landed. Declaring\n the edge indirectly is fine (config → module → schema); leaving it out is not.\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 settings rail placement config from the accepted placement plan | `shape_user_experience` | `settings-placement-authoring` |\n| Author the sidebar, command palette or user menu placement config from the accepted placement plan | `shape_user_experience` | `config-app-shell` |\n\nBind by the FILE the surface is configured in. The settings rail is `settings-hub.config.ts`. The sidebar, the palette\nand the user menu (its `settingsEntries`) are `app-shell.config.ts`, and `settings-placement-authoring` itself sends\nwork on them to `config-app-shell`: binding it there hands the agent a skill that tells it to go elsewhere. Only\n`config-app-shell` teaches `runtimeAvailability.visibleToRoles`, which a sidebar group or entry the plan restricts to\nsome roles needs.\n\nAny task whose HOW includes **writing JSX for a bespoke surface** — a ui-behavior\nstage, a custom or composite view, an app-level screen — binds\n`frontend-component-catalog` alongside its own skill. It is what tells the coding\nagent which components the framework exports and how to spell their props; without\nit the agent builds the surface from raw `div`s and hand-written utility classes,\nbypassing the theme, the surface policy and the accessibility behaviour every\npreset carries. Do NOT bind it to a task that writes no markup (a schema stage, a\nconfig stage, a migration).\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, the owner's read and edit pages,\n and both specs coherently). The owner's UI task runs before the FK exists, so showing the\n reference on its pages is THIS task's work; say so in the objective. 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- **Never invent an endpoint.** A relationship-draft whose source or target resource no\n module declares cannot be wired, and it is not yours to repair: emit no wiring task for\n it and do not add the resource to any task. The conception owns that fault, and the\n judge's `conception-buildable` verdict sends the application back to it. A plan that\n invents the resource to wire it hides the fault the conception needs to see.\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. Write\n the cardinality WITH its direction — \"many-to-one from `customer` to\n `country-context`, customer holds the reference\" — because the draft's label is\n read source → target and a bare \"one-to-many\" cannot be wired without knowing\n which end it was read from. 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 catalog your brief\ncarries** — every installed skill's name and what it does, under \"Application-knowledge\nskills\". Every skill name you emit MUST appear there, spelled exactly. Do **not** guess a\nskill name and do not recall one: a name that is not in that list addresses no skill\nfolder, and the task bound to it cannot be dispatched.\n\n### Every requirement verb becomes a task\n\nDefault verbs (create, read, update, list, delete) are what Step 1 already gives every resource.\nEverything a requirement says the product DOES beyond them is work this step must emit.\n\n**Start with the domain plan's `lifecycles`.** Each declared transition is one `RESOURCE_OPERATION`\ntask on its resource (target `RESOURCE_STAGE` CONFIG, `operationRef` = the `transitionRef`), skill\n`resource-status-lifecycle`, ordered after that resource's config task; its objective names the\nstates it moves between and who performs it. A transition with `createsResourceRef` adds a\n`MODULE_BACKEND` task for the write that creates the target, skill `backend-custom-operation`,\nordered after both resources' config tasks. The resource's SCHEMA task objective names the status\nenum with every declared state, the `initialState` as its default, and each transition's `stampsField`,\nall excluded from create and update: a transition is the only way to move them.\nFor a resource with `lockedStates` or `finalStates`, the objective of each transition task that moves INTO\none of them also restricts the resource's UPDATE to the states that are neither locked nor final. Never plan\nthat freeze as its own `update` operation task: the scaffold already writes `update`, so such a task reads\nas built before it runs.\n\nThen read every functional requirement's acceptance criteria for verbs no lifecycle carries, and\nclassify each:\n\n| The criterion says… | Emit | Skill |\n|---|---|---|\n| a record CHANGES STATE (\"an accepted quote\", \"issue the invoice\", \"mark it paid\", \"close the case\", \"a submitted request can be approved\") | one `RESOURCE_OPERATION` per transition, on the resource whose state changes, target `RESOURCE_STAGE` (CONFIG). Its objective names the states it moves between and who may call it | `resource-status-lifecycle` |\n| one record CREATES or FILLS another (\"an accepted quote creates a job\", \"invoice the job\") | a `RESOURCE_OPERATION` on the SOURCE resource, plus a `MODULE_BACKEND` task carrying the implementation that writes the target; ordered after both resources' config tasks | `backend-custom-operation` |\n| a record must not change any more (\"an issued invoice cannot be edited\") | the objective of the `RESOURCE_OPERATION` task for the transition into that locked or final state also restricts its UPDATE to the open states (never a separate `update` task, which the scaffold already writes) | `resource-status-lifecycle` |\n| a user group may or may not do something (\"technicians cannot see invoices\") | an `APPLICATION_ROLES` task (see below), or, for core roles alone, the config tasks' objectives | `application-roles-authoring` / `resource-config-wiring` |\n| the product PRODUCES a document (\"send the quote as a PDF\", \"print the invoice\") | a `PDF_TEMPLATE` task bound to a generated-file field of that resource | `pdf-template-authoring` |\n| the product SENDS a message (\"email the customer\", \"remind the office\") | the `email-templates` generation step, and a `RESOURCE_OPERATION` task whose objective declares the notification on the operation that triggers it | `email-add-template` |\n| something is shown or computed from other records (\"the next action\", \"what is overdue\") | NOT a stored field: a view task from the experience plan, or a computed value in the owning resource's config task objective | — |\n\nA task emitted from a requirement verb is justified by that requirement: name it in `servesRefs`.\nIt is never the \"justified by nothing\" speculative work the rule further down warns about. A plan\nwhose requirements describe a workflow and which carries no `define_interaction_semantics` task is\nnot a lighter plan — it is a CRUD shell, and the reviewer reports it as a gap.\n\n**Every surface below has its own target kind and its own product kind. Use them.**\nUntil 2026-09-22 only resources had a vocabulary, so a task for any of these surfaces\neither declared no product (and could never be proven landed) or borrowed `MODULE`\nwith a product its scope could not prove. A task that squeezes a website page into a\n`MODULE` target, or declares a view with no product, is the defect this vocabulary\nreplaced — the judge reports it as a gap.\n\n- **`define_interaction_semantics`** — custom operations, lifecycle behaviour, access /\n role / scope rules, rate limits — interaction beyond the default resource verbs.\n Target `RESOURCE_STAGE` (CONFIG), product `RESOURCE_OPERATION`. Skills: the Backend and\n Resources domains of the router (`backend-custom-operation`, `rate-limit-authoring`,\n `authorization-unit-narrowing`). **Derive these from the requirements' VERBS** — read\n \"Every requirement verb becomes a task\" below before emitting anything else in this step.\n- **`shape_user_experience`** — the cross-resource UX, and you do NOT decide it here. The\n **experience plan** (`bottom_up.experience-plan`) already did: which surfaces exist, what\n each is for, which presets it reuses, and how the shell, navigation, design system and\n global views are composed. Read it and emit:\n - one task per VIEW, target `MODULE_FRONTEND` on the view's own module, product matching\n its kind (`RESOURCE_COMPOSITE_VIEW`, `RESOURCE_CUSTOM_VIEW`, `RESOURCE_CHART_VIEW`,\n `APPLICATION_VIEW`, `CUSTOM_COMPONENT`; an execution view is a `RESOURCE_CUSTOM_VIEW`\n product, which is what its file is). A composite, custom or app-level view's product\n carries the plan's `viewRef` verbatim — a ref the plan does not carry is refused as\n dangling, and the dispatch looks the view up by it; a chart names its `chartRef` and a\n component its `componentRef`. Its skill is the one its view kind names (the dispatch\n derives it from the product and loads it first). Carry the view's `reusesComponentRefs` into the task's\n objective — the presets are the decision, and an objective that drops them hands the\n agent a blank surface;\n - one task per CONFIGURATION, target `APPLICATION_FRONTEND_CONFIG` with that surface,\n product `APPLICATION_FRONTEND_CONFIG` naming the surface's own `declarationRefs`, and\n its skill the one the surface names (`config-navigation`, `config-design-system`,\n `config-app-shell`; `views-app-level` for global views — derived at dispatch too).\n When the plan decides a `home`, the `GLOBAL_VIEWS` task sets it: its objective says to make\n `homeDefinitionFactory` in `frontend/src/config/global-views.config.ts` return that home, carrying\n the home's rationale. A `VIEW` home is an application view: `{ compositeViewReference: <the view's\n ref constant> }`, and the task depends on the task that builds that view. A `RESOURCE_OPERATION`\n home is `{ resourceOperationPath: … }` naming the resource's registered type (camelCase, not the\n slug), the operation, `isOperationDefault: true`, `isBulkOperation: false` and the default variant's\n `variantKey`: the root matches all of them exactly and silently shows the welcome page on a\n mismatch. That task depends on the resource's config task. Without the home the application opens\n on the framework's welcome page whatever the plan says.\n - one task per planned MILESTONE, target `MODULE_BACKEND` on the milestone's module,\n product `APPLICATION_MILESTONE` naming its `milestoneRef`, skill\n `milestones-and-celebrations` (`EXPERIENCE_MILESTONE_SKILL_REF`). It depends on the config stage of its\n `triggerResourceRef` — the operation that earns it must exist before it can be counted.\n Carry the planned moment into the objective;\n - one task per planned piece of GUIDANCE, target `MODULE_FRONTEND` on its module, product\n `APPLICATION_GUIDANCE` naming its `guidanceKind` (the plan's `kind`) and `guidanceRef`,\n skill `guidance-onboarding-authoring` (`EXPERIENCE_GUIDANCE_SKILL_REF`, the same for both\n kinds). It depends on the milestone tasks its `gatedByMilestoneRefs` name, and on the\n resources whose operations it responds to. Carry the planned purpose and gate into the\n objective — the gate is what makes it appear at the right moment. For an\n `ONBOARDING_DOCUMENT`, also carry its `hostViewRef` — the objective must say which view\n embeds it with `EmbedOnboarding` (a view of the document's own module, so inside the task's\n scope) — and depend on that view's task when the plan builds it:\n landing proves the document is declared, not that anything shows it.\n Do not choose any of these skills yourself: every map is total over its vocabulary, and the\n build dispatch DERIVES each task's skill from its product and loads it first, whatever the\n task declares. Declare the skill the product's kind names anyway (the view skill for a view,\n `config-<surface>` for a configuration), so the plan reads right; add a second only when the\n task genuinely needs one no map would give it. With no experience plan,\n emit nothing here — an improvised surface is the state this family replaced. That\n absence is not silent: the reviewer's experience-coverage invariant records it, naming\n what the application will lack, so a build that goes ahead without the plan says so.\n (A placement DECIDED by the placement plan is Step 1b's `SHELL_PLACEMENT`, not this.)\n- **`extend_application`** — the controlled extension points where the declarative model\n is not enough:\n - a custom UI component / widget → target `MODULE_FRONTEND`, product `CUSTOM_COMPONENT`;\n skills `engine-component-registration`, `frontend-component-catalog`;\n - a PDF template / renderer → target `MODULE_BACKEND`, product `PDF_TEMPLATE`; skill\n `pdf-template-authoring` (the dispatch adds it whatever you write);\n - custom backend implementation logic → target `MODULE_BACKEND`, product the\n `RESOURCE_OPERATION` it serves; skill `backend-addon-wiring`;\n - workers and minions → you do NOT decide them here. The **integration plan**\n (`bottom_up.integration-plan`) already did: which surfaces run beside the backend, on\n which runtime, and exactly which resources a minion's tick may read and write. Read it\n and emit one task per WORKER (target `WORKER` with its `runtime`, product\n `APPLICATION_WORKER` naming its `jobRefs`, skill `worker-authoring` — both `NODE` and\n `RUST`, which is what `INTEGRATION_WORKER_SKILL_REF` holds) and one per MINION (target\n `MINION`, product `APPLICATION_MINION` naming its `behaviorRefs`, skill\n `minion-authoring`). Carry the minion's\n `readsResourceRefs` / `writesResourceRefs` into the task's objective: the whitelist\n starts DENY-ALL and an empty one keeps running, so an objective that drops them hands\n the agent a minion that looks healthy and touches nothing. The PACKAGE is composed by\n the foundation, one scenario per surface, so the task authors the BEHAVIOUR. With no\n integration plan, emit nothing here.\n - inbound channels → also decided by the **integration plan** (`inboundChannels`): work that\n ARRIVES — clients emailing documents to a matter, customers writing to a support address.\n Emit one task per declared channel: target `MODULE_BACKEND` in the module whose records the\n messages concern, product `INBOUND_CHANNEL_HANDLER` with the channel and a `handlerRef`\n (`<moduleRef>.<purpose>`), skill `inbound-channels` (the dispatch adds it whatever you write,\n so the agent is never without it). The channel's `purpose` is the task's objective, and its\n `servesRefs` are the task's. Make it depend on the tasks that register the resources the\n handler writes. The foundation already switched the receiving capability on; nothing here\n configures a provider.\n- **`connect_runtime_and_external_capabilities`** — providers and external connectors,\n and the **integration plan** decided these too: one task per PROVIDER BINDING it\n declares, target `PROVIDER_BINDING`, product `PROVIDER_BINDING` with the binding's own\n `scope`, and its skill taken from that scope through\n `INTEGRATION_PROVIDER_BINDING_SKILL_REF` — do not choose it yourself, the map is total\n over the scope vocabulary. The binding's `rationale` is the task's objective. Reach for\n `provider-operation-calls` and `configure-billing` as the task's further reading when the\n binding is one an application then CALLS. Environment and infra config are the\n foundation's, not a build task's.\n- **What the domain plan left to the engine** — its `engineRealizedRequirements` name the\n requirements met by configuration rather than a module. Each still owes configuration work:\n `APPLICATION_ROLES` → the roles task below; `NOTIFICATIONS` → the triggering operation's task\n (the verb table above); `PERSONAL_DATA` and `AUDIT_TRAIL` → the declarations in the resource\n config tasks' objectives; `BILLING` → the billing catalogue task; `GUIDANCE` → the experience\n plan's guidance tasks; `GOVERNED_DOCUMENT` → no build task (the compliance lane composes it);\n `ORGANIZATION_MEMBERSHIP` and `LOCALIZATION` → no task beyond the foundation's capabilities.\n Never emit a task that builds one of these as a resource.\n- **The application roles** — target `APPLICATION_ROLES`, when a requirement names groups of\n users with different access (\"office and field staff\", \"technicians cannot see invoices\",\n \"read-only reviewers\"). Emit ONE task (the role table is one file) producing one\n `APPLICATION_ROLE` per group that no core role covers, skill `application-roles-authoring`\n (the dispatch adds it whatever you write), and `servesRefs` naming the requirement. Reuse the\n core roles first: the broadest internal group usually holds `ORG_MEMBER`, and a requirement met by\n them alone (\"only administrators may delete\") needs no roles task, only config tasks that say which\n operations are restricted. The task declares the roles, offers them on the organization types,\n and narrows the `roles` of the operations they govern, so order it AFTER the config tasks of every\n resource it narrows, and say in its objective which operations each role may call. Never answer a\n role requirement with a resource holding roles, permissions or role assignments: nothing in the\n engine reads it.\n- **The billing catalogue** — target `BILLING_CATALOG`, and the **business model** decided it:\n its pricing plans are the products the application sells. Emit ONE task (the catalogue is one\n file, so two tasks would write over each other) producing one `APPLICATION_BILLING_PRODUCT` per\n plan, with a short `productKey` per plan (`free`, `team`, not the plan's `pricing-plan-…` ref),\n skill `configure-billing` (the dispatch adds it whatever you write), and `servesRefs` naming\n every plan it realises. Its objective carries what each plan decided, so the agent writes typed\n money rather than prose: the price and its billing period, whether it is per member or flat, and\n the three pricing-surface facts the plan implies — `isRecommended` for the plan the product is\n designed for (never because it sorts second), `priceDisclosure: STARTING_AT` when part of the\n price is not decided and `ON_REQUEST` when it is quoted, `availability: UPCOMING` when the plan\n is announced but the requirements do not yet build it. Order it after the module and resource\n tasks whose features the plans grant. The website's PRICING section task depends on it: the\n section reads this catalogue, so it must exist first. No business model, or one with no plans,\n emits nothing.\n- **Data seeds** — target `MODULE_BACKEND` on the seed's module, product `APPLICATION_DATA_SEED`,\n skill `seeding-authoring` (the dispatch adds it whatever you write). A built application must not\n open EMPTY: an empty list is not something a creator can judge, try or show. Emit two kinds, and\n never mix them in one seed:\n - **`REFERENCE`** — rows the application needs wherever it runs, in production too: a closed list\n the domain plan stores as rows rather than as an enum, a default record each organization\n starts with. Emit one only where the domain plan implies such rows; most applications need few\n or none.\n - **`DEMONSTRATION`** — sample rows that make a freshly created application look lived-in: a few\n plausible records (three to eight) for each main resource a person meets first, in the market's\n own language and examples, consistent with each other (an enquiry names a customer that exists).\n One seed per resource. The seed declares `allowedApplicationEnvironments` without production,\n and the task lands only once it does, so these rows can never sit beside real ones. A resource\n that belongs to an organization is seeded per organization, on organization creation.\n A seed whose rows point at rows ANOTHER seed writes (a contact's customer, a quote's customer, an\n invoice's job) links them with `referenceDataSeedRow` and lists that seed in `dependsOn` — the\n engine resolves each reference to the row's `_id`, and nothing else can, because the id is\n generated. Say so in the task's objective: name the seed it references and the field each\n reference fills, so the worker does not have to discover the mechanism. Order a seed after its\n resource's schema and config tasks, after the relationship tasks for the links its rows carry,\n and after the task of every seed whose rows it references. Name each `seedKey`\n `<moduleRef>:<purpose>` (`crm:demo-customers`): the namespace keeps one module's seeds apart from\n another's. Never a seed for a resource the engine owns (users, organizations, memberships).\n- **The website** — target `WEBSITE`, and you do NOT decide its content here. The\n **website plan** (`bottom_up.website-plan`) already decided it: which pages, what each\n is for, and the sections that carry each page's argument in reading order. Read it and\n emit, in this order:\n - one `WEBSITE_PAGE` task per page (`produces: { kind: WEBSITE_PAGE, pageRef }`), skill\n `website-page-authoring`, its objective the page's own purpose. A page task authors the\n PAGE — route, bridge, component, manifest, registration and an EMPTY sections list —\n and never its sections: say so in the objective. On the first run that built a website\n the page tasks wrote every section themselves, so no section skill was ever applied;\n - one `WEBSITE_SECTION` task per section (`produces: { kind: WEBSITE_SECTION, pageRef,\n sectionRef }`), **with its page's task as a prerequisite** — a section is declared in\n its page's sections file, so the page must exist first — and its skill taken from the\n section's KIND through `WEBSITE_SECTION_SKILL_REF`: `HERO` → `website-section-hero`,\n `FEATURE_BENEFIT_SUMMARY` → `website-section-feature-benefit-summary`,\n `FEATURE_DETAIL` → `website-section-feature-detail`, `PRICING` →\n `website-section-pricing`, `SOCIAL_PROOF` → `website-section-social-proof`, `FAQ` →\n `website-section-faq`, `CTA` → `website-section-cta`, `FOOTER_CTA` →\n `website-section-footer-cta`, `CONTACT` → `website-section-contact`. Name it; the\n dispatch derives the same skill from the plan and puts it first whatever you wrote, so a\n wrong one is harmless but a right one keeps the plan readable.\n A plan whose disposition is `NOT_APPLICABLE`, or no plan at all, emits NOTHING here — the\n application has no `website/` workspace for a task to write in.\n- **Technical documentation** — target `TECHNICAL_DOCUMENTATION`, and you do not choose\n the chapters here either. The **documentation plan** (`bottom_up.documentation-plan`)\n decided them: read it and emit one task per chapter, product\n `DOCUMENTATION_CHAPTER` with its `chapterRef`, skill\n `application-consumer-documentation-authoring`, and an objective carrying the chapter's\n own purpose, audiences and the specifications it documents. A `NOT_APPLICABLE` plan, or\n none, emits nothing. The portal's generated tree is never written by a task — the\n target's own policy prohibits it, because the companion publishes there.\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(Label and 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). A task serving a requirement verb\n (the table above) always earns it, even when no feature-draft mentions the operation.\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 in the application's PRIMARY locale. Order it\n after the resources / ui-behavior / views / milestones / guidance whose labels it\n generates — a milestone's title and a flow's words are generated from their declarations.\n Translation into the other enabled locales is a separate step, `i18n-translations`, which\n the dispatch host derives after this one for an application that enables more than one\n locale. Do not author it, and never make another task wait for translation: a step that\n needs labels (documentation publication, for one) needs only the primary locale.\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. Author it only when the brand brief appears in your\n inputs (it is declared as a map: what the brand holds, not its content), and order\n it after that 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. Its `servesRefs` name the brand\n elements it realises — the brief's logo direction and the brand name, by the refs the\n brand brief shows (`brand.logo-direction`, `brand.name`). Name only refs the brief holds.\n\n- **`database-migrations`** — `wildo db generate`: turns the drift the schema stages created into a\n committed migration, and advances the accepted plan with it. **PostgreSQL-backed applications\n ONLY** (`applicationDatabase: { engine: DatabaseEngine.POSTGRESQL }`); on MongoDB a collection\n appears on first write and this step must not be authored at all — it REFUSES on an application\n whose declared store is not PostgreSQL (or cannot be read), because generating there would author\n a table set nothing uses. A PostgreSQL application with no accepted plan yet is the opposite case:\n the step renders the whole model as the INITIAL migration and writes the baseline beside it, and\n the dispatch host derives that step itself when the plan omits it.\n\n Order it **after the schema stages whose drift it migrates** — practically, after the last\n resource's schema stage in the band. Author it ONCE: one step migrates all accumulated drift, and\n re-running it over a clean plan reports \"nothing to generate\" rather than writing an empty\n migration. It needs a BUILT `backend-api`, because the plan is computed by importing the compiled\n registry; it refuses on an unbuilt tree instead of authoring a migration for a model nobody has.\n\nThere is no seeds GENERATION step: do **not** author one — an unknown `generationStepRef`\nrefuses at dispatch instead of parking the build. Seeding is a CODING task: an\n`APPLICATION_DATA_SEED` product under the module's backend (Step 3, \"Data seeds\").\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- **Your answer is the WHOLE plan, never a delta.** What you return replaces the\n plan on record, so a task you leave out is deleted. On a re-run, copy every task\n that still holds into your answer unchanged, under its existing ref, and change\n only what the domain plan or a prerequisite genuinely changed: add a task, re-order\n one, or add or correct a relationship-wiring task. Every resource and relationship\n the domain plan declares must still have its tasks when you are done — a plan that\n leaves one out is refused.\n- **Keep what still holds.** Do not re-decompose modules or resources whose tasks are\n already correct; carry them over as they are.\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## Validation and product review\n\n`BuildPlanTaskGraphGeneration` constrains the generated shape. The runtime normalizes\nit into `BuildPlanTaskGraph` and runs `validateBuildPlanTaskGraph`. Cycles and missing\nrequired prerequisite edges between stages present in the graph are hard failures;\na stage absent from the graph and a coding task without products produce warnings.\nSchema checks also reject unknown prerequisite refs and duplicate product ownership.\n\nThe `build-plan-coherent` checklist below complements those structural checks with\nproduct review: resource coverage, useful objectives, meaningful products and suitable\nmethods. Since 2026-09-22 it is also this playbook's compiled evaluation treatment: the\nADVISORY judge reads its invariants against the landed build plan and the domain plan\nafter every run, and its per-criterion verdicts reach the creator's review. A verdict is\na note, never a refusal. The method declares `approve_result`; neither shape validation,\nthe judge nor approval proves the application behavior that the plan intends to deliver.\n\n## Decomposition boundary\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.** Dispatch locking and concurrency, 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`, `SHELL_PLACEMENT` 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 The `bottom_up.assemble-verify` method owns application-wide verification.\n Keep its work separate from the build targets decomposed here.\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 explicit\n `prerequisiteTaskRefs`; 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- **Framework contract design.** Use the existing `BuildPlanTaskGraph` schema and\n validator. This method authors an application plan; it does not reshape the\n framework's `_core` contracts or implement a new scheduling engine.\n\nKeep the output at decomposition depth. The dispatch and verification methods consume\nit and perform their own work; a task graph is not evidence that those runs succeeded.\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 (views,\n frontend configuration, components, PDF templates, workers, minions, provider bindings,\n website pages and sections, documentation chapters — each over its own target and\n product kind), any module-ensure tasks foundation did not cover, and the interleaved\n companion-generation steps — each carrying its target, **the artifacts it produces**,\n its one functional topic, its skill(s), and explicit `prerequisiteTaskRefs`.\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\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `resource-add-module` — the module-scaffolding vocabulary, for\n the conditional ensure-module task (only where the foundation step did not establish the\n module slice).\n- `resource-add-resource` — the resource vocabulary (the\n resource-skeleton task in the schema stage).\n- `resource-schema-authoring` — the schema stage (first\n per-resource task).\n- `resource-config-wiring` — the config stage (second\n per-resource task).\n- `resource-ui-behavior` — the ui-behavior stage (third\n per-resource task).\n- `spec-resource-update` — the spec stage (fourth per-resource\n task).\n- `module-relationships` — the relationship-wiring task's HOW\n (cardinality-to-FK-holder resolution, at dispatch time — named here, not performed).\n- `module-registration` — the cross-runtime module-registration\n task's HOW.\n- the skills CATALOG, which your brief carries as its own section — 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\nThese twelve invariants are the criteria of this playbook's compiled evaluation treatment (`application-creation:evaluation-treatment/build-plan-coherent`, one criterion per invariant, invariants 2 and 2b sharing one), which the advisory judge runs after every landing. They are kept here as creator-facing review guidance too, so a reviewer and the judge read the same words:\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 twelve 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. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product is a GAP. A plan with main resources and no `DEMONSTRATION` `APPLICATION_DATA_SEED` task is a CONCERN: the application would open empty. A seed task whose rows reference another seed's rows (a contact's customer) that is not ordered after that seed's task is a GAP — the reference resolves only against rows already written. (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. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (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 whose two endpoints are resources the domain plan declares 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. A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) 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. The migration step follows the schema stages whose drift it migrates and is not authored for MongoDB. Do NOT flag the absence of an `i18n-translations` step — the dispatch host derives it after `i18n-labels`. Do NOT flag the absence of a seeds GENERATION step — none exists; seeding is an `APPLICATION_DATA_SEED` coding task, judged under invariant (1). (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 (dispatch locking and concurrency, 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). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises) that the build would have to invent to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (9) EXPERIENCE COVERAGE — every view, configuration, milestone and piece of guidance the experience plan declares has its task (a view task carrying the plan's viewRef verbatim, an onboarding document's objective naming its hostViewRef), and a decided `home` is set by the `GLOBAL_VIEWS` task's objective (it names `homeDefinitionFactory` and the home); an entry with no task, or a decided home no objective sets, is a GAP, and an objective that drops what the plan decided for its entry (reused components, the moment, the gate) is a CONCERN. With NO experience plan the plan rightly carries none of these tasks: mark PASS and begin the note with 'NO EXPERIENCE PLAN:' naming what the application will lack — never a CONCERN or GAP, because the decomposer cannot produce an upstream family by revising. (10) ROLE COVERAGE — every requirement that names groups of users with different access is served by an `APPLICATION_ROLES` task producing one `APPLICATION_ROLE` per group no core role covers, ordered after the config tasks of the resources it narrows; a group with no role, or a role requirement answered by a task or resource that stores roles or permissions as data, is a GAP; a roles task ordered before a config task it narrows, or whose objective does not say which operations each role may call, is a CONCERN. (11) INTERACTION COVERAGE — every transition the domain plan's lifecycles declare has its `RESOURCE_OPERATION` task (and a `MODULE_BACKEND` task when it creates a resource), and every functional acceptance criterion whose verb goes beyond the default resource verbs (a state change, one record creating or filling another, a record that must stop changing, a produced document, a sent message) is served by a task of the matching kind (`RESOURCE_OPERATION`, a `MODULE_BACKEND` implementation, `PDF_TEMPLATE`, the email generation step) whose `servesRefs` name the requirement; a plan whose requirements describe a workflow and which carries no interaction task, or a state change served only by a config task that leaves the status freely editable, is a GAP; a derived value (a next action, an overdue flag) planned as a stored field is a CONCERN. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)\n",
72
110
  "skillRefs": [
73
111
  "resource-add-module",
74
112
  "resource-add-resource",