@wildo-ai/framework-knowledge 1.1.3 → 1.1.5

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 (841) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +349 -17
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  6. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.loader.js +47 -1
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
  13. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  14. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
  15. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  25. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  26. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
  27. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  28. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  29. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  30. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
  31. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  32. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
  33. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  34. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
  35. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  36. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  41. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  44. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
  45. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
  47. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
  49. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  50. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
  51. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  52. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  53. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  54. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
  55. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  56. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  57. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
  60. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  61. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  63. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
  64. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  65. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  68. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  69. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  70. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  71. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  72. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  74. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
  76. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
  78. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  80. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  81. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  82. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
  84. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
  86. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  87. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
  88. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  89. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
  90. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  92. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
  94. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  95. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
  96. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  99. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
  100. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  101. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  103. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
  104. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  105. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
  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 +191 -5
  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 +2 -1
  112. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  113. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
  114. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
  116. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  117. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
  118. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  120. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  121. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  122. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  123. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  124. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  125. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
  126. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  127. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  128. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  129. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
  130. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  131. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  132. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  133. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
  134. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  135. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  136. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  137. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
  138. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  139. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
  140. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  141. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
  142. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  143. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
  144. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
  146. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  147. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  148. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  149. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  150. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  151. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
  152. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  153. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
  154. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
  156. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  157. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
  158. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  159. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
  160. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  161. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
  162. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  163. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  164. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  165. package/dist/knowledge/manifest.json +9 -8
  166. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  167. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  168. package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
  169. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
  170. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  171. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  172. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
  173. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
  174. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  175. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  176. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
  177. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
  178. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
  179. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
  180. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
  181. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
  182. package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
  183. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
  184. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
  185. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
  186. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
  187. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
  188. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
  189. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
  190. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
  191. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
  192. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
  193. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  194. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  195. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
  196. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  197. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
  198. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
  199. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
  200. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  201. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
  202. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  203. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
  204. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  205. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  206. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
  207. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  208. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  209. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  210. package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
  211. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
  212. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  213. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  214. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
  215. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  216. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  217. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  218. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
  219. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
  220. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
  221. package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
  222. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
  223. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  224. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
  225. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  226. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  227. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
  228. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
  229. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  230. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
  231. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  232. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  233. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
  234. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
  235. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  236. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
  237. package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
  238. package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
  239. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  240. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
  241. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  242. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
  243. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  244. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
  245. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  246. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
  247. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  248. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  249. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
  250. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
  251. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  252. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  253. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  254. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
  255. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
  256. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
  257. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  258. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  259. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  260. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
  261. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
  262. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
  263. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  264. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  265. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
  266. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
  267. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  268. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
  269. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  270. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  271. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  272. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  273. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  274. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  275. package/dist/knowledge/references/application-maturity.config.md +319 -0
  276. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  277. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  278. package/dist/knowledge/references/brand.asset.config.md +8 -16
  279. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  280. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  281. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  282. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  283. package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
  284. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  285. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  286. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  287. package/dist/knowledge/references/capability-composition.config.md +155 -0
  288. package/dist/knowledge/references/cli.market.utils.md +1 -0
  289. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  290. package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
  291. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  292. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  293. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  294. package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
  295. package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
  296. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
  297. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  298. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  299. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  300. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  301. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
  302. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
  303. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  304. package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
  305. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  306. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  307. package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
  308. package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
  309. package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
  310. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
  311. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
  312. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  313. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
  314. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
  315. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
  316. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
  317. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  318. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  319. package/dist/knowledge/references/experience-plan.config.md +311 -0
  320. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
  321. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  322. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
  323. package/dist/knowledge/references/integration-plan.config.md +185 -0
  324. package/dist/knowledge/references/market.alternative.config.md +1 -1
  325. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  326. package/dist/knowledge/references/market.channel.config.md +3 -3
  327. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  328. package/dist/knowledge/references/market.gain.config.md +1 -1
  329. package/dist/knowledge/references/market.icp.config.md +2 -2
  330. package/dist/knowledge/references/market.job.config.md +1 -1
  331. package/dist/knowledge/references/market.message-template.config.md +2 -2
  332. package/dist/knowledge/references/market.objection.config.md +1 -1
  333. package/dist/knowledge/references/market.pain.config.md +1 -1
  334. package/dist/knowledge/references/market.persona.config.md +2 -2
  335. package/dist/knowledge/references/market.proof.config.md +1 -1
  336. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  337. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  338. package/dist/knowledge/references/market.trigger.config.md +1 -1
  339. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  340. package/dist/knowledge/references/placement-plan.config.md +369 -0
  341. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  342. package/dist/knowledge/references/platform.config.backing-services.md +0 -21
  343. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  344. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  345. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  346. package/dist/knowledge/references/platform.config.saas.md +261 -9
  347. package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
  348. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  349. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  350. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  351. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  352. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  353. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  354. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  355. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  356. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
  357. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  358. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  359. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
  360. package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
  361. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  362. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
  363. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  364. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
  365. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  366. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  367. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
  368. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  369. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  370. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  371. package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
  372. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  373. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  374. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  375. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  376. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  377. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  378. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  379. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
  380. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  381. package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
  382. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  383. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  384. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  385. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  386. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  387. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  388. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  389. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  390. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  391. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  392. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  393. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  394. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
  395. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  396. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  397. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
  398. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
  399. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
  400. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  401. package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
  402. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  403. package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
  404. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  405. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
  406. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
  407. package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
  408. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  409. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
  410. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  411. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  412. package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
  413. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
  414. package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
  415. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  416. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  417. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  418. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  419. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  420. package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
  421. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  422. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  423. package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
  424. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  425. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  426. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
  427. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
  428. package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
  429. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
  430. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  431. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  432. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
  433. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  434. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  435. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  436. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  437. package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
  438. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
  439. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  440. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  441. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
  442. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  443. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  444. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  445. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
  446. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  447. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  448. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  449. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  450. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  451. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  452. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  453. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  454. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  455. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  456. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  457. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  458. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  459. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  460. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
  461. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
  462. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  463. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  464. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  465. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  466. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  467. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  468. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  469. package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
  470. package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
  471. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  472. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  473. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  474. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  475. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  476. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  477. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  478. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
  479. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
  480. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
  481. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  482. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
  483. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  484. package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
  485. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
  486. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  487. package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
  488. package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
  489. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  490. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
  491. package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
  492. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  493. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  494. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  495. package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
  496. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  497. package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
  498. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  499. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  500. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  501. package/dist/knowledge/references/website-plan.config.md +205 -0
  502. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  503. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  504. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  505. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
  506. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
  507. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
  508. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  509. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  510. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  511. package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
  512. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
  513. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
  514. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  515. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  516. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  517. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  518. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
  519. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
  520. package/dist/knowledge/references/zod.factories.address.md +118 -0
  521. package/dist/knowledge/references/zod.factories.code.md +2 -0
  522. package/dist/knowledge/references/zod.factories.duration.md +2 -0
  523. package/dist/knowledge/references/zod.factories.money.md +2 -0
  524. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  525. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  526. package/dist/knowledge/registries/framework-topics.json +1215 -11
  527. package/dist/knowledge/registries/playbooks.json +454 -50
  528. package/dist/knowledge/registries/source-tags.json +3153 -1043
  529. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  530. package/dist/knowledge/rules/live-context-door.md +108 -0
  531. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  532. package/dist/knowledge/skills/INDEX.md +46 -11
  533. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
  534. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  535. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  536. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
  537. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  538. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  539. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
  540. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
  541. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
  542. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
  543. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  544. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
  545. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  546. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  547. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  548. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
  549. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
  550. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  551. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  552. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
  553. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  554. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
  555. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  556. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  557. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  558. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
  559. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
  560. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
  561. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
  562. package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
  563. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
  564. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  565. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  566. package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
  567. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  568. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  569. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  570. package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
  571. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  572. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
  573. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  574. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  575. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
  576. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
  577. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  578. package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
  579. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
  580. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
  581. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  582. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
  583. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
  584. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  585. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
  586. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
  587. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  588. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  589. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  590. package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
  591. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  592. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  593. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  594. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  595. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
  596. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  597. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
  598. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  599. package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
  600. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
  601. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
  602. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
  603. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  604. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
  605. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  606. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
  607. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
  608. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
  609. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
  610. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  611. package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
  612. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  613. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
  614. package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
  615. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
  616. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  617. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  618. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  619. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  620. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
  621. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  622. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  623. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
  624. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
  625. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
  626. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
  627. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
  628. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
  629. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  630. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  631. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
  632. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  633. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
  634. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
  635. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  636. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  637. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  638. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  639. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
  640. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
  641. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
  642. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
  643. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
  644. package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
  645. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  646. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
  647. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  648. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  649. package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
  650. package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
  651. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
  652. package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
  653. package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
  654. package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
  655. package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
  656. package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
  657. package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
  658. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
  659. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  660. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  661. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
  662. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
  663. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  664. package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
  665. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  666. package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
  667. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
  668. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
  669. package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
  670. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
  671. package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
  672. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
  673. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
  674. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
  675. package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
  676. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
  677. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
  678. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  679. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
  680. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
  681. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
  682. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  683. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  684. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  685. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  686. package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
  687. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  688. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  689. package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
  690. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
  691. package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
  692. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
  693. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
  694. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  695. package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
  696. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  697. package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
  698. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  699. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  700. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  701. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
  702. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  703. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
  704. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
  705. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  706. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
  707. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
  708. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
  709. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
  710. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
  711. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  712. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  713. package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
  714. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
  715. package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
  716. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
  717. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  718. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  719. package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
  720. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
  721. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
  722. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
  723. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
  724. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
  725. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  726. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  727. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  728. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
  729. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  730. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
  731. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  732. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
  733. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  734. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
  735. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
  736. package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
  737. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
  738. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  739. package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
  740. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
  741. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
  742. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
  743. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
  744. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  745. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  746. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  747. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
  748. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
  749. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  750. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  751. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
  752. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  753. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  754. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
  755. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
  756. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  757. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  758. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
  759. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
  760. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  761. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
  762. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  763. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  764. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  765. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  766. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
  767. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
  768. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
  769. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
  770. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
  771. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  772. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
  773. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
  774. package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
  775. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  776. package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
  777. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  778. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  779. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  780. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
  781. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
  782. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  783. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
  784. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
  785. package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
  786. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  787. package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
  788. package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
  789. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  790. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
  791. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
  792. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
  793. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  794. package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
  795. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  796. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
  797. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
  798. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  799. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
  800. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  801. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  802. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
  803. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
  804. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
  805. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
  806. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
  807. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
  808. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
  809. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
  810. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
  811. package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
  812. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  813. package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
  814. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
  815. package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
  816. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
  817. package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
  818. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
  819. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
  820. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
  821. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
  822. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
  823. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
  824. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
  825. package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
  826. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
  827. package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
  828. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
  829. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
  830. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
  831. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
  832. package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
  833. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  834. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  835. package/dist/knowledge/topic-index.json +5335 -1010
  836. package/dist/tsconfig.build.tsbuildinfo +1 -1
  837. package/dist/tsconfig.tsbuildinfo +1 -1
  838. package/package.json +4 -4
  839. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  840. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  841. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -1,4 +1,4 @@
1
- # Build Decompose — Domain Plan → Ordered Coding-Agent Task Graph (v1 scaffold)
1
+ # Build Decompose — Domain Plan → Ordered Coding-Agent Task Graph
2
2
 
3
3
  ### Target Application Framing
4
4
 
@@ -12,13 +12,10 @@ Read and apply these patterns from the application-developer point of view:
12
12
  - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
13
 
14
14
 
