@wildo-ai/framework-knowledge 1.1.4 → 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 (848) 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 +227 -6
  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/framework-knowledge.schemas.d.ts.map +1 -1
  10. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  11. package/dist/esm/index.d.ts.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  13. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
  17. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  18. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
  19. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  20. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
  21. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
  23. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
  25. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
  27. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  31. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  32. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
  33. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  36. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
  37. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  38. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
  39. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  40. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
  41. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  42. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  43. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
  45. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  47. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  48. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
  49. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  50. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
  51. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
  53. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
  55. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  56. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
  57. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  58. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  59. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  60. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
  61. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  62. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  63. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
  65. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
  67. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  68. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
  69. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  70. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
  71. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  72. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
  73. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  74. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  75. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  76. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  77. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  78. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  79. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  81. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  82. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
  83. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
  85. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  87. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  88. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  89. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  90. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
  91. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
  93. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
  95. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
  97. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  99. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
  101. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
  103. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
  105. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
  107. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  108. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
  109. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  110. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
  111. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
  113. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  114. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
  115. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  116. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
  117. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  118. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
  119. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
  121. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  122. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
  123. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  124. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
  125. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  126. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  127. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  128. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  129. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  130. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  131. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  132. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
  133. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  134. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  135. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  136. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
  137. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  138. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  139. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  140. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
  141. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  142. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  143. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  144. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
  145. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  146. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
  147. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  148. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
  149. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  150. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
  151. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  152. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
  153. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  154. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  155. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  156. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  157. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  158. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
  159. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  160. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
  161. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  162. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
  163. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  164. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
  165. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  166. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
  167. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  168. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
  169. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  170. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  171. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  172. package/dist/knowledge/manifest.json +9 -8
  173. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  174. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  175. package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
  176. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
  177. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  178. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  179. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
  180. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
  181. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  182. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  183. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
  184. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
  185. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
  186. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
  187. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
  188. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
  189. package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
  190. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
  191. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
  192. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
  193. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
  194. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
  195. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
  196. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
  197. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
  198. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
  199. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
  200. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  201. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  202. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
  203. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  204. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
  205. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
  206. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
  207. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  208. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
  209. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  210. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
  211. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  212. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  213. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
  214. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  215. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  216. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  217. package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
  218. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
  219. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  220. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  221. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
  222. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  223. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  224. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  225. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
  226. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
  227. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
  228. package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
  229. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
  230. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  231. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
  232. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  233. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  234. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
  235. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
  236. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  237. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
  238. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  239. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  240. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
  241. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
  242. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  243. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
  244. package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
  245. package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
  246. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  247. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
  248. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  249. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
  250. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  251. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
  252. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  253. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
  254. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  255. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  256. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
  257. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
  258. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  259. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  260. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  261. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
  262. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
  263. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
  264. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  265. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  266. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  267. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
  268. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
  269. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
  270. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  271. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  272. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
  273. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
  274. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  275. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
  276. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  277. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  278. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  279. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  280. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  281. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  282. package/dist/knowledge/references/application-maturity.config.md +319 -0
  283. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  284. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  285. package/dist/knowledge/references/brand.asset.config.md +8 -16
  286. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  287. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  288. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  289. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  290. package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
  291. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  292. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  293. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  294. package/dist/knowledge/references/capability-composition.config.md +155 -0
  295. package/dist/knowledge/references/cli.market.utils.md +1 -0
  296. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  297. package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
  298. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  299. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  300. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  301. package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
  302. package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
  303. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
  304. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  305. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  306. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  307. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  308. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
  309. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
  310. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  311. package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
  312. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  313. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  314. package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
  315. package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
  316. package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
  317. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
  318. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
  319. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  320. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
  321. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
  322. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
  323. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
  324. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  325. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  326. package/dist/knowledge/references/experience-plan.config.md +311 -0
  327. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
  328. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  329. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
  330. package/dist/knowledge/references/integration-plan.config.md +185 -0
  331. package/dist/knowledge/references/market.alternative.config.md +1 -1
  332. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  333. package/dist/knowledge/references/market.channel.config.md +3 -3
  334. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  335. package/dist/knowledge/references/market.gain.config.md +1 -1
  336. package/dist/knowledge/references/market.icp.config.md +2 -2
  337. package/dist/knowledge/references/market.job.config.md +1 -1
  338. package/dist/knowledge/references/market.message-template.config.md +2 -2
  339. package/dist/knowledge/references/market.objection.config.md +1 -1
  340. package/dist/knowledge/references/market.pain.config.md +1 -1
  341. package/dist/knowledge/references/market.persona.config.md +2 -2
  342. package/dist/knowledge/references/market.proof.config.md +1 -1
  343. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  344. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  345. package/dist/knowledge/references/market.trigger.config.md +1 -1
  346. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  347. package/dist/knowledge/references/placement-plan.config.md +369 -0
  348. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  349. package/dist/knowledge/references/platform.config.backing-services.md +0 -21
  350. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  351. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  352. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  353. package/dist/knowledge/references/platform.config.saas.md +261 -9
  354. package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
  355. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  356. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  357. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  358. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  359. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  360. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  361. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  362. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  363. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
  364. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  365. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  366. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
  367. package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
  368. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  369. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
  370. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  371. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
  372. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  373. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  374. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
  375. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  376. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  377. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  378. package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
  379. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  380. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  381. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  382. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  383. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  384. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  385. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  386. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
  387. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  388. package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
  389. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  390. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  391. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  392. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  393. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  394. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  395. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  396. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  397. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  398. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  399. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  400. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  401. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
  402. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  403. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  404. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
  405. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
  406. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
  407. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  408. package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
  409. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  410. package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
  411. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  412. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
  413. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
  414. package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
  415. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  416. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
  417. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  418. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  419. package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
  420. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
  421. package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
  422. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  423. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  424. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  425. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  426. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  427. package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
  428. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  429. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  430. package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
  431. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  432. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  433. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
  434. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
  435. package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
  436. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
  437. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  438. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  439. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
  440. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  441. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  442. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  443. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  444. package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
  445. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
  446. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  447. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  448. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
  449. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  450. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  451. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  452. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
  453. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  454. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  455. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  456. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  457. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  458. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  459. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  460. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  461. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  462. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  463. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  464. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  465. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  466. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  467. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
  468. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
  469. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  470. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  471. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  472. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  473. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  474. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  475. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  476. package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
  477. package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
  478. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  479. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  480. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  481. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  482. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  483. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  484. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  485. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
  486. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
  487. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
  488. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  489. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
  490. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  491. package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
  492. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
  493. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  494. package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
  495. package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
  496. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  497. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
  498. package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
  499. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  500. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  501. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  502. package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
  503. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  504. package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
  505. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  506. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  507. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  508. package/dist/knowledge/references/website-plan.config.md +205 -0
  509. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  510. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  511. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  512. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
  513. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
  514. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
  515. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  516. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  517. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  518. package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
  519. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
  520. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
  521. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  522. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  523. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  524. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  525. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
  526. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
  527. package/dist/knowledge/references/zod.factories.address.md +118 -0
  528. package/dist/knowledge/references/zod.factories.code.md +2 -0
  529. package/dist/knowledge/references/zod.factories.duration.md +2 -0
  530. package/dist/knowledge/references/zod.factories.money.md +2 -0
  531. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  532. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  533. package/dist/knowledge/registries/framework-topics.json +1215 -11
  534. package/dist/knowledge/registries/playbooks.json +454 -50
  535. package/dist/knowledge/registries/source-tags.json +3153 -1043
  536. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  537. package/dist/knowledge/rules/live-context-door.md +108 -0
  538. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  539. package/dist/knowledge/skills/INDEX.md +46 -11
  540. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
  541. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  542. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  543. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
  544. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  545. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  546. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
  547. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
  548. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
  549. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
  550. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  551. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
  552. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  553. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  554. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  555. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
  556. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
  557. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  558. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  559. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
  560. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  561. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
  562. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  563. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  564. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  565. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
  566. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
  567. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
  568. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
  569. package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
  570. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
  571. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  572. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  573. package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
  574. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  575. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  576. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  577. package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
  578. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  579. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
  580. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  581. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  582. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
  583. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
  584. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  585. package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
  586. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
  587. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
  588. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  589. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
  590. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
  591. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  592. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
  593. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
  594. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  595. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  596. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  597. package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
  598. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  599. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  600. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  601. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  602. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
  603. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  604. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
  605. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  606. package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
  607. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
  608. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
  609. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
  610. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  611. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
  612. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  613. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
  614. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
  615. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
  616. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
  617. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  618. package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
  619. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  620. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
  621. package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
  622. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
  623. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  624. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  625. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  626. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  627. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
  628. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  629. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  630. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
  631. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
  632. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
  633. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
  634. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
  635. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
  636. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  637. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  638. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
  639. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  640. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
  641. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
  642. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  643. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  644. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  645. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  646. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
  647. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
  648. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
  649. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
  650. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
  651. package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
  652. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  653. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
  654. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  655. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  656. package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
  657. package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
  658. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
  659. package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
  660. package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
  661. package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
  662. package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
  663. package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
  664. package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
  665. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
  666. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  667. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  668. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
  669. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
  670. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  671. package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
  672. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  673. package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
  674. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
  675. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
  676. package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
  677. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
  678. package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
  679. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
  680. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
  681. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
  682. package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
  683. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
  684. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
  685. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  686. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
  687. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
  688. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
  689. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  690. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  691. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  692. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  693. package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
  694. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  695. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  696. package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
  697. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
  698. package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
  699. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
  700. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
  701. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  702. package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
  703. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  704. package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
  705. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  706. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  707. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  708. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
  709. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  710. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
  711. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
  712. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  713. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
  714. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
  715. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
  716. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
  717. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
  718. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  719. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  720. package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
  721. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
  722. package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
  723. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
  724. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  725. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  726. package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
  727. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
  728. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
  729. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
  730. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
  731. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
  732. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  733. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  734. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  735. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
  736. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  737. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
  738. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  739. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
  740. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  741. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
  742. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
  743. package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
  744. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
  745. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  746. package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
  747. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
  748. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
  749. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
  750. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
  751. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  752. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  753. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  754. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
  755. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
  756. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  757. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  758. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
  759. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  760. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  761. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
  762. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
  763. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  764. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  765. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
  766. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
  767. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  768. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
  769. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  770. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  771. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  772. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  773. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
  774. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
  775. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
  776. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
  777. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
  778. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  779. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
  780. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
  781. package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
  782. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  783. package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
  784. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  785. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  786. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  787. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
  788. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
  789. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  790. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
  791. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
  792. package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
  793. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  794. package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
  795. package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
  796. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  797. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
  798. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
  799. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
  800. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  801. package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
  802. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  803. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
  804. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
  805. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  806. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
  807. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  808. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  809. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
  810. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
  811. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
  812. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
  813. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
  814. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
  815. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
  816. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
  817. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
  818. package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
  819. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  820. package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
  821. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
  822. package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
  823. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
  824. package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
  825. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
  826. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
  827. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
  828. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
  829. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
  830. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
  831. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
  832. package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
  833. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
  834. package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
  835. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
  836. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
  837. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
  838. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
  839. package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
  840. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  841. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  842. package/dist/knowledge/topic-index.json +5335 -1010
  843. package/dist/tsconfig.build.tsbuildinfo +1 -1
  844. package/dist/tsconfig.tsbuildinfo +1 -1
  845. package/package.json +4 -4
  846. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  847. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  848. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -3,12 +3,7 @@
3
3
  "version": "0.1.0",
4
4
  "phase": "bottom_up",
5
5
  "intent": "Bottom-up build dispatch — the SECOND build-execution playbook, the pivot from DECOMPOSING the build (the build-plan task graph) to DISPATCHING it: turning one ordered task into an actually-run, verified coding-agent run under the D4 dispatch contract. Reads the approved TYPED build-plan (`BuildPlanTaskGraph` — each task carries a closed target kind, ONE MetaWorkflow_FunctionalTopic, its skill refs, and DECLARED prerequisite task refs) and the current journey state, selects the NEXT READY task (`selectReadyBuildPlanTasks`: every declared prerequisite has landed — resolved by the host, never inferred from prose; SINGLE-FLIGHT — exactly ONE workspace-mutating run at a time), and dispatches exactly that typed task: (1) the runner builds the context pack (task brief + the task's skill pointers + the relevant journey/definition artifacts + introspected app reality + repo paths); (2) it runs ONE prompt turn against the coding agent over the Agent Client Protocol, in a session rooted at the app workspace (cwd = app root, so CLAUDE.md / .claude skills load naturally), answering the agent's permission requests within the execution profile's declared ceiling and refusing anything above it or outside the task's mutation scope; (3) it captures the change-set around the run (git baseline/post-run worktree snapshots → per-file attribution → a structured GitChangeSetCapture recorded on the task row); (4) it runs the VERIFY gate OUTSIDE the coding agent (a deterministic typecheck the runner maps onto the dispatch verification hook — pnpm exec tsc --noEmit — the trust-but-verify floor); (5) it records the result + applies the onFailure disposition (keep_and_flag: a failed/timed-out run keeps its captured change-set flagged for human triage, never a silent half-applied state). Then loop to the next ready task. This playbook PRODUCES the per-task dispatch contract + execution semantics; it authors no schemas and generates no code (the coding agent does that at dispatch time). It does NOT decompose the plan (that is the build-decompose playbook, upstream — it owns the task graph) and does NOT solve multi-agent SCALE — parallelism across several coding agents, the concurrency schedule, and interleaving the companion generation steps at scale are the downstream scale playbook. v1 scaffold: the single-flight dispatch contract; multi-agent parallelism, a run-completion serializer, and a revert_changeset failure path are later phases (revert is a MUTATING git op outside the read-only change-set carve-out, deliberately deferred).",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "bottom_up"
11
- },
12
7
  {
13
8
  "kind": "artifact_exists",
14
9
  "selector": {
@@ -22,24 +17,23 @@
22
17
  }
23
18
  ],
24
19
  "outputs": [],