15
- > **This is a v1 scaffold methodology.** It is a working first cut meant to be
16
- > iterated. The decomposition heuristic, the per-resource stage order, and the
17
- > task-shape convention below are deliberately explicit so they can be tuned against
18
- > real runs — treat them as a starting rubric, not a frozen contract. The *analytical
19
- > depth* of build planning (a typed task-graph contract, a dependency-DAG solver with
20
- > transitive ordering, a collection validator, cost/effort estimation) is intentionally
21
- > shallow here and is deepened in a later phase; do not perfect it in this playbook.
15
+ The output follows the existing `BuildPlanTaskGraph` contract. The host checks its
16
+ shape and graph consistency, then uses `prerequisiteTaskRefs` to determine readiness.
17
+ Functional topics organize context; they do not create scheduling edges. Decompose
18
+ the work using the current contracts rather than designing a replacement planner.
22
19
 
23
20
  ## Where you are in the journey
24
21
 
@@ -43,8 +40,8 @@ of coding-agent tasks turns this domain plan into a running app?"* You produce *
43
40
  artifact**: the **build-plan** family — an **ordered task graph**, each task bound
44
41
  onto the **7-topic functional taxonomy** and the **app-knowledge skill catalog**.
45
42
 
46
- This is a **decomposition pass**. You name tasks, their target, their topic, their
47
- skill(s), and their ordering intent. You do **not** dispatch any task, capture any
43
+ This is a **decomposition pass**. You name tasks, their target, **what each one
44
+ produces**, their topic, their skill(s), and their ordering intent. You do **not** dispatch any task, capture any
48
45
  change-set, author any schema, or generate any code — that is the job of the
49
46
  downstream dispatch / scale playbooks and the coding agents they run.
50
47
 
@@ -67,10 +64,9 @@ anything:
67
64
  sequenced before later ones) and the **requirements** + **feature-drafts** (the
68
65
  prose contracts each task's brief points the coding agent at).
69
66
 
70
- // TODO CLI COMMAND: wildo context journey-status
71
- // (read current journey scope + approved domain plan + any existing build plan)
72
- // TODO CLI COMMAND: wildo context domain-plan
73
- // (read the module decomposition + per-module resource inventory to decompose)
67
+ (Both are already in your brief: the domain plan renders under "# Accepted application truth", and
68
+ the real module/resource state arrives as the declared `workspace_truth` context section of your brief. There is no command to
69
+ run in this mode.)
74
70
 
75
71
  You **read** `domain-plan` (incl. its relationship drafts) + `roadmap` + `requirements` +
76
72
  `feature-drafts`; you **write** the `build-plan` family.
@@ -85,6 +81,850 @@ You **read** `domain-plan` (incl. its relationship drafts) + `roadmap` + `requir
85
81
  An objective that asks to "create" or "scaffold" such a resource describes work that
86
82
  is already done, and the dispatched coding run will correctly change nothing.
87
83
 
84
+ ## Every task declares WHAT IT PRODUCES
85
+
86
+ Each task carries `produces`: the artifacts the finished application will contain
87
+ *because this task ran*. It is how the host answers **"has this task landed?"**, and
88
+ it is not optional thinking: without declared products the host cannot probe the
89
+ intended result. A COMPLETED durable run lets the loop advance, but the task remains
90
+ explicitly marked in `unverifiableLandedTaskRefs` as ran, not proven.
91
+
92
+ **`target` and `produces` answer different questions, and a task needs both.**
93
+ `target` is the WRITE SCOPE — which module tree this run may edit. Several tasks
94
+ legitimately share one. `produces` is the PRODUCT IDENTITY — what this task, and no
95
+ other, is accountable for. Wonder CRM's plan proved they cannot be the same field:
96
+ its pipeline-view task and its follow-through-operation task carry byte-identical
97
+ targets, so nothing derived from `target` could ever tell them apart, and 40 of its
98
+ 42 tasks were reported finished while none had run.
99
+
100
+ **The one rule that makes a product real: name something the SCAFFOLD does not
101
+ already contain.** Every module, every resource file and every resource
102
+ specification is written by composition before any task exists. So "the resource
103
+ config file" is not a product — it was there on day one. The VERBS it gains are.
104
+ Apply that test to every product you write.
105
+
106
+ | product | you name | use it for |
107
+ |---|---|---|
108
+ | `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 |
109
+ | `RESOURCE_REGISTRATION` | `resourceRef` + the `operationRefs` it gains | a config stage |
110
+ | `RESOURCE_UI_BEHAVIOR` | `resourceRef` | a ui-behavior stage — the one artifact composition never writes |
111
+ | `RESOURCE_SPECIFICATION` | `resourceRef` + the `fieldRefs` it documents | a spec stage. The fields again: the spec file is scaffolded too |
112
+
113
+ **A product ref is an ARTIFACT IDENTITY, not a concept.** Every `produces` entry is read back by a
114
+ LANDING PROBE that searches the application's own source for that ref — in its plain, camelCase,
115
+ PascalCase and SCREAMING_SNAKE spellings — and a task lands only when the probe finds it. So a ref
116
+ naming something that will never appear in the tree makes the task permanently unlandable, however
117
+ correctly it is built.
118
+
119
+ Measured on the first end-to-end journey run (#1273): all sixteen schema tasks declared refs like
120
+ `private-workspace-shape`, `membership-access-shape` and `one-sentence-rationale-shape` — eighteen
121
+ refs, not one of them a field. The schemas were authored correctly and committed; every task stayed
122
+ unlanded, the loop guard then refused the whole band at task one, and the board read 9 of 94 while
123
+ the work was being done.
124
+
125
+ Name what a reader will find in the file. `slug`, `description`, `archivedAt` — not the idea they
126
+ serve together. If you cannot name the fields yet, the task is not decomposed far enough to declare a
127
+ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a placeholder concept.
128
+ | `RESOURCE_RELATIONSHIP` | `relationshipRef` + `sourceResourceRef` + `targetResourceRef` | a relationship-wiring task. Both endpoints, because the scaffold already declares each resource's own edges |
129
+ | `RESOURCE_OPERATION` | `resourceRef` + `operationRef` | a custom operation |
130
+ | `APPLICATION_VIEW` | `viewRef` | an app-level view |
131
+ | `APPLICATION_DOCUMENT` | `documentRef` | a governed document the engine catalog DEFINES — see the closed list below. Never a document you name yourself |
132
+ | `APPLICATION_MODULE` | `moduleRef` | an ensure-module task. The REGISTRY entry, not the directory |
133
+ | `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 |
134
+ | `RESOURCE_COMPOSITE_VIEW` | `resourceRef` + `viewRef` | a composite view of one resource, bound in its ui-behavior's `compositeViews` |
135
+ | `RESOURCE_CUSTOM_VIEW` | `resourceRef` + `viewRef` | a custom operation view or an execution view of one resource, bound in its ui-behavior |
136
+ | `RESOURCE_CHART_VIEW` | `resourceRef` + `chartRef` | a chart view declared under the resource's `chartViews` |
137
+ | `CUSTOM_COMPONENT` | `componentRef` | a custom frontend component, registered on the module's frontend index or in the engine registrations |
138
+ | `APPLICATION_MILESTONE` | `milestoneRef` | a milestone the module declares — the experience plan's identifier, as a slug |
139
+ | `APPLICATION_GUIDANCE` | `guidanceKind` + `guidanceRef` | an onboarding document or guidance flow the module declares — the experience plan's `kind` and ref |
140
+ | `PDF_TEMPLATE` | `resourceRef` + `templateRef` | a PDF template BOUND to a resource's generated-file field (`generatedSummaryPdf`) |
141
+ | `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 |
142
+ | `APPLICATION_MINION` | `minionRef` + the `behaviorRefs` its entry file declares | a minion's tick behaviour. Same rule: `add-minion` writes the package |
143
+ | `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` |
144
+ | `WEBSITE_PAGE` | `pageRef` | a marketing page, registered in `website-root.config.ts` by its manifest |
145
+ | `WEBSITE_SECTION` | `pageRef` + `sectionRef` | one section of one page, declared in `<pageRef>.sections.tsx` |
146
+ | `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>` |
147
+
148
+ **A GOVERNED DOCUMENT is chosen from a closed list, never invented.** There are six,
149
+ and a `documentRef` names one of them in exactly this form:
150
+
151
+ ```
152
+ document:public.privacy-notice document:governance.program-handbook
153
+ document:public.service-terms document:governance.scope-system-description
154
+ document:governance.roles-responsibilities
155
+ document:governance.document-record-control
156
+ ```
157
+
158
+ A document is drafted against a BLUEPRINT — the required sections, the required
159
+ facts, the claim guards — and the blueprint is what the catalog holds. A ref outside
160
+ this list resolves to no blueprint, so the only thing a coding agent could do is
161
+ INVENT the document's structure, which its authoring skill forbids. The task is then
162
+ unbuildable by any run, and the dispatcher skips it by name rather than spending an
163
+ agent turn rediscovering that.
164
+
165
+ This is not a hypothetical constraint. A plan authored against the previous wording
166
+ of the row above — "a notice, a governance statement" — declared
167
+ `gdpr-data-handling-governance` and `terminal-access-governance`: two plausible
168
+ governance statements, neither of which names anything. Both sat permanently ready,
169
+ and the one that was dispatched spent a full turn establishing that the document does
170
+ not exist. **If the obligation you have in mind is not on this list, it belongs in a
171
+ document that IS** — GDPR data-handling scope, retention and subject rights are
172
+ `document:public.privacy-notice`'s subject matter — or it is not a build task at all.
173
+
174
+ **A cross-resource FOREIGN KEY belongs to the RELATIONSHIP task, never to the schema
175
+ task of the resource that holds it.** The domain plan makes the FK derivable — an
176
+ `ownershipIntent` of SOURCE_HOLDS_REFERENCE on `contact-company` says contact carries
177
+ `companyId` — and that is exactly why the mistake is easy: the field is derivable, so
178
+ it is tempting to declare it on the schema task that will contain it. Step 2 below
179
+ makes the relationship task the SINGLE home for cross-resource wiring, and the
180
+ `module-relationships` skill coordinates that FK across the owner's schema and config.
181
+ Declaring it in both places attributes one artifact to two tasks — the ambiguity
182
+ `produces` exists to remove, reintroduced through the field that removes it. A schema
183
+ task's products are the resource's OWN domain fields.
184
+
185
+ Two further rules the graph enforces, so authoring against them saves a rejection:
186
+
187
+ - **No two tasks may claim the same artifact.** That is what makes landing decidable.
188
+ Two tasks may both enrich one resource's schema — it is the FIELDS that must not
189
+ overlap, so split by field, never by prose.
190
+ - **A `COMPANION_GENERATION_STEP` declares NO products.** Its landing is the
191
+ generation step's own condition, computed by the companion. A product declared
192
+ beside one is refused.
193
+
194
+ Products stay SEMANTIC. You name a resource, a field, a relationship, a view — never
195
+ a path and never a command, exactly as with `target`. The host alone turns a product
196
+ into a question about the working tree.
197
+
198
+ The contract itself, so the vocabulary below is read from the source rather than
199
+ from this prose:
200
+
201
+ ## Import Origins
202
+
203
+ - `@wildo-ai/saas-specifications`
204
+
205
+ ## Source Excerpts
206
+
207
+ ### Origin Package: `@wildo-ai/saas-specifications`
208
+
209
+ ```typescript
210
+ *
211
+ * Versioning for the build-plan task-graph payload format itself. `V1` —
212
+ * initial shape (one ordered `tasks` collection with typed targets and
213
+ * declared prerequisites). The shape grows additively across versions; the
214
+ * `version` field is the explicit marker for consumers that branch on era.
215
+ */
216
+ export enum BuildPlanTaskGraphVersion {
217
+ V1 = 'v1',
218
+ }
219
+
220
+ /** Stable prefix every build-plan task ref carries; the trusted runtime stamps it, a provider supplies only the slug. */
221
+ export const BUILD_PLAN_TASK_REF_PREFIX = 'build-task-';
222
+
223
+ /**
224
+ * WHAT a build task builds — a closed vocabulary, because the host derives
225
+ * the physical mutation scope and verification policy from the target kind
226
+ * and the model must never author those powers through free text.
227
+ */
228
+ export enum BuildPlanTaskTargetKind {
229
+ /** A whole application module (its shared-lib registration, backend module and frontend module skeletons). */
230
+ MODULE = 'MODULE',
231
+ /** One build stage of one resource: schema → config → ui-behavior → spec. */
232
+ RESOURCE_STAGE = 'RESOURCE_STAGE',
233
+ /** One relationship between two resources. */
234
+ RELATIONSHIP = 'RELATIONSHIP',
235
+ /** A companion-owned deterministic generation step (labels, email templates, logo or database migrations) interleaved by the build loop, never a coding-agent run. */
236
+ COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',
237
+ /**
238
+ * Authoring one SHELL SURFACE's placement configuration from the accepted
239
+ * placement plan — the settings rail, the sidebar, the user menu or the
240
+ * command palette.
241
+ *
242
+ * Its own kind rather than a reuse of the neighbours, because none of them is
243
+ * true of it: it is not a MODULE or a RESOURCE_STAGE (it is application-wide
244
+ * and belongs to no resource), not a RELATIONSHIP, and emphatically not a
245
+ * COMPANION_GENERATION_STEP — that kind is documented as "never a coding-agent
246
+ * run" and writing `settings-hub.config.ts` is exactly a coding-agent run.
247
+ * Borrowing one would hand the host the wrong mutation scope and the wrong
248
+ * verification, which is what the closed vocabulary exists to prevent.
249
+ */
250
+ SHELL_PLACEMENT = 'SHELL_PLACEMENT',
251
+ /*
252
+ * THE NON-RESOURCE SURFACES (#1490). Until 2026-09-22 the five kinds above were the whole
253
+ * vocabulary, and every one of them is about a resource or the shell placement of one. The
254
+ * decompose method meanwhile told the planner to emit tasks for views, navigation, the design
255
+ * system, custom components, PDF templates, workers, minions, providers, the website and the
256
+ * documentation — surfaces the framework's own composition scenarios and 85 of its 111 skills
257
+ * already build. A task for any of them had no kind to declare, so it either declared none
258
+ * (landing as RAN-not-PROVEN forever) or borrowed `MODULE` with a product the module scope could
259
+ * not prove. The members below are those surfaces, one per write scope the host can derive.
260
+ */
261
+ /**
262
+ * The FRONTEND and SPECIFICATION layers of one module — its composite, custom and chart views,
263
+ * its custom components and their specifications.
264
+ *
265
+ * Narrower than `MODULE` on purpose: a view task never touches `shared-lib` or `backend-api`, so
266
+ * handing it the four-layer scope also hands it four typechecks and the FK sweep for a change
267
+ * that can only break the frontend and the specifications package.
268
+ */
269
+ MODULE_FRONTEND = 'MODULE_FRONTEND',
270
+ /**
271
+ * The BACKEND layer of one module beside its shared-lib declarations — PDF templates and their
272
+ * bindings, backend addons (services, controllers, flows-actors), email definitions.
273
+ *
274
+ * Shared-lib is in scope because a PDF template is bound to a resource FIELD the config declares
275
+ * (`generatedSummaryPdf`), and a backend addon usually declares its contract there first.
276
+ */
277
+ MODULE_BACKEND = 'MODULE_BACKEND',
278
+ /**
279
+ * ONE application-wide frontend configuration surface — navigation, the design system, the app
280
+ * shell's composition, the global views — named by {@link FrontendConfigSurface}.
281
+ *
282
+ * Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the
283
+ * shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES
284
+ * the surface itself (which sidebar sections exist, which transitions the primary zone uses,
285
+ * which palette the product carries). Same file for `APP_SHELL`, different question.
286
+ */
287
+ APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',
288
+ /** The marketing website workspace (`website/`), composed by the `add-website` scenario. Pages and sections are its products. */
289
+ WEBSITE = 'WEBSITE',
290
+ /**
291
+ * The technical-documentation workspace (`technical-doc/`) and the specification package's
292
+ * `technical-documentation/` declarations that feed it. Its generated tree is never written by a
293
+ * task: the companion publishes into it, and the coding policy prohibits it by prefix.
294
+ */
295
+ TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',
296
+ /** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */
297
+ WORKER = 'WORKER',
298
+ /** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */
299
+ MINION = 'MINION',
300
+ /**
301
+ * Declaring one provider in the application — the SaaS config's provider scopes, the backend
302
+ * package dependency, the frontend provider module and its companion contribution.
303
+ *
304
+ * Application-wide by construction: a provider binding names no module, and the four files it
305
+ * may touch are the same for every provider.
306
+ */
307
+ PROVIDER_BINDING = 'PROVIDER_BINDING',
308
+ }
309
+
310
+ /**
311
+ * WHICH application-wide frontend configuration surface a task composes — one file each, in
312
+ * `frontend/src/config/`, and the coding policy resolves the member to that file exactly as
313
+ * `SHELL_PLACEMENT` resolves a `PlacementSurface`.
314
+ *
315
+ * Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a
316
+ * subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of
317
+ * those live in one file. A configuration surface is WHICH FILE a composition task authors, and
318
+ * navigation and the design system are not places anything is placed.
319
+ */
320
+ export enum FrontendConfigSurface {
321
+ /** `frontend/src/config/navigation.config.ts` — zones, transitions, overlay appearance. */
322
+ NAVIGATION = 'NAVIGATION',
323
+ /** `frontend/src/config/design-system.config.ts` — palette, typography, shell appearance from the brand's visual tone. */
324
+ DESIGN_SYSTEM = 'DESIGN_SYSTEM',
325
+ /** `frontend/src/config/app-shell.config.ts` — top bar, sidebar sections, quick switcher: the shell's COMPOSITION, not a placement into it. */
326
+ APP_SHELL = 'APP_SHELL',
327
+ /** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */
328
+ GLOBAL_VIEWS = 'GLOBAL_VIEWS',
329
+ }
330
+
331
+ /**
332
+ * The two shapes of guidance an application gives a person, and the file each is declared in.
333
+ *
334
+ * They are distinct because they are found differently: an onboarding DOCUMENT is embedded in a
335
+ * screen (`EmbedOnboarding`) and is there whenever that screen is, while a guidance FLOW is started
336
+ * by an event and shows once. Both are listed on the owning frontend module — `onboardingViews` and
337
+ * `guidanceFlows`. Each kind has a CONVENTIONAL definitions file, which the authoring skill teaches
338
+ * and a landing probe reads for the declared ref (alongside the module's `index.ts`, where a small
339
+ * module may declare inline). A convention for generated applications: a hand-authored application
340
+ * may keep its declarations elsewhere, and then simply is not probed by a build plan.
341
+ */
342
+ export enum ApplicationGuidanceKind {
343
+ /** `frontend/src/modules/<m>/app-level-views/onboarding-views.definitions.ts` — an embedded onboarding document. */
344
+ ONBOARDING_DOCUMENT = 'ONBOARDING_DOCUMENT',
345
+ /** `frontend/src/modules/<m>/app-level-views/guidance-flows.definitions.ts` — a triggered guidance flow. */
346
+ GUIDANCE_FLOW = 'GUIDANCE_FLOW',
347
+ }
348
+
349
+ /**
350
+ * The two worker runtimes the framework composes (`add-worker-node`, `add-worker-rust`). The
351
+ * runtime decides the entry file a landing probe reads and whether a typecheck exists to run: a
352
+ * Node worker is verified by its package typecheck, a Rust worker has no TypeScript to check and
353
+ * the policy says so rather than inventing a command.
354
+ *
355
+ * Not the SaaS config's `WorkerRuntime`, which is a free-form `{ type, language }` pair an
356
+ * application authors for deployment; this is the closed set a creation run can COMPOSE.
357
+ */
358
+ export enum BuildPlanWorkerRuntime {
359
+ NODE = 'NODE',
360
+ RUST = 'RUST',
361
+ }
362
+
363
+ /**
364
+ * WHERE a provider is bound — which runtime owner's scope its declaration lands in. Each member
365
+ * is a different file, so a probe and a write grant both derive from it.
366
+ *
367
+ * Named after the SaaS config's own scope keys (`providers.scopes.backend`, `.companion`,
368
+ * `.frontendServices.app`, `.frontendServices.website`), which the `add-provider` and
369
+ * `add-file-picker-provider` scenarios write. Minion and worker scopes are deliberately absent:
370
+ * a provider reaching a minion is declared on that minion's own `providers` block and belongs to
371
+ * the {@link BuildPlanTaskTargetKind.MINION} task that builds it.
372
+ */
373
+ export enum ProviderBindingScope {
374
+ BACKEND = 'BACKEND',
375
+ COMPANION = 'COMPANION',
376
+ FRONTEND_APP = 'FRONTEND_APP',
377
+ WEBSITE = 'WEBSITE',
378
+ }
379
+
380
+ /** The per-resource build stages, in their fixed order. */
381
+ export enum BuildPlanResourceStage {
382
+ SCHEMA = 'SCHEMA',
383
+ CONFIG = 'CONFIG',
384
+ UI_BEHAVIOR = 'UI_BEHAVIOR',
385
+ SPEC = 'SPEC',
386
+ }
387
+
388
+ const SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);
389
+
390
+ /**
391
+ * The governed document a task produces, named as a COMPLIANCE-DOCUMENT CANDIDATE names it:
392
+ * `document:<namespace>.<id>`, e.g. `document:public.privacy-notice`.
393
+ *
394
+ * **This field was `SlugSchema`, and a slug cannot name a governed document — so until 2026-09-16 no
395
+ * build plan in any application could declare a document the engine catalog defines.** A slug forbids
396
+ * the colon and the dot, the catalog's definitions are `document-definition:public.privacy-notice`,
397
+ * and `selectAssuranceDocumentBlueprintForDocumentRef` joins the two namespaces by exact suffix — so
398
+ * every authored `documentRef` resolved to NO blueprint, and a blueprint is what says which sections,
399
+ * facts and claim guards the document owes. The two vocabularies were disjoint by construction.
400
+ *
401
+ * The cost is measured rather than theoretical. Wonder CRM's plan declares two such products
402
+ * (`gdpr-data-handling-governance`, `terminal-access-governance`), neither of which names anything;
403
+ * the first was dispatched, and its agent spent a full turn establishing — with a positive control —
404
+ * that the document does not exist and could only be invented, which the authoring skill forbids.
405
+ *
406
+ * The bare slug is STILL ACCEPTED, and that is deliberate rather than tidiness left undone: tightening
407
+ * this to the namespaced form alone would make every already-accepted plan carrying one fail to parse,
408
+ * and a build plan that cannot be READ stops the whole lane — the gate
409
+ * `application-creation-directive.md` forbids, for a task nobody can fix by re-running anything. A slug
410
+ * simply resolves to no blueprint, so the dispatcher skips that task with a message naming the ref,
411
+ * and the rest of the plan proceeds.
412
+ */
413
+ const DocumentProductRefSchema = z.union([
414
+ z.string().regex(/^document:[a-z0-9]+(?:-[a-z0-9]+)*\.[a-z0-9]+(?:-[a-z0-9]+)*$/),
415
+ SlugSchema,
416
+ ]);
417
+ /**
418
+ * A skill ref is the skill's FOLDER id in the app-knowledge catalog, which is
419
+ * also its `SKILL.md` frontmatter `name` — one id, kebab-case. The host refuses
420
+ * any skill name outside `[a-z0-9-]+`, so a ref that does not match this shape
421
+ * can never resolve to an installed skill.
422
+ */
423
+ const SkillRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);
424
+ const NonEmptyStringSchema = z.string().trim().min(1);
425
+
426
+ /**
427
+ * WHAT a build task PRODUCES — the artifact whose presence in the application
428
+ * proves the task is done.
429
+ *
430
+ * **This is not `target`, and the difference is the whole reason it exists.**
431
+ * `target` is a WRITE SCOPE: the host turns it into the path prefixes a run may
432
+ * mutate, and several tasks legitimately share one. `produces` is a PRODUCT
433
+ * IDENTITY: it says which artifact this task, and no other, is accountable for.
434
+ *
435
+ * Measured 2026-09-10 on Wonder CRM (issue #597): `build-task-pipeline-view`
436
+ * and `build-task-deal-follow-through-operation` carry BYTE-IDENTICAL targets
437
+ * (`{ kind: MODULE, moduleRef: 'deals' }`), and 7 of that plan's 42 tasks share
438
+ * 3 targets. Landing had been answered by narrowing the target to a module
439
+ * DIRECTORY — which `wildo compose` commits on day one, and which cannot tell
440
+ * two tasks apart even in principle. The loop reported 40 of 42 tasks landed
441
+ * while no coding task had ever run, so `dispatch-next` skipped every one of
442
+ * them and the phase-advance gate read a build that was all but complete.
443
+ *
444
+ * Like `target`, this stays SEMANTIC: a product names a resource, a field, a
445
+ * relationship or a view — never a path, and never a command. The host owns the
446
+ * translation from a product to the physical question it asks of the working
447
+ * tree, exactly as it owns the translation from a target kind to path prefixes.
448
+ * A model that could author the path could author its own mutation scope.
449
+ */
450
+ export enum BuildPlanTaskProductKind {
451
+ /**
452
+ * Named fields on one resource's schema.
453
+ *
454
+ * The shape an ENRICHMENT task needs, and the reason a product cannot always
455
+ * be "a file": every resource file already exists, written by the scaffold
456
+ * with its self-described STARTER shape, so file presence answers nothing.
457
+ * The FIELDS are what the task adds.
458
+ */
459
+ RESOURCE_SCHEMA_FIELDS = 'RESOURCE_SCHEMA_FIELDS',
460
+ /**
461
+ * One resource's declared operations — its registry presence, named by the verbs it gains.
462
+ *
463
+ * The VERBS, not the config file: `<r>.resources-config.ts` is written by the scaffold, so its
464
+ * existence is satisfied before any task runs. That is the exact shape of the defect this
465
+ * vocabulary replaces, and a kind that reproduced it would be worse than no kind at all.
466
+ */
467
+ RESOURCE_REGISTRATION = 'RESOURCE_REGISTRATION',
468
+ /** One resource's frontend ui-behavior. */
469
+ RESOURCE_UI_BEHAVIOR = 'RESOURCE_UI_BEHAVIOR',
470
+ /**
471
+ * One resource's specification, named by the fields it documents.
472
+ *
473
+ * The FIELDS, for the same reason as {@link RESOURCE_REGISTRATION}: every resource is scaffolded
474
+ * with a `*.resource.specification.ts` documenting only the starter shape, so file existence
475
+ * proves nothing about the task that was meant to enrich it.
476
+ */
477
+ RESOURCE_SPECIFICATION = 'RESOURCE_SPECIFICATION',
478
+ /** One relationship edge between two resources, named by the domain plan's `relationshipRef`. */
479
+ RESOURCE_RELATIONSHIP = 'RESOURCE_RELATIONSHIP',
480
+ /** One named custom operation on one resource. */
481
+ RESOURCE_OPERATION = 'RESOURCE_OPERATION',
482
+ /** One named application-level view. */
483
+ APPLICATION_VIEW = 'APPLICATION_VIEW',
484
+ /** One named governed application document (a compliance notice, a governance statement). */
485
+ APPLICATION_DOCUMENT = 'APPLICATION_DOCUMENT',
486
+ /** One application module, registered across the layer registries under one module identity. */
487
+ APPLICATION_MODULE = 'APPLICATION_MODULE',
488
+ /*
489
+ * THE NON-RESOURCE PRODUCTS (#1490). Each names an artifact of a surface the five target kinds
490
+ * above `MODULE_FRONTEND` could not express, and each is probed by the host from committed bytes —
491
+ * a declaration in the one file that registers it, never a directory a scenario already wrote.
492
+ */
493
+ /**
494
+ * Named declarations in ONE application-wide frontend configuration file — a sidebar section
495
+ * ref the app shell gains, a zone the navigation config declares, a token the design system sets.
496
+ *
497
+ * The DECLARATIONS, never the file: every `frontend/src/config/*.config.ts` is written by
498
+ * `wildo init`, so its presence is true before any task runs. Same reasoning as
499
+ * {@link RESOURCE_SCHEMA_FIELDS}, one level up.
500
+ */
501
+ APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',
502
+ /**
503
+ * One composite view of one resource — the cross-resource surface a resource's ui-behavior
504
+ * declares under `compositeViews`. Distinct from {@link APPLICATION_VIEW}, which is
505
+ * application-level and owned by a module rather than a resource.
506
+ */
507
+ RESOURCE_COMPOSITE_VIEW = 'RESOURCE_COMPOSITE_VIEW',
508
+ /** One custom operation or execution view of one resource, bound in its ui-behavior. */
509
+ RESOURCE_CUSTOM_VIEW = 'RESOURCE_CUSTOM_VIEW',
510
+ /** One chart view of one resource, declared under its ui-behavior's `chartViews`. */
511
+ RESOURCE_CHART_VIEW = 'RESOURCE_CHART_VIEW',
512
+ /** One custom frontend component, registered by `componentRef` in the module's or the engine's registrations. */
513
+ CUSTOM_COMPONENT = 'CUSTOM_COMPONENT',
514
+ /**
515
+ * One milestone a module declares — the moment the application recognises and celebrates.
516
+ *
517
+ * Named by its identifier, which is what the module's `milestones.ts` declares
518
+ * (`first-project-created` is spelled `FIRST_PROJECT_CREATED` there). The module FILE is not the
519
+ * product: a module may carry milestones before this task runs, and only the identifier says this
520
+ * one landed.
521
+ */
522
+ APPLICATION_MILESTONE = 'APPLICATION_MILESTONE',
523
+ /** One onboarding document or guidance flow a module declares, named by its ref. */
524
+ APPLICATION_GUIDANCE = 'APPLICATION_GUIDANCE',
525
+ /** One PDF template bound to one resource's generated-file field. */
526
+ PDF_TEMPLATE = 'PDF_TEMPLATE',
527
+ /**
528
+ * One worker's JOBS — the named handlers its entry file declares.
529
+ *
530
+ * The jobs, not the package: `add-worker-node` writes the package, so its directory proves
531
+ * nothing. What a coding task adds is behaviour, and behaviour is a symbol in the entry file.
532
+ */
533
+ APPLICATION_WORKER = 'APPLICATION_WORKER',
534
+ /** One minion's BEHAVIOURS — the named tick handlers its entry file declares. Same reasoning as the worker. */
535
+ APPLICATION_MINION = 'APPLICATION_MINION',
536
+ /** One provider declared in one runtime owner's scope. */
537
+ PROVIDER_BINDING = 'PROVIDER_BINDING',
538
+ /** One website page, registered in the website root config by its manifest. */
539
+ WEBSITE_PAGE = 'WEBSITE_PAGE',
540
+ /** One section of one website page, declared in that page's sections file. */
541
+ WEBSITE_SECTION = 'WEBSITE_SECTION',
542
+ /**
543
+ * One authored documentation chapter — a consumer guide the specifications package declares
544
+ * for the documentation portal to publish (#874's publication input).
545
+ */
546
+ DOCUMENTATION_CHAPTER = 'DOCUMENTATION_CHAPTER',
547
+ }
548
+
549
+ /**
550
+ * One artifact a task is accountable for. Closed by construction: a product the
551
+ * host cannot ask a question about is a product that can never be shown to have
552
+ * landed, so the vocabulary only grows alongside the resolver that answers it.
553
+ */
554
+ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
555
+ z.strictObject({
556
+ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS).systemEnum('BuildPlanTaskProductKind'),
557
+ resourceRef: SlugSchema,
558
+ /**
559
+ * At least one field, because a task that enriches a schema with nothing is
560
+ * the vacuity this whole field exists to stop: it would land the moment the
561
+ * scaffold existed, which is the defect being fixed.
562
+ */
563
+ fieldRefs: z.array(NonEmptyStringSchema).min(1),
564
+ }),
565
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_REGISTRATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRefs: z.array(NonEmptyStringSchema).min(1) }),
566
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),
567
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SPECIFICATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, fieldRefs: z.array(NonEmptyStringSchema).min(1) }),
568
+ z.strictObject({
569
+ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP).systemEnum('BuildPlanTaskProductKind'),
570
+ relationshipRef: SlugSchema,
571
+ /*
572
+ * The two resources the edge relates, NAMED rather than parsed out of the ref.
573
+ *
574
+ * A ref is `<source>-<target>` by convention and that convention is not invertible:
575
+ * `next-step-deal` splits as (`next`, `step-deal`) or (`next-step`, `deal`) and only the domain
576
+ * plan knows which. The domain plan already carries both, so the plan passes them on instead of
577
+ * making the host guess — a host that guesses wrong probes for a resource that does not exist
578
+ * and reports the task permanently unlanded.
579
+ */
580
+ sourceResourceRef: SlugSchema,
581
+ targetResourceRef: SlugSchema,
582
+ }),
583
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_OPERATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRef: SlugSchema }),
584
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_VIEW).systemEnum('BuildPlanTaskProductKind'), viewRef: SlugSchema }),
585
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DOCUMENT).systemEnum('BuildPlanTaskProductKind'), documentRef: DocumentProductRefSchema }),
586
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MODULE).systemEnum('BuildPlanTaskProductKind'), moduleRef: SlugSchema }),
587
+ z.strictObject({
588
+ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG).systemEnum('BuildPlanTaskProductKind'),
589
+ configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),
590
+ /** At least one, for the same vacuity reason as a schema's `fieldRefs`: the file exists on day one. */
591
+ declarationRefs: z.array(NonEmptyStringSchema).min(1),
592
+ }),
593
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),
594
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),
595
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CHART_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, chartRef: SlugSchema }),
596
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.CUSTOM_COMPONENT).systemEnum('BuildPlanTaskProductKind'), componentRef: SlugSchema }),
597
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MILESTONE).systemEnum('BuildPlanTaskProductKind'), milestoneRef: SlugSchema }),
598
+ z.strictObject({
599
+ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_GUIDANCE).systemEnum('BuildPlanTaskProductKind'),
600
+ /** Which definitions file carries it — a document and a flow live in different ones. */
601
+ guidanceKind: z.enum(ApplicationGuidanceKind).systemEnum('ApplicationGuidanceKind'),
602
+ guidanceRef: SlugSchema,
603
+ }),
604
+ z.strictObject({
605
+ kind: z.literal(BuildPlanTaskProductKind.PDF_TEMPLATE).systemEnum('BuildPlanTaskProductKind'),
606
+ resourceRef: SlugSchema,
607
+ /** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */
608
+ templateRef: NonEmptyStringSchema,
609
+ }),
610
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),
611
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),
612
+ z.strictObject({
613
+ kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),
614
+ providerRef: SlugSchema,
615
+ scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),
616
+ }),
617
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),
618
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),
619
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),
620
+ ]);
621
+ export type BuildPlanTaskProduct = z.infer<typeof BuildPlanTaskProductSchema>;
622
+
623
+ /**
624
+ * Every artifact identity a product claims — one string per artifact, not one
625
+ * per product, because a product may claim several.
626
+ *
627
+ * `RESOURCE_SCHEMA_FIELDS` is why this returns a list. Two tasks may both enrich
628
+ * one resource's schema (a domain shape and a billing concern, say), and that is
629
+ * legitimate; what must never overlap is the FIELDS. Comparing whole products
630
+ * would refuse the legitimate pair, and comparing only the resource would let two
631
+ * tasks claim one field and make landing ambiguous again.
632
+ *
633
+ * Derived from the product's own members rather than stored, and total over the
634
+ * vocabulary, so a kind added tomorrow must state its identity here or fail to
635
+ * compile — it cannot be silently treated as equal to its siblings.
636
+ */
637
+ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): readonly string[] {
638
+ switch (product.kind) {
639
+ case BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS:
640
+ return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);
641
+ case BuildPlanTaskProductKind.RESOURCE_REGISTRATION:
642
+ return product.operationRefs.map((operationRef) => `${product.kind}:${product.resourceRef}:${operationRef}`);
643
+ case BuildPlanTaskProductKind.RESOURCE_SPECIFICATION:
644
+ return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);
645
+ case BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR:
646
+ return [`${product.kind}:${product.resourceRef}`];
647
+ case BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP:
648
+ return [`${product.kind}:${product.relationshipRef}`];
649
+ case BuildPlanTaskProductKind.RESOURCE_OPERATION:
650
+ return [`${product.kind}:${product.resourceRef}:${product.operationRef}`];
651
+ case BuildPlanTaskProductKind.APPLICATION_VIEW:
652
+ return [`${product.kind}:${product.viewRef}`];
653
+ case BuildPlanTaskProductKind.APPLICATION_DOCUMENT:
654
+ /*
655
+ * The ref AS AUTHORED, so a slug and a namespaced ref are different artifact identities even
656
+ * where they mean the same document — the duplicate-artifact refusal cannot see two tasks
657
+ * claiming one document if they spell it differently. Not normalisable: a slug carries no
658
+ * namespace, so nothing can recover `public.` from `privacy-notice`. It costs nothing today
659
+ * because a slug names no catalogued document at all, and the dispatcher skips such a task.
660
+ */
661
+ return [`${product.kind}:${product.documentRef}`];
662
+ case BuildPlanTaskProductKind.APPLICATION_MODULE:
663
+ return [`${product.kind}:${product.moduleRef}`];
664
+ // One identity per DECLARATION, like schema fields: two tasks may compose one config file as
665
+ // long as they declare different things in it.
666
+ case BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG:
667
+ return product.declarationRefs.map((declarationRef) => `${product.kind}:${product.configSurface}:${declarationRef}`);
668
+ case BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW:
669
+ case BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW:
670
+ return [`${product.kind}:${product.resourceRef}:${product.viewRef}`];
671
+ case BuildPlanTaskProductKind.RESOURCE_CHART_VIEW:
672
+ return [`${product.kind}:${product.resourceRef}:${product.chartRef}`];
673
+ case BuildPlanTaskProductKind.CUSTOM_COMPONENT:
674
+ return [`${product.kind}:${product.componentRef}`];
675
+ case BuildPlanTaskProductKind.APPLICATION_MILESTONE:
676
+ return [`${product.kind}:${product.milestoneRef}`];
677
+ // The ref alone: a document and a flow sharing one ref is still one guidance identity, and the
678
+ // runtime keys a person's saved state by it — two artifacts claiming it would collide there too.
679
+ case BuildPlanTaskProductKind.APPLICATION_GUIDANCE:
680
+ return [`${product.kind}:${product.guidanceRef}`];
681
+ case BuildPlanTaskProductKind.PDF_TEMPLATE:
682
+ return [`${product.kind}:${product.resourceRef}:${product.templateRef}`];
683
+ case BuildPlanTaskProductKind.APPLICATION_WORKER:
684
+ return product.jobRefs.map((jobRef) => `${product.kind}:${product.workerRef}:${jobRef}`);
685
+ case BuildPlanTaskProductKind.APPLICATION_MINION:
686
+ return product.behaviorRefs.map((behaviorRef) => `${product.kind}:${product.minionRef}:${behaviorRef}`);
687
+ // The SCOPE is part of the identity: one provider bound on the backend and on the website is two artifacts.
688
+ case BuildPlanTaskProductKind.PROVIDER_BINDING:
689
+ return [`${product.kind}:${product.scope}:${product.providerRef}`];
690
+ case BuildPlanTaskProductKind.WEBSITE_PAGE:
691
+ return [`${product.kind}:${product.pageRef}`];
692
+ case BuildPlanTaskProductKind.WEBSITE_SECTION:
693
+ return [`${product.kind}:${product.pageRef}:${product.sectionRef}`];
694
+ case BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER:
695
+ return [`${product.kind}:${product.chapterRef}`];
696
+ default: {
697
+ const unhandled: never = product;
698
+ throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);
699
+ }
700
+ }
701
+ }
702
+
703
+ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
704
+ z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: SlugSchema }),
705
+ z.strictObject({
706
+ kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),
707
+ moduleRef: SlugSchema,
708
+ resourceRef: SlugSchema,
709
+ stage: z.enum(BuildPlanResourceStage),
710
+ }),
711
+ z.strictObject({
712
+ kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),
713
+ moduleRef: SlugSchema,
714
+ relationshipRef: SlugSchema,
715
+ }),
716
+ z.strictObject({
717
+ kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),
718
+ /** The companion generation step this task runs (e.g. i18n-labels, email-templates); resolved by the companion, never by a coding agent. */
719
+ generationStepRef: SlugSchema,
720
+ }),
721
+ z.strictObject({
722
+ kind: z.literal(BuildPlanTaskTargetKind.SHELL_PLACEMENT),
723
+ /**
724
+ * Which shell surface this task authors — the placement family's OWN
725
+ * `PlacementSurface`, deliberately not a build-plan copy of it.
726
+ *
727
+ * A copy was written first and was a defect, caught by probing the landing
728
+ * renderer rather than by any test: `PlacementAddress` discriminates on
729
+ * `surface` with `z.literal(...)` per option, so only the VALUES survive into
730
+ * the schema, and the renderer resolves a discriminator by matching that value
731
+ * SET against the exported enums. Two enums with identical values made the
732
+ * match ambiguous, the renderer correctly refused to guess an owner, and the
733
+ * address discriminator became unnameable — a landed placement plan would have
734
+ * emitted `surface: "SETTINGS_HUB"` as a bare string instead of
735
+ * `PlacementSurface.SETTINGS_HUB`. One concept, one named source.
736
+ */
737
+ surface: z.enum(PlacementSurface).systemEnum('PlacementSurface'),
738
+ }),
739
+ z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_FRONTEND), moduleRef: SlugSchema }),
740
+ z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_BACKEND), moduleRef: SlugSchema }),
741
+ z.strictObject({
742
+ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_FRONTEND_CONFIG),
743
+ configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),
744
+ }),
745
+ z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.WEBSITE) }),
746
+ z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),
747
+ z.strictObject({
748
+ kind: z.literal(BuildPlanTaskTargetKind.WORKER),
749
+ /** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */
750
+ workerRef: SlugSchema,
751
+ runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),
752
+ }),
753
+ z.strictObject({
754
+ kind: z.literal(BuildPlanTaskTargetKind.MINION),
755
+ /** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */
756
+ minionRef: SlugSchema,
757
+ }),
758
+ z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
759
+ ]);
760
+ export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
761
+
762
+ /**
763
+ * One ordered build task. It names WHAT to build and WHY; it never carries
764
+ * HOW (no paths, commands, prompts, cwd, model, profile). The host resolves
765
+ * the physical allowed/prohibited paths and the fixed verification from the
766
+ * target kind, and the installed skills from `skillRefs` against the app
767
+ * knowledge catalog.
768
+ *
769
+ * Dependency readiness is DECLARED as prerequisite task refs and RESOLVED by
770
+ * the host (a prerequisite is satisfied when its task has landed), never a
771
+ * solved DAG the model must get right.
772
+ */
773
+ export const BuildPlanTaskSchema = z.strictObject({
774
+ /** `build-task-<slug>`, stamped by the trusted runtime. */
775
+ taskRef: z.string().regex(new RegExp(`^${BUILD_PLAN_TASK_REF_PREFIX}[a-z0-9]+(?:-[a-z0-9]+)*$`)),
776
+ /**
777
+ * One sentence of intent: what this task delivers.
778
+ *
779
+ * Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also
780
+ * hold. A display decorator mutates the instance it is applied to, and the workbench gives those
781
+ * refs a receding identifier look, which the objective sentence then took too.
782
+ */
783
+ objective: z.string().trim().min(1),
784
+ target: BuildPlanTaskTargetSchema,
785
+ /**
786
+ * The artifacts this task is accountable for — what proves it done.
787
+ *
788
+ * Coding tasks should declare at least one product that composition did not already
789
+ * write. A target is a shared mutation scope; its scaffolded file is not evidence
790
+ * that this task's intended work exists. Products identify the output to probe.
791
+ *
792
+ * Empty declarations remain representable and produce the advisory
793
+ * `TASK_DECLARES_NO_PRODUCT`. The host may advance after a COMPLETED durable run,
794
+ * while naming the task in `unverifiableLandedTaskRefs`: it ran, but its output
795
+ * cannot be proven from a product declaration. An unexecuted task is not landed.
796
+ * This distinction avoids repeatedly dispatching the same unprovable task without
797
+ * presenting execution history as evidence that the intended product is correct.
798
+ *
799
+ * The ONE hard exception is a `COMPANION_GENERATION_STEP`, which must declare NONE.
800
+ * That kind already carries its own typed landed condition, owned by the
801
+ * generation-step service — a set computed asynchronously (planner units x
802
+ * enabled locales), and for the migration step a STATE rather than files. A
803
+ * product declared beside it would be read by nothing, which is the inert
804
+ * declaration this field exists to avoid. Enforced on the graph below, in both
805
+ * directions.
806
+ */
807
+ produces: z.array(BuildPlanTaskProductSchema).default([]),
808
+ /**
809
+ * Exactly ONE functional topic this task belongs to.
810
+ *
811
+ * **It does NOT drive ordering** — this said "drives cross-app ordering" until 2026-08-30 and
812
+ * nothing ever ordered by it. Sequencing is `prerequisiteTaskRefs`, resolved by the host, and it
813
+ * is the only thing that decides what may run next.
814
+ *
815
+ * What it DOES: the dispatch host stamps it into the coding-agent's task payload beside
816
+ * `skillRefs`, so the agent is told which phase of building the application this task belongs to.
817
+ * That is context an LLM reads, not a value the runtime branches on — the distinction matters,
818
+ * because a reader who believes it orders will look here for a scheduling bug that lives in the
819
+ * prerequisite graph. See issue #124.
820
+ */
821
+ functionalTopic: z.enum(MetaWorkflow_FunctionalTopic).systemEnum('MetaWorkflow_FunctionalTopic'),
822
+ /** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */
823
+ skillRefs: z.array(SkillRefSchema).min(1),
824
+ /** Task refs that must have landed first; resolved by the host, not solved by the model. */
825
+ prerequisiteTaskRefs: z.array(z.string()).default([]),
826
+ /**
827
+ * What this task is accountable to — traceability only, NEVER scope authority.
828
+ *
829
+ * The vocabulary is the five aspects `BUILD_PLAN_FAMILY_ASPECTS` declares as targets: functional
830
+ * and non-functional requirements, roadmap phases, and the vision's success criteria and
831
+ * constraints. It reads "Requirement / roadmap refs" until 2026-09-11, and the last two were added
832
+ * because the producer had been writing them all along (#629) — the generation contract asks for a
833
+ * plain string list, so nothing here has ever refused a key.
834
+ *
835
+ * A key outside those five is not rejected and must not be: this is traceability a human or a
836
+ * model wrote down, and dropping it loses the intent. The workbench renders such a key as visibly
837
+ * unresolved instead, which is what makes a producer drift legible rather than silent.
838
+ */
839
+ servesRefs: z.array(NonEmptyStringSchema).default([]),
840
+ });
841
+ export type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;
842
+
843
+ /**
844
+ * THE build-plan payload — a **single aggregate per product**: the ORDERED
845
+ * task graph that turns the accepted domain plan into buildable units.
846
+ *
847
+ * **Artifact-family id: `build-plan`.** This schema is the shape of the
848
+ * journey artifact selected by `MetaWorkflow_ArtifactSelector.family ===
849
+ * 'build-plan'` (the `family` vocabulary stays an open string owned by the
850
+ * selector surface; this note is the single place tying the SHAPE to the
851
+ * NAME). Produced by the build-decompose playbook, consumed one task at a
852
+ * time by build-dispatch (single-flight coding dispatch) and by the scale
853
+ * playbook.
854
+ *
855
+ * Invariants enforced here: unique task refs; every prerequisite names a task
856
+ * in this graph; no self-prerequisite. Cycle detection and ordering
857
+ * soundness are the deterministic validator's job (`validateBuildPlanTaskGraph`).
858
+ */
859
+ export const BuildPlanTaskGraphSchema = z.object({
860
+ version: z.enum(BuildPlanTaskGraphVersion).default(BuildPlanTaskGraphVersion.V1),
861
+ /**
862
+ * At least one task, at the SCHEMA — not merely as a validator warning. The first live playbook-loop
863
+ * run (2026-08-24) proved why: build-decompose answered `tasks: []`, which was schema-valid, passed
864
+ * `_core` validation as a mere warning, and LANDED — overwriting a completed 3-task plan with a
865
+ * vacuous artifact. Decomposing to zero tasks is a refusal ("nothing to decompose"), never an
866
+ * artifact: an empty plan carries no information a reader could act on, and the file it replaces
867
+ * does. Same vacuity class already closed on the requirements family (`functional: min(1)`).
868
+ */
869
+ tasks: z.array(BuildPlanTaskSchema).min(1),
870
+ }).superRefine((graph, context) => {
871
+ const refs = new Set<string>();
872
+ graph.tasks.forEach((task, index) => {
873
+ if (refs.has(task.taskRef)) {
874
+ context.addIssue({ code: 'custom', message: `duplicate build task ref "${task.taskRef}"`, path: ['tasks', index, 'taskRef'] });
875
+ }
876
+ refs.add(task.taskRef);
877
+ });
878
+ /*
879
+ * No two tasks claim the same artifact.
880
+ *
881
+ * This is what makes landing DECIDABLE, not a tidiness rule. If two tasks name
882
+ * one product, the host cannot tell which of them a present artifact proves —
883
+ * exactly the ambiguity that shared `target`s created, arriving through the
884
+ * field that replaced them. Enforced here rather than left to the validator
885
+ * because a graph that cannot answer "has this task landed?" is not a graph
886
+ * the loop may run at all.
887
+ */
888
+ graph.tasks.forEach((task, index) => {
889
+ const isGenerationStep = task.target.kind === BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP;
890
+ if (isGenerationStep && task.produces.length > 0) {
891
+ context.addIssue({
892
+ code: 'custom',
893
+ message: `build task "${task.taskRef}" is a companion generation step and must declare no products; its landing is the generation step's own condition`,
894
+ path: ['tasks', index, 'produces'],
895
+ });
896
+ }
897
+ });
898
+ const productOwners = new Map<string, string>();
899
+ graph.tasks.forEach((task, index) => {
900
+ task.produces.forEach((product, productIndex) => {
901
+ buildPlanTaskProductIdentities(product).forEach((identity) => {
902
+ const owner = productOwners.get(identity);
903
+ if (owner !== undefined) {
904
+ context.addIssue({
905
+ code: 'custom',
906
+ message: `build task "${task.taskRef}" claims the same artifact as "${owner}" (${identity}); an artifact is produced by exactly one task`,
907
+ path: ['tasks', index, 'produces', productIndex],
908
+ });
909
+ return;
910
+ }
911
+ productOwners.set(identity, task.taskRef);
912
+ });
913
+ });
914
+ });
915
+ graph.tasks.forEach((task, index) => {
916
+ task.prerequisiteTaskRefs.forEach((prerequisite, prerequisiteIndex) => {
917
+ if (prerequisite === task.taskRef) {
918
+ context.addIssue({ code: 'custom', message: `build task "${task.taskRef}" cannot be its own prerequisite`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });
919
+ } else if (!refs.has(prerequisite)) {
920
+ context.addIssue({ code: 'custom', message: `build task "${task.taskRef}" names an unknown prerequisite "${prerequisite}"`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });
921
+ }
922
+ });
923
+ });
924
+ });
925
+ export type BuildPlanTaskGraph = z.infer<typeof BuildPlanTaskGraphSchema>;
926
+ ```
927
+
88
928
  ## The two ordering axes
89
929
 
90
930
  Every task you emit is placed on **two ordering axes**. They are **distinct** — the
@@ -95,9 +935,14 @@ chain — so keep them separate and satisfy both:
95
935
  `Depends On`): `configure_application_foundation` → `model_domain_graph` →
96
936
  `define_interaction_semantics` → app-level `shape_user_experience` →
97
937
  `extend_application` → `connect_runtime_and_external_capabilities` →
98
- `assemble_verify_and_iterate`. You author neither the foundation (a sibling
99
- playbook, Topic 1) nor the final assemble/verify (a sibling playbook, Topic 7) —
100
- you decompose the middle bands (Topics 2–6). The edges you must respect: an
938
+ `assemble_verify_and_iterate`. You author neither the foundation nor the final
939
+ assemble/verify — you decompose the middle bands (Topics 2–6). Topic 1 IS a sibling
940
+ playbook (`bottom_up.foundation`), and Topic 7 IS one again
941
+ (`bottom_up.assemble-verify`, rebuilt under issue #147 after its producer was removed
942
+ with the verification/digest demolition). You still emit no Topic 7 task, and the reason
943
+ is structural rather than a delegation: `BuildPlanTaskTargetKind` has no verification
944
+ member, so app-wide verification cannot be expressed as a build-plan task at all — see
945
+ the verify/quality-gate exclusion below. The edges you must respect: an
101
946
  operation task after the resources it acts on; an **app-level** view / navigation
102
947
  task after the interaction semantics and resources it composes; an extension after
103
948
  the UX it extends; an integration after the resources it connects.
@@ -137,9 +982,9 @@ emit the ordered per-resource stage tasks:
137
982
  | Task | Functional topic | Skill (the HOW) |
138
983
  |---|---|---|
139
984
  | **(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` |