20
+ "stepOutputs": [],
25
21
  "method": {
26
- "guidance": "# Build Dispatch — One Build-Plan Task → One Verified Coding-Agent Run (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut of the\n> *single-flight* dispatch contract — dispatch exactly ONE build-plan task at a\n> time, capture its change-set, verify it outside the coding agent, record it, and\n> apply the failure disposition. The context-pack shape, the verify gate, and the\n> failure-handling below are deliberately explicit so they can be tuned against real\n> runs. Multi-agent parallelism, a concurrency scheduler, a run-completion\n> serializer, and a `revert_changeset` failure path are a **later phase** — do not\n> build them here (see the boundary section).\n\n## Where you are in the journey\n\nThis is the **second build-execution playbook** — the pivot from **decomposing the\nbuild** (the build-plan: the ordered coding-agent task graph) to **dispatching it**\n(turning one ordered task into an actually-run, verified coding-agent run). It runs\nin the **bottom-up phase**, after the build plan exists (`artifact_exists\nbuild-plan`) and the foundation step has authored the app's config and skeleton.\nYou are not re-opening the decomposition\nhere — you are turning one *approved, ordered* task into a *dispatched, verified*\nchange to the application.\n\nUpstream, the **build-decompose** playbook produced the ordered task graph you\nconsume; downstream, the **scale** playbook generalises this single-flight contract\nto many concurrent coding agents and interleaves the companion generation steps.\n**You author neither of those concerns** — see the boundary section.\n\n## The typed task you dispatch\n\nThe build plan is a typed family (`BuildPlanTaskGraph`): dispatch selects ONE\nREADY task (all declared prerequisite task refs have landed) and hands the\ncoding host exactly that task's `objective`, `target`, `functionalTopic` and\n`skillRefs`. The host derives the physical allowed/prohibited paths and the\nfixed verification from the target kind; nothing in the task — and nothing in\nthis method prose — authors a path, a command, a prompt or a runtime control.\n\n## Import Origins\n\n- `@wildo-ai/saas-specifications`\n\n## Source Excerpts\n\n### Origin Package: `@wildo-ai/saas-specifications`\n\n```typescript\n *\n * Versioning for the build-plan task-graph payload format itself. `V1` —\n * initial shape (one ordered `tasks` collection with typed targets and\n * declared prerequisites). The shape grows additively across versions; the\n * `version` field is the explicit marker for consumers that branch on era.\n */\nexport enum BuildPlanTaskGraphVersion {\n V1 = 'v1',\n}\n\n/** Stable prefix every build-plan task ref carries; the trusted runtime stamps it, a provider supplies only the slug. */\nexport const BUILD_PLAN_TASK_REF_PREFIX = 'build-task-';\n\n/**\n * WHAT a build task builds — a closed vocabulary, because the host derives\n * the physical mutation scope and verification policy from the target kind\n * and the model must never author those powers through free text.\n */\nexport enum BuildPlanTaskTargetKind {\n /** A whole application module (its shared-lib registration, backend module and frontend module skeletons). */\n MODULE = 'MODULE',\n /** One build stage of one resource: schema → config → ui-behavior → spec. */\n RESOURCE_STAGE = 'RESOURCE_STAGE',\n /** One relationship between two resources. */\n RELATIONSHIP = 'RELATIONSHIP',\n /** A companion-owned deterministic generation step (labels, seeds, emails…) interleaved by the build loop, never a coding-agent run. */\n COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',\n}\n\n/** The per-resource build stages, in their fixed order. */\nexport enum BuildPlanResourceStage {\n SCHEMA = 'SCHEMA',\n CONFIG = 'CONFIG',\n UI_BEHAVIOR = 'UI_BEHAVIOR',\n SPEC = 'SPEC',\n}\n\nconst SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n/**\n * A skill ref is the skill's FOLDER id in the app-knowledge catalog, which is\n * also its `SKILL.md` frontmatter `name` — one id, kebab-case. The host refuses\n * any skill name outside `[a-z0-9-]+`, so a ref that does not match this shape\n * can never resolve to an installed skill.\n */\nconst SkillRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\nconst NonEmptyStringSchema = z.string().trim().min(1);\n\nexport const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),\n moduleRef: SlugSchema,\n resourceRef: SlugSchema,\n stage: z.enum(BuildPlanResourceStage),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),\n moduleRef: SlugSchema,\n relationshipRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),\n /** The companion generation step this task runs (e.g. labels, seeds); resolved by the companion, never by a coding agent. */\n generationStepRef: SlugSchema,\n }),\n]);\nexport type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;\n\n/**\n * One ordered build task. It names WHAT to build and WHY; it never carries\n * HOW (no paths, commands, prompts, cwd, model, profile). The host resolves\n * the physical allowed/prohibited paths and the fixed verification from the\n * target kind, and the installed skills from `skillRefs` against the app\n * knowledge catalog.\n *\n * Dependency readiness is DECLARED as prerequisite task refs and RESOLVED by\n * the host (a prerequisite is satisfied when its task has landed), never a\n * solved DAG the model must get right.\n */\nexport const BuildPlanTaskSchema = z.strictObject({\n /** `build-task-<slug>`, stamped by the trusted runtime. */\n taskRef: z.string().regex(new RegExp(`^${BUILD_PLAN_TASK_REF_PREFIX}[a-z0-9]+(?:-[a-z0-9]+)*$`)),\n /** One sentence of intent: what this task delivers. */\n objective: NonEmptyStringSchema,\n target: BuildPlanTaskTargetSchema,\n /** Exactly ONE functional topic this task belongs to (drives cross-app ordering). */\n functionalTopic: z.enum(MetaWorkflow_FunctionalTopic),\n /** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */\n skillRefs: z.array(SkillRefSchema).min(1),\n /** Task refs that must have landed first; resolved by the host, not solved by the model. */\n prerequisiteTaskRefs: z.array(z.string()).default([]),\n /** Requirement / roadmap refs this task serves (traceability only; never scope authority). */\n servesRefs: z.array(NonEmptyStringSchema).default([]),\n});\nexport type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;\n\n/**\n * THE build-plan payload — a **single aggregate per product**: the ORDERED\n * task graph that turns the accepted domain plan into buildable units.\n *\n * **Artifact-family id: `build-plan`.** This schema is the shape of the\n * journey artifact selected by `MetaWorkflow_ArtifactSelector.family ===\n * 'build-plan'` (the `family` vocabulary stays an open string owned by the\n * selector surface; this note is the single place tying the SHAPE to the\n * NAME). Produced by the build-decompose playbook, consumed one task at a\n * time by build-dispatch (single-flight coding dispatch) and by the scale\n * playbook.\n *\n * Invariants enforced here: unique task refs; every prerequisite names a task\n * in this graph; no self-prerequisite. Cycle detection and ordering\n * soundness are the deterministic validator's job (`validateBuildPlanTaskGraph`).\n */\nexport const BuildPlanTaskGraphSchema = z.object({\n version: z.enum(BuildPlanTaskGraphVersion).default(BuildPlanTaskGraphVersion.V1),\n /**\n * At least one task, at the SCHEMA — not merely as a validator warning. The first live playbook-loop\n * run (2026-08-24) proved why: build-decompose answered `tasks: []`, which was schema-valid, passed\n * `_core` validation as a mere warning, and LANDED — overwriting a completed 3-task plan with a\n * vacuous artifact. Decomposing to zero tasks is a refusal (\"nothing to decompose\"), never an\n * artifact: an empty plan carries no information a reader could act on, and the file it replaces\n * does. Same vacuity class already closed on the requirements family (`functional: min(1)`).\n */\n tasks: z.array(BuildPlanTaskSchema).min(1),\n}).superRefine((graph, context) => {\n const refs = new Set<string>();\n graph.tasks.forEach((task, index) => {\n if (refs.has(task.taskRef)) {\n context.addIssue({ code: 'custom', message: `duplicate build task ref \"${task.taskRef}\"`, path: ['tasks', index, 'taskRef'] });\n }\n refs.add(task.taskRef);\n });\n graph.tasks.forEach((task, index) => {\n task.prerequisiteTaskRefs.forEach((prerequisite, prerequisiteIndex) => {\n if (prerequisite === task.taskRef) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" cannot be its own prerequisite`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n } else if (!refs.has(prerequisite)) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" names an unknown prerequisite \"${prerequisite}\"`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n }\n });\n });\n});\nexport type BuildPlanTaskGraph = z.infer<typeof BuildPlanTaskGraphSchema>;\n```\n\n## What this playbook does\n\nYou are the **dispatch orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, for *one* task at a time: *\"dispatch this\ntask safely, verify it, and record what happened.\"* You do **not** produce a new\njourney artifact — the dispatch's observable result (the change-set + the task\nstatus) is materialized by the runner on the task row, not authored here (see \"What\nyou emit\"). You do **not** decompose the plan, author any schema, or write any code\n— the coding agent writes the code at dispatch time; the plan is the\nbuild-decompose playbook's; scale is the scale playbook's.\n\n## The dispatch contract — the runner owns the mechanism, you sequence it\n\nMost of the D4 dispatch contract is **runner mechanism**, not prose you re-implement:\nthe runner composes the context pack, opens a coding session with the agent over the\nAgent Client Protocol and sends one prompt turn, answers the agent's permission\nrequests within the declared ceiling, captures the change-set, runs the verify hook,\nholds the single-flight lock, and enforces the budget floor. Your method here is the **declarative recipe** the runner interprets —\n*which* task to dispatch next, *when* it is authorized, and *how* its outcome is\njudged. Do not hand-compose a dispatch prompt or drive git yourself; let the runner\nown composition and change-set capture.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the loop by one task*.\nBefore dispatching anything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the **build plan** is present\n and approved, and confirm the **foundation** ran. For each build-plan task,\n determine its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify), or\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run or a\n failed verify). This tri-state matters: under `keep_and_flag` a **failed** task\n *also* has a captured change-set, so \"has a change-set\" alone does NOT mean the\n task is done — read the task's terminal status + verify outcome, not just the\n presence of a change-set.\n2. Read the approved **build plan** (`build-plan` — the ordered task graph). It is your\n work list.\n\n Evidence that the foundation ran is `./wildo.saas.config.ts` itself, committed: the\n app either has a config and a skeleton or it does not, and git answers that without a\n journey artifact standing in for it. (A `foundation-manifest` family was that stand-in\n until 2026-08-25; it was retired with the app-creation verification/digest aspect, and\n this playbook no longer gates on it.) The honest limitation inherited from the\n foundation step still applies: at scaffold depth the on-disk skeleton *materialization*\n depends on greenfield bring-up tooling (deferred). The dispatch contract is real and\n runs against an **existing** app skeleton — the dogfood app already has one.\n\n// TODO CLI COMMAND: wildo journey status\n// (read current journey scope + the approved build plan + which tasks already dispatched)\n\nYou **read** `build-plan`; you **write** no journey artifact\n— the runner records the change-set + task status on the dispatched task's row.\n\n## Step 1 — Select the next dispatchable task (single-flight)\n\nWalk the build plan in its authored order and pick the **first** task that is not\nyet dispatched (or a previously-**failed** task cleared for retry — see Step 5) and\nwhose prose prerequisites have all **succeeded**. Dispatch **exactly one** such task\nper run. If **no** task is ready — every task has already succeeded, or the only\nundispatched tasks are blocked behind a still-unresolved failure — there is nothing\nto dispatch: report the loop as done (or blocked on the failed task) and stop. An\nempty build plan is the same: nothing to dispatch, stop.\n\n- **Single-flight — one workspace-mutating run at a time.** The dispatch lane holds\n ONE workspace-mutation lock for the whole background run; a run plan carries **at\n most one** coding-agent task, and a second concurrent dispatch is refused. This is\n a hard runner floor, not a suggestion — do not try to dispatch two tasks in one\n run to \"go faster\". Batching across many agents is the scale playbook's job.\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task is ready\n only when every task it depends on is dispatched-and-succeeded (verify passed).\n A prerequisite that is dispatched-and-**failed** (its change-set is flagged for\n triage under `keep_and_flag`) does **not** satisfy the dependency — its dependents\n stay **blocked** until the failure is triaged and the prerequisite re-dispatched\n successfully. Do not build a config on a schema whose run failed. Never dispatch a\n task before the stage it depends on (a config before its schema, a spec before its\n ui-behavior — the build-decompose playbook ordered these).\n- **Companion-generation steps are not coding-agent dispatches.** A build-plan task\n marked as a companion-owned generation step (labels / i18n, email templates,\n seeds) runs through its deterministic companion endpoint, not the coding-agent\n dispatch lane. Route it there; do not dispatch a coding agent for it. Interleaving\n those steps *concurrently* with coding runs at scale is the scale playbook's job —\n here you simply run the ready one in its turn.\n\n## Step 2 — Authorize the mutating run (approve_before)\n\nA coding-agent dispatch **mutates the application workspace** — the highest-stakes\naction in the journey. This playbook's approval posture is `approve_before`: the run\nis authorized **before** it touches the tree. Settle the exact pending Authority\nRequest through the `journey-approve` interface-relay workflow; never start the\ndispatch on your own judgment.\n\n- Under the **GUIDED** autonomy preset the gate is verbatim; under **YOLO_LIGHT** it\n downgrades to a post-hoc result review; under **YOLO** it is auto (the\n non-bypassable **budget floor** — per-playbook and per-journey run/wall-time\n ceilings — is the guardrail no preset can lift).\n- **v1 gate granularity (be honest about the floor's reach).** The approval gate is\n currently **playbook-scoped for the journey**, not scoped to a single dispatch: the\n first authorization of this dispatch playbook admits the subsequent dispatches of it\n too (bounded by the run-count budget floor), rather than re-prompting per task. So\n `approve_before` here means \"the creator authorizes the **dispatch loop** before any\n task mutates the workspace\" — a real pre-mutation floor. A per-run, single-use gate\n is a deferred runner posture; until it lands, the budget ceiling + the per-task\n change-set capture + the verify gate are what bound the authorized loop.\n- The floor still hard-gates regardless of preset: once the dispatch playbook's run\n ceiling is reached, further dispatches are **refused** — that refusal is the\n correct outcome; report it, do not work around it.\n\n## Step 3 — Dispatch the task through the coding-agent contract\n\nTrigger the run through the `journey-run` skill. The runner then performs the D4\ndispatch contract for you (you do not hand-assemble any of it):\n\n1. **Context pack** — the runner composes the prompt: the task brief, the task's\n skill pointers (`Read .claude/skills/<skillRef>/SKILL.md first` — the per-task\n HOW-skills the build plan named on this task), the relevant journey / definition\n artifacts, an introspected app-reality block, and the repo paths.\n2. **Session and one prompt turn** — the runner starts the agent over the Agent\n Client Protocol and opens a session rooted at the app workspace (cwd = the\n application root, so `./CLAUDE.md`, the sub-`CLAUDE.md`s, and the `.claude/` rules\n and skills load naturally), then sends the task as a single prompt turn. It is a\n session rather than a one-shot process, which is what makes the next three things\n possible at all:\n - **Permissions are answered, not assumed.** The agent asks before each action it\n considers privileged; the runner answers within the execution profile's declared\n ceiling and refuses anything above it, or anything touching a path outside the\n task's mutation scope. Refusals are counted on the task row, so a run that was\n held back is distinguishable from a run that had nothing to do.\n - **The turn can be cancelled.** Cancellation asks the agent to stop and waits, so\n the run terminalises with its change-set intact instead of being killed — an\n operator who stops a run still needs to know what it had already written.\n - **Usage is reported.** Tokens and cost come back from the run itself rather than\n being unavailable, which is what lets the budget floor mean anything.\n3. **Change-set capture** — the runner captures a git worktree snapshot before and\n after the run and attributes each touched file (the run's own edit vs. an\n already-dirty parallel-session file vs. a file that appeared during the run),\n recording a structured change-set on the task row. On the dogfood tree,\n dirty-at-dispatch is the NORMAL state (parallel sessions), so the capture\n *attributes* rather than assuming the run had the tree to itself.\n\n// TODO CLI COMMAND: wildo journey run <playbookRef>\n// (trigger the dispatch; the runner composes the context pack + runs one ACP prompt turn + captures the change-set)\n\n## Step 4 — Verify OUTSIDE the coding agent\n\nTrust, but verify. The verify gate runs **outside** the coding agent, after the run,\nso the agent cannot mark its own homework:\n\n- **`dispatch-typecheck` (deterministic — the auto-run trust floor).** The runner\n maps this `deterministic_validator` gate (`validatorRef: typecheck`) onto the\n dispatch verification hook and runs a typecheck (`pnpm exec tsc --noEmit`) over the\n application workspace after the run, **outside** the coding agent. This is a\n **real, wired** gate — it actually executes and its result is recorded on the task\n row. A run whose typecheck fails is a failed run (apply the failure disposition in\n Step 5). At scaffold depth the gate is a **workspace-wide** typecheck (one static\n gate for every dispatch of this playbook); narrowing it to the specific package a\n given task touched — a per-task `typecheck:<pkgDir>` or a `vitest:<path>` targeted\n at the task's tests — is a later refinement, since a static playbook gate cannot\n vary per task.\n- **`dispatch-outcome-sound` (declarative reviewer checklist).** The six-invariant\n reviewer checklist (task accomplished, change-set scoped to the task, verify ran +\n passed, attribution clean, failure disposition correct, boundary discipline)\n is the *trust-but-verify reviewer* pass. It is **declarative** — the creator's\n review checklist; the compiled build-dispatch Evaluation Treatment is what the\n runtime judges with, and the deterministic typecheck above is what runs\n automatically.\n\n## Step 5 — Record the result and apply the failure disposition\n\nThe runner records the change-set + the task's terminal status on the task row. On a\n**failed or timed-out** run, this playbook's `onFailure` is **`keep_and_flag`**: the\ncaptured change-set is **kept and flagged for human triage** — never silently\nreverted, and never left as an un-recorded half-applied state. The change-set capture\n*is* the flag: it attributes exactly which files the run touched, so a human can\nreview, keep, or unwind them.\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a failed\n> run's edits is a *mutating* git operation, deliberately **outside** the read-only\n> change-set carve-out the dispatch lane observes (the runner *observes* git —\n> baseline/post-run snapshots — but stage/commit/revert stay a human/CLI concern).\n> So `keep_and_flag` is both the correct F-5 workspace-safety posture (no silent\n> half-applied state) and the behavior the runner actually enforces today. Wiring a\n> `revert_changeset` path is a deliberate later boundary decision, not a gap this\n> playbook papers over.\n\nOn a **succeeded** run (change-set captured + verify passed), the task is done and\nits dependents become eligible. On a **failed** run, the task is **not** done — it is\nflagged for human triage, and its dependents stay blocked (Step 1) until it is\ntriaged and cleared for re-dispatch. Triage is a human decision: keep + fix forward,\nunwind the flagged change-set by hand, or re-dispatch the task once its blocker is\nresolved. This playbook does not auto-retry a failed task — automated retry / backoff\nis a deferred build-loop-resilience concern, and human triage is the v1 disposition;\nhere the loop simply surfaces the failure and stops advancing that dependency chain.\n\nThen **loop**: on the next run of this playbook, `journey-status` reflects the\njust-dispatched task's outcome, and you select the next ready task (Step 1). Close a\nsignificant stretch of dispatches with a `journey-report` summary — what was\nproduced, which change-sets landed, what verify said, and any failed task left\nflagged for triage.\n\n## Refine, don't re-dispatch\n\n- **Never re-dispatch a SUCCEEDED task.** A task that is dispatched-and-succeeded\n (change-set captured + verify passed) is done — advance to the next ready task, do\n not re-run it because the plan was re-opened elsewhere. A dispatched-and-**failed**\n task is a different case: it is re-dispatchable once triaged (Step 5) — a captured\n change-set alone does not make a task \"finished\".\n- **Follow the plan's order.** If the build plan was refined upstream (a task added,\n an ordering corrected), respect the new order on the next selection — do not cache\n a stale work list across runs.\n- **A budget refusal is a real stop.** When the run ceiling is hit, stop dispatching\n and report what remains; do not do the coding work out-of-band to \"finish the\n build\" — that makes the journey's task history a lie.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **single-flight dispatch depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order the\n graph, or add tasks — the **build-decompose** playbook owns the task graph. You\n read it and dispatch from it.\n- **Multi-agent scale + interleaving.** Running MANY coding agents concurrently, a\n concurrency scheduler, a run-completion serializer, and interleaving the companion\n generation steps *concurrently* with coding runs is the **scale** playbook. You\n dispatch **one** task at a time under the single-flight lock; you do NOT design the\n concurrency schedule.\n- **A `revert_changeset` failure path.** Undoing a failed run's edits is a mutating\n git op outside the read-only change-set carve-out — deferred. `keep_and_flag` (keep\n + flag the captured change-set for triage) is the v1 disposition.\n- **Auto-executed reviewer checklist.** The checklist ships **declarative** —\n the deterministic typecheck gate runs automatically and the compiled Evaluation\n Treatment is the judged protocol; nothing executes the checklist prose. Do not\n assume it auto-ran.\n- **Schema / field authoring + code generation.** You dispatch a task; the **coding\n agent** authors the fields, schemas, ui-behavior, and code at dispatch time. If you\n catch yourself writing application code or a resource schema here, stop — that is\n the dispatched agent's job, not the orchestrator's.\n\nIf you find yourself designing how MANY agents run concurrently rather than how ONE\ntask dispatches safely, stop — that is the scale playbook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable result\nof a dispatch — the **change-set** (files touched, attributed, summarized) and the\n**task status** — is materialized by the runner on the dispatched task's row, not\nauthored by this playbook. That is deliberately not duplicated into a separate\njourney artifact family: the task row already *is* the dispatch record, and a second\nhome for the same record would drift.\n\nThe creator authorizes each dispatch (approval posture `approve_before`) before it\nmutates the workspace, and reviews the recorded change-set + verify outcome after —\none verified task at a time, until the build plan is fully dispatched.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state,\n scope, and budget; confirm the build plan is approved and the foundation ran, and\n see which tasks already dispatched.\n- `.claude/skills/journey-approve/SKILL.md` — relay the exact pre-dispatch Authority Request\n gate decision that authorizes the workspace-mutating dispatch (never self-approve).\n- `.claude/skills/journey-run/SKILL.md` — trigger the dispatch and monitor it; the\n runner composes the context pack, runs one prompt turn against the coding agent in\n the app workspace, captures the change-set, and runs the verify hook.\n- `.claude/skills/journey-report/SKILL.md` — summarize a stretch of dispatches:\n what was produced, which change-sets landed, and what the verify gates said.\n\n## Reviewer checklist — `dispatch-outcome-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim (minus the retired runner's closing sentence, and with repository-specific wording made application-neutral):\n\nJudge whether ONE dispatched build-plan task ran soundly under the D4 dispatch contract — the trust-but-verify reviewer pass OUTSIDE the coding agent. Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) TASK ACCOMPLISHED — the change-set the run produced actually implements the dispatched task's target + stage (e.g. a schema task added the persisted shape; a ui-behavior task added field displays); a run whose change-set does not advance the task's stated target is a GAP (the dispatch produced nothing useful), and an empty change-set on a task that should have authored files is a GAP. (2) CHANGE-SET SCOPED TO THE TASK — the files touched belong to the task's target (its module / resource / stage) and the app workspace; edits sprawling into unrelated modules, Wildo package source outside the application workspace, or files no build-plan task owns are a CONCERN (scope creep the reviewer must flag). On the dogfood tree, files attributed BASELINE_DIRTY_AMBIGUOUS (already dirty at dispatch baseline — a parallel session, not this run) are review-required and must NOT be counted against the run. (3) VERIFY RAN + PASSED — the deterministic verify gate (typecheck) ran OUTSIDE the coding agent after the run and passed; a run recorded as succeeded whose typecheck the reviewer cannot confirm passed is a CONCERN, and a run whose typecheck FAILED but was recorded succeeded is a GAP. (4) ATTRIBUTION CLEAN (the single-flight signal) — the run's edits are cleanly attributable to it in the captured change-set (files classed RUN_EXCLUSIVE or APPEARED_DURING_RUN), consistent with the single-flight lock having held for this dispatch. A change-set the capture could NOT cleanly attribute to the run — dominated by BASELINE_DIRTY_AMBIGUOUS overlap, or captured across a HEAD that moved mid-run — is a CONCERN the reviewer must resolve by hand before accepting the run, not a clean pass (single-flight is a hard runner floor, so this invariant reads the attribution the run actually recorded rather than re-proving the lock). (5) FAILURE DISPOSITION CORRECT — a failed/timed-out run's captured change-set is KEPT + FLAGGED for human triage (keep_and_flag), never silently reverted nor silently left as an un-recorded half-applied state; a failed run with no recorded change-set flag is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the dispatch stays at single-task depth: it dispatches ONE task, captures + verifies + records it, and applies onFailure. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT run MANY coding agents concurrently / design a concurrency scheduler / interleave the companion generation steps at scale (the scale playbook), and does NOT itself author schemas / fields / code (the coding agent does that at dispatch time). Evidence of re-decomposition, multi-agent scale orchestration, or the dispatcher authoring code itself is a CONCERN (scope creep out of the single-flight dispatch lane). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)\n",
22
+ "guidance": "# Build Dispatch — One Build-Plan Task → One Verified Coding-Agent Run (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut of the\n> *single-flight* dispatch contract — dispatch exactly ONE build-plan task at a\n> time, capture its change-set, verify it outside the coding agent, record it, and\n> apply the failure disposition. The context-pack shape, the verify gate, and the\n> failure-handling below are deliberately explicit so they can be tuned against real\n> runs. Multi-agent parallelism, a concurrency scheduler, a run-completion\n> serializer, and a `revert_changeset` failure path are a **later phase** — do not\n> build them here (see the boundary section).\n\n## Where you are in the journey\n\nThis is the **second build-execution playbook** — the pivot from **decomposing the\nbuild** (the build-plan: the ordered coding-agent task graph) to **dispatching it**\n(turning one ordered task into an actually-run, verified coding-agent run). It runs\nin the **bottom-up phase**, after the build plan exists (`artifact_exists\nbuild-plan`) and the foundation step has authored the app's config and skeleton.\nYou are not re-opening the decomposition\nhere — you are turning one *approved, ordered* task into a *dispatched, verified*\nchange to the application.\n\nUpstream, the **build-decompose** playbook produced the ordered task graph you\nconsume; downstream, the **scale** playbook generalises this single-flight contract\nto many concurrent coding agents and interleaves the companion generation steps.\n**You author neither of those concerns** — see the boundary section.\n\n## The typed task you dispatch\n\nThe build plan is a typed family (`BuildPlanTaskGraph`): dispatch selects ONE\nREADY task (all declared prerequisite task refs have landed) and hands the\ncoding host exactly that task's `objective`, `target`, `produces`,\n`functionalTopic` and `skillRefs`. The host derives the physical\nallowed/prohibited paths and the fixed verification from the target kind;\nnothing in the task — and nothing in this method prose — authors a path, a\ncommand, a prompt or a runtime control.\n\n`target` and `produces` answer two different questions, and a task needs both.\n`target` is the WRITE SCOPE — where this run may edit, and several tasks\nlegitimately share one. `produces` is what the run is ACCOUNTABLE for: the\nartifacts whose presence in the application proves the task done. A task has\nlanded when every artifact it declares is present and committed, so a run that\nsatisfies the objective's prose without delivering those artifacts is not\nfinished — the plan will offer the task again.\n\n## Import Origins\n\n- `@wildo-ai/saas-specifications`\n\n## Source Excerpts\n\n### Origin Package: `@wildo-ai/saas-specifications`\n\n```typescript\n *\n * Versioning for the build-plan task-graph payload format itself. `V1` —\n * initial shape (one ordered `tasks` collection with typed targets and\n * declared prerequisites). The shape grows additively across versions; the\n * `version` field is the explicit marker for consumers that branch on era.\n */\nexport enum BuildPlanTaskGraphVersion {\n V1 = 'v1',\n}\n\n/** Stable prefix every build-plan task ref carries; the trusted runtime stamps it, a provider supplies only the slug. */\nexport const BUILD_PLAN_TASK_REF_PREFIX = 'build-task-';\n\n/**\n * WHAT a build task builds — a closed vocabulary, because the host derives\n * the physical mutation scope and verification policy from the target kind\n * and the model must never author those powers through free text.\n */\nexport enum BuildPlanTaskTargetKind {\n /** A whole application module (its shared-lib registration, backend module and frontend module skeletons). */\n MODULE = 'MODULE',\n /** One build stage of one resource: schema → config → ui-behavior → spec. */\n RESOURCE_STAGE = 'RESOURCE_STAGE',\n /** One relationship between two resources. */\n RELATIONSHIP = 'RELATIONSHIP',\n /** A companion-owned deterministic generation step (labels, email templates, logo or database migrations) interleaved by the build loop, never a coding-agent run. */\n COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',\n /**\n * Authoring one SHELL SURFACE's placement configuration from the accepted\n * placement plan — the settings rail, the sidebar, the user menu or the\n * command palette.\n *\n * Its own kind rather than a reuse of the neighbours, because none of them is\n * true of it: it is not a MODULE or a RESOURCE_STAGE (it is application-wide\n * and belongs to no resource), not a RELATIONSHIP, and emphatically not a\n * COMPANION_GENERATION_STEP — that kind is documented as \"never a coding-agent\n * run\" and writing `settings-hub.config.ts` is exactly a coding-agent run.\n * Borrowing one would hand the host the wrong mutation scope and the wrong\n * verification, which is what the closed vocabulary exists to prevent.\n */\n SHELL_PLACEMENT = 'SHELL_PLACEMENT',\n /*\n * THE NON-RESOURCE SURFACES (#1490). Until 2026-09-22 the five kinds above were the whole\n * vocabulary, and every one of them is about a resource or the shell placement of one. The\n * decompose method meanwhile told the planner to emit tasks for views, navigation, the design\n * system, custom components, PDF templates, workers, minions, providers, the website and the\n * documentation — surfaces the framework's own composition scenarios and 85 of its 111 skills\n * already build. A task for any of them had no kind to declare, so it either declared none\n * (landing as RAN-not-PROVEN forever) or borrowed `MODULE` with a product the module scope could\n * not prove. The members below are those surfaces, one per write scope the host can derive.\n */\n /**\n * The FRONTEND and SPECIFICATION layers of one module — its composite, custom and chart views,\n * its custom components and their specifications.\n *\n * Narrower than `MODULE` on purpose: a view task never touches `shared-lib` or `backend-api`, so\n * handing it the four-layer scope also hands it four typechecks and the FK sweep for a change\n * that can only break the frontend and the specifications package.\n */\n MODULE_FRONTEND = 'MODULE_FRONTEND',\n /**\n * The BACKEND layer of one module beside its shared-lib declarations — PDF templates and their\n * bindings, backend addons (services, controllers, flows-actors), email definitions.\n *\n * Shared-lib is in scope because a PDF template is bound to a resource FIELD the config declares\n * (`generatedSummaryPdf`), and a backend addon usually declares its contract there first.\n */\n MODULE_BACKEND = 'MODULE_BACKEND',\n /**\n * ONE application-wide frontend configuration surface — navigation, the design system, the app\n * shell's composition, the global views — named by {@link FrontendConfigSurface}.\n *\n * Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the\n * shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES\n * the surface itself (which sidebar sections exist, which transitions the primary zone uses,\n * which palette the product carries). Same file for `APP_SHELL`, different question.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /** The marketing website workspace (`website/`), composed by the `add-website` scenario. Pages and sections are its products. */\n WEBSITE = 'WEBSITE',\n /**\n * The technical-documentation workspace (`technical-doc/`) and the specification package's\n * `technical-documentation/` declarations that feed it. Its generated tree is never written by a\n * task: the companion publishes into it, and the coding policy prohibits it by prefix.\n */\n TECHNICAL_DOCUMENTATION = 'TECHNICAL_DOCUMENTATION',\n /** One worker package (`workers/<workerRef>/`), Node or Rust, plus its declaration in the SaaS config. */\n WORKER = 'WORKER',\n /** One cron minion package (`minions/<minionRef>/`) plus its declaration in the SaaS config. */\n MINION = 'MINION',\n /**\n * Declaring one provider in the application — the SaaS config's provider scopes, the backend\n * package dependency, the frontend provider module and its companion contribution.\n *\n * Application-wide by construction: a provider binding names no module, and the four files it\n * may touch are the same for every provider.\n */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n}\n\n/**\n * WHICH application-wide frontend configuration surface a task composes — one file each, in\n * `frontend/src/config/`, and the coding policy resolves the member to that file exactly as\n * `SHELL_PLACEMENT` resolves a `PlacementSurface`.\n *\n * Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a\n * subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of\n * those live in one file. A configuration surface is WHICH FILE a composition task authors, and\n * navigation and the design system are not places anything is placed.\n */\nexport enum FrontendConfigSurface {\n /** `frontend/src/config/navigation.config.ts` — zones, transitions, overlay appearance. */\n NAVIGATION = 'NAVIGATION',\n /** `frontend/src/config/design-system.config.ts` — palette, typography, shell appearance from the brand's visual tone. */\n DESIGN_SYSTEM = 'DESIGN_SYSTEM',\n /** `frontend/src/config/app-shell.config.ts` — top bar, sidebar sections, quick switcher: the shell's COMPOSITION, not a placement into it. */\n APP_SHELL = 'APP_SHELL',\n /** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */\n GLOBAL_VIEWS = 'GLOBAL_VIEWS',\n}\n\n/**\n * The two shapes of guidance an application gives a person, and the file each is declared in.\n *\n * They are distinct because they are found differently: an onboarding DOCUMENT is embedded in a\n * screen (`EmbedOnboarding`) and is there whenever that screen is, while a guidance FLOW is started\n * by an event and shows once. Both are listed on the owning frontend module — `onboardingViews` and\n * `guidanceFlows`. Each kind has a CONVENTIONAL definitions file, which the authoring skill teaches\n * and a landing probe reads for the declared ref (alongside the module's `index.ts`, where a small\n * module may declare inline). A convention for generated applications: a hand-authored application\n * may keep its declarations elsewhere, and then simply is not probed by a build plan.\n */\nexport enum ApplicationGuidanceKind {\n /** `frontend/src/modules/<m>/app-level-views/onboarding-views.definitions.ts` — an embedded onboarding document. */\n ONBOARDING_DOCUMENT = 'ONBOARDING_DOCUMENT',\n /** `frontend/src/modules/<m>/app-level-views/guidance-flows.definitions.ts` — a triggered guidance flow. */\n GUIDANCE_FLOW = 'GUIDANCE_FLOW',\n}\n\n/**\n * The two worker runtimes the framework composes (`add-worker-node`, `add-worker-rust`). The\n * runtime decides the entry file a landing probe reads and whether a typecheck exists to run: a\n * Node worker is verified by its package typecheck, a Rust worker has no TypeScript to check and\n * the policy says so rather than inventing a command.\n *\n * Not the SaaS config's `WorkerRuntime`, which is a free-form `{ type, language }` pair an\n * application authors for deployment; this is the closed set a creation run can COMPOSE.\n */\nexport enum BuildPlanWorkerRuntime {\n NODE = 'NODE',\n RUST = 'RUST',\n}\n\n/**\n * WHERE a provider is bound — which runtime owner's scope its declaration lands in. Each member\n * is a different file, so a probe and a write grant both derive from it.\n *\n * Named after the SaaS config's own scope keys (`providers.scopes.backend`, `.companion`,\n * `.frontendServices.app`, `.frontendServices.website`), which the `add-provider` and\n * `add-file-picker-provider` scenarios write. Minion and worker scopes are deliberately absent:\n * a provider reaching a minion is declared on that minion's own `providers` block and belongs to\n * the {@link BuildPlanTaskTargetKind.MINION} task that builds it.\n */\nexport enum ProviderBindingScope {\n BACKEND = 'BACKEND',\n COMPANION = 'COMPANION',\n FRONTEND_APP = 'FRONTEND_APP',\n WEBSITE = 'WEBSITE',\n}\n\n/** The per-resource build stages, in their fixed order. */\nexport enum BuildPlanResourceStage {\n SCHEMA = 'SCHEMA',\n CONFIG = 'CONFIG',\n UI_BEHAVIOR = 'UI_BEHAVIOR',\n SPEC = 'SPEC',\n}\n\nconst SlugSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\n\n/**\n * The governed document a task produces, named as a COMPLIANCE-DOCUMENT CANDIDATE names it:\n * `document:<namespace>.<id>`, e.g. `document:public.privacy-notice`.\n *\n * **This field was `SlugSchema`, and a slug cannot name a governed document — so until 2026-09-16 no\n * build plan in any application could declare a document the engine catalog defines.** A slug forbids\n * the colon and the dot, the catalog's definitions are `document-definition:public.privacy-notice`,\n * and `selectAssuranceDocumentBlueprintForDocumentRef` joins the two namespaces by exact suffix — so\n * every authored `documentRef` resolved to NO blueprint, and a blueprint is what says which sections,\n * facts and claim guards the document owes. The two vocabularies were disjoint by construction.\n *\n * The cost is measured rather than theoretical. Wonder CRM's plan declares two such products\n * (`gdpr-data-handling-governance`, `terminal-access-governance`), neither of which names anything;\n * the first was dispatched, and its agent spent a full turn establishing — with a positive control —\n * that the document does not exist and could only be invented, which the authoring skill forbids.\n *\n * The bare slug is STILL ACCEPTED, and that is deliberate rather than tidiness left undone: tightening\n * this to the namespaced form alone would make every already-accepted plan carrying one fail to parse,\n * and a build plan that cannot be READ stops the whole lane — the gate\n * `application-creation-directive.md` forbids, for a task nobody can fix by re-running anything. A slug\n * simply resolves to no blueprint, so the dispatcher skips that task with a message naming the ref,\n * and the rest of the plan proceeds.\n */\nconst DocumentProductRefSchema = z.union([\n z.string().regex(/^document:[a-z0-9]+(?:-[a-z0-9]+)*\\.[a-z0-9]+(?:-[a-z0-9]+)*$/),\n SlugSchema,\n]);\n/**\n * A skill ref is the skill's FOLDER id in the app-knowledge catalog, which is\n * also its `SKILL.md` frontmatter `name` — one id, kebab-case. The host refuses\n * any skill name outside `[a-z0-9-]+`, so a ref that does not match this shape\n * can never resolve to an installed skill.\n */\nconst SkillRefSchema = z.string().regex(/^[a-z0-9]+(?:-[a-z0-9]+)*$/);\nconst NonEmptyStringSchema = z.string().trim().min(1);\n\n/**\n * WHAT a build task PRODUCES — the artifact whose presence in the application\n * proves the task is done.\n *\n * **This is not `target`, and the difference is the whole reason it exists.**\n * `target` is a WRITE SCOPE: the host turns it into the path prefixes a run may\n * mutate, and several tasks legitimately share one. `produces` is a PRODUCT\n * IDENTITY: it says which artifact this task, and no other, is accountable for.\n *\n * Measured 2026-09-10 on Wonder CRM (issue #597): `build-task-pipeline-view`\n * and `build-task-deal-follow-through-operation` carry BYTE-IDENTICAL targets\n * (`{ kind: MODULE, moduleRef: 'deals' }`), and 7 of that plan's 42 tasks share\n * 3 targets. Landing had been answered by narrowing the target to a module\n * DIRECTORY — which `wildo compose` commits on day one, and which cannot tell\n * two tasks apart even in principle. The loop reported 40 of 42 tasks landed\n * while no coding task had ever run, so `dispatch-next` skipped every one of\n * them and the phase-advance gate read a build that was all but complete.\n *\n * Like `target`, this stays SEMANTIC: a product names a resource, a field, a\n * relationship or a view — never a path, and never a command. The host owns the\n * translation from a product to the physical question it asks of the working\n * tree, exactly as it owns the translation from a target kind to path prefixes.\n * A model that could author the path could author its own mutation scope.\n */\nexport enum BuildPlanTaskProductKind {\n /**\n * Named fields on one resource's schema.\n *\n * The shape an ENRICHMENT task needs, and the reason a product cannot always\n * be \"a file\": every resource file already exists, written by the scaffold\n * with its self-described STARTER shape, so file presence answers nothing.\n * The FIELDS are what the task adds.\n */\n RESOURCE_SCHEMA_FIELDS = 'RESOURCE_SCHEMA_FIELDS',\n /**\n * One resource's declared operations — its registry presence, named by the verbs it gains.\n *\n * The VERBS, not the config file: `<r>.resources-config.ts` is written by the scaffold, so its\n * existence is satisfied before any task runs. That is the exact shape of the defect this\n * vocabulary replaces, and a kind that reproduced it would be worse than no kind at all.\n */\n RESOURCE_REGISTRATION = 'RESOURCE_REGISTRATION',\n /** One resource's frontend ui-behavior. */\n RESOURCE_UI_BEHAVIOR = 'RESOURCE_UI_BEHAVIOR',\n /**\n * One resource's specification, named by the fields it documents.\n *\n * The FIELDS, for the same reason as {@link RESOURCE_REGISTRATION}: every resource is scaffolded\n * with a `*.resource.specification.ts` documenting only the starter shape, so file existence\n * proves nothing about the task that was meant to enrich it.\n */\n RESOURCE_SPECIFICATION = 'RESOURCE_SPECIFICATION',\n /** One relationship edge between two resources, named by the domain plan's `relationshipRef`. */\n RESOURCE_RELATIONSHIP = 'RESOURCE_RELATIONSHIP',\n /** One named custom operation on one resource. */\n RESOURCE_OPERATION = 'RESOURCE_OPERATION',\n /** One named application-level view. */\n APPLICATION_VIEW = 'APPLICATION_VIEW',\n /** One named governed application document (a compliance notice, a governance statement). */\n APPLICATION_DOCUMENT = 'APPLICATION_DOCUMENT',\n /** One application module, registered across the layer registries under one module identity. */\n APPLICATION_MODULE = 'APPLICATION_MODULE',\n /*\n * THE NON-RESOURCE PRODUCTS (#1490). Each names an artifact of a surface the five target kinds\n * above `MODULE_FRONTEND` could not express, and each is probed by the host from committed bytes —\n * a declaration in the one file that registers it, never a directory a scenario already wrote.\n */\n /**\n * Named declarations in ONE application-wide frontend configuration file — a sidebar section\n * ref the app shell gains, a zone the navigation config declares, a token the design system sets.\n *\n * The DECLARATIONS, never the file: every `frontend/src/config/*.config.ts` is written by\n * `wildo init`, so its presence is true before any task runs. Same reasoning as\n * {@link RESOURCE_SCHEMA_FIELDS}, one level up.\n */\n APPLICATION_FRONTEND_CONFIG = 'APPLICATION_FRONTEND_CONFIG',\n /**\n * One composite view of one resource — the cross-resource surface a resource's ui-behavior\n * declares under `compositeViews`. Distinct from {@link APPLICATION_VIEW}, which is\n * application-level and owned by a module rather than a resource.\n */\n RESOURCE_COMPOSITE_VIEW = 'RESOURCE_COMPOSITE_VIEW',\n /** One custom operation or execution view of one resource, bound in its ui-behavior. */\n RESOURCE_CUSTOM_VIEW = 'RESOURCE_CUSTOM_VIEW',\n /** One chart view of one resource, declared under its ui-behavior's `chartViews`. */\n RESOURCE_CHART_VIEW = 'RESOURCE_CHART_VIEW',\n /** One custom frontend component, registered by `componentRef` in the module's or the engine's registrations. */\n CUSTOM_COMPONENT = 'CUSTOM_COMPONENT',\n /**\n * One milestone a module declares — the moment the application recognises and celebrates.\n *\n * Named by its identifier, which is what the module's `milestones.ts` declares\n * (`first-project-created` is spelled `FIRST_PROJECT_CREATED` there). The module FILE is not the\n * product: a module may carry milestones before this task runs, and only the identifier says this\n * one landed.\n */\n APPLICATION_MILESTONE = 'APPLICATION_MILESTONE',\n /** One onboarding document or guidance flow a module declares, named by its ref. */\n APPLICATION_GUIDANCE = 'APPLICATION_GUIDANCE',\n /** One PDF template bound to one resource's generated-file field. */\n PDF_TEMPLATE = 'PDF_TEMPLATE',\n /**\n * One worker's JOBS — the named handlers its entry file declares.\n *\n * The jobs, not the package: `add-worker-node` writes the package, so its directory proves\n * nothing. What a coding task adds is behaviour, and behaviour is a symbol in the entry file.\n */\n APPLICATION_WORKER = 'APPLICATION_WORKER',\n /** One minion's BEHAVIOURS — the named tick handlers its entry file declares. Same reasoning as the worker. */\n APPLICATION_MINION = 'APPLICATION_MINION',\n /** One provider declared in one runtime owner's scope. */\n PROVIDER_BINDING = 'PROVIDER_BINDING',\n /** One website page, registered in the website root config by its manifest. */\n WEBSITE_PAGE = 'WEBSITE_PAGE',\n /** One section of one website page, declared in that page's sections file. */\n WEBSITE_SECTION = 'WEBSITE_SECTION',\n /**\n * One authored documentation chapter — a consumer guide the specifications package declares\n * for the documentation portal to publish (#874's publication input).\n */\n DOCUMENTATION_CHAPTER = 'DOCUMENTATION_CHAPTER',\n}\n\n/**\n * One artifact a task is accountable for. Closed by construction: a product the\n * host cannot ask a question about is a product that can never be shown to have\n * landed, so the vocabulary only grows alongside the resolver that answers it.\n */\nexport const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /**\n * At least one field, because a task that enriches a schema with nothing is\n * the vacuity this whole field exists to stop: it would land the moment the\n * scaffold existed, which is the defect being fixed.\n */\n fieldRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_REGISTRATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_SPECIFICATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, fieldRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP).systemEnum('BuildPlanTaskProductKind'),\n relationshipRef: SlugSchema,\n /*\n * The two resources the edge relates, NAMED rather than parsed out of the ref.\n *\n * A ref is `<source>-<target>` by convention and that convention is not invertible:\n * `next-step-deal` splits as (`next`, `step-deal`) or (`next-step`, `deal`) and only the domain\n * plan knows which. The domain plan already carries both, so the plan passes them on instead of\n * making the host guess — a host that guesses wrong probes for a resource that does not exist\n * and reports the task permanently unlanded.\n */\n sourceResourceRef: SlugSchema,\n targetResourceRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_OPERATION).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, operationRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_VIEW).systemEnum('BuildPlanTaskProductKind'), viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_DOCUMENT).systemEnum('BuildPlanTaskProductKind'), documentRef: DocumentProductRefSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MODULE).systemEnum('BuildPlanTaskProductKind'), moduleRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG).systemEnum('BuildPlanTaskProductKind'),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n /** At least one, for the same vacuity reason as a schema's `fieldRefs`: the file exists on day one. */\n declarationRefs: z.array(NonEmptyStringSchema).min(1),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, viewRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_CHART_VIEW).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema, chartRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.CUSTOM_COMPONENT).systemEnum('BuildPlanTaskProductKind'), componentRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MILESTONE).systemEnum('BuildPlanTaskProductKind'), milestoneRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.APPLICATION_GUIDANCE).systemEnum('BuildPlanTaskProductKind'),\n /** Which definitions file carries it — a document and a flow live in different ones. */\n guidanceKind: z.enum(ApplicationGuidanceKind).systemEnum('ApplicationGuidanceKind'),\n guidanceRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PDF_TEMPLATE).systemEnum('BuildPlanTaskProductKind'),\n resourceRef: SlugSchema,\n /** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */\n templateRef: NonEmptyStringSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),\n providerRef: SlugSchema,\n scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),\n]);\nexport type BuildPlanTaskProduct = z.infer<typeof BuildPlanTaskProductSchema>;\n\n/**\n * Every artifact identity a product claims — one string per artifact, not one\n * per product, because a product may claim several.\n *\n * `RESOURCE_SCHEMA_FIELDS` is why this returns a list. Two tasks may both enrich\n * one resource's schema (a domain shape and a billing concern, say), and that is\n * legitimate; what must never overlap is the FIELDS. Comparing whole products\n * would refuse the legitimate pair, and comparing only the resource would let two\n * tasks claim one field and make landing ambiguous again.\n *\n * Derived from the product's own members rather than stored, and total over the\n * vocabulary, so a kind added tomorrow must state its identity here or fail to\n * compile — it cannot be silently treated as equal to its siblings.\n */\nexport function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): readonly string[] {\n switch (product.kind) {\n case BuildPlanTaskProductKind.RESOURCE_SCHEMA_FIELDS:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_REGISTRATION:\n return product.operationRefs.map((operationRef) => `${product.kind}:${product.resourceRef}:${operationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_SPECIFICATION:\n return product.fieldRefs.map((fieldRef) => `${product.kind}:${product.resourceRef}:${fieldRef}`);\n case BuildPlanTaskProductKind.RESOURCE_UI_BEHAVIOR:\n return [`${product.kind}:${product.resourceRef}`];\n case BuildPlanTaskProductKind.RESOURCE_RELATIONSHIP:\n return [`${product.kind}:${product.relationshipRef}`];\n case BuildPlanTaskProductKind.RESOURCE_OPERATION:\n return [`${product.kind}:${product.resourceRef}:${product.operationRef}`];\n case BuildPlanTaskProductKind.APPLICATION_VIEW:\n return [`${product.kind}:${product.viewRef}`];\n case BuildPlanTaskProductKind.APPLICATION_DOCUMENT:\n /*\n * The ref AS AUTHORED, so a slug and a namespaced ref are different artifact identities even\n * where they mean the same document — the duplicate-artifact refusal cannot see two tasks\n * claiming one document if they spell it differently. Not normalisable: a slug carries no\n * namespace, so nothing can recover `public.` from `privacy-notice`. It costs nothing today\n * because a slug names no catalogued document at all, and the dispatcher skips such a task.\n */\n return [`${product.kind}:${product.documentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MODULE:\n return [`${product.kind}:${product.moduleRef}`];\n // One identity per DECLARATION, like schema fields: two tasks may compose one config file as\n // long as they declare different things in it.\n case BuildPlanTaskProductKind.APPLICATION_FRONTEND_CONFIG:\n return product.declarationRefs.map((declarationRef) => `${product.kind}:${product.configSurface}:${declarationRef}`);\n case BuildPlanTaskProductKind.RESOURCE_COMPOSITE_VIEW:\n case BuildPlanTaskProductKind.RESOURCE_CUSTOM_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.viewRef}`];\n case BuildPlanTaskProductKind.RESOURCE_CHART_VIEW:\n return [`${product.kind}:${product.resourceRef}:${product.chartRef}`];\n case BuildPlanTaskProductKind.CUSTOM_COMPONENT:\n return [`${product.kind}:${product.componentRef}`];\n case BuildPlanTaskProductKind.APPLICATION_MILESTONE:\n return [`${product.kind}:${product.milestoneRef}`];\n // The ref alone: a document and a flow sharing one ref is still one guidance identity, and the\n // runtime keys a person's saved state by it — two artifacts claiming it would collide there too.\n case BuildPlanTaskProductKind.APPLICATION_GUIDANCE:\n return [`${product.kind}:${product.guidanceRef}`];\n case BuildPlanTaskProductKind.PDF_TEMPLATE:\n return [`${product.kind}:${product.resourceRef}:${product.templateRef}`];\n case BuildPlanTaskProductKind.APPLICATION_WORKER:\n return product.jobRefs.map((jobRef) => `${product.kind}:${product.workerRef}:${jobRef}`);\n case BuildPlanTaskProductKind.APPLICATION_MINION:\n return product.behaviorRefs.map((behaviorRef) => `${product.kind}:${product.minionRef}:${behaviorRef}`);\n // The SCOPE is part of the identity: one provider bound on the backend and on the website is two artifacts.\n case BuildPlanTaskProductKind.PROVIDER_BINDING:\n return [`${product.kind}:${product.scope}:${product.providerRef}`];\n case BuildPlanTaskProductKind.WEBSITE_PAGE:\n return [`${product.kind}:${product.pageRef}`];\n case BuildPlanTaskProductKind.WEBSITE_SECTION:\n return [`${product.kind}:${product.pageRef}:${product.sectionRef}`];\n case BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER:\n return [`${product.kind}:${product.chapterRef}`];\n default: {\n const unhandled: never = product;\n throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);\n }\n }\n}\n\nexport const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RESOURCE_STAGE),\n moduleRef: SlugSchema,\n resourceRef: SlugSchema,\n stage: z.enum(BuildPlanResourceStage),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),\n moduleRef: SlugSchema,\n relationshipRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),\n /** The companion generation step this task runs (e.g. i18n-labels, email-templates); resolved by the companion, never by a coding agent. */\n generationStepRef: SlugSchema,\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.SHELL_PLACEMENT),\n /**\n * Which shell surface this task authors — the placement family's OWN\n * `PlacementSurface`, deliberately not a build-plan copy of it.\n *\n * A copy was written first and was a defect, caught by probing the landing\n * renderer rather than by any test: `PlacementAddress` discriminates on\n * `surface` with `z.literal(...)` per option, so only the VALUES survive into\n * the schema, and the renderer resolves a discriminator by matching that value\n * SET against the exported enums. Two enums with identical values made the\n * match ambiguous, the renderer correctly refused to guess an owner, and the\n * address discriminator became unnameable — a landed placement plan would have\n * emitted `surface: \"SETTINGS_HUB\"` as a bare string instead of\n * `PlacementSurface.SETTINGS_HUB`. One concept, one named source.\n */\n surface: z.enum(PlacementSurface).systemEnum('PlacementSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_FRONTEND), moduleRef: SlugSchema }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE_BACKEND), moduleRef: SlugSchema }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_FRONTEND_CONFIG),\n configSurface: z.enum(FrontendConfigSurface).systemEnum('FrontendConfigSurface'),\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.WEBSITE) }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.TECHNICAL_DOCUMENTATION) }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.WORKER),\n /** The worker's directory under `workers/` and its key in the SaaS config, in slug form. */\n workerRef: SlugSchema,\n runtime: z.enum(BuildPlanWorkerRuntime).systemEnum('BuildPlanWorkerRuntime'),\n }),\n z.strictObject({\n kind: z.literal(BuildPlanTaskTargetKind.MINION),\n /** The minion's directory under `minions/` and its key in the SaaS config, in slug form. */\n minionRef: SlugSchema,\n }),\n z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),\n]);\nexport type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;\n\n/**\n * One ordered build task. It names WHAT to build and WHY; it never carries\n * HOW (no paths, commands, prompts, cwd, model, profile). The host resolves\n * the physical allowed/prohibited paths and the fixed verification from the\n * target kind, and the installed skills from `skillRefs` against the app\n * knowledge catalog.\n *\n * Dependency readiness is DECLARED as prerequisite task refs and RESOLVED by\n * the host (a prerequisite is satisfied when its task has landed), never a\n * solved DAG the model must get right.\n */\nexport const BuildPlanTaskSchema = z.strictObject({\n /** `build-task-<slug>`, stamped by the trusted runtime. */\n taskRef: z.string().regex(new RegExp(`^${BUILD_PLAN_TASK_REF_PREFIX}[a-z0-9]+(?:-[a-z0-9]+)*$`)),\n /**\n * One sentence of intent: what this task delivers.\n *\n * Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also\n * hold. A display decorator mutates the instance it is applied to, and the workbench gives those\n * refs a receding identifier look, which the objective sentence then took too.\n */\n objective: z.string().trim().min(1),\n target: BuildPlanTaskTargetSchema,\n /**\n * The artifacts this task is accountable for — what proves it done.\n *\n * Coding tasks should declare at least one product that composition did not already\n * write. A target is a shared mutation scope; its scaffolded file is not evidence\n * that this task's intended work exists. Products identify the output to probe.\n *\n * Empty declarations remain representable and produce the advisory\n * `TASK_DECLARES_NO_PRODUCT`. The host may advance after a COMPLETED durable run,\n * while naming the task in `unverifiableLandedTaskRefs`: it ran, but its output\n * cannot be proven from a product declaration. An unexecuted task is not landed.\n * This distinction avoids repeatedly dispatching the same unprovable task without\n * presenting execution history as evidence that the intended product is correct.\n *\n * The ONE hard exception is a `COMPANION_GENERATION_STEP`, which must declare NONE.\n * That kind already carries its own typed landed condition, owned by the\n * generation-step service — a set computed asynchronously (planner units x\n * enabled locales), and for the migration step a STATE rather than files. A\n * product declared beside it would be read by nothing, which is the inert\n * declaration this field exists to avoid. Enforced on the graph below, in both\n * directions.\n */\n produces: z.array(BuildPlanTaskProductSchema).default([]),\n /**\n * Exactly ONE functional topic this task belongs to.\n *\n * **It does NOT drive ordering** — this said \"drives cross-app ordering\" until 2026-08-30 and\n * nothing ever ordered by it. Sequencing is `prerequisiteTaskRefs`, resolved by the host, and it\n * is the only thing that decides what may run next.\n *\n * What it DOES: the dispatch host stamps it into the coding-agent's task payload beside\n * `skillRefs`, so the agent is told which phase of building the application this task belongs to.\n * That is context an LLM reads, not a value the runtime branches on — the distinction matters,\n * because a reader who believes it orders will look here for a scheduling bug that lives in the\n * prerequisite graph. See issue #124.\n */\n functionalTopic: z.enum(MetaWorkflow_FunctionalTopic).systemEnum('MetaWorkflow_FunctionalTopic'),\n /** Installed app-knowledge skill folders that carry the technical HOW; resolved via the skills router at dispatch. */\n skillRefs: z.array(SkillRefSchema).min(1),\n /** Task refs that must have landed first; resolved by the host, not solved by the model. */\n prerequisiteTaskRefs: z.array(z.string()).default([]),\n /**\n * What this task is accountable to — traceability only, NEVER scope authority.\n *\n * The vocabulary is the five aspects `BUILD_PLAN_FAMILY_ASPECTS` declares as targets: functional\n * and non-functional requirements, roadmap phases, and the vision's success criteria and\n * constraints. It reads \"Requirement / roadmap refs\" until 2026-09-11, and the last two were added\n * because the producer had been writing them all along (#629) — the generation contract asks for a\n * plain string list, so nothing here has ever refused a key.\n *\n * A key outside those five is not rejected and must not be: this is traceability a human or a\n * model wrote down, and dropping it loses the intent. The workbench renders such a key as visibly\n * unresolved instead, which is what makes a producer drift legible rather than silent.\n */\n servesRefs: z.array(NonEmptyStringSchema).default([]),\n});\nexport type BuildPlanTask = z.infer<typeof BuildPlanTaskSchema>;\n\n/**\n * THE build-plan payload — a **single aggregate per product**: the ORDERED\n * task graph that turns the accepted domain plan into buildable units.\n *\n * **Artifact-family id: `build-plan`.** This schema is the shape of the\n * journey artifact selected by `MetaWorkflow_ArtifactSelector.family ===\n * 'build-plan'` (the `family` vocabulary stays an open string owned by the\n * selector surface; this note is the single place tying the SHAPE to the\n * NAME). Produced by the build-decompose playbook, consumed one task at a\n * time by build-dispatch (single-flight coding dispatch) and by the scale\n * playbook.\n *\n * Invariants enforced here: unique task refs; every prerequisite names a task\n * in this graph; no self-prerequisite. Cycle detection and ordering\n * soundness are the deterministic validator's job (`validateBuildPlanTaskGraph`).\n */\nexport const BuildPlanTaskGraphSchema = z.object({\n version: z.enum(BuildPlanTaskGraphVersion).default(BuildPlanTaskGraphVersion.V1),\n /**\n * At least one task, at the SCHEMA — not merely as a validator warning. The first live playbook-loop\n * run (2026-08-24) proved why: build-decompose answered `tasks: []`, which was schema-valid, passed\n * `_core` validation as a mere warning, and LANDED — overwriting a completed 3-task plan with a\n * vacuous artifact. Decomposing to zero tasks is a refusal (\"nothing to decompose\"), never an\n * artifact: an empty plan carries no information a reader could act on, and the file it replaces\n * does. Same vacuity class already closed on the requirements family (`functional: min(1)`).\n */\n tasks: z.array(BuildPlanTaskSchema).min(1),\n}).superRefine((graph, context) => {\n const refs = new Set<string>();\n graph.tasks.forEach((task, index) => {\n if (refs.has(task.taskRef)) {\n context.addIssue({ code: 'custom', message: `duplicate build task ref \"${task.taskRef}\"`, path: ['tasks', index, 'taskRef'] });\n }\n refs.add(task.taskRef);\n });\n /*\n * No two tasks claim the same artifact.\n *\n * This is what makes landing DECIDABLE, not a tidiness rule. If two tasks name\n * one product, the host cannot tell which of them a present artifact proves —\n * exactly the ambiguity that shared `target`s created, arriving through the\n * field that replaced them. Enforced here rather than left to the validator\n * because a graph that cannot answer \"has this task landed?\" is not a graph\n * the loop may run at all.\n */\n graph.tasks.forEach((task, index) => {\n const isGenerationStep = task.target.kind === BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP;\n if (isGenerationStep && task.produces.length > 0) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" is a companion generation step and must declare no products; its landing is the generation step's own condition`,\n path: ['tasks', index, 'produces'],\n });\n }\n });\n const productOwners = new Map<string, string>();\n graph.tasks.forEach((task, index) => {\n task.produces.forEach((product, productIndex) => {\n buildPlanTaskProductIdentities(product).forEach((identity) => {\n const owner = productOwners.get(identity);\n if (owner !== undefined) {\n context.addIssue({\n code: 'custom',\n message: `build task \"${task.taskRef}\" claims the same artifact as \"${owner}\" (${identity}); an artifact is produced by exactly one task`,\n path: ['tasks', index, 'produces', productIndex],\n });\n return;\n }\n productOwners.set(identity, task.taskRef);\n });\n });\n });\n graph.tasks.forEach((task, index) => {\n task.prerequisiteTaskRefs.forEach((prerequisite, prerequisiteIndex) => {\n if (prerequisite === task.taskRef) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" cannot be its own prerequisite`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n } else if (!refs.has(prerequisite)) {\n context.addIssue({ code: 'custom', message: `build task \"${task.taskRef}\" names an unknown prerequisite \"${prerequisite}\"`, path: ['tasks', index, 'prerequisiteTaskRefs', prerequisiteIndex] });\n }\n });\n });\n});\nexport type BuildPlanTaskGraph = z.infer<typeof BuildPlanTaskGraphSchema>;\n```\n\n## What this playbook does\n\nYou are the **dispatch orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, for *one* task at a time: *\"dispatch this\ntask safely, verify it, and record what happened.\"* You do **not** produce a new\njourney artifact — the dispatch's observable result (the change-set + the task\nstatus) is materialized by the runner on the task row, not authored here (see \"What\nyou emit\"). You do **not** decompose the plan, author any schema, or write any code\n— the coding agent writes the code at dispatch time; the plan is the\nbuild-decompose playbook's; scale is the scale playbook's.\n\n## The dispatch contract — the runner owns the mechanism, you sequence it\n\nMost of the D4 dispatch contract is **runner mechanism**, not prose you re-implement:\nthe runner composes the context pack, opens a coding session with the agent over the\nAgent Client Protocol and sends one prompt turn, answers the agent's permission\nrequests within the declared ceiling, captures the change-set, runs the verify hook,\nholds the single-flight lock and applies its configured execution limits. Your method here is the **declarative recipe** the runner interprets —\n*which* task to dispatch next, *when* it is authorized, and *how* its outcome is\njudged. Do not hand-compose a dispatch prompt or drive git yourself; let the runner\nown composition and change-set capture.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the loop by one task*.\nBefore dispatching anything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the **build plan** is present\n and approved, and confirm the **foundation** ran. For each build-plan task,\n determine its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify), or\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run or a\n failed verify). This tri-state matters: under `keep_and_flag` a **failed** task\n *also* has a captured change-set, so \"has a change-set\" alone does NOT mean the\n task is done — read the task's terminal status + verify outcome, not just the\n presence of a change-set.\n2. Read the approved **build plan** (`build-plan` — the ordered task graph). It is your\n work list.\n\n Evidence that the foundation ran is `./wildo.saas.config.ts` itself, committed: the\n app either has a config and a skeleton or it does not, and git answers that without a\n journey artifact standing in for it. (A `foundation-manifest` family was that stand-in\n until 2026-08-25; it was retired with the app-creation verification/digest aspect, and\n this playbook no longer gates on it.) The honest limitation inherited from the\n foundation step still applies: at scaffold depth the on-disk skeleton *materialization*\n depends on greenfield bring-up tooling (deferred). The dispatch contract is real and\n runs against an **existing** app skeleton — the dogfood app already has one.\n\n// Operator status: `wildo context journey` (eligibility board + runs in flight). Which tasks already\n// landed is read from GIT by the runner itself — a task is landed when every file it produces is\n// committed clean.\n\nYou **read** `build-plan`; you **write** no journey artifact\n— the runner records the change-set + task status on the dispatched task's row.\n\n## Precondition — the application must establish the agent's role, or dispatch stalls\n\nCheck this before the first dispatch of an application's life. It costs one look and it is the\ndifference between a working lane and one that burns model time producing nothing.\n\n**The application needs a root `CLAUDE.md` stating that a task dispatched by its dev companion is\nlegitimate work.** Without it the agent is right to refuse, and refusing is what it does.\n\nThe reason is structural rather than a matter of tone. A dispatched task reaches the agent as an\nordinary prompt — a user turn carrying an objective, a mutation scope and skill refs. Nothing in\nthat turn proves where it came from. So the agent is being handed conversational content that\ntells it to write files into a repository, which is indistinguishable from the thing every\ncareful agent is supposed to decline, and the more trustworthy the agent the more reliably it\ndeclines. Measured on a real application with no such file: two dispatched runs stalled, one\nanswering *\"content that arrives as conversational input doesn't get to reassign what I am\"*.\n\nThe failure does not look like a missing file. It looks like an agent that deliberates well,\nidentifies exactly which files it would author, explains its reasoning, asks a human to confirm,\nand ends its turn — `end_turn`, no error, no denial, an empty change set, and a bill for the\ntokens. Read as \"the agent chose not to work\", which invites prompt-tuning that cannot fix it.\n\n`wildo init` scaffolds this file. An application created before that, or one whose `CLAUDE.md`\ncovers only its own conventions, needs the section added. What it must establish:\n\n- the task is **selected by the host** from the accepted build plan, not composed by a caller;\n- its **file edits** are **confined before they arrive** — the host answers every permission request\n against the declared mutation scope and refuses paths outside it;\n- its **shell commands are NOT**, and the section must say so. A command declares no `locations`, so\n the scope predicate never runs for one; telling an agent it \"need not police itself\" is true of its\n edits and false of its commands, and that is the half a stray write comes through. Name the\n compensations with it: the post-run change set and the companion's warning DETECT such a write,\n they do not prevent it;\n- it is **reversible** — every write is an uncommitted working edit until something commits it. Do\n not state WHO commits as a property of the lane: that is the host's autonomy posture, it changes,\n and an agent that reads \"a human commits\" from a scaffold written under a different posture is\n working from a stale contract.\n\nTwo smaller things belong in the same section, because both were observed costing a run:\n\n- **Say what `allowedPathPrefixes` are relative to.** The agent receives bare prefixes such as\n `shared-lib/src/modules/<module>/` with no root, and cannot verify its own confinement against\n them. One sentence naming the application root removes the ambiguity.\n- **Do not name a task so it reads as a fixture.** An agent that concludes it is looking at a\n smoke test will say so and stop. Name the task after the product change it makes.\n\n## Step 1 — Select the next dispatchable task (single-flight)\n\nWalk the build plan in its authored order and pick the **first** task that is not\nyet dispatched (or a previously-**failed** task cleared for retry — see Step 5) and\nwhose prose prerequisites have all **succeeded**. Dispatch **exactly one** such task\nper run. If **no** task is ready — every task has already succeeded, or the only\nundispatched tasks are blocked behind a still-unresolved failure — there is nothing\nto dispatch: report the loop as done (or blocked on the failed task) and stop. An\nempty build plan is the same: nothing to dispatch, stop.\n\n- **Single-flight — one workspace-mutating run at a time.** The dispatch lane holds\n ONE workspace-mutation lock for the whole background run; a run plan carries **at\n most one** coding-agent task, and a second concurrent dispatch is refused. This is\n a hard runner floor, not a suggestion — do not try to dispatch two tasks in one\n run to \"go faster\". Batching across many agents is the scale playbook's job.\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task is ready\n only when every task it depends on is dispatched-and-succeeded (verify passed).\n A prerequisite that is dispatched-and-**failed** (its change-set is flagged for\n triage under `keep_and_flag`) does **not** satisfy the dependency — its dependents\n stay **blocked** until the failure is triaged and the prerequisite re-dispatched\n successfully. Do not build a config on a schema whose run failed. Never dispatch a\n task before the stage it depends on (a config before its schema, a spec before its\n ui-behavior — the build-decompose playbook ordered these).\n- **Companion-generation steps are not coding-agent dispatches.** A build-plan task\n marked as a companion-owned generation step (labels / i18n, email templates,\n seeds) runs through its deterministic companion endpoint, not the coding-agent\n dispatch lane. Route it there; do not dispatch a coding agent for it. Interleaving\n those steps *concurrently* with coding runs at scale is the scale playbook's job —\n here you simply run the ready one in its turn.\n\n## Step 2 — Check the actual host authorization boundary\n\nA coding dispatch writes the application workspace. Read its selected task, readiness,\nmutation scope and the configured coding host's authorization policy before invoking it.\nThe single-flight mutation lock still applies to the current shared workspace.\n\nThe playbook's `approval` declaration and the journey autonomy presets express policy\nintent. The current playbook runner does not interpret them as pre-dispatch gates,\nautomatic authorization, or a GUIDED/YOLO mapping. A declared `approve_before` does\nnot create a pending Authority Request. Use `journey-approve` only for an actual\nrequest from an explicitly connected authority workflow; never invent one from an enum.\n\nLikewise, do not infer enforced per-playbook or per-journey run ceilings from declared\nbudget fields. Respect the limits actually reported by the execution host. Inspect the\nrecorded changes and verification result after each task; no preset commits or accepts them.\n\n## Step 3 — Dispatch the task through the coding-agent contract\n\nTrigger the run through the `journey-run` skill. The runner then performs the D4\ndispatch contract for you (you do not hand-assemble any of it):\n\n1. **Context pack** — the runner composes the prompt: the task brief, the task's\n skill pointers (`Read .claude/skills/<skillRef>/SKILL.md first` — the per-task\n HOW-skills the build plan named on this task), the relevant journey / definition\n artifacts, an introspected app-reality block, and the repo paths.\n2. **Session and one prompt turn** — the runner starts the agent over the Agent\n Client Protocol and opens a session rooted at the app workspace (cwd = the\n application root, so `./CLAUDE.md`, the sub-`CLAUDE.md`s, and the `.claude/` rules\n and skills load naturally), then sends the task as a single prompt turn. It is a\n session rather than a one-shot process, which is what makes the next three things\n possible at all:\n - **Permissions are answered, not assumed.** The agent asks before each action it\n considers privileged; the runner answers within the execution profile's declared\n ceiling and refuses anything above it, or anything touching a path outside the\n task's mutation scope. Refusals are counted on the task row, so a run that was\n held back is distinguishable from a run that had nothing to do.\n - **The turn can be cancelled.** Cancellation asks the agent to stop and waits, so\n the run terminalises with its change-set intact instead of being killed — an\n operator who stops a run still needs to know what it had already written.\n - **Usage is reported.** Tokens and cost come back from the run itself rather than\n being unavailable, which lets the host report a terminal timeout instead of leaving the run ambiguous.\n3. **Change-set capture** — the runner captures a git worktree snapshot before and\n after the run and attributes each touched file (the run's own edit vs. an\n already-dirty parallel-session file vs. a file that appeared during the run),\n recording a structured change-set on the task row. On the dogfood tree,\n dirty-at-dispatch is the NORMAL state (parallel sessions), so the capture\n *attributes* rather than assuming the run had the tree to itself.\n\n// The trigger is the companion's run route (`POST /api/companion/playbooks/<ref>/run`, via the\n// workbench or HTTP) — there is no CLI trigger yet. The runner composes the typed context pack,\n// runs one ACP prompt turn, and captures the change-set.\n// That route is MUTATING, so the call must carry `x-wildo-companion-token`, read from\n// `./.wildo-saas/state/companion.token` (mode 0600). Without it the companion answers `401` with a\n// body that names nothing — the explanation is in the companion's own log.\n\n## Step 4 — Verify OUTSIDE the coding agent\n\nTrust, but verify. The verify gate runs **outside** the coding agent, after the run,\nso the agent cannot mark its own homework:\n\n- **`dispatch-typecheck` (deterministic — the auto-run trust floor).** The runner\n maps this `deterministic_validator` gate (`validatorRef: typecheck`) onto the\n dispatch verification hook and runs a typecheck (`pnpm exec tsc --noEmit`) over the\n application workspace after the run, **outside** the coding agent. This is a\n **real, wired** gate — it actually executes and its result is recorded on the task\n row. A run whose typecheck fails is a failed run (apply the failure disposition in\n Step 5). At scaffold depth the gate is a **workspace-wide** typecheck (one static\n gate for every dispatch of this playbook); narrowing it to the specific package a\n given task touched — a per-task `typecheck:<pkgDir>` or a `vitest:<path>` targeted\n at the task's tests — is a later refinement, since a static playbook gate cannot\n vary per task.\n- **`dispatch-outcome-sound` (declarative reviewer checklist).** The six-invariant\n reviewer checklist (task accomplished, change-set scoped to the task, verify ran +\n passed, attribution clean, failure disposition correct, boundary discipline)\n is the *trust-but-verify reviewer* pass. It is **declarative** — the creator's\n review checklist; the compiled build-dispatch Evaluation Treatment is what the\n runtime judges with, and the deterministic typecheck above is what runs\n automatically.\n\n## Step 5 — Record the result and apply the failure disposition\n\nThe runner records the change-set + the task's terminal status on the task row. On a\n**failed or timed-out** run, the current coding host retains its captured changes for inspection (the declaration describes this as **`keep_and_flag`**): the\ncaptured change-set is **kept and flagged for human triage** — never silently\nreverted, and never left as an un-recorded half-applied state. The change-set capture\n*is* the flag: it attributes exactly which files the run touched, so a human can\nreview, keep, or unwind them.\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a failed\n> run's edits is a *mutating* git operation, deliberately **outside** the read-only\n> change-set carve-out the dispatch lane observes (the runner *observes* git —\n> baseline/post-run snapshots — but stage/commit/revert stay a human/CLI concern).\n> So `keep_and_flag` is both the correct F-5 workspace-safety posture (no silent\n> half-applied state) and the behavior the runner actually enforces today. Wiring a\n> `revert_changeset` path is a deliberate later boundary decision, not a gap this\n> playbook papers over.\n\nOn a **succeeded** run (change-set captured + verify passed), the task is done and\nits dependents become eligible. On a **failed** run, the task is **not** done — it is\nflagged for human triage, and its dependents stay blocked (Step 1) until it is\ntriaged and cleared for re-dispatch. Triage is a human decision: keep + fix forward,\nunwind the flagged change-set by hand, or re-dispatch the task once its blocker is\nresolved. This playbook does not auto-retry a failed task — automated retry / backoff\nis a deferred build-loop-resilience concern, and human triage is the v1 disposition;\nhere the loop simply surfaces the failure and stops advancing that dependency chain.\n\nThen **loop**: on the next run of this playbook, `journey-status` reflects the\njust-dispatched task's outcome, and you select the next ready task (Step 1). Close a\nsignificant stretch of dispatches with a `journey-report` summary — what was\nproduced, which change-sets landed, what verify said, and any failed task left\nflagged for triage.\n\n## Refine, don't re-dispatch\n\n- **Never re-dispatch a SUCCEEDED task.** A task that is dispatched-and-succeeded\n (change-set captured + verify passed) is done — advance to the next ready task, do\n not re-run it because the plan was re-opened elsewhere. A dispatched-and-**failed**\n task is a different case: it is re-dispatchable once triaged (Step 5) — a captured\n change-set alone does not make a task \"finished\".\n- **Follow the plan's order.** If the build plan was refined upstream (a task added,\n an ordering corrected), respect the new order on the next selection — do not cache\n a stale work list across runs.\n- **A host execution refusal is a real stop.** When an actual execution limit is reported, stop dispatching\n and report what remains; do not do the coding work out-of-band to \"finish the\n build\" — that makes the journey's task history a lie.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **single-flight dispatch depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order the\n graph, or add tasks — the **build-decompose** playbook owns the task graph. You\n read it and dispatch from it.\n- **Multi-agent scale + interleaving.** Running MANY coding agents concurrently, a\n concurrency scheduler, a run-completion serializer, and interleaving the companion\n generation steps *concurrently* with coding runs is the **scale** playbook. You\n dispatch **one** task at a time under the single-flight lock; you do NOT design the\n concurrency schedule.\n- **A `revert_changeset` failure path.** Undoing a failed run's edits is a mutating\n git op outside the read-only change-set carve-out — deferred. `keep_and_flag` (keep\n + flag the captured change-set for triage) is the v1 disposition.\n- **Auto-executed reviewer checklist.** The checklist ships **declarative** —\n the deterministic typecheck gate runs automatically and the compiled Evaluation\n Treatment is the judged protocol; nothing executes the checklist prose. Do not\n assume it auto-ran.\n- **Schema / field authoring + code generation.** You dispatch a task; the **coding\n agent** authors the fields, schemas, ui-behavior, and code at dispatch time. If you\n catch yourself writing application code or a resource schema here, stop — that is\n the dispatched agent's job, not the orchestrator's.\n\nIf you find yourself designing how MANY agents run concurrently rather than how ONE\ntask dispatches safely, stop — that is the scale playbook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable result\nof a dispatch — the **change-set** (files touched, attributed, summarized) and the\n**task status** — is materialized by the runner on the dispatched task's row, not\nauthored by this playbook. That is deliberately not duplicated into a separate\njourney artifact family: the task row already *is* the dispatch record, and a second\nhome for the same record would drift.\n\nDispatch uses the configured host's actual authorization boundary. The creator reviews\nthe recorded change-set and verification outcome afterwards —\none verified task at a time, until the build plan is fully dispatched.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state,\n scope, and budget; confirm the build plan is approved and the foundation ran, and\n see which tasks already dispatched.\n- `.claude/skills/journey-run/references/framework-playbook-approval-policy.md` — declaration semantics and the actual runner boundary.\n- `.claude/skills/journey-run/SKILL.md` — trigger the dispatch and monitor it; the\n runner composes the context pack, runs one prompt turn against the coding agent in\n the app workspace, captures the change-set, and runs the verify hook.\n- `.claude/skills/journey-report/SKILL.md` — summarize a stretch of dispatches:\n what was produced, which change-sets landed, and what the verify gates said.\n\n## Reviewer checklist — `dispatch-outcome-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim (minus the retired runner's closing sentence, and with repository-specific wording made application-neutral):\n\nJudge whether ONE dispatched build-plan task ran soundly under the D4 dispatch contract — the trust-but-verify reviewer pass OUTSIDE the coding agent. Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) TASK ACCOMPLISHED — the change-set the run produced actually implements the dispatched task's target + stage (e.g. a schema task added the persisted shape; a ui-behavior task added field displays); a run whose change-set does not advance the task's stated target is a GAP (the dispatch produced nothing useful), and an empty change-set on a task that should have authored files is a GAP. (2) CHANGE-SET SCOPED TO THE TASK — the files touched belong to the task's target (its module / resource / stage) and the app workspace; edits sprawling into unrelated modules, Wildo package source outside the application workspace, or files no build-plan task owns are a CONCERN (scope creep the reviewer must flag). Files attributed BASELINE_DIRTY_AMBIGUOUS were already dirty and changed again during the run; this establishes uncertainty, not ownership by a parallel editor. Every changed path outside the declared scope — ambiguous or not, and including a parallel session's edits, which the capture cannot tell apart from the run's own — is RECORDED on the result as `outOfScopePaths`; nothing refuses the run for it. Treat each as a CONCERN and resolve its authorship during review, never as a GAP by itself. Committed-window entries and recognized concurrent host-lane paths are classified separately and left off that list. (3) VERIFY RAN + PASSED — the deterministic verify gate (typecheck) ran OUTSIDE the coding agent after the run and passed; a run recorded as succeeded whose typecheck the reviewer cannot confirm passed is a CONCERN, and a run whose typecheck FAILED but was recorded succeeded is a GAP. (4) ATTRIBUTION CLEAN (the single-flight signal) — the run's edits are cleanly attributable to it in the captured change-set (files classed RUN_EXCLUSIVE or APPEARED_DURING_RUN), consistent with the single-flight lock having held for this dispatch. A change-set the capture could NOT cleanly attribute to the run — dominated by BASELINE_DIRTY_AMBIGUOUS overlap, or captured across a HEAD that moved mid-run — is a CONCERN the reviewer must resolve by hand before accepting the run, not a clean pass (single-flight is a hard runner floor, so this invariant reads the attribution the run actually recorded rather than re-proving the lock). (5) FAILURE DISPOSITION CORRECT — a failed/timed-out run's captured change-set is KEPT + FLAGGED for human triage (keep_and_flag), never silently reverted nor silently left as an un-recorded half-applied state; a failed run with no recorded change-set flag is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the dispatch stays at single-task depth: it dispatches ONE task, captures + verifies + records it, and applies onFailure. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT run MANY coding agents concurrently / design a concurrency scheduler / interleave the companion generation steps at scale (the scale playbook), and does NOT itself author schemas / fields / code (the coding agent does that at dispatch time). Evidence of re-decomposition, multi-agent scale orchestration, or the dispatcher authoring code itself is a CONCERN (scope creep out of the single-flight dispatch lane). (The checklist is declarative: nothing executes it; the current host's deterministic checks apply; the approval enum alone adds no gate.)\n",
27
23
  "skillRefs": [
28
24
  "journey-status",
29
25
  "journey-approve",
30
26
  "journey-run",
31
27
  "journey-report"
32
- ]
28
+ ],
29
+ "skillBodyRefs": [],
30
+ "contextSources": [],
31
+ "draftableDocumentDefinitionRefs": [],
32
+ "suspendsForClarification": false,
33
+ "briefAdequacyGate": false,
34
+ "briefAdequacyExcludedSources": []
33
35
  },