140
- | 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) |
985
+ | 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) |
141
986
  | 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` |
142
- | Resource `<name>` — ui-behavior (field displays / forms / enum chrome — the resource's own UX) | `shape_user_experience` | `resource-ui-behavior` |
987
+ | 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` |
143
988
  | Resource `<name>` — spec (canonical business semantics — the per-resource documentation capstone) | `model_domain_graph` | `spec-resource-update` |
144
989
 
145
990
  > **Two things this table is careful about.** (a) **`ui-behavior` is `shape_user_experience`,
@@ -156,6 +1001,25 @@ emit the ordered per-resource stage tasks:
156
1001
  > module slice where foundation genuinely did not (e.g. a module added to the plan after
157
1002
  > foundation ran).
158
1003
 
1004
+ ### The schema stage owes a migration on PostgreSQL
1005
+
1006
+ The workspace-truth section above ends with **"Where this application STORES its data"**, computed
1007
+ from the accepted schema plan and the authored store declaration. Read it, and follow what it says
1008
+ about binding `application-database-migrations` to the schema stage.
1009
+
1010
+ Do not try to find this out yourself. You have no shell and no file access: this method used to
1011
+ instruct you to run `rg -n "applicationDatabase"`, which you could not do, and what you answered
1012
+ instead was unanchored. If the section reports the store as UNKNOWN, say so in the plan and bind
1013
+ nothing — a wrong guess either way costs more than a stated gap.
1014
+
1015
+ **Do not emit a separate coding task for the migration.** Generating one is deterministic work —
1016
+ `wildo db generate` writes it — so it is not a coding-agent objective at all. It is a
1017
+ `COMPANION_GENERATION_STEP`, and Step 4 below carries its slug.
1018
+
1019
+ The application-wide backstop is the assemble/verify playbook, whose check set includes
1020
+ `check:schema-plan-in-sync`. That gate catches a missed migration; it is not a licence to omit
1021
+ the obligation here, because a build that fails at the capstone has already spent every task.
1022
+
159
1023
  Rules for a buildable domain-graph band:
160
1024
 
161
1025
  - **Cover every module and every resource** in the inventory (both `mainResources`
@@ -167,8 +1031,13 @@ Rules for a buildable domain-graph band:
167
1031
  but no ui-behavior (it has no first-class UX surface). Emit the stages the resource
168
1032
  genuinely needs, and say why a stage is omitted — do NOT pad every supporting
169
1033
  resource with a UX task it will never use.
170
- - **Respect the per-resource stage order** (schema → config → ui-behavior → spec) as
171
- prose prerequisite references on each task ("depends on: resource `<name>` — schema").
1034
+ - **Respect the per-resource stage order** (schema → config → ui-behavior → spec) through
1035
+ `prerequisiteTaskRefs` naming the actual predecessor task refs.
1036
+ This is checked, and it is a REFUSAL rather than a note: dispatch order is computed
1037
+ from the declared prerequisites and from nothing else, so a config task that names a
1038
+ schema task in the same plan without depending on it may be dispatched first — the
1039
+ agent would author a resources-config for a schema that has not landed. Declaring
1040
+ the edge indirectly is fine (config → module → schema); leaving it out is not.
172
1041
  - **State objectives against workspace reality.** A task for a resource the workspace
173
1042
  section already lists says what to ENRICH ("author the deal-pipeline stage enum and
174
1043
  amount/close-date fields the domain plan declares on `deals`"), never "create the
@@ -182,6 +1051,47 @@ Rules for a buildable domain-graph band:
182
1051
  reminder date" — is objective-writing, not field authoring; listing concrete
183
1052
  field-by-field types would be.)
184
1053
 
1054
+ ## Step 1b — Emit the shell-placement tasks (when a placement plan exists)
1055
+
1056
+ The **placement plan** decides WHERE every settings destination, resource operation
1057
+ and view sits in the shell, and why. It runs before you — it depends on the domain
1058
+ plan, not on your output, which is what keeps the two from forming a cycle. You do
1059
+ not re-decide any of it; you turn it into buildable work.
1060
+
1061
+ Emit **one task per SURFACE the plan actually places something on**, never one per
1062
+ decision — the config files are per-surface, so a task per decision would have N
1063
+ tasks editing one file:
1064
+
1065
+ | Task | Functional topic | Skill (the HOW) |
1066
+ |---|---|---|
1067
+ | Author the `<surface>` placement config from the accepted placement plan | `shape_user_experience` | `settings-placement-authoring` |
1068
+
1069
+ Any task whose HOW includes **writing JSX for a bespoke surface** — a ui-behavior
1070
+ stage, a custom or composite view, an app-level screen — binds
1071
+ `frontend-component-catalog` alongside its own skill. It is what tells the coding
1072
+ agent which components the framework exports and how to spell their props; without
1073
+ it the agent builds the surface from raw `div`s and hand-written utility classes,
1074
+ bypassing the theme, the surface policy and the accessibility behaviour every
1075
+ preset carries. Do NOT bind it to a task that writes no markup (a schema stage, a
1076
+ config stage, a migration).
1077
+
1078
+ Rules:
1079
+
1080
+ - **Target kind is `SHELL_PLACEMENT`, carrying the surface.** Not
1081
+ `COMPANION_GENERATION_STEP` — that kind is "never a coding-agent run" and this is
1082
+ one. The host derives the mutation scope from the kind, so borrowing a neighbour's
1083
+ gives the task the wrong permissions.
1084
+ - **A surface the plan places nothing on gets no task.** An empty settings rail is
1085
+ not something to author.
1086
+ - **Order after the resources and views a surface references.** Placing a resource's
1087
+ LIST in the sidebar before that resource exists is a task that cannot verify.
1088
+ - **Carry the decision, not the config.** The task names the surface and points at
1089
+ the skill; which category a destination lands in and in what order is IN the plan,
1090
+ read by the coding agent at dispatch. Do not restate placements in the objective.
1091
+ - **No placement plan? Emit nothing here and say so.** Do not invent placement — a
1092
+ guessed arrangement is exactly what the plan exists to replace, and it would be
1093
+ invisible to the reader who assumes a placement task came from a decision.
1094
+
185
1095
  ## Step 2 — Emit the relationship-wiring tasks
186
1096
 
187
1097
  For each **relationship-draft**, emit one wiring task:
@@ -211,29 +1121,129 @@ Rules:
211
1121
 
212
1122
  Once the domain graph is decomposed, emit the tasks for the later topic bands, drawn
213
1123
  from the requirements + feature-drafts. Bind each task to **one** functional topic and
214
- to the skill(s) that carry its HOW, resolved from the **skills router**
215
- (`.claude/skills/INDEX.md` in the app — the catalog index that routes a task to its
216
- skill folder). Do **not** guess a skill name; route through the index.
1124
+ to the skill(s) that carry its HOW, resolved from the **skills catalog your brief
1125
+ carries** — every installed skill's name and what it does, under "Application-knowledge
1126
+ skills". Every skill name you emit MUST appear there, spelled exactly. Do **not** guess a
1127
+ skill name and do not recall one: a name that is not in that list addresses no skill
1128
+ folder, and the task bound to it cannot be dispatched.
1129
+
1130
+ **Every surface below has its own target kind and its own product kind. Use them.**
1131
+ Until 2026-09-22 only resources had a vocabulary, so a task for any of these surfaces
1132
+ either declared no product (and could never be proven landed) or borrowed `MODULE`
1133
+ with a product its scope could not prove. A task that squeezes a website page into a
1134
+ `MODULE` target, or declares a view with no product, is the defect this vocabulary
1135
+ replaced — the judge reports it as a gap.
217
1136
 
218
1137
  - **`define_interaction_semantics`** — custom operations, lifecycle behaviour, access /
219
1138
  role / scope rules, rate limits — interaction beyond the default resource verbs.
220
- - **`shape_user_experience`** — app-level composite views, navigation, layouts, the app
221
- shell, design-system application, charts (the cross-resource UX; a resource's own
222
- field-display ui-behavior was already emitted in Step 1).
223
- - **`extend_application`** — custom UI components / widgets, custom implementation
224
- logic, PDF templates / renderers, workers / minions and other auxiliary execution
225
- surfaces (the controlled extension points where the declarative model is not enough).
226
- - **`connect_runtime_and_external_capabilities`** — providers, external connectors,
227
- billing wiring, email / notification wiring, storage, infra / environment config.
228
-
229
- (Seed authoring and the label / email generation are companion-owned generation steps —
1139
+ Target `RESOURCE_STAGE` (CONFIG), product `RESOURCE_OPERATION`. Skills: the Backend and
1140
+ Resources domains of the router (`backend-custom-operation`, `rate-limit-authoring`,
1141
+ `authorization-unit-narrowing`).
1142
+ - **`shape_user_experience`** — the cross-resource UX, and you do NOT decide it here. The
1143
+ **experience plan** (`bottom_up.experience-plan`) already did: which surfaces exist, what
1144
+ each is for, which presets it reuses, and how the shell, navigation, design system and
1145
+ global views are composed. Read it and emit:
1146
+ - one task per VIEW, target `MODULE_FRONTEND` on the view's own module, product matching
1147
+ its kind (`RESOURCE_COMPOSITE_VIEW`, `RESOURCE_CUSTOM_VIEW`, `RESOURCE_CHART_VIEW`,
1148
+ `APPLICATION_VIEW`, `CUSTOM_COMPONENT`; an execution view is a `RESOURCE_CUSTOM_VIEW`
1149
+ product, which is what its file is), and its skill taken from the kind through
1150
+ `EXPERIENCE_VIEW_SKILL_REF`. Carry the view's `reusesComponentRefs` into the task's
1151
+ objective — the presets are the decision, and an objective that drops them hands the
1152
+ agent a blank surface;
1153
+ - one task per CONFIGURATION, target `APPLICATION_FRONTEND_CONFIG` with that surface,
1154
+ product `APPLICATION_FRONTEND_CONFIG` naming the surface's own `declarationRefs`, and
1155
+ its skill from `EXPERIENCE_CONFIGURATION_SKILL_REF`.
1156
+ - one task per planned MILESTONE, target `MODULE_BACKEND` on the milestone's module,
1157
+ product `APPLICATION_MILESTONE` naming its `milestoneRef`, skill
1158
+ `milestones-and-celebrations` (`EXPERIENCE_MILESTONE_SKILL_REF`). It depends on the config stage of its
1159
+ `triggerResourceRef` — the operation that earns it must exist before it can be counted.
1160
+ Carry the planned moment into the objective;
1161
+ - one task per planned piece of GUIDANCE, target `MODULE_FRONTEND` on its module, product
1162
+ `APPLICATION_GUIDANCE` naming its `guidanceKind` (the plan's `kind`) and `guidanceRef`,
1163
+ skill `guidance-onboarding-authoring` (`EXPERIENCE_GUIDANCE_SKILL_REF`, the same for both
1164
+ kinds). It depends on the milestone tasks its `gatedByMilestoneRefs` name, and on the
1165
+ resources whose operations it responds to. Carry the planned purpose and gate into the
1166
+ objective — the gate is what makes it appear at the right moment. For an
1167
+ `ONBOARDING_DOCUMENT`, also carry its `hostViewRef` — the objective must say which view
1168
+ embeds it with `EmbedOnboarding` (a view of the document's own module, so inside the task's
1169
+ scope) — and depend on that view's task when the plan builds it:
1170
+ landing proves the document is declared, not that anything shows it.
1171
+ Do not choose any of these skills yourself: every map is total over its vocabulary, which
1172
+ is what makes the view, configuration, milestone and guidance skills reachable. With no experience plan,
1173
+ emit nothing here — an improvised surface is the state this family replaced.
1174
+ (A placement DECIDED by the placement plan is Step 1b's `SHELL_PLACEMENT`, not this.)
1175
+ - **`extend_application`** — the controlled extension points where the declarative model
1176
+ is not enough:
1177
+ - a custom UI component / widget → target `MODULE_FRONTEND`, product `CUSTOM_COMPONENT`;
1178
+ skills `engine-component-registration`, `frontend-component-catalog`;
1179
+ - a PDF template / renderer → target `MODULE_BACKEND`, product `PDF_TEMPLATE`; skill
1180
+ `pdf-template-authoring`;
1181
+ - custom backend implementation logic → target `MODULE_BACKEND`, product the
1182
+ `RESOURCE_OPERATION` it serves; skill `backend-addon-wiring`;
1183
+ - workers and minions → you do NOT decide them here. The **integration plan**
1184
+ (`bottom_up.integration-plan`) already did: which surfaces run beside the backend, on
1185
+ which runtime, and exactly which resources a minion's tick may read and write. Read it
1186
+ and emit one task per WORKER (target `WORKER` with its `runtime`, product
1187
+ `APPLICATION_WORKER` naming its `jobRefs`, skill `worker-authoring` — both `NODE` and
1188
+ `RUST`, which is what `INTEGRATION_WORKER_SKILL_REF` holds) and one per MINION (target
1189
+ `MINION`, product `APPLICATION_MINION` naming its `behaviorRefs`, skill
1190
+ `minion-authoring`). Carry the minion's
1191
+ `readsResourceRefs` / `writesResourceRefs` into the task's objective: the whitelist
1192
+ starts DENY-ALL and an empty one keeps running, so an objective that drops them hands
1193
+ the agent a minion that looks healthy and touches nothing. The PACKAGE is composed by
1194
+ the foundation, one scenario per surface, so the task authors the BEHAVIOUR. With no
1195
+ integration plan, emit nothing here.
1196
+ - **`connect_runtime_and_external_capabilities`** — providers and external connectors,
1197
+ and the **integration plan** decided these too: one task per PROVIDER BINDING it
1198
+ declares, target `PROVIDER_BINDING`, product `PROVIDER_BINDING` with the binding's own
1199
+ `scope`, and its skill taken from that scope through
1200
+ `INTEGRATION_PROVIDER_BINDING_SKILL_REF` — do not choose it yourself, the map is total
1201
+ over the scope vocabulary. The binding's `rationale` is the task's objective. Reach for
1202
+ `provider-operation-calls` and `configure-billing` as the task's further reading when the
1203
+ binding is one an application then CALLS. Environment and infra config are the
1204
+ foundation's, not a build task's.
1205
+ - **The website** — target `WEBSITE`, and you do NOT decide its content here. The
1206
+ **website plan** (`bottom_up.website-plan`) already decided it: which pages, what each
1207
+ is for, and the sections that carry each page's argument in reading order. Read it and
1208
+ emit, in this order:
1209
+ - one `WEBSITE_PAGE` task per page (`produces: { kind: WEBSITE_PAGE, pageRef }`), skill
1210
+ `website-page-authoring`, its objective the page's own purpose;
1211
+ - one `WEBSITE_SECTION` task per section (`produces: { kind: WEBSITE_SECTION, pageRef,
1212
+ sectionRef }`), **with its page's task as a prerequisite** — a section is declared in
1213
+ its page's sections file, so the page must exist first — and its skill taken from the
1214
+ section's KIND through `WEBSITE_SECTION_SKILL_REF` (`HERO` →
1215
+ `website-section-hero`, `PRICING` → `website-section-pricing`, and so on). Do not
1216
+ choose that skill yourself: the map is total over the section vocabulary, which is what
1217
+ makes all nine section skills reachable.
1218
+ A plan whose disposition is `NOT_APPLICABLE`, or no plan at all, emits NOTHING here — the
1219
+ application has no `website/` workspace for a task to write in.
1220
+ - **Technical documentation** — target `TECHNICAL_DOCUMENTATION`, and you do not choose
1221
+ the chapters here either. The **documentation plan** (`bottom_up.documentation-plan`)
1222
+ decided them: read it and emit one task per chapter, product
1223
+ `DOCUMENTATION_CHAPTER` with its `chapterRef`, skill
1224
+ `application-consumer-documentation-authoring`, and an objective carrying the chapter's
1225
+ own purpose, audiences and the specifications it documents. A `NOT_APPLICABLE` plan, or
1226
+ none, emits nothing. The portal's generated tree is never written by a task — the
1227
+ target's own policy prohibits it, because the companion publishes there.
1228
+
1229
+ ## Posture constraints are work, not commentary
1230
+
1231
+ The vision family's compliance posture and constraints are INPUT on equal footing with the
1232
+ requirements: an obligation the posture states — a retention/erasure rule over customer data, a
1233
+ terminal-access (cookie/telemetry) posture, an operational-vs-marketing email distinction — needs a
1234
+ task that lands it, serving the nfr it substantiates. Do not compress a posture into an adjective
1235
+ inside another task's objective ("GDPR-appropriate handling"): an adjective is not schedulable,
1236
+ reviewable or landable. If the posture states an obligation and no task expresses it, the
1237
+ decomposition is incomplete.
1238
+
1239
+ (Label and email generation are companion-owned generation steps —
230
1240
  see Step 4 — not coding-agent extension tasks.)
231
1241
 
232
1242
  Rules:
233
1243
 
234
1244
  - **Every task names a real topic + a real skill.** A task with an invented topic or a
235
1245
  skill folder that does not exist is a GAP (the dispatch playbook would have nothing
236
- to run). Route through the skills index; do not invent.
1246
+ to run). Route through the declared `skill_catalog` context section of your brief; do not invent.
237
1247
  - **Respect the topic dependency edges.** An operation task after the resources it acts
238
1248
  on; an app-level view / navigation task after the interaction semantics **and** every
239
1249
  resource it composes; an extension after the UX it extends; an integration after the
@@ -252,9 +1262,33 @@ closed vocabulary; any other slug refuses at dispatch) — and **order them afte
252
1262
  surfaces whose output they consume**:
253
1263
 
254
1264
  - **`i18n-labels`** — label generation + translation to every enabled locale. Order it
255
- after the resources / ui-behavior / views whose labels it generates.
1265
+ after the resources / ui-behavior / views / milestones / guidance whose labels it
1266
+ generates — a milestone's title and a flow's words are generated from their declarations.
256
1267
  - **`email-templates`** — email template + label generation and label translation.
257
1268
  Order it after the notification/email surfaces it renders.
1269
+ - **`logo`** — the brand mark: an expert panel derives creative directions, marks are
1270
+ generated, a vision judge scores them, and the winner is promoted into the
1271
+ specifications brand SSOT. Author it only when the brand brief appears in your
1272
+ inputs (it is declared as a map: what the brand holds, not its content), and order
1273
+ it after that brief exists; it depends on no
1274
+ code surface, so it may run early and in parallel with resource work. Author it at
1275
+ most once — an application has one accepted mark, and the step skips itself without
1276
+ calling a model when one is already accepted.
1277
+
1278
+ - **`database-migrations`** — `wildo db generate`: turns the drift the schema stages created into a
1279
+ committed migration, and advances the accepted plan with it. **PostgreSQL-backed applications
1280
+ ONLY** (`applicationDatabase: { engine: DatabaseEngine.POSTGRESQL }`); on MongoDB a collection
1281
+ appears on first write and this step must not be authored at all — it REFUSES on an application
1282
+ whose declared store is not PostgreSQL (or cannot be read), because generating there would author
1283
+ a table set nothing uses. A PostgreSQL application with no accepted plan yet is the opposite case:
1284
+ the step renders the whole model as the INITIAL migration and writes the baseline beside it, and
1285
+ the dispatch host derives that step itself when the plan omits it.
1286
+
1287
+ Order it **after the schema stages whose drift it migrates** — practically, after the last
1288
+ resource's schema stage in the band. Author it ONCE: one step migrates all accumulated drift, and
1289
+ re-running it over a clean plan reports "nothing to generate" rather than writing an empty
1290
+ migration. It needs a BUILT `backend-api`, because the plan is computed by importing the compiled
1291
+ registry; it refuses on an unbuilt tree instead of authoring a migration for a model nobody has.
258
1292
 
259
1293
  Seed generation joins this vocabulary when its companion pipeline exists. Until then,
260
1294
  do **not** author a seeds generation step — an unknown `generationStepRef` refuses at
@@ -276,19 +1310,23 @@ playbook's job — see the boundary below).
276
1310
  task that is actually in the plan. If you remove or rename a task, follow it into
277
1311
  every prerequisite reference.
278
1312
 
279
- ## Quality gate — `build-plan-coherent` (declarative at scaffold depth)
1313
+ ## Validation and product review
280
1314
 
281
- The build plan is checked against the `build-plan-coherent` **reviewer checklist** (see the end of this method):
282
- seven invariants (module + resource coverage, task well-formedness, per-resource stage
283
- order, topic dependency order, relationship coverage, companion-generation interleave,
284
- and decomposition-depth boundary discipline), each marked PASS / CONCERN / GAP.
1315
+ `BuildPlanTaskGraphGeneration` constrains the generated shape. The runtime normalizes
1316
+ it into `BuildPlanTaskGraph` and runs `validateBuildPlanTaskGraph`. Cycles and missing
1317
+ required prerequisite edges between stages present in the graph are hard failures;
1318
+ a stage absent from the graph and a coding task without products produce warnings.
1319
+ Schema checks also reject unknown prerequisite refs and duplicate product ownership.
285
1320
 
286
- This checklist is **declarative**: no runtime executes it (rubric-only judge gates were retired at the flexible-intelligence hard cut — judgment runs only through a compiled Evaluation Treatment, and this playbook has none yet), so it ships as the **creator's review checklist** — nothing runs it automatically. The **trust floor** for accepting the build plan today is the
287
- creator's `approve_result` review of the produced task graph. There is intentionally
288
- **no deterministic gate**: no typed build-task-graph contract or collection validator
289
- exists at this phase (see the boundary below).
1321
+ The `build-plan-coherent` checklist below complements those structural checks with
1322
+ product review: resource coverage, useful objectives, meaningful products and suitable
1323
+ methods. Since 2026-09-22 it is also this playbook's compiled evaluation treatment: the
1324
+ ADVISORY judge reads its invariants against the landed build plan and the domain plan
1325
+ after every run, and its per-criterion verdicts reach the creator's review. A verdict is
1326
+ a note, never a refusal. The method declares `approve_result`; neither shape validation,
1327
+ the judge nor approval proves the application behavior that the plan intends to deliver.
290
1328
 
291
- ## Scaffold-depth boundary (deferred to a later depth phase, or owned by a sibling)
1329
+ ## Decomposition boundary
292
1330
 
293
1331
  Keep this playbook at decomposition depth. Explicitly **out of scope here**:
294
1332
 
@@ -300,36 +1338,40 @@ Keep this playbook at decomposition depth. Explicitly **out of scope here**:
300
1338
  are the dispatch playbook's concern — NOT modelled here. A task that describes *how* it
301
1339
  is captured or locked is out of this playbook's depth.
302
1340
  - **Verify / quality-gate mechanics.** Running typecheck, validators, tests, or reviewer
303
- agents *around* a dispatched task is the dispatch playbook's verify step, and the app-wide
304
- assemble / verify phase (Topic 7) is its own sibling playbook — you emit **neither**. You
305
- decompose Topics 2–6 only.
1341
+ agents *around* a dispatched task is the dispatch playbook's verify step — you do not model it.
1342
+ The app-wide assemble / verify phase (Topic 7) you also do not emit, and the reason is
1343
+ STRUCTURAL rather than delegation: a build-plan task's `target.kind` is one of `MODULE`,
1344
+ `RESOURCE_STAGE`, `RELATIONSHIP`, `SHELL_PLACEMENT` or `COMPANION_GENERATION_STEP`, and none of them can express
1345
+ "verify the assembled application". There is no vocabulary for it, so a task claiming to do it
1346
+ would be a task no executor could run.
1347
+ The `bottom_up.assemble-verify` method owns application-wide verification.
1348
+ Keep its work separate from the build targets decomposed here.
306
1349
  - **Multi-agent scale + interleaving.** Parallelising tasks across multiple coding
307
1350
  agents, and interleaving the companion generation steps concurrently with coding-agent
308
- runs, is the **scale** playbook. You produce a linear-enough ordered graph with prose
309
- prerequisite intent; you do NOT solve the concurrency schedule.
1351
+ runs, is the **scale** playbook. You produce a linear-enough ordered graph with explicit
1352
+ `prerequisiteTaskRefs`; you do NOT solve the concurrency schedule.
310
1353
  - **Schema / field authoring + code generation.** You name resources and stages; you do
311
1354
  NOT author fields, enums, decorators, Zod schemas, or any code, and you do NOT resolve
312
1355
  a cardinality intent into a concrete FK. That is the coding agent at dispatch time.
313
- - **A typed build-task-graph contract + a collection validator.** The `build-plan`
314
- family has **no schemaRef** because the framework ships no `_core` build-task-graph
315
- shape, and it has no deterministic gate because no task-graph validator exists. A typed
316
- task contract, a dependency-DAG solver, and a module-set coverage validator are all a
317
- filed depth-phase item — do **NOT** reshape `_core` here.
1356
+ - **Framework contract design.** Use the existing `BuildPlanTaskGraph` schema and
1357
+ validator. This method authors an application plan; it does not reshape the
1358
+ framework's `_core` contracts or implement a new scheduling engine.
318
1359
 
319
- If you find yourself perfecting any of the above, stop and leave the slice at
320
- decomposition depth — depth is a dedicated later pass, and dispatch/scale are sibling
321
- playbooks.
1360
+ Keep the output at decomposition depth. The dispatch and verification methods consume
1361
+ it and perform their own work; a task graph is not evidence that those runs succeeded.
322
1362
 
323
1363
  ## What you emit
324
1364
 
325
1365
  One artifact for this journey:
326
1366
 
327
- - The **build-plan** at `.wildo-saas/journey/<journeyId>/build-plan/` — an ordered task
1367
+ - The **build-plan** at `specifications/src/build-plan/index.ts` — an ordered task
328
1368
  graph: the per-resource (schema / config / ui-behavior / spec) tasks, the
329
- relationship-wiring tasks, the interaction / UX / extension / integration tasks, any
330
- module-ensure tasks foundation did not cover, and the interleaved companion-generation
331
- steps — each carrying its target, its one functional topic, its skill(s), and its prose
332
- ordering intent.
1369
+ relationship-wiring tasks, the interaction / UX / extension / integration tasks (views,
1370
+ frontend configuration, components, PDF templates, workers, minions, provider bindings,
1371
+ website pages and sections, documentation chapters — each over its own target and
1372
+ product kind), any module-ensure tasks foundation did not cover, and the interleaved
1373
+ companion-generation steps — each carrying its target, **the artifacts it produces**,
1374
+ its one functional topic, its skill(s), and explicit `prerequisiteTaskRefs`.
333
1375
 
334
1376
  The creator reviews the result (approval posture `approve_result`) before it is accepted
335
1377
  as the journey's build plan, which the dispatch-orchestration and scale playbooks then
@@ -337,31 +1379,35 @@ turn into dispatched, verified coding-agent runs.
337
1379
 
338
1380
  ## References
339
1381
 
340
- - `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,
1382
+ These are skill FOLDERS installed in the application, named so each piece of work has an
1383
+ authoring contract a later coding agent can open. This step has no tools and does not open them;
1384
+ what reaches you is this method, your declared inputs, and the brief's own sections.
1385
+
1386
+ - `journey-status` — read the current journey state and scope,
341
1387
  and confirm the approved domain plan is in place to decompose the build from.
342
- - `.claude/skills/resource-add-module/SKILL.md` — the module-scaffolding vocabulary, for
1388
+ - `resource-add-module` — the module-scaffolding vocabulary, for
343
1389
  the conditional ensure-module task (only where the foundation step did not establish the
344
1390
  module slice).
345
- - `.claude/skills/resource-add-resource/SKILL.md` — the resource vocabulary (the
1391
+ - `resource-add-resource` — the resource vocabulary (the
346
1392
  resource-skeleton task in the schema stage).
347
- - `.claude/skills/resource-schema-authoring/SKILL.md` — the schema stage (first
1393
+ - `resource-schema-authoring` — the schema stage (first
348
1394
  per-resource task).
349
- - `.claude/skills/resource-config-wiring/SKILL.md` — the config stage (second
1395
+ - `resource-config-wiring` — the config stage (second
350
1396
  per-resource task).
351
- - `.claude/skills/resource-ui-behavior/SKILL.md` — the ui-behavior stage (third
1397
+ - `resource-ui-behavior` — the ui-behavior stage (third
352
1398
  per-resource task).
353
- - `.claude/skills/spec-resource-update/SKILL.md` — the spec stage (fourth per-resource
1399
+ - `spec-resource-update` — the spec stage (fourth per-resource
354
1400
  task).
355
- - `.claude/skills/module-relationships/SKILL.md` — the relationship-wiring task's HOW
1401
+ - `module-relationships` — the relationship-wiring task's HOW
356
1402
  (cardinality-to-FK-holder resolution, at dispatch time — named here, not performed).
357
- - `.claude/skills/module-registration/SKILL.md` — the cross-runtime module-registration
1403
+ - `module-registration` — the cross-runtime module-registration
358
1404
  task's HOW.
359
- - `.claude/skills/INDEX.md` — the skills router: consult it to bind each interaction /
1405
+ - the skills CATALOG, which your brief carries as its own section — the skills router: consult it to bind each interaction /
360
1406
  UX / extension / integration task to its real skill folder from the full catalog. Do
361
1407
  not invent skill names; route through the index.
362
1408
 
363
1409
  ## Reviewer checklist — `build-plan-coherent`
364
1410
 
365
- Formerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:
1411
+ These eight 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:
366
1412
 
367
- Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess seven invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. Do NOT flag the absence of a seeds step — seed generation has no companion pipeline yet and must not be authored. (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (single-flight locking, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)
1413
+ Judge 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 eight invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (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 has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, 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). (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)