34
- "executor": "composite",
35
- "qualityGates": [
36
- {
37
- "ref": "dispatch-typecheck",
38
- "kind": "deterministic_validator",
39
- "validatorRef": "typecheck",
40
- "required": true
41
- }
42
- ],
36
+ "executor": "coding_agent",
43
37
  "approval": "approve_before",
44
38
  "budget": {
45
39
  "maxInputTokens": 15000000,
@@ -60,7 +60,7 @@ Most of the *per-task* mechanism is **not yours**: selecting one task,
60
60
  composing its context pack, running one prompt turn against the coding agent over
61
61
  the Agent Client Protocol (answering its permission requests within the declared
62
62
  ceiling), capturing the change-set, running the verify hook, holding the
63
- single-flight lock, enforcing the budget floor — all of that is the **build-dispatch** contract, which each
63
+ single-flight lock, applying the host's actual execution limits — all of that is the **build-dispatch** contract, which each
64
64
  parallel slot invokes. Your method here is the **declarative concurrency
65
65
  recipe** the runner (or a future runner-serializer) interprets: *which set* of
66
66
  tasks is ready, *how many* run at once, *how* they are isolated, *when* the
@@ -96,8 +96,8 @@ Before scheduling anything:
96
96
  bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale
97
97
  contract runs against an existing workspace.
98
98
 
99
- // TODO CLI COMMAND: wildo journey status
100
- // (read journey scope + the approved build plan + every task's dispatch state)
99
+ // Operator status: `wildo context journey` (eligibility board + runs in flight); per-task landed
100
+ // state is read from git by the runner.
101
101
 
102
102
  You **read** `build-plan`; you **write** no journey
103
103
  artifact — the runner records each dispatched task's change-set + status on its
@@ -189,30 +189,28 @@ today's runner, see the caveat below.
189
189
  arrive only with git worktree-per-agent isolation (the runner task in Step 5's
190
190
  gap note). Until then, keep the input-ready *ordering* and serialize.
191
191
 
192
- // TODO CLI COMMAND: wildo journey run <playbookRef>
193
- // (trigger the scheduled wave; each coding slot invokes the single-flight dispatch contract, each generation step runs its deterministic endpoint)
194
-
195
- ## Step 4 — Authorize the fan-out (approve_before)
196
-
197
- Fanning out **several** coding agents that **mutate the application workspace**
198
- is the highest-stakes action in the journey. This playbook's approval posture is
199
- `approve_before`: the scale run is authorized **before** it touches the tree.
200
- Settle the exact pending Authority Request through the `journey-approve` skill; never start
201
- the fan-out on your own judgment.
202
-
203
- - Under the **GUIDED** autonomy preset the gate is verbatim; under
204
- **YOLO_LIGHT** it downgrades to a post-hoc result review; under **YOLO** it is
205
- auto (the non-bypassable **budget floor** — per-playbook and per-journey
206
- run/wall-time ceilings — is the guardrail no preset can lift).
207
- - **v1 gate granularity (be honest about the floor's reach).** The approval gate
208
- is currently **playbook-scoped for the journey**, not scoped to a single wave:
209
- the first authorization of this scale playbook admits its subsequent runs too
210
- (bounded by the run-count budget floor), rather than re-prompting per wave. So
211
- `approve_before` here means "the creator authorizes the **scale loop** before
212
- any task mutates the workspace" — a real pre-fan-out floor. A per-wave,
213
- single-use gate is a deferred runner posture; until it lands, the budget
214
- ceiling + the per-task change-set capture + the verify gate bound the
215
- authorized loop.
192
+ // The trigger is the companion's run route (`POST /api/companion/playbooks/<ref>/run`) — no CLI
193
+ // trigger yet. Each coding slot invokes the single-flight dispatch contract; each generation step
194
+ // runs its deterministic endpoint.
195
+ // That route is MUTATING, so the call must carry `x-wildo-companion-token`, read from
196
+ // `./.wildo-saas/state/companion.token` (mode 0600). Without it the companion answers `401` with a
197
+ // body that names nothing — the explanation is in the companion's own log.
198
+
199
+ ## Step 4 — Check the actual host authorization boundary
200
+
201
+ A coding dispatch writes the application workspace. Read its selected task, readiness,
202
+ mutation scope and the configured coding host's authorization policy before invoking it.
203
+ The single-flight mutation lock still applies to the current shared workspace.
204
+
205
+ The playbook's `approval` declaration and the journey autonomy presets express policy
206
+ intent. The current playbook runner does not interpret them as pre-dispatch gates,
207
+ automatic authorization, or a GUIDED/YOLO mapping. A declared `approve_before` does
208
+ not create a pending Authority Request. Use `journey-approve` only for an actual
209
+ request from an explicitly connected authority workflow; never invent one from an enum.
210
+
211
+ Likewise, do not infer enforced per-playbook or per-journey run ceilings from declared
212
+ budget fields. Respect the limits actually reported by the execution host. Inspect the
213
+ recorded changes and verification result after each task; no preset commits or accepts them.
216
214
 
217
215
  ## Step 5 — Reconcile wave completion, then advance
218
216
 
@@ -224,7 +222,7 @@ as a blocked / flagged failure. Only then does the next frontier open (Step 1).
224
222
  tasks are still in-flight, or with an unreconciled failure, risks a downstream
225
223
  task building on an unfinished prerequisite. Reconcile first.
226
224
  - **Failure disposition across siblings + downstream** — this playbook's
227
- `onFailure` is **`keep_and_flag`**: a failed/timed-out task keeps its captured
225
+ declared `onFailure` describes **`keep_and_flag`**; the current host retains changes for review. A failed/timed-out task keeps its captured
228
226
  change-set flagged for human triage (never silently reverted, never an
229
227
  un-recorded half-applied state). Its already-dispatched **siblings** in the
230
228
  same wave are left to complete; its **dependents** in later waves stay
@@ -318,18 +316,16 @@ task rows (the build-dispatch playbook's mechanism), not authored here. A
318
316
  separate schedule / wave-log artifact family is deliberately not added: the task
319
317
  rows already *are* the dispatch record and a second home for the same record
320
318
  would drift (a typed wave-schedule / run-ledger contract is a filed later-phase
321
- item). The creator authorizes the scale run (`approve_before`) before it fans
322
- out, and reviews the recorded change-sets + verify outcomes after — wave by
323
- wave, until the build plan is fully dispatched.
319
+ item). Use the configured host's actual authorization boundary and review its
320
+ recorded changes and verification outcomes. The approval declaration alone does
321
+ not authorize or gate dispatch.
324
322
 
325
323
  ## References
326
324
 
327
325
  - `.claude/skills/journey-status/SKILL.md` — read the current journey state,
328
326
  scope, and budget; confirm the build plan is approved and the foundation ran,
329
327
  and read every task's dispatch state to compute the frontier.
330
- - `.claude/skills/journey-approve/SKILL.md` — relay the exact pre-fan-out Authority Request
331
- gate decision that authorizes the workspace-mutating fan-out (never
332
- self-approve).
328
+ - `.claude/skills/journey-run/references/framework-playbook-approval-policy.md` — declaration semantics and the actual runner boundary.
333
329
  - `.claude/skills/journey-run/SKILL.md` — trigger a scheduled wave; each coding
334
330
  slot invokes the single-flight dispatch contract and each deterministic
335
331
  generation step runs its companion endpoint.
@@ -341,4 +337,4 @@ wave, until the build plan is fully dispatched.
341
337
 
342
338
  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:
343
339
 
344
- Judge whether the SCALE orchestration ran the build soundly — the trust-but-verify reviewer pass over how MANY tasks were scheduled, parallelised, and reconciled, WITHOUT straying into how ONE task dispatches (that is the build-dispatch playbook's rubric) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task dispatched in a wave had ALL its prose prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP (the build stage ran against a missing prerequisite). A prerequisite whose run FAILED (its change-set flagged under keep_and_flag) does NOT satisfy the dependency — its dependents must stay blocked, and dispatching them anyway is a GAP. (2) PARALLELISM SAFETY / ATTRIBUTION — the concurrent coding runs in a wave were isolated so each run's change-set is cleanly attributable (files RUN_EXCLUSIVE / APPEARED_DURING_RUN per run), via git worktree-per-agent isolation OR a module/resource partition that puts every concurrent agent on a DISJOINT file set. Two concurrent coding agents mutating the SAME worktree — which makes every touched file BASELINE_DIRTY_AMBIGUOUS and destroys per-run attribution — is a GAP (the single-flight floor was bypassed without an isolation answer). Note the honest floor: the runner enforces single-flight today, so on the current runner a 'wave' degrades to SEQUENTIAL single-flight dispatch and this invariant reads whether the METHOD declared a sound isolation model, not whether concurrency actually ran. (3) COMPANION-GENERATION INTERLEAVE — the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) ran through their deterministic companion endpoints AFTER the resources / modules whose output they consume existed, at the right point in the schedule order; a generation step ordered before its inputs exist, or a missing generation step for authored surfaces, is a CONCERN; treating a deterministic generation step as a coding-agent dispatch (dispatching an agent for it) is a CONCERN. Note the honest floor: the generation steps do NOT take the coding single-flight lock, but the coding change-set capture is a whole-worktree time-window diff, so a generation step writing files WHILE a coding dispatch is capturing is misattributed to that coding run — so on today's runner the generation steps also serialize outside an active coding-capture window, and this invariant reads whether they ran at the right point in the ORDER, not whether they truly overlapped a coding run (safe overlap needs worktree isolation). (4) WAVE-COMPLETION RECONCILIATION — the next wave opened only after every task in the current frontier reached a terminal SUCCEEDED outcome (or was explicitly held as a blocked / flagged failure); advancing the schedule while a wave's tasks were still in-flight or with an unreconciled failure is a GAP (a downstream task could build on an unfinished prerequisite). (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task in a wave kept its captured change-set flagged for human triage (keep_and_flag), its already-dispatched siblings in the same wave were left to complete, and its DEPENDENTS in later waves stayed blocked until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the orchestration stays at SCALE depth: it derives ready-sets, schedules waves, sets the parallelism + isolation model, interleaves the companion-generation steps, and reconciles completion. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT re-specify the per-task dispatch mechanics (single-flight lock / context-pack / change-set capture / verify — the build-dispatch playbook owns those; the scale orchestrator INVOKES that contract per slot), and does NOT itself author schemas / fields / code (the coding agents do that at dispatch time). Evidence of re-decomposition, re-authoring the single-task dispatch contract, or the orchestrator authoring code itself is a CONCERN (scope creep out of the scale lane). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)
340
+ Judge whether the SCALE orchestration ran the build soundly — the trust-but-verify reviewer pass over how MANY tasks were scheduled, parallelised, and reconciled, WITHOUT straying into how ONE task dispatches (that is the build-dispatch playbook's rubric) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task dispatched in a wave had ALL its prose prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP (the build stage ran against a missing prerequisite). A prerequisite whose run FAILED (its change-set flagged under keep_and_flag) does NOT satisfy the dependency — its dependents must stay blocked, and dispatching them anyway is a GAP. (2) PARALLELISM SAFETY / ATTRIBUTION — the concurrent coding runs in a wave were isolated so each run's change-set is cleanly attributable (files RUN_EXCLUSIVE / APPEARED_DURING_RUN per run), via git worktree-per-agent isolation OR a module/resource partition that puts every concurrent agent on a DISJOINT file set. Two concurrent coding agents mutating the SAME worktree — which makes every touched file BASELINE_DIRTY_AMBIGUOUS and destroys per-run attribution — is a GAP (the single-flight floor was bypassed without an isolation answer). Note the honest floor: the runner enforces single-flight today, so on the current runner a 'wave' degrades to SEQUENTIAL single-flight dispatch and this invariant reads whether the METHOD declared a sound isolation model, not whether concurrency actually ran. (3) COMPANION-GENERATION INTERLEAVE — the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) ran through their deterministic companion endpoints AFTER the resources / modules whose output they consume existed, at the right point in the schedule order; a generation step ordered before its inputs exist, or a missing generation step for authored surfaces, is a CONCERN; treating a deterministic generation step as a coding-agent dispatch (dispatching an agent for it) is a CONCERN. Note the honest floor: the generation steps do NOT take the coding single-flight lock, but the coding change-set capture is a whole-worktree time-window diff, so a generation step writing files WHILE a coding dispatch is capturing is misattributed to that coding run — so on today's runner the generation steps also serialize outside an active coding-capture window, and this invariant reads whether they ran at the right point in the ORDER, not whether they truly overlapped a coding run (safe overlap needs worktree isolation). (4) WAVE-COMPLETION RECONCILIATION — the next wave opened only after every task in the current frontier reached a terminal SUCCEEDED outcome (or was explicitly held as a blocked / flagged failure); advancing the schedule while a wave's tasks were still in-flight or with an unreconciled failure is a GAP (a downstream task could build on an unfinished prerequisite). (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task in a wave kept its captured change-set flagged for human triage (keep_and_flag), its already-dispatched siblings in the same wave were left to complete, and its DEPENDENTS in later waves stayed blocked until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the orchestration stays at SCALE depth: it derives ready-sets, schedules waves, sets the parallelism + isolation model, interleaves the companion-generation steps, and reconciles completion. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT re-specify the per-task dispatch mechanics (single-flight lock / context-pack / change-set capture / verify — the build-dispatch playbook owns those; the scale orchestrator INVOKES that contract per slot), and does NOT itself author schemas / fields / code (the coding agents do that at dispatch time). Evidence of re-decomposition, re-authoring the single-task dispatch contract, or the orchestrator authoring code itself is a CONCERN (scope creep out of the scale lane). (The checklist is declarative: nothing executes it; the current host's deterministic checks apply; the approval enum alone adds no gate.)
@@ -3,12 +3,7 @@
3
3
  "version": "0.1.0",
4
4
  "phase": "bottom_up",
5
5
  "intent": "Bottom-up build scale — the THIRD and final build-execution playbook, the pivot from dispatching ONE task safely (the single-flight dispatch contract) to running the build at SCALE: parallelism across several coding agents, the concurrency schedule, and interleaving the companion-owned generation steps concurrently with coding runs. Reads the approved build-plan (the ordered coding-agent task graph, each task carrying a target, ONE MetaWorkflow_FunctionalTopic, its skill(s), and prose prerequisite ordering) and the current journey state, and answers the SCALE questions the single-flight dispatch playbook deliberately left open: (1) derive the ready-SET (a wave / frontier of tasks whose prose prerequisites have ALL SUCCEEDED — not merely been attempted); (2) decide the parallelism degree (how many coding agents run at once) and the worktree-isolation model that keeps each concurrent run's change-set cleanly attributable; (3) schedule the waves respecting the DEPENDS_ON ordering the build-plan encodes; (4) interleave the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) concurrently with coding runs at the points their inputs exist — those steps run through their deterministic companion endpoints, NOT the coding-agent single-flight lock, so they genuinely overlap coding runs; (5) reconcile wave completion across the concurrent runs (all tasks in the frontier SUCCEEDED before the next wave opens) and apply onFailure across siblings + downstream. Then advance to the next wave and loop. Each parallel slot INVOKES the single-flight dispatch contract (the build-dispatch playbook, upstream — select-next / context-pack / one ACP prompt turn / change-set capture / verify-outside / record + onFailure); this playbook does NOT re-specify those per-task mechanics and does NOT re-decompose the plan (the build-decompose playbook owns the task graph) and authors no schemas / no code. IMPORTANT HONESTY: the companion runner HARD-ENFORCES single-flight today (a run plan carries at most ONE coding-agent task; a concurrent dispatch is refused; the workspace-mutation lock + the lock-free cursor + the missing run-outcome observation loop all assume one dispatch at a time). So this v1 scale METHOD is the DECLARATIVE TARGET a runner-serializer slice will realize — on the current runner the waves DEGRADE to sequential single-flight dispatch. And even the deterministic companion-generation steps, though they do not take the coding single-flight lock, cannot SAFELY overlap an active coding run today: the coding run's change-set is captured as a whole-worktree time-window diff, so a generation step writing files inside that window is misattributed to the coding run (the same whole-worktree pollution that forbids two concurrent coding agents) — so the generation steps also serialize outside an active coding-capture window today, and genuine concurrency (coding-parallel OR generation-overlap) both arrive only with the git worktree-per-agent isolation runner task. v1 scaffold: a multi-CODING_AGENT run-completion serializer, git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock are companion-runner mechanism filed as runner tasks, NOT built here; a priority/work-stealing scheduler and cost-optimal packing are a later depth phase.",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "bottom_up"
11
- },
12
7
  {
13
8
  "kind": "artifact_exists",
14
9
  "selector": {
@@ -22,24 +17,23 @@
22
17
  }
23
18
  ],
24
19
  "outputs": [],
20
+ "stepOutputs": [],
25
21
  "method": {
26
- "guidance": "# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and a deliberately honest one.** It is a\n> working first cut of the *scale* orchestration — derive a wave of ready tasks,\n> run several coding agents in parallel under an isolation model, interleave the\n> deterministic companion-generation steps, and reconcile wave completion. But\n> the companion runner **hard-enforces single-flight today**: it refuses a run\n> plan with more than one coding-agent task, refuses a second dispatch while one\n> is active, holds one workspace-mutation lock per run, and has no run-outcome\n> reconciler. So the concurrency described below is the **declarative target** a\n> runner-serializer slice will realize. **On the current runner the waves\n> degrade to sequential single-flight dispatch** — read the \"What the runner\n> actually does today\" section before you assume anything ran in parallel. Do\n> not overclaim concurrency the runner cannot do.\n\n## Where you are in the journey\n\nThis is the **third and final build-execution playbook** — the pivot from\n**dispatching one task safely** (the build-dispatch playbook's single-flight\ncontract) to **running the build at scale**. It runs in the **bottom-up phase**,\nafter the build plan exists (`artifact_exists build-plan`) and the foundation\nstep has authored the app's config and skeleton. You\nare not re-opening the decomposition here, and you are not re-specifying how one\ntask dispatches — you are deciding **how many** tasks run **concurrently** and\n**safely**, in **what order**, with the companion-generation steps interleaved.\n\nUpstream: the **build-decompose** playbook produced the ordered task graph you\nschedule; the **build-dispatch** playbook defined how ONE task dispatches\nsafely — you **invoke that contract per parallel slot**, you do not re-author\nit. **You author neither of those concerns** — see the boundary section.\n\n## What this playbook does\n\nYou are the **scale orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, across the *whole* build: *\"which set\nof tasks is ready to run now, how many run at once and on what isolation, when\ndo the deterministic generation steps run, and when has a wave actually\nfinished?\"* You do **not** produce a new journey artifact — the observable\nresult of the build is the per-task change-sets + task statuses the runner\nrecords on the task rows (the build-dispatch playbook's mechanism), not a\nschedule artifact authored here (see \"What you emit\"). You do **not** decompose\nthe plan, re-specify the per-task dispatch mechanics, author any schema, or\nwrite any code.\n\n## The scale contract — you sequence waves, the dispatch playbook runs each slot\n\nMost of the *per-task* mechanism is **not yours**: selecting one task,\ncomposing its context pack, running one prompt turn against the coding agent over\nthe Agent Client Protocol (answering its permission requests within the declared\nceiling), capturing the change-set, running the verify hook, holding the\nsingle-flight lock, enforcing the budget floor — all of that is the **build-dispatch** contract, which each\nparallel slot invokes. Your method here is the **declarative concurrency\nrecipe** the runner (or a future runner-serializer) interprets: *which set* of\ntasks is ready, *how many* run at once, *how* they are isolated, *when* the\ndeterministic generation steps interleave, and *when* a wave is done. Do not\nhand-drive git, do not compose a dispatch prompt, do not re-implement the\nsingle-flight capture — invoke the dispatch contract per slot and let it own\nthose.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the schedule by one\nwave* (and, on today's single-flight runner, by one task within that wave).\nBefore scheduling anything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here). Confirm the **build plan** is\n present and approved and the **foundation** ran. For each build-plan task,\n read its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify),\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run\n or a failed verify), or **in-flight**. This full state — not just \"has a\n change-set\" — is what the wave derivation keys on (under `keep_and_flag` a\n *failed* task also has a captured change-set, so presence of a change-set\n alone never means \"done\").\n2. Read the approved **build plan** (`build-plan` — the ordered task graph, with\n each task's prose prerequisite references). It is your work list.\n\n That there is an application to dispatch into is answered by the committed\n `./wildo.saas.config.ts` and skeleton, not by a journey artifact. (A\n `foundation-manifest` played that role until 2026-08-25 and was retired with the\n app-creation verification/digest aspect.) The honest limitation the foundation step\n carries still applies: on-disk skeleton materialization depends on greenfield\n bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale\n contract runs against an existing workspace.\n\n// TODO CLI COMMAND: wildo journey status\n// (read journey scope + the approved build plan + every task's dispatch state)\n\nYou **read** `build-plan`; you **write** no journey\nartifact — the runner records each dispatched task's change-set + status on its\nrow.\n\n## Step 1 — Derive the ready-set (the wave / frontier)\n\nWalk the build plan and compute the **frontier**: the set of tasks that are\n**not yet dispatched** (or previously-**failed** tasks cleared for retry) and\nwhose prose prerequisites have **all SUCCEEDED**. That set is the next **wave**.\n\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task\n enters the frontier only when every task it depends on is\n dispatched-and-succeeded (verify passed). A prerequisite that is\n dispatched-and-**failed** (its change-set flagged for triage under\n `keep_and_flag`), still **in-flight**, or un-run does **not** satisfy the\n dependency — its dependents stay **out of the frontier** until it succeeds.\n This is the U13b readiness discipline, lifted to a set: do not open a wave on\n a schema whose run has not verified.\n- **The wave respects the build-plan ordering.** The build-decompose playbook\n encoded the DEPENDS_ON edges (the per-resource stage order schema → config →\n ui-behavior → spec, the cross-topic edges, relationship-after-endpoints); the\n frontier is exactly the tasks with no unsatisfied edge remaining. You do not\n re-derive or re-order those edges — you read them and compute the ready-set.\n- **An empty frontier is a terminal state.** If no task is ready — every task\n has succeeded, or the only undispatched tasks are blocked behind an\n unresolved failure — the build is done (or blocked on a flagged failure):\n report it and stop. An empty build plan is the same.\n\n## Step 2 — Decide the parallelism degree + the worktree-isolation model\n\nFor the frontier, decide **how many** coding agents run at once and **on what\nisolation**. This is the core scale decision, and it is bounded by a hard\nsafety constraint, not just throughput:\n\n- **Change-set attribution requires isolation.** The dispatch contract captures\n each run's change-set by diffing the worktree around the run and attributing\n every file as `RUN_EXCLUSIVE`, `APPEARED_DURING_RUN`, or\n `BASELINE_DIRTY_AMBIGUOUS`. **Two coding agents mutating the SAME worktree\n concurrently make every touched file `BASELINE_DIRTY_AMBIGUOUS`** — each run\n looks like it started against a tree the other was dirtying — which\n **destroys per-run attribution**. So real parallelism needs one of:\n - **git worktree-per-agent isolation** — each concurrent coding agent runs in\n its own git worktree (a disjoint checkout of the same repo), so each run's\n change-set is captured against a tree only it mutates; the worktrees are\n reconciled/merged after the wave. This is the general answer.\n - **module / resource partitioning** — schedule concurrent agents only onto\n tasks whose targets touch **disjoint file sets** (different modules /\n resources), so even on one shared worktree no two runs collide. This is the\n cheaper answer when the frontier naturally partitions by module.\n - **or keep coding single-flight** and only parallelise the deterministic\n companion-generation steps (Step 3), which are not coding-locked.\n- **Pick the degree deliberately, not maximally.** At scaffold depth prefer a\n small degree (or a module partition) over max fan-out — cost-optimal packing,\n a priority / work-stealing scheduler, and backoff are a later depth phase, not\n this scaffold. State the isolation model you chose; a wave with degree > 1 and\n **no** isolation answer is unsafe (the reviewer rubric flags it as a GAP).\n\n## Step 3 — Interleave the deterministic companion-generation steps\n\nThe build plan carries **companion-owned generation steps** — labels / i18n,\nemail templates, seeds — as tasks. These are **deterministic companion\nendpoints**, not coding-agent dispatches: they do **not** contend for the\ncoding single-flight lock. It is tempting to conclude they can freely run\n*alongside* a coding run — but there is a subtlety that makes that unsafe on\ntoday's runner, see the caveat below.\n\n- **Run each generation step at its input-ready point.** A labels/i18n step runs\n after the resources it labels exist; an email step after its templates'\n definition surfaces exist; a seed step after the resources it seeds exist.\n Schedule each at its input-ready point in the wave sequence — do not block a\n coding wave on them and do not run them before their inputs exist. (The\n *ordering* is what matters here; the *concurrency* is deferred — see the\n caveat.)\n- **Route them to their deterministic endpoint, not the coding lane.** Do not\n dispatch a coding agent for a labels/email/seed step — it has a deterministic\n companion generator. Treating a generation step as a coding dispatch is scope\n creep the reviewer flags.\n- **CAVEAT — no attribution-safe overlap with an active coding run today.** The\n coding run's change-set is captured as a **whole-worktree time-window diff**\n (every tracked-dirty + untracked file in the window). So a generation step\n writing label / email / seed files **while a coding dispatch is capturing** is\n misattributed to that coding run — its files show up as the coding run's own\n edits. This is the *same* whole-worktree pollution that forbids two concurrent\n coding agents (Step 2), and it applies identically to coding + generation. So\n on today's runner the generation steps must **also** be serialized to run\n **outside** an active coding-capture window (i.e. between coding runs). Genuine\n overlap — generation alongside coding, and coding alongside coding — both\n arrive only with git worktree-per-agent isolation (the runner task in Step 5's\n gap note). Until then, keep the input-ready *ordering* and serialize.\n\n// TODO CLI COMMAND: wildo journey run <playbookRef>\n// (trigger the scheduled wave; each coding slot invokes the single-flight dispatch contract, each generation step runs its deterministic endpoint)\n\n## Step 4 — Authorize the fan-out (approve_before)\n\nFanning out **several** coding agents that **mutate the application workspace**\nis the highest-stakes action in the journey. This playbook's approval posture is\n`approve_before`: the scale run is authorized **before** it touches the tree.\nSettle the exact pending Authority Request through the `journey-approve` skill; never start\nthe fan-out on your own judgment.\n\n- Under the **GUIDED** autonomy preset the gate is verbatim; under\n **YOLO_LIGHT** it downgrades to a post-hoc result review; under **YOLO** it is\n auto (the non-bypassable **budget floor** — per-playbook and per-journey\n run/wall-time ceilings — is the guardrail no preset can lift).\n- **v1 gate granularity (be honest about the floor's reach).** The approval gate\n is currently **playbook-scoped for the journey**, not scoped to a single wave:\n the first authorization of this scale playbook admits its subsequent runs too\n (bounded by the run-count budget floor), rather than re-prompting per wave. So\n `approve_before` here means \"the creator authorizes the **scale loop** before\n any task mutates the workspace\" — a real pre-fan-out floor. A per-wave,\n single-use gate is a deferred runner posture; until it lands, the budget\n ceiling + the per-task change-set capture + the verify gate bound the\n authorized loop.\n\n## Step 5 — Reconcile wave completion, then advance\n\nA wave is done only when **every task in the frontier reached a terminal\nSUCCEEDED outcome** (change-set captured + verify passed) or is explicitly held\nas a blocked / flagged failure. Only then does the next frontier open (Step 1).\n\n- **Do not open the next wave on an unfinished one.** Advancing while a wave's\n tasks are still in-flight, or with an unreconciled failure, risks a downstream\n task building on an unfinished prerequisite. Reconcile first.\n- **Failure disposition across siblings + downstream** — this playbook's\n `onFailure` is **`keep_and_flag`**: a failed/timed-out task keeps its captured\n change-set flagged for human triage (never silently reverted, never an\n un-recorded half-applied state). Its already-dispatched **siblings** in the\n same wave are left to complete; its **dependents** in later waves stay\n **blocked** (Step 1) until it is triaged and re-dispatched successfully.\n Triage is a human decision: keep + fix forward, unwind the flagged change-set\n by hand, or re-dispatch once the blocker is resolved. This playbook does not\n auto-retry a failed task (automated retry / backoff is a deferred build-loop\n resilience concern).\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a\n> failed run's edits is a *mutating* git op, deliberately **outside** the\n> read-only change-set carve-out the dispatch lane observes. So `keep_and_flag`\n> is both the correct F-5 workspace-safety posture and the behavior the runner\n> enforces today; a `revert_changeset` path is a deliberate later boundary.\n\nThen **loop**: on the next run, `journey-status` reflects the just-completed\nwave's outcomes, and you derive the next frontier (Step 1). Close a significant\nstretch of the build with a `journey-report` summary — which waves ran, which\nchange-sets landed, what verify said, which generation steps interleaved, and\nany failed task left flagged for triage.\n\n## What the runner actually does today (do not overclaim)\n\nBe honest with the creator about the gap between this method and the runner:\n\n- **The runner enforces single-flight.** It refuses a run plan carrying more\n than one coding-agent task, refuses a second dispatch while one is active, and\n holds one workspace-mutation lock per background run. So a wave with\n parallelism degree > 1 is **not** realizable on today's runner — the wave\n **degrades to sequential single-flight dispatch** (repeated invocation of the\n build-dispatch contract, one task at a time, in frontier order). The frontier\n math, the readiness discipline, and the reconciliation are all still correct\n and useful sequentially — you just do not get concurrency yet.\n- **No overlap is attribution-safe today — not even a companion-generation\n step.** The generation endpoints are not coding-locked, but the coding\n change-set capture is a whole-worktree time-window diff, so a generation step\n writing files while a coding dispatch is capturing is misattributed to that\n run (Step 3's caveat). So the generation steps **also** serialize outside an\n active coding-capture window: their input-ready *ordering* holds, only the\n *concurrency* is deferred. Safe overlap of generation-with-coding, and\n coding-with-coding, both require git worktree-per-agent isolation.\n- **The concurrency this method describes is the declarative target** for a\n runner-serializer slice (multi-coding-agent run-completion serialization,\n git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock)\n — filed as runner tasks, **not** built by this scaffold playbook. Until they\n land, run the waves sequentially and do not claim a parallel run (or a\n generation-alongside-coding overlap) happened when it did not.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **scale-orchestration depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order\n the graph, or add tasks — the **build-decompose** playbook owns the task\n graph. You read it and schedule from it.\n- **The per-task dispatch contract.** You do NOT re-specify single-flight\n locking, context-pack composition, change-set capture, or the verify hook —\n the **build-dispatch** playbook owns \"how ONE task dispatches safely\", and\n each parallel slot **invokes** that contract. If you catch yourself describing\n how a single task captures its change-set, stop — that is the dispatch\n playbook.\n- **The runner-serializer mechanism.** The multi-coding-agent serializer, git\n worktree-per-agent provisioning, the run-outcome reconciler, and the cursor\n lock are **companion-runner mechanism**, filed as runner tasks — this\n declarative method does not build them.\n- **A priority / work-stealing scheduler + cost-optimal packing.** Deciding an\n optimal task ordering within a band, work-stealing across idle slots, backoff,\n and cost-optimal packing are a later depth phase — the v1 scaffold picks a\n small parallelism degree (or a module partition) and a simple frontier order.\n- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the v1\n disposition.\n- **Auto-executed reviewer checklist.** The scale-soundness checklist ships\n **declarative** — the deterministic typecheck gate runs automatically; nothing\n executes the checklist prose (rubric-only judge gates were retired at the\n flexible-intelligence hard cut). Do not assume it auto-ran.\n- **Schema / field authoring + code generation.** The **coding agents** author\n fields, schemas, ui-behavior, and code at dispatch time — never the\n orchestrator.\n\nIf you find yourself designing how ONE task dispatches safely rather than how\nMANY tasks are scheduled + reconciled, stop — that is the build-dispatch\nplaybook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable\nresult of the build — each task's **change-set** (files touched, attributed,\nsummarized) and **status** — is materialized by the runner on the dispatched\ntask rows (the build-dispatch playbook's mechanism), not authored here. A\nseparate schedule / wave-log artifact family is deliberately not added: the task\nrows already *are* the dispatch record and a second home for the same record\nwould drift (a typed wave-schedule / run-ledger contract is a filed later-phase\nitem). The creator authorizes the scale run (`approve_before`) before it fans\nout, and reviews the recorded change-sets + verify outcomes after — wave by\nwave, until the build plan is fully dispatched.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state,\n scope, and budget; confirm the build plan is approved and the foundation ran,\n and read every task's dispatch state to compute the frontier.\n- `.claude/skills/journey-approve/SKILL.md` — relay the exact pre-fan-out Authority Request\n gate decision that authorizes the workspace-mutating fan-out (never\n self-approve).\n- `.claude/skills/journey-run/SKILL.md` — trigger a scheduled wave; each coding\n slot invokes the single-flight dispatch contract and each deterministic\n generation step runs its companion endpoint.\n- `.claude/skills/journey-report/SKILL.md` — summarize a stretch of the build:\n which waves ran, which change-sets landed, what verify said, and any failed\n task left flagged for triage.\n\n## Reviewer checklist — `scale-schedule-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the SCALE orchestration ran the build soundly — the trust-but-verify reviewer pass over how MANY tasks were scheduled, parallelised, and reconciled, WITHOUT straying into how ONE task dispatches (that is the build-dispatch playbook's rubric) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task dispatched in a wave had ALL its prose prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP (the build stage ran against a missing prerequisite). A prerequisite whose run FAILED (its change-set flagged under keep_and_flag) does NOT satisfy the dependency — its dependents must stay blocked, and dispatching them anyway is a GAP. (2) PARALLELISM SAFETY / ATTRIBUTION — the concurrent coding runs in a wave were isolated so each run's change-set is cleanly attributable (files RUN_EXCLUSIVE / APPEARED_DURING_RUN per run), via git worktree-per-agent isolation OR a module/resource partition that puts every concurrent agent on a DISJOINT file set. Two concurrent coding agents mutating the SAME worktree — which makes every touched file BASELINE_DIRTY_AMBIGUOUS and destroys per-run attribution — is a GAP (the single-flight floor was bypassed without an isolation answer). Note the honest floor: the runner enforces single-flight today, so on the current runner a 'wave' degrades to SEQUENTIAL single-flight dispatch and this invariant reads whether the METHOD declared a sound isolation model, not whether concurrency actually ran. (3) COMPANION-GENERATION INTERLEAVE — the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) ran through their deterministic companion endpoints AFTER the resources / modules whose output they consume existed, at the right point in the schedule order; a generation step ordered before its inputs exist, or a missing generation step for authored surfaces, is a CONCERN; treating a deterministic generation step as a coding-agent dispatch (dispatching an agent for it) is a CONCERN. Note the honest floor: the generation steps do NOT take the coding single-flight lock, but the coding change-set capture is a whole-worktree time-window diff, so a generation step writing files WHILE a coding dispatch is capturing is misattributed to that coding run — so on today's runner the generation steps also serialize outside an active coding-capture window, and this invariant reads whether they ran at the right point in the ORDER, not whether they truly overlapped a coding run (safe overlap needs worktree isolation). (4) WAVE-COMPLETION RECONCILIATION — the next wave opened only after every task in the current frontier reached a terminal SUCCEEDED outcome (or was explicitly held as a blocked / flagged failure); advancing the schedule while a wave's tasks were still in-flight or with an unreconciled failure is a GAP (a downstream task could build on an unfinished prerequisite). (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task in a wave kept its captured change-set flagged for human triage (keep_and_flag), its already-dispatched siblings in the same wave were left to complete, and its DEPENDENTS in later waves stayed blocked until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the orchestration stays at SCALE depth: it derives ready-sets, schedules waves, sets the parallelism + isolation model, interleaves the companion-generation steps, and reconciles completion. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT re-specify the per-task dispatch mechanics (single-flight lock / context-pack / change-set capture / verify — the build-dispatch playbook owns those; the scale orchestrator INVOKES that contract per slot), and does NOT itself author schemas / fields / code (the coding agents do that at dispatch time). Evidence of re-decomposition, re-authoring the single-task dispatch contract, or the orchestrator authoring code itself is a CONCERN (scope creep out of the scale lane). (The checklist is declarative: nothing executes it; the deterministic gates and the creator's approval remain the floors.)\n",
22
+ "guidance": "# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and a deliberately honest one.** It is a\n> working first cut of the *scale* orchestration — derive a wave of ready tasks,\n> run several coding agents in parallel under an isolation model, interleave the\n> deterministic companion-generation steps, and reconcile wave completion. But\n> the companion runner **hard-enforces single-flight today**: it refuses a run\n> plan with more than one coding-agent task, refuses a second dispatch while one\n> is active, holds one workspace-mutation lock per run, and has no run-outcome\n> reconciler. So the concurrency described below is the **declarative target** a\n> runner-serializer slice will realize. **On the current runner the waves\n> degrade to sequential single-flight dispatch** — read the \"What the runner\n> actually does today\" section before you assume anything ran in parallel. Do\n> not overclaim concurrency the runner cannot do.\n\n## Where you are in the journey\n\nThis is the **third and final build-execution playbook** — the pivot from\n**dispatching one task safely** (the build-dispatch playbook's single-flight\ncontract) to **running the build at scale**. It runs in the **bottom-up phase**,\nafter the build plan exists (`artifact_exists build-plan`) and the foundation\nstep has authored the app's config and skeleton. You\nare not re-opening the decomposition here, and you are not re-specifying how one\ntask dispatches — you are deciding **how many** tasks run **concurrently** and\n**safely**, in **what order**, with the companion-generation steps interleaved.\n\nUpstream: the **build-decompose** playbook produced the ordered task graph you\nschedule; the **build-dispatch** playbook defined how ONE task dispatches\nsafely — you **invoke that contract per parallel slot**, you do not re-author\nit. **You author neither of those concerns** — see the boundary section.\n\n## What this playbook does\n\nYou are the **scale orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, across the *whole* build: *\"which set\nof tasks is ready to run now, how many run at once and on what isolation, when\ndo the deterministic generation steps run, and when has a wave actually\nfinished?\"* You do **not** produce a new journey artifact — the observable\nresult of the build is the per-task change-sets + task statuses the runner\nrecords on the task rows (the build-dispatch playbook's mechanism), not a\nschedule artifact authored here (see \"What you emit\"). You do **not** decompose\nthe plan, re-specify the per-task dispatch mechanics, author any schema, or\nwrite any code.\n\n## The scale contract — you sequence waves, the dispatch playbook runs each slot\n\nMost of the *per-task* mechanism is **not yours**: selecting one task,\ncomposing its context pack, running one prompt turn against the coding agent over\nthe Agent Client Protocol (answering its permission requests within the declared\nceiling), capturing the change-set, running the verify hook, holding the\nsingle-flight lock, applying the host's actual execution limits — all of that is the **build-dispatch** contract, which each\nparallel slot invokes. Your method here is the **declarative concurrency\nrecipe** the runner (or a future runner-serializer) interprets: *which set* of\ntasks is ready, *how many* run at once, *how* they are isolated, *when* the\ndeterministic generation steps interleave, and *when* a wave is done. Do not\nhand-drive git, do not compose a dispatch prompt, do not re-implement the\nsingle-flight capture — invoke the dispatch contract per slot and let it own\nthose.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the schedule by one\nwave* (and, on today's single-flight runner, by one task within that wave).\nBefore scheduling anything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here). Confirm the **build plan** is\n present and approved and the **foundation** ran. For each build-plan task,\n read its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify),\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run\n or a failed verify), or **in-flight**. This full state — not just \"has a\n change-set\" — is what the wave derivation keys on (under `keep_and_flag` a\n *failed* task also has a captured change-set, so presence of a change-set\n alone never means \"done\").\n2. Read the approved **build plan** (`build-plan` — the ordered task graph, with\n each task's prose prerequisite references). It is your work list.\n\n That there is an application to dispatch into is answered by the committed\n `./wildo.saas.config.ts` and skeleton, not by a journey artifact. (A\n `foundation-manifest` played that role until 2026-08-25 and was retired with the\n app-creation verification/digest aspect.) The honest limitation the foundation step\n carries still applies: on-disk skeleton materialization depends on greenfield\n bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale\n contract runs against an existing workspace.\n\n// Operator status: `wildo context journey` (eligibility board + runs in flight); per-task landed\n// state is read from git by the runner.\n\nYou **read** `build-plan`; you **write** no journey\nartifact — the runner records each dispatched task's change-set + status on its\nrow.\n\n## Step 1 — Derive the ready-set (the wave / frontier)\n\nWalk the build plan and compute the **frontier**: the set of tasks that are\n**not yet dispatched** (or previously-**failed** tasks cleared for retry) and\nwhose prose prerequisites have **all SUCCEEDED**. That set is the next **wave**.\n\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task\n enters the frontier only when every task it depends on is\n dispatched-and-succeeded (verify passed). A prerequisite that is\n dispatched-and-**failed** (its change-set flagged for triage under\n `keep_and_flag`), still **in-flight**, or un-run does **not** satisfy the\n dependency — its dependents stay **out of the frontier** until it succeeds.\n This is the U13b readiness discipline, lifted to a set: do not open a wave on\n a schema whose run has not verified.\n- **The wave respects the build-plan ordering.** The build-decompose playbook\n encoded the DEPENDS_ON edges (the per-resource stage order schema → config →\n ui-behavior → spec, the cross-topic edges, relationship-after-endpoints); the\n frontier is exactly the tasks with no unsatisfied edge remaining. You do not\n re-derive or re-order those edges — you read them and compute the ready-set.\n- **An empty frontier is a terminal state.** If no task is ready — every task\n has succeeded, or the only undispatched tasks are blocked behind an\n unresolved failure — the build is done (or blocked on a flagged failure):\n report it and stop. An empty build plan is the same.\n\n## Step 2 — Decide the parallelism degree + the worktree-isolation model\n\nFor the frontier, decide **how many** coding agents run at once and **on what\nisolation**. This is the core scale decision, and it is bounded by a hard\nsafety constraint, not just throughput:\n\n- **Change-set attribution requires isolation.** The dispatch contract captures\n each run's change-set by diffing the worktree around the run and attributing\n every file as `RUN_EXCLUSIVE`, `APPEARED_DURING_RUN`, or\n `BASELINE_DIRTY_AMBIGUOUS`. **Two coding agents mutating the SAME worktree\n concurrently make every touched file `BASELINE_DIRTY_AMBIGUOUS`** — each run\n looks like it started against a tree the other was dirtying — which\n **destroys per-run attribution**. So real parallelism needs one of:\n - **git worktree-per-agent isolation** — each concurrent coding agent runs in\n its own git worktree (a disjoint checkout of the same repo), so each run's\n change-set is captured against a tree only it mutates; the worktrees are\n reconciled/merged after the wave. This is the general answer.\n - **module / resource partitioning** — schedule concurrent agents only onto\n tasks whose targets touch **disjoint file sets** (different modules /\n resources), so even on one shared worktree no two runs collide. This is the\n cheaper answer when the frontier naturally partitions by module.\n - **or keep coding single-flight** and only parallelise the deterministic\n companion-generation steps (Step 3), which are not coding-locked.\n- **Pick the degree deliberately, not maximally.** At scaffold depth prefer a\n small degree (or a module partition) over max fan-out — cost-optimal packing,\n a priority / work-stealing scheduler, and backoff are a later depth phase, not\n this scaffold. State the isolation model you chose; a wave with degree > 1 and\n **no** isolation answer is unsafe (the reviewer rubric flags it as a GAP).\n\n## Step 3 — Interleave the deterministic companion-generation steps\n\nThe build plan carries **companion-owned generation steps** — labels / i18n,\nemail templates, seeds — as tasks. These are **deterministic companion\nendpoints**, not coding-agent dispatches: they do **not** contend for the\ncoding single-flight lock. It is tempting to conclude they can freely run\n*alongside* a coding run — but there is a subtlety that makes that unsafe on\ntoday's runner, see the caveat below.\n\n- **Run each generation step at its input-ready point.** A labels/i18n step runs\n after the resources it labels exist; an email step after its templates'\n definition surfaces exist; a seed step after the resources it seeds exist.\n Schedule each at its input-ready point in the wave sequence — do not block a\n coding wave on them and do not run them before their inputs exist. (The\n *ordering* is what matters here; the *concurrency* is deferred — see the\n caveat.)\n- **Route them to their deterministic endpoint, not the coding lane.** Do not\n dispatch a coding agent for a labels/email/seed step — it has a deterministic\n companion generator. Treating a generation step as a coding dispatch is scope\n creep the reviewer flags.\n- **CAVEAT — no attribution-safe overlap with an active coding run today.** The\n coding run's change-set is captured as a **whole-worktree time-window diff**\n (every tracked-dirty + untracked file in the window). So a generation step\n writing label / email / seed files **while a coding dispatch is capturing** is\n misattributed to that coding run — its files show up as the coding run's own\n edits. This is the *same* whole-worktree pollution that forbids two concurrent\n coding agents (Step 2), and it applies identically to coding + generation. So\n on today's runner the generation steps must **also** be serialized to run\n **outside** an active coding-capture window (i.e. between coding runs). Genuine\n overlap — generation alongside coding, and coding alongside coding — both\n arrive only with git worktree-per-agent isolation (the runner task in Step 5's\n gap note). Until then, keep the input-ready *ordering* and serialize.\n\n// The trigger is the companion's run route (`POST /api/companion/playbooks/<ref>/run`) — no CLI\n// trigger yet. Each coding slot invokes the single-flight dispatch contract; each generation step\n// runs its deterministic endpoint.\n// That route is MUTATING, so the call must carry `x-wildo-companion-token`, read from\n// `./.wildo-saas/state/companion.token` (mode 0600). Without it the companion answers `401` with a\n// body that names nothing — the explanation is in the companion's own log.\n\n## Step 4 — Check the actual host authorization boundary\n\nA coding dispatch writes the application workspace. Read its selected task, readiness,\nmutation scope and the configured coding host's authorization policy before invoking it.\nThe single-flight mutation lock still applies to the current shared workspace.\n\nThe playbook's `approval` declaration and the journey autonomy presets express policy\nintent. The current playbook runner does not interpret them as pre-dispatch gates,\nautomatic authorization, or a GUIDED/YOLO mapping. A declared `approve_before` does\nnot create a pending Authority Request. Use `journey-approve` only for an actual\nrequest from an explicitly connected authority workflow; never invent one from an enum.\n\nLikewise, do not infer enforced per-playbook or per-journey run ceilings from declared\nbudget fields. Respect the limits actually reported by the execution host. Inspect the\nrecorded changes and verification result after each task; no preset commits or accepts them.\n\n## Step 5 — Reconcile wave completion, then advance\n\nA wave is done only when **every task in the frontier reached a terminal\nSUCCEEDED outcome** (change-set captured + verify passed) or is explicitly held\nas a blocked / flagged failure. Only then does the next frontier open (Step 1).\n\n- **Do not open the next wave on an unfinished one.** Advancing while a wave's\n tasks are still in-flight, or with an unreconciled failure, risks a downstream\n task building on an unfinished prerequisite. Reconcile first.\n- **Failure disposition across siblings + downstream** — this playbook's\n declared `onFailure` describes **`keep_and_flag`**; the current host retains changes for review. A failed/timed-out task keeps its captured\n change-set flagged for human triage (never silently reverted, never an\n un-recorded half-applied state). Its already-dispatched **siblings** in the\n same wave are left to complete; its **dependents** in later waves stay\n **blocked** (Step 1) until it is triaged and re-dispatched successfully.\n Triage is a human decision: keep + fix forward, unwind the flagged change-set\n by hand, or re-dispatch once the blocker is resolved. This playbook does not\n auto-retry a failed task (automated retry / backoff is a deferred build-loop\n resilience concern).\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a\n> failed run's edits is a *mutating* git op, deliberately **outside** the\n> read-only change-set carve-out the dispatch lane observes. So `keep_and_flag`\n> is both the correct F-5 workspace-safety posture and the behavior the runner\n> enforces today; a `revert_changeset` path is a deliberate later boundary.\n\nThen **loop**: on the next run, `journey-status` reflects the just-completed\nwave's outcomes, and you derive the next frontier (Step 1). Close a significant\nstretch of the build with a `journey-report` summary — which waves ran, which\nchange-sets landed, what verify said, which generation steps interleaved, and\nany failed task left flagged for triage.\n\n## What the runner actually does today (do not overclaim)\n\nBe honest with the creator about the gap between this method and the runner:\n\n- **The runner enforces single-flight.** It refuses a run plan carrying more\n than one coding-agent task, refuses a second dispatch while one is active, and\n holds one workspace-mutation lock per background run. So a wave with\n parallelism degree > 1 is **not** realizable on today's runner — the wave\n **degrades to sequential single-flight dispatch** (repeated invocation of the\n build-dispatch contract, one task at a time, in frontier order). The frontier\n math, the readiness discipline, and the reconciliation are all still correct\n and useful sequentially — you just do not get concurrency yet.\n- **No overlap is attribution-safe today — not even a companion-generation\n step.** The generation endpoints are not coding-locked, but the coding\n change-set capture is a whole-worktree time-window diff, so a generation step\n writing files while a coding dispatch is capturing is misattributed to that\n run (Step 3's caveat). So the generation steps **also** serialize outside an\n active coding-capture window: their input-ready *ordering* holds, only the\n *concurrency* is deferred. Safe overlap of generation-with-coding, and\n coding-with-coding, both require git worktree-per-agent isolation.\n- **The concurrency this method describes is the declarative target** for a\n runner-serializer slice (multi-coding-agent run-completion serialization,\n git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock)\n — filed as runner tasks, **not** built by this scaffold playbook. Until they\n land, run the waves sequentially and do not claim a parallel run (or a\n generation-alongside-coding overlap) happened when it did not.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **scale-orchestration depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order\n the graph, or add tasks — the **build-decompose** playbook owns the task\n graph. You read it and schedule from it.\n- **The per-task dispatch contract.** You do NOT re-specify single-flight\n locking, context-pack composition, change-set capture, or the verify hook —\n the **build-dispatch** playbook owns \"how ONE task dispatches safely\", and\n each parallel slot **invokes** that contract. If you catch yourself describing\n how a single task captures its change-set, stop — that is the dispatch\n playbook.\n- **The runner-serializer mechanism.** The multi-coding-agent serializer, git\n worktree-per-agent provisioning, the run-outcome reconciler, and the cursor\n lock are **companion-runner mechanism**, filed as runner tasks — this\n declarative method does not build them.\n- **A priority / work-stealing scheduler + cost-optimal packing.** Deciding an\n optimal task ordering within a band, work-stealing across idle slots, backoff,\n and cost-optimal packing are a later depth phase — the v1 scaffold picks a\n small parallelism degree (or a module partition) and a simple frontier order.\n- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the v1\n disposition.\n- **Auto-executed reviewer checklist.** The scale-soundness checklist ships\n **declarative** — the deterministic typecheck gate runs automatically; nothing\n executes the checklist prose (rubric-only judge gates were retired at the\n flexible-intelligence hard cut). Do not assume it auto-ran.\n- **Schema / field authoring + code generation.** The **coding agents** author\n fields, schemas, ui-behavior, and code at dispatch time — never the\n orchestrator.\n\nIf you find yourself designing how ONE task dispatches safely rather than how\nMANY tasks are scheduled + reconciled, stop — that is the build-dispatch\nplaybook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable\nresult of the build — each task's **change-set** (files touched, attributed,\nsummarized) and **status** — is materialized by the runner on the dispatched\ntask rows (the build-dispatch playbook's mechanism), not authored here. A\nseparate schedule / wave-log artifact family is deliberately not added: the task\nrows already *are* the dispatch record and a second home for the same record\nwould drift (a typed wave-schedule / run-ledger contract is a filed later-phase\nitem). Use the configured host's actual authorization boundary and review its\nrecorded changes and verification outcomes. The approval declaration alone does\nnot authorize or gate dispatch.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state,\n scope, and budget; confirm the build plan is approved and the foundation ran,\n and read every task's dispatch state to compute the frontier.\n- `.claude/skills/journey-run/references/framework-playbook-approval-policy.md` — declaration semantics and the actual runner boundary.\n- `.claude/skills/journey-run/SKILL.md` — trigger a scheduled wave; each coding\n slot invokes the single-flight dispatch contract and each deterministic\n generation step runs its companion endpoint.\n- `.claude/skills/journey-report/SKILL.md` — summarize a stretch of the build:\n which waves ran, which change-sets landed, what verify said, and any failed\n task left flagged for triage.\n\n## Reviewer checklist — `scale-schedule-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the SCALE orchestration ran the build soundly — the trust-but-verify reviewer pass over how MANY tasks were scheduled, parallelised, and reconciled, WITHOUT straying into how ONE task dispatches (that is the build-dispatch playbook's rubric) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task dispatched in a wave had ALL its prose prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP (the build stage ran against a missing prerequisite). A prerequisite whose run FAILED (its change-set flagged under keep_and_flag) does NOT satisfy the dependency — its dependents must stay blocked, and dispatching them anyway is a GAP. (2) PARALLELISM SAFETY / ATTRIBUTION — the concurrent coding runs in a wave were isolated so each run's change-set is cleanly attributable (files RUN_EXCLUSIVE / APPEARED_DURING_RUN per run), via git worktree-per-agent isolation OR a module/resource partition that puts every concurrent agent on a DISJOINT file set. Two concurrent coding agents mutating the SAME worktree — which makes every touched file BASELINE_DIRTY_AMBIGUOUS and destroys per-run attribution — is a GAP (the single-flight floor was bypassed without an isolation answer). Note the honest floor: the runner enforces single-flight today, so on the current runner a 'wave' degrades to SEQUENTIAL single-flight dispatch and this invariant reads whether the METHOD declared a sound isolation model, not whether concurrency actually ran. (3) COMPANION-GENERATION INTERLEAVE — the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) ran through their deterministic companion endpoints AFTER the resources / modules whose output they consume existed, at the right point in the schedule order; a generation step ordered before its inputs exist, or a missing generation step for authored surfaces, is a CONCERN; treating a deterministic generation step as a coding-agent dispatch (dispatching an agent for it) is a CONCERN. Note the honest floor: the generation steps do NOT take the coding single-flight lock, but the coding change-set capture is a whole-worktree time-window diff, so a generation step writing files WHILE a coding dispatch is capturing is misattributed to that coding run — so on today's runner the generation steps also serialize outside an active coding-capture window, and this invariant reads whether they ran at the right point in the ORDER, not whether they truly overlapped a coding run (safe overlap needs worktree isolation). (4) WAVE-COMPLETION RECONCILIATION — the next wave opened only after every task in the current frontier reached a terminal SUCCEEDED outcome (or was explicitly held as a blocked / flagged failure); advancing the schedule while a wave's tasks were still in-flight or with an unreconciled failure is a GAP (a downstream task could build on an unfinished prerequisite). (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task in a wave kept its captured change-set flagged for human triage (keep_and_flag), its already-dispatched siblings in the same wave were left to complete, and its DEPENDENTS in later waves stayed blocked until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the orchestration stays at SCALE depth: it derives ready-sets, schedules waves, sets the parallelism + isolation model, interleaves the companion-generation steps, and reconciles completion. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT re-specify the per-task dispatch mechanics (single-flight lock / context-pack / change-set capture / verify — the build-dispatch playbook owns those; the scale orchestrator INVOKES that contract per slot), and does NOT itself author schemas / fields / code (the coding agents do that at dispatch time). Evidence of re-decomposition, re-authoring the single-task dispatch contract, or the orchestrator authoring code itself is a CONCERN (scope creep out of the scale lane). (The checklist is declarative: nothing executes it; the current host's deterministic checks apply; the approval enum alone adds no gate.)\n",
27
23
  "skillRefs": [
28
24
  "journey-status",
29
25
  "journey-approve",
30
26
  "journey-run",
31
27
  "journey-report"
32
- ]
28
+ ],
29
+ "skillBodyRefs": [],
30
+ "contextSources": [],
31
+ "draftableDocumentDefinitionRefs": [],
32
+ "suspendsForClarification": false,
33
+ "briefAdequacyGate": false,
34
+ "briefAdequacyExcludedSources": []
33
35
  },
34
- "executor": "composite",
35
- "qualityGates": [
36
- {
37
- "ref": "scale-typecheck",
38
- "kind": "deterministic_validator",
39
- "validatorRef": "typecheck",
40
- "required": true
41
- }
42
- ],
36
+ "executor": "coding_agent",
43
37
  "approval": "approve_before",
44
38
  "budget": {
45
39
  "maxRuns": 30