@wildo-ai/framework-knowledge 1.1.5 → 1.1.6

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 (835) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +14 -0
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
  3. package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
  4. package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
  5. package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
  7. package/dist/{knowledge/skills/journey-run/references/framework-playbook-approval-policy.md → claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md} +10 -8
  8. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
  9. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
  10. package/dist/{knowledge/skills/journey-run → claude-marketplace/plugins/wildo}/references/expert-personas-and-deliberations.md +8 -8
  11. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
  12. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
  14. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
  15. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
  17. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
  18. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
  19. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
  20. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
  21. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  22. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  23. package/dist/esm/framework-knowledge.definitions.js +320 -11
  24. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +0 -3
  28. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +12 -2
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +33 -2
  32. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +8 -5
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +55 -10
  36. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -6
  40. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  42. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  43. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -6
  44. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  45. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  46. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
  47. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +0 -1
  48. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  49. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +2 -2
  50. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  51. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -4
  52. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  53. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +10 -3
  54. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
  55. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +7 -3
  56. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
  57. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +8 -3
  59. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +1 -1
  61. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +0 -1
  63. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +7 -3
  65. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +9 -4
  67. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +3 -2
  69. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +4 -3
  71. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +1 -1
  73. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +1 -3
  75. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  77. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
  79. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +10 -3
  81. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +8 -3
  83. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +12 -5
  85. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +33 -5
  87. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +1 -1
  89. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +1 -1
  90. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
  92. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
  93. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
  94. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
  95. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
  96. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
  97. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
  98. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -0
  99. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  100. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +1 -1
  101. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
  103. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
  104. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
  105. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
  106. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +1 -1
  107. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +1 -1
  108. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  109. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +1 -1
  110. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
  111. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
  113. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  114. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +1 -1
  115. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +1 -1
  116. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  117. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +1 -1
  118. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +1 -1
  119. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +1 -1
  121. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +1 -1
  122. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  123. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +1 -1
  124. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +1 -1
  125. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  126. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +1 -1
  127. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +1 -1
  128. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  129. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +36 -17
  130. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  131. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +67 -17
  132. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  133. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +1 -1
  134. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +1 -1
  135. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +45 -0
  137. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
  138. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
  139. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -0
  140. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +1 -1
  141. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  142. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +1 -1
  143. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  144. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +1 -1
  145. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  146. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  148. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  149. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +1 -1
  150. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +1 -1
  151. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  152. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +1 -1
  153. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +1 -1
  154. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +1 -1
  156. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +1 -1
  157. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  158. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +1 -1
  159. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +1 -1
  160. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  161. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +1 -1
  162. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  163. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  164. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  165. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +1 -1
  166. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  167. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -3
  168. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  169. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  170. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  171. package/dist/knowledge/manifest.json +8 -8
  172. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -3
  173. package/dist/knowledge/playbooks/bottom_up.build/method.md +4 -2
  174. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +31 -7
  175. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  176. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  177. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +134 -26
  178. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +7 -4
  179. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +84 -29
  180. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -7
  181. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +12 -23
  182. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -7
  183. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +12 -14
  184. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -2
  185. package/dist/knowledge/playbooks/bottom_up.conception/method.md +20 -2
  186. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +15 -7
  187. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +8 -6
  188. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +11 -4
  189. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +2 -4
  190. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
  191. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +18 -2
  192. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +1 -2
  193. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +2 -4
  194. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -5
  195. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +16 -2
  196. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +3 -3
  197. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +1 -3
  198. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +1 -2
  199. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +8 -7
  200. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +11 -4
  201. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +27 -5
  202. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +1 -4
  203. package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
  204. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
  205. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
  206. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -0
  207. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +112 -21
  208. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  209. package/dist/knowledge/playbooks/refinement.document-facts/method.md +7 -2
  210. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -4
  211. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
  212. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
  213. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +6 -0
  214. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
  215. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +0 -4
  216. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +1 -2
  217. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +1 -3
  218. package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -4
  219. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -2
  220. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +1 -3
  221. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +5 -3
  222. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +2 -4
  223. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +1 -3
  224. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +0 -4
  225. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +2 -4
  226. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -3
  227. package/dist/knowledge/playbooks/top_down.definition/method.md +7 -4
  228. package/dist/knowledge/playbooks/top_down.definition/playbook.json +52 -7
  229. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +1 -1
  230. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +2 -4
  231. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
  232. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
  233. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +0 -1
  234. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -1
  235. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -1
  236. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +2 -4
  237. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -2
  238. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +1 -1
  239. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
  240. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +17 -1
  241. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +2 -5
  242. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -3
  243. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +15 -7
  244. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +2 -4
  245. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -4
  246. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +1 -2
  247. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  248. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +12 -5
  249. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +212 -0
  250. package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
  251. package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
  252. package/dist/knowledge/references/build-plan.task-graph.config.md +71 -6
  253. package/dist/knowledge/references/capability-composition.config.md +20 -1
  254. package/dist/knowledge/references/cli.market.generate-command.md +18 -2
  255. package/dist/knowledge/references/engine.client-bundle.allow-list.md +7 -22
  256. package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
  257. package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
  258. package/dist/knowledge/references/example.backend.addon-wiring.module.md +5 -0
  259. package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
  260. package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
  261. package/dist/knowledge/references/example.config.app-shell.full.md +11 -0
  262. package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
  263. package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
  264. package/dist/knowledge/references/example.config.backend.required-floors.md +7 -0
  265. package/dist/knowledge/references/example.config.navigation.full.md +45 -2
  266. package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
  267. package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
  268. package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -0
  269. package/dist/knowledge/references/example.flows-actors.autonomous-agent.md +23 -0
  270. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
  271. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +26 -3
  272. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +1 -1
  273. package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
  274. package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
  275. package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
  276. package/dist/knowledge/references/example.infra.environment-config.local.md +14 -30
  277. package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
  278. package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
  279. package/dist/knowledge/references/example.module.companion-exports.full.md +8 -13
  280. package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
  281. package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
  282. package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
  283. package/dist/knowledge/references/example.provider.backend-module-shape.md +3 -0
  284. package/dist/knowledge/references/example.provider.frontend-app.module.md +9 -0
  285. package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
  286. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +14 -13
  287. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +18 -0
  288. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +11 -11
  289. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +5 -0
  290. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +2 -0
  291. package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
  292. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
  293. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +24 -6
  294. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +36 -25
  295. package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
  296. package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
  297. package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
  298. package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
  299. package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
  300. package/dist/knowledge/references/example.website.page.manifest.md +30 -0
  301. package/dist/knowledge/references/experience-plan.config.md +11 -4
  302. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +20 -0
  303. package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
  304. package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
  305. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
  306. package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
  307. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
  308. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
  309. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
  310. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +21 -0
  311. package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
  312. package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
  313. package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
  314. package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
  315. package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
  316. package/dist/knowledge/references/integration-plan.config.md +34 -2
  317. package/dist/knowledge/references/market.alternative.config.md +1 -1
  318. package/dist/knowledge/references/market.buying-journey.config.md +1 -1
  319. package/dist/knowledge/references/market.category.config.md +1 -1
  320. package/dist/knowledge/references/market.channel.config.md +1 -1
  321. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  322. package/dist/knowledge/references/market.gain.config.md +1 -1
  323. package/dist/knowledge/references/market.icp.config.md +1 -1
  324. package/dist/knowledge/references/market.job.config.md +1 -1
  325. package/dist/knowledge/references/market.message-template.config.md +1 -1
  326. package/dist/knowledge/references/market.objection.config.md +1 -1
  327. package/dist/knowledge/references/market.pain.config.md +1 -1
  328. package/dist/knowledge/references/market.persona.config.md +1 -1
  329. package/dist/knowledge/references/market.positioning.config.md +1 -1
  330. package/dist/knowledge/references/market.proof.config.md +1 -1
  331. package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
  332. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  333. package/dist/knowledge/references/market.trigger.config.md +1 -1
  334. package/dist/knowledge/references/placement-plan.config.md +7 -1
  335. package/dist/knowledge/references/platform.config.backing-services.md +15 -15
  336. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +57 -57
  337. package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
  338. package/dist/knowledge/references/presets.3d.layout-contract.md +213 -0
  339. package/dist/knowledge/references/presets.3d.register-layout.md +95 -0
  340. package/dist/knowledge/references/presets.models.labelling.sections.md +5 -0
  341. package/dist/knowledge/references/presets.models.shell-region.md +47 -0
  342. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
  343. package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
  344. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
  345. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +7 -6
  346. package/dist/knowledge/references/saas.backend.compliance.governed-documents-pdf-template.md +370 -0
  347. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +7 -0
  348. package/dist/knowledge/references/saas.backend.domain-module.md +93 -15
  349. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
  350. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
  351. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +200 -0
  352. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +2 -0
  353. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +73 -0
  354. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +33 -9
  355. package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
  356. package/dist/knowledge/references/saas.backend.system-access-service.md +98 -0
  357. package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
  358. package/dist/knowledge/references/saas.config.providers.augmentations.md +61 -0
  359. package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
  360. package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -0
  361. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +56 -2
  362. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +2 -2
  363. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +250 -0
  364. package/dist/knowledge/references/saas.frontend.billing-context.md +25 -2
  365. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
  366. package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
  367. package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
  368. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
  369. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +7 -5
  370. package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
  371. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +17 -2
  372. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
  373. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
  374. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +9 -0
  375. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +100 -5
  376. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
  377. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +61 -0
  378. package/dist/knowledge/references/saas.market.generation-agent.md +0 -1
  379. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
  380. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
  381. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
  382. package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
  383. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
  384. package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
  385. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
  386. package/dist/knowledge/references/saas.models.audit.trail-config.md +15 -9
  387. package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
  388. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +8 -0
  389. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +54 -1
  390. package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
  391. package/dist/knowledge/references/saas.models.config.organization-types.md +74 -0
  392. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +31 -14
  393. package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
  394. package/dist/knowledge/references/saas.models.data-mode-read-list.md +4 -4
  395. package/dist/knowledge/references/saas.models.engine-capabilities.md +12 -0
  396. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +5 -1
  397. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
  398. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
  399. package/dist/knowledge/references/saas.models.external-data-pipeline.md +667 -6
  400. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +98 -0
  401. package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
  402. package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
  403. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
  404. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
  405. package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
  406. package/dist/knowledge/references/saas.models.http-api-binding.md +812 -29
  407. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
  408. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
  409. package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
  410. package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
  411. package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
  412. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +28 -0
  413. package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
  414. package/dist/knowledge/references/saas.models.navigation.layout.md +11 -7
  415. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +32 -23
  416. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +8 -4
  417. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +22 -20
  418. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +14 -0
  419. package/dist/knowledge/references/saas.models.notifications.targets.md +20 -12
  420. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +61 -34
  421. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +9 -0
  422. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
  423. package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
  424. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
  425. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
  426. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
  427. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
  428. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
  429. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
  430. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
  431. package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
  432. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
  433. package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
  434. package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
  435. package/dist/knowledge/references/saas.models.provider-capabilities.md +34 -0
  436. package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
  437. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
  438. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +61 -0
  439. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +98 -13
  440. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
  441. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -28
  442. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
  443. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +6 -0
  444. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +8 -0
  445. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -0
  446. package/dist/knowledge/references/saas.models.system-of-record-actions.md +226 -0
  447. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
  448. package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
  449. package/dist/knowledge/references/saas.models.systems-of-record.md +242 -7
  450. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
  451. package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
  452. package/dist/knowledge/references/saas.public-runtime.contract.md +75 -7
  453. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +20 -0
  454. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +106 -13
  455. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
  456. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
  457. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
  458. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
  459. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
  460. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +6 -4
  461. package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
  462. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +14 -2
  463. package/dist/knowledge/references/saas.specifications.processor-register.md +77 -0
  464. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
  465. package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
  466. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +112 -45
  467. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +13 -1
  468. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
  469. package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
  470. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
  471. package/dist/knowledge/references/saas.website.astro.bridge.md +32 -9
  472. package/dist/knowledge/references/saas.website.astro.head-renderer.md +1 -1
  473. package/dist/knowledge/references/saas.website.astro.label-loader.md +7 -4
  474. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +15 -15
  475. package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
  476. package/dist/knowledge/references/saas.website.blog.bridge.md +17 -4
  477. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
  478. package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
  479. package/dist/knowledge/references/saas.website.consent.banner.md +10 -10
  480. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -4
  481. package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
  482. package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
  483. package/dist/knowledge/references/saas.website.page-layout.component.md +5 -2
  484. package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
  485. package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
  486. package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
  487. package/dist/knowledge/references/saas.website.runtime.context.md +23 -4
  488. package/dist/knowledge/references/saas.website.sections.definition-schema.md +14 -7
  489. package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
  490. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
  491. package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
  492. package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
  493. package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
  494. package/dist/knowledge/references/website-plan.config.md +39 -6
  495. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +2 -1
  496. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +21 -0
  497. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +1 -2
  498. package/dist/knowledge/references/zod.decorators.file-schema.md +11 -10
  499. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +7 -4
  500. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +8 -2
  501. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +5 -1
  502. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +5 -1
  503. package/dist/knowledge/references/zod.factories.address.md +7 -7
  504. package/dist/knowledge/references/zod.factories.code.md +2 -2
  505. package/dist/knowledge/references/zod.factories.duration.md +4 -4
  506. package/dist/knowledge/references/zod.factories.money.md +3 -3
  507. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  508. package/dist/knowledge/registries/framework-topics.json +1238 -54
  509. package/dist/knowledge/registries/playbooks.json +81 -109
  510. package/dist/knowledge/registries/source-tags.json +3191 -1126
  511. package/dist/knowledge/rules/live-context-door.md +29 -0
  512. package/dist/knowledge/skills/INDEX.md +27 -24
  513. package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
  514. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
  515. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
  516. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
  517. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
  518. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
  519. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
  520. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
  521. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
  522. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +31 -0
  523. package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -0
  524. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +1 -0
  525. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +9 -0
  526. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
  527. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +94 -16
  528. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +21 -8
  529. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +7 -0
  530. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +13 -5
  531. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +30 -6
  532. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +160 -32
  533. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +20 -0
  534. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +14 -2
  535. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +88 -0
  536. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +112 -14
  537. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
  538. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
  539. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
  540. package/dist/knowledge/skills/config-app-shell/SKILL.md +21 -0
  541. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +2 -2
  542. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +276 -0
  543. package/dist/knowledge/skills/config-app-shell/references/framework-shell-region-markers-api.md +66 -0
  544. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -0
  545. package/dist/knowledge/skills/config-navigation/SKILL.md +114 -16
  546. package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
  547. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +11 -7
  548. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +29 -5
  549. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +40 -27
  550. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +22 -20
  551. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +112 -5
  552. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +10 -10
  553. package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
  554. package/dist/knowledge/skills/config-saas/SKILL.md +3 -1
  555. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +7 -0
  556. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +21 -11
  557. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +5 -1
  558. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +59 -9
  559. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +46 -0
  560. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +251 -12
  561. package/dist/knowledge/skills/config-saas-backend/SKILL.md +8 -0
  562. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +81 -0
  563. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +37 -15
  564. package/dist/knowledge/skills/configure-billing/SKILL.md +64 -24
  565. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +35 -2
  566. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +14 -0
  567. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +3 -0
  568. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +25 -2
  569. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +73 -1
  570. package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
  571. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +27 -12
  572. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +11 -2
  573. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +26 -2
  574. package/dist/knowledge/skills/email-add-template/SKILL.md +61 -24
  575. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +5 -2
  576. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
  577. package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
  578. package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
  579. package/dist/knowledge/skills/engine-component-registration/SKILL.md +1 -0
  580. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +6 -0
  581. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +27 -3
  582. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +180 -0
  583. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
  584. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
  585. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
  586. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
  587. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +31 -4
  588. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +26 -3
  589. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
  590. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
  591. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +202 -0
  592. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +93 -15
  593. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +96 -11
  594. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +2 -1
  595. package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
  596. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -0
  597. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -2
  598. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +14 -9
  599. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +1 -0
  600. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +1 -0
  601. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +5 -0
  602. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
  603. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +5 -0
  604. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +8 -1
  605. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +5 -0
  606. package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
  607. package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
  608. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
  609. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
  610. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
  611. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
  612. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
  613. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
  614. package/dist/knowledge/skills/infra-environment-config/SKILL.md +150 -44
  615. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +83 -74
  616. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +176 -0
  617. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
  618. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +223 -0
  619. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +103 -0
  620. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +256 -0
  621. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
  622. package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +29 -0
  623. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
  624. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +32 -1
  625. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +2 -1
  626. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +36 -4
  627. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +2 -1
  628. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  629. package/dist/knowledge/skills/market-alternatives/SKILL.md +3 -2
  630. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
  631. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
  632. package/dist/knowledge/skills/market-category/SKILL.md +2 -1
  633. package/dist/knowledge/skills/market-channels/SKILL.md +2 -1
  634. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +7 -4
  635. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +6 -4
  636. package/dist/knowledge/skills/market-generation-cli/SKILL.md +28 -13
  637. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +18 -3
  638. package/dist/knowledge/skills/market-icp/SKILL.md +2 -1
  639. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +4 -3
  640. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -1
  641. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  642. package/dist/knowledge/skills/market-persona/SKILL.md +2 -1
  643. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
  644. package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
  645. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +3 -2
  646. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
  647. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -0
  648. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +2 -1
  649. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +3 -2
  650. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +1 -0
  651. package/dist/knowledge/skills/minion-authoring/SKILL.md +5 -1
  652. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +143 -0
  653. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
  654. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
  655. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
  656. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
  657. package/dist/knowledge/skills/module-companion-exports/SKILL.md +17 -16
  658. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +6 -4
  659. package/dist/knowledge/skills/module-registration/SKILL.md +2 -1
  660. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +93 -15
  661. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +86 -1
  662. package/dist/knowledge/skills/module-relationships/SKILL.md +3 -2
  663. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
  664. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
  665. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
  666. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
  667. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
  668. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
  669. package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
  670. package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -33
  671. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +227 -0
  672. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
  673. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
  674. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -0
  675. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-allow-list-api.md +111 -0
  676. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
  677. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +132 -23
  678. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +399 -0
  679. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +29 -0
  680. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
  681. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
  682. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
  683. package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
  684. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
  685. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +75 -24
  686. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +3 -3
  687. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +61 -0
  688. package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
  689. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +17 -2
  690. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +15 -0
  691. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
  692. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +25 -0
  693. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +6 -0
  694. package/dist/knowledge/skills/resource-add-field/SKILL.md +1 -0
  695. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
  696. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +105 -6
  697. package/dist/knowledge/skills/resource-add-module/SKILL.md +1 -0
  698. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +2 -1
  699. package/dist/knowledge/skills/resource-add-resource/SKILL.md +3 -0
  700. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +124 -30
  701. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +1 -0
  702. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +8 -0
  703. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +9 -0
  704. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +17 -1
  705. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +124 -30
  706. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +7 -6
  707. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +142 -34
  708. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +98 -0
  709. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +86 -52
  710. package/dist/knowledge/skills/resource-custom-view/SKILL.md +1 -0
  711. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +100 -5
  712. package/dist/knowledge/skills/resource-external-data/SKILL.md +1026 -28
  713. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
  714. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
  715. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
  716. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +686 -11
  717. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +904 -31
  718. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +166 -6
  719. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
  720. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
  721. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
  722. package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
  723. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
  724. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
  725. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
  726. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
  727. package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
  728. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
  729. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -0
  730. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +1 -0
  731. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +12 -0
  732. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +186 -0
  733. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
  734. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
  735. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
  736. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
  737. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
  738. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
  739. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +2 -2
  740. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
  741. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +3 -1
  742. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +2 -1
  743. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +28 -0
  744. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +5 -1
  745. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +34 -30
  746. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +5 -1
  747. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +101 -42
  748. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +21 -0
  749. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +1 -2
  750. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +125 -6
  751. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +8 -2
  752. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
  753. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +61 -1
  754. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +110 -9
  755. package/dist/knowledge/skills/seeding-authoring/SKILL.md +1 -0
  756. package/dist/knowledge/skills/seeding-operations/SKILL.md +1 -0
  757. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +455 -0
  758. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
  759. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
  760. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
  761. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
  762. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
  763. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -0
  764. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +61 -0
  765. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
  766. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
  767. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +14 -16
  768. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +6 -4
  769. package/dist/knowledge/skills/spec-component-update/SKILL.md +1 -0
  770. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
  771. package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
  772. package/dist/knowledge/skills/spec-feature-update/SKILL.md +1 -0
  773. package/dist/knowledge/skills/spec-resource-update/SKILL.md +13 -0
  774. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +158 -46
  775. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
  776. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
  777. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +5 -1
  778. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +1 -0
  779. package/dist/knowledge/skills/views-app-level/SKILL.md +2 -1
  780. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +43 -1
  781. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
  782. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +5 -1
  783. package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
  784. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -0
  785. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +29 -6
  786. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
  787. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +17 -4
  788. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +23 -28
  789. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +7 -22
  790. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +167 -20
  791. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
  792. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +63 -6
  793. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
  794. package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
  795. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -2
  796. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -2
  797. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +2 -1
  798. package/dist/knowledge/skills/website-page-authoring/SKILL.md +117 -33
  799. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
  800. package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
  801. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
  802. package/dist/knowledge/skills/website-section-contact/SKILL.md +65 -36
  803. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -11
  804. package/dist/knowledge/skills/website-section-cta/SKILL.md +32 -22
  805. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -11
  806. package/dist/knowledge/skills/website-section-faq/SKILL.md +99 -63
  807. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -11
  808. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +27 -18
  809. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -11
  810. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +33 -22
  811. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -11
  812. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +31 -20
  813. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -11
  814. package/dist/knowledge/skills/website-section-hero/SKILL.md +65 -44
  815. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -11
  816. package/dist/knowledge/skills/website-section-pricing/SKILL.md +217 -200
  817. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -11
  818. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
  819. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +45 -34
  820. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -11
  821. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
  822. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
  823. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +30 -25
  824. package/dist/knowledge/skills/worker-authoring/SKILL.md +1 -0
  825. package/dist/knowledge/topic-index.json +5887 -1695
  826. package/dist/tsconfig.build.tsbuildinfo +1 -1
  827. package/dist/tsconfig.tsbuildinfo +1 -1
  828. package/package.json +4 -4
  829. package/dist/knowledge/skills/journey-approve/SKILL.md +0 -63
  830. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -77
  831. package/dist/knowledge/skills/journey-next/SKILL.md +0 -82
  832. package/dist/knowledge/skills/journey-report/SKILL.md +0 -56
  833. package/dist/knowledge/skills/journey-run/SKILL.md +0 -140
  834. package/dist/knowledge/skills/journey-status/SKILL.md +0 -60
  835. /package/dist/{knowledge/skills/journey-approve → claude-marketplace/plugins/wildo}/references/specification-family-map.md +0 -0
@@ -75,8 +75,8 @@ This playbook is **idempotent** and, on a re-run, *advances the schedule by one
75
75
  wave* (and, on today's single-flight runner, by one task within that wave).
76
76
  Before scheduling anything:
77
77
 
78
- 1. Read the current journey state and scope through the `journey-status` skill
79
- (it owns the read; do not re-derive it here). Confirm the **build plan** is
78
+ 1. Read the current journey state and scope from what this run is given — the loaded
79
+ specifications and the workspace sections of your brief — and do not re-derive it. Confirm the **build plan** is
80
80
  present and approved and the **foundation** ran. For each build-plan task,
81
81
  read its dispatch state from its task row — **not yet dispatched**,
82
82
  **dispatched-and-succeeded** (a captured change-set + a passed verify),
@@ -189,12 +189,9 @@ today's runner, see the caveat below.
189
189
  arrive only with git worktree-per-agent isolation (the runner task in Step 5's
190
190
  gap note). Until then, keep the input-ready *ordering* and serialize.
191
191
 
192
- // 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.
192
+ // The trigger is `wildo creation run <playbookRef>` (or `/wildo:run` from a Claude Code session),
193
+ // which reaches the companion's run route with the local token attached. Each coding slot invokes the
194
+ // single-flight dispatch contract; each generation step runs its deterministic endpoint.
198
195
 
199
196
  ## Step 4 — Check the actual host authorization boundary
200
197
 
@@ -205,8 +202,8 @@ The single-flight mutation lock still applies to the current shared workspace.
205
202
  The playbook's `approval` declaration and the journey autonomy presets express policy
206
203
  intent. The current playbook runner does not interpret them as pre-dispatch gates,
207
204
  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.
205
+ not create a pending Authority Request, and no authority workflow exists to create one —
206
+ never invent one from an enum.
210
207
 
211
208
  Likewise, do not infer enforced per-playbook or per-journey run ceilings from declared
212
209
  budget fields. Respect the limits actually reported by the execution host. Inspect the
@@ -238,9 +235,9 @@ as a blocked / flagged failure. Only then does the next frontier open (Step 1).
238
235
  > is both the correct F-5 workspace-safety posture and the behavior the runner
239
236
  > enforces today; a `revert_changeset` path is a deliberate later boundary.
240
237
 
241
- Then **loop**: on the next run, `journey-status` reflects the just-completed
242
- wave's outcomes, and you derive the next frontier (Step 1). Close a significant
243
- stretch of the build with a `journey-report` summary — which waves ran, which
238
+ Then **loop**: on the next run, the build plan's task records reflect the just-completed
239
+ wave's outcomes (`wildo build tasks`), and you derive the next frontier (Step 1). Close a
240
+ significant stretch of the build with a progress summary — which waves ran, which
244
241
  change-sets landed, what verify said, which generation steps interleaved, and
245
242
  any failed task left flagged for triage.
246
243
 
@@ -322,16 +319,8 @@ not authorize or gate dispatch.
322
319
 
323
320
  ## References
324
321
 
325
- - `.claude/skills/journey-status/SKILL.md` — read the current journey state,
326
- scope, and budget; confirm the build plan is approved and the foundation ran,
327
- and read every task's dispatch state to compute the frontier.
328
- - `.claude/skills/journey-run/references/framework-playbook-approval-policy.md` — declaration semantics and the actual runner boundary.
329
- - `.claude/skills/journey-run/SKILL.md` — trigger a scheduled wave; each coding
330
- slot invokes the single-flight dispatch contract and each deterministic
331
- generation step runs its companion endpoint.
332
- - `.claude/skills/journey-report/SKILL.md` — summarize a stretch of the build:
333
- which waves ran, which change-sets landed, what verify said, and any failed
334
- task left flagged for triage.
322
+ - A playbook's declared `approval` and failure policy gate nothing on a leaf run; they are read only
323
+ at a composite lane's boundary, where they frame a decision for the person and revert nothing.
335
324
 
336
325
  ## Reviewer checklist — `scale-schedule-sound`
337
326
 
@@ -19,13 +19,8 @@
19
19
  "outputs": [],
20
20
  "stepOutputs": [],
21
21
  "method": {
22
- "guidance": "# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and a deliberately honest one.** It is a\n> working first cut of the *scale* orchestration — derive a wave of ready tasks,\n> run several coding agents in parallel under an isolation model, interleave the\n> deterministic companion-generation steps, and reconcile wave completion. But\n> the companion runner **hard-enforces single-flight today**: it refuses a run\n> plan with more than one coding-agent task, refuses a second dispatch while one\n> is active, holds one workspace-mutation lock per run, and has no run-outcome\n> reconciler. So the concurrency described below is the **declarative target** a\n> runner-serializer slice will realize. **On the current runner the waves\n> degrade to sequential single-flight dispatch** — read the \"What the runner\n> actually does today\" section before you assume anything ran in parallel. Do\n> not overclaim concurrency the runner cannot do.\n\n## Where you are in the journey\n\nThis is the **third and final build-execution playbook** — the pivot from\n**dispatching one task safely** (the build-dispatch playbook's single-flight\ncontract) to **running the build at scale**. It runs in the **bottom-up phase**,\nafter the build plan exists (`artifact_exists build-plan`) and the foundation\nstep has authored the app's config and skeleton. You\nare not re-opening the decomposition here, and you are not re-specifying how one\ntask dispatches — you are deciding **how many** tasks run **concurrently** and\n**safely**, in **what order**, with the companion-generation steps interleaved.\n\nUpstream: the **build-decompose** playbook produced the ordered task graph you\nschedule; the **build-dispatch** playbook defined how ONE task dispatches\nsafely — you **invoke that contract per parallel slot**, you do not re-author\nit. **You author neither of those concerns** — see the boundary section.\n\n## What this playbook does\n\nYou are the **scale orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, across the *whole* build: *\"which set\nof tasks is ready to run now, how many run at once and on what isolation, when\ndo the deterministic generation steps run, and when has a wave actually\nfinished?\"* You do **not** produce a new journey artifact — the observable\nresult of the build is the per-task change-sets + task statuses the runner\nrecords on the task rows (the build-dispatch playbook's mechanism), not a\nschedule artifact authored here (see \"What you emit\"). You do **not** decompose\nthe plan, re-specify the per-task dispatch mechanics, author any schema, or\nwrite any code.\n\n## The scale contract — you sequence waves, the dispatch playbook runs each slot\n\nMost of the *per-task* mechanism is **not yours**: selecting one task,\ncomposing its context pack, running one prompt turn against the coding agent over\nthe Agent Client Protocol (answering its permission requests within the declared\nceiling), capturing the change-set, running the verify hook, holding the\nsingle-flight lock, applying the host's actual execution limits — all of that is the **build-dispatch** contract, which each\nparallel slot invokes. Your method here is the **declarative concurrency\nrecipe** the runner (or a future runner-serializer) interprets: *which set* of\ntasks is ready, *how many* run at once, *how* they are isolated, *when* the\ndeterministic generation steps interleave, and *when* a wave is done. Do not\nhand-drive git, do not compose a dispatch prompt, do not re-implement the\nsingle-flight capture — invoke the dispatch contract per slot and let it own\nthose.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the schedule by one\nwave* (and, on today's single-flight runner, by one task within that wave).\nBefore scheduling anything:\n\n1. Read the current journey state and scope 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",
23
- "skillRefs": [
24
- "journey-status",
25
- "journey-approve",
26
- "journey-run",
27
- "journey-report"
28
- ],
22
+ "guidance": "# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology, and a deliberately honest one.** It is a\n> working first cut of the *scale* orchestration — derive a wave of ready tasks,\n> run several coding agents in parallel under an isolation model, interleave the\n> deterministic companion-generation steps, and reconcile wave completion. But\n> the companion runner **hard-enforces single-flight today**: it refuses a run\n> plan with more than one coding-agent task, refuses a second dispatch while one\n> is active, holds one workspace-mutation lock per run, and has no run-outcome\n> reconciler. So the concurrency described below is the **declarative target** a\n> runner-serializer slice will realize. **On the current runner the waves\n> degrade to sequential single-flight dispatch** — read the \"What the runner\n> actually does today\" section before you assume anything ran in parallel. Do\n> not overclaim concurrency the runner cannot do.\n\n## Where you are in the journey\n\nThis is the **third and final build-execution playbook** — the pivot from\n**dispatching one task safely** (the build-dispatch playbook's single-flight\ncontract) to **running the build at scale**. It runs in the **bottom-up phase**,\nafter the build plan exists (`artifact_exists build-plan`) and the foundation\nstep has authored the app's config and skeleton. You\nare not re-opening the decomposition here, and you are not re-specifying how one\ntask dispatches — you are deciding **how many** tasks run **concurrently** and\n**safely**, in **what order**, with the companion-generation steps interleaved.\n\nUpstream: the **build-decompose** playbook produced the ordered task graph you\nschedule; the **build-dispatch** playbook defined how ONE task dispatches\nsafely — you **invoke that contract per parallel slot**, you do not re-author\nit. **You author neither of those concerns** — see the boundary section.\n\n## What this playbook does\n\nYou are the **scale orchestrator**. This playbook reads the approved build plan\nand the current journey state and answers, across the *whole* build: *\"which set\nof tasks is ready to run now, how many run at once and on what isolation, when\ndo the deterministic generation steps run, and when has a wave actually\nfinished?\"* You do **not** produce a new journey artifact — the observable\nresult of the build is the per-task change-sets + task statuses the runner\nrecords on the task rows (the build-dispatch playbook's mechanism), not a\nschedule artifact authored here (see \"What you emit\"). You do **not** decompose\nthe plan, re-specify the per-task dispatch mechanics, author any schema, or\nwrite any code.\n\n## The scale contract — you sequence waves, the dispatch playbook runs each slot\n\nMost of the *per-task* mechanism is **not yours**: selecting one task,\ncomposing its context pack, running one prompt turn against the coding agent over\nthe Agent Client Protocol (answering its permission requests within the declared\nceiling), capturing the change-set, running the verify hook, holding the\nsingle-flight lock, applying the host's actual execution limits — all of that is the **build-dispatch** contract, which each\nparallel slot invokes. Your method here is the **declarative concurrency\nrecipe** the runner (or a future runner-serializer) interprets: *which set* of\ntasks is ready, *how many* run at once, *how* they are isolated, *when* the\ndeterministic generation steps interleave, and *when* a wave is done. Do not\nhand-drive git, do not compose a dispatch prompt, do not re-implement the\nsingle-flight capture — invoke the dispatch contract per slot and let it own\nthose.\n\n## Read state first — no artifact to write\n\nThis playbook is **idempotent** and, on a re-run, *advances the schedule by one\nwave* (and, on today's single-flight runner, by one task within that wave).\nBefore scheduling anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the **build plan** is\n present and approved and the **foundation** ran. For each build-plan task,\n read its dispatch state from its task row — **not yet dispatched**,\n **dispatched-and-succeeded** (a captured change-set + a passed verify),\n **dispatched-and-failed** (a captured change-set but a failed/timed-out run\n or a failed verify), or **in-flight**. This full state — not just \"has a\n change-set\" — is what the wave derivation keys on (under `keep_and_flag` a\n *failed* task also has a captured change-set, so presence of a change-set\n alone never means \"done\").\n2. Read the approved **build plan** (`build-plan` — the ordered task graph, with\n each task's prose prerequisite references). It is your work list.\n\n That there is an application to dispatch into is answered by the committed\n `./wildo.saas.config.ts` and skeleton, not by a journey artifact. (A\n `foundation-manifest` played that role until 2026-08-25 and was retired with the\n app-creation verification/digest aspect.) The honest limitation the foundation step\n carries still applies: on-disk skeleton materialization depends on greenfield\n bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale\n contract runs against an existing workspace.\n\n// Operator status: `wildo context journey` (eligibility board + runs in flight); per-task landed\n// state is read from git by the runner.\n\nYou **read** `build-plan`; you **write** no journey\nartifact — the runner records each dispatched task's change-set + status on its\nrow.\n\n## Step 1 — Derive the ready-set (the wave / frontier)\n\nWalk the build plan and compute the **frontier**: the set of tasks that are\n**not yet dispatched** (or previously-**failed** tasks cleared for retry) and\nwhose prose prerequisites have **all SUCCEEDED**. That set is the next **wave**.\n\n- **A prerequisite must have SUCCEEDED, not merely been attempted.** A task\n enters the frontier only when every task it depends on is\n dispatched-and-succeeded (verify passed). A prerequisite that is\n dispatched-and-**failed** (its change-set flagged for triage under\n `keep_and_flag`), still **in-flight**, or un-run does **not** satisfy the\n dependency — its dependents stay **out of the frontier** until it succeeds.\n This is the U13b readiness discipline, lifted to a set: do not open a wave on\n a schema whose run has not verified.\n- **The wave respects the build-plan ordering.** The build-decompose playbook\n encoded the DEPENDS_ON edges (the per-resource stage order schema → config →\n ui-behavior → spec, the cross-topic edges, relationship-after-endpoints); the\n frontier is exactly the tasks with no unsatisfied edge remaining. You do not\n re-derive or re-order those edges — you read them and compute the ready-set.\n- **An empty frontier is a terminal state.** If no task is ready — every task\n has succeeded, or the only undispatched tasks are blocked behind an\n unresolved failure — the build is done (or blocked on a flagged failure):\n report it and stop. An empty build plan is the same.\n\n## Step 2 — Decide the parallelism degree + the worktree-isolation model\n\nFor the frontier, decide **how many** coding agents run at once and **on what\nisolation**. This is the core scale decision, and it is bounded by a hard\nsafety constraint, not just throughput:\n\n- **Change-set attribution requires isolation.** The dispatch contract captures\n each run's change-set by diffing the worktree around the run and attributing\n every file as `RUN_EXCLUSIVE`, `APPEARED_DURING_RUN`, or\n `BASELINE_DIRTY_AMBIGUOUS`. **Two coding agents mutating the SAME worktree\n concurrently make every touched file `BASELINE_DIRTY_AMBIGUOUS`** — each run\n looks like it started against a tree the other was dirtying — which\n **destroys per-run attribution**. So real parallelism needs one of:\n - **git worktree-per-agent isolation** — each concurrent coding agent runs in\n its own git worktree (a disjoint checkout of the same repo), so each run's\n change-set is captured against a tree only it mutates; the worktrees are\n reconciled/merged after the wave. This is the general answer.\n - **module / resource partitioning** — schedule concurrent agents only onto\n tasks whose targets touch **disjoint file sets** (different modules /\n resources), so even on one shared worktree no two runs collide. This is the\n cheaper answer when the frontier naturally partitions by module.\n - **or keep coding single-flight** and only parallelise the deterministic\n companion-generation steps (Step 3), which are not coding-locked.\n- **Pick the degree deliberately, not maximally.** At scaffold depth prefer a\n small degree (or a module partition) over max fan-out — cost-optimal packing,\n a priority / work-stealing scheduler, and backoff are a later depth phase, not\n this scaffold. State the isolation model you chose; a wave with degree > 1 and\n **no** isolation answer is unsafe (the reviewer rubric flags it as a GAP).\n\n## Step 3 — Interleave the deterministic companion-generation steps\n\nThe build plan carries **companion-owned generation steps** — labels / i18n,\nemail templates, seeds — as tasks. These are **deterministic companion\nendpoints**, not coding-agent dispatches: they do **not** contend for the\ncoding single-flight lock. It is tempting to conclude they can freely run\n*alongside* a coding run — but there is a subtlety that makes that unsafe on\ntoday's runner, see the caveat below.\n\n- **Run each generation step at its input-ready point.** A labels/i18n step runs\n after the resources it labels exist; an email step after its templates'\n definition surfaces exist; a seed step after the resources it seeds exist.\n Schedule each at its input-ready point in the wave sequence — do not block a\n coding wave on them and do not run them before their inputs exist. (The\n *ordering* is what matters here; the *concurrency* is deferred — see the\n caveat.)\n- **Route them to their deterministic endpoint, not the coding lane.** Do not\n dispatch a coding agent for a labels/email/seed step — it has a deterministic\n companion generator. Treating a generation step as a coding dispatch is scope\n creep the reviewer flags.\n- **CAVEAT — no attribution-safe overlap with an active coding run today.** The\n coding run's change-set is captured as a **whole-worktree time-window diff**\n (every tracked-dirty + untracked file in the window). So a generation step\n writing label / email / seed files **while a coding dispatch is capturing** is\n misattributed to that coding run — its files show up as the coding run's own\n edits. This is the *same* whole-worktree pollution that forbids two concurrent\n coding agents (Step 2), and it applies identically to coding + generation. So\n on today's runner the generation steps must **also** be serialized to run\n **outside** an active coding-capture window (i.e. between coding runs). Genuine\n overlap — generation alongside coding, and coding alongside coding — both\n arrive only with git worktree-per-agent isolation (the runner task in Step 5's\n gap note). Until then, keep the input-ready *ordering* and serialize.\n\n// The trigger is `wildo creation run <playbookRef>` (or `/wildo:run` from a Claude Code session),\n// which reaches the companion's run route with the local token attached. Each coding slot invokes the\n// single-flight dispatch contract; each generation step runs its deterministic endpoint.\n\n## Step 4 — Check the actual host authorization boundary\n\nA coding dispatch writes the application workspace. Read its selected task, readiness,\nmutation scope and the configured coding host's authorization policy before invoking it.\nThe single-flight mutation lock still applies to the current shared workspace.\n\nThe playbook's `approval` declaration and the journey autonomy presets express policy\nintent. The current playbook runner does not interpret them as pre-dispatch gates,\nautomatic authorization, or a GUIDED/YOLO mapping. A declared `approve_before` does\nnot create a pending Authority Request, and no authority workflow exists to create one —\nnever invent one from an enum.\n\nLikewise, do not infer enforced per-playbook or per-journey run ceilings from declared\nbudget fields. Respect the limits actually reported by the execution host. Inspect the\nrecorded changes and verification result after each task; no preset commits or accepts them.\n\n## Step 5 — Reconcile wave completion, then advance\n\nA wave is done only when **every task in the frontier reached a terminal\nSUCCEEDED outcome** (change-set captured + verify passed) or is explicitly held\nas a blocked / flagged failure. Only then does the next frontier open (Step 1).\n\n- **Do not open the next wave on an unfinished one.** Advancing while a wave's\n tasks are still in-flight, or with an unreconciled failure, risks a downstream\n task building on an unfinished prerequisite. Reconcile first.\n- **Failure disposition across siblings + downstream** — this playbook's\n declared `onFailure` describes **`keep_and_flag`**; the current host retains changes for review. A failed/timed-out task keeps its captured\n change-set flagged for human triage (never silently reverted, never an\n un-recorded half-applied state). Its already-dispatched **siblings** in the\n same wave are left to complete; its **dependents** in later waves stay\n **blocked** (Step 1) until it is triaged and re-dispatched successfully.\n Triage is a human decision: keep + fix forward, unwind the flagged change-set\n by hand, or re-dispatch once the blocker is resolved. This playbook does not\n auto-retry a failed task (automated retry / backoff is a deferred build-loop\n resilience concern).\n\n> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a\n> failed run's edits is a *mutating* git op, deliberately **outside** the\n> read-only change-set carve-out the dispatch lane observes. So `keep_and_flag`\n> is both the correct F-5 workspace-safety posture and the behavior the runner\n> enforces today; a `revert_changeset` path is a deliberate later boundary.\n\nThen **loop**: on the next run, the build plan's task records reflect the just-completed\nwave's outcomes (`wildo build tasks`), and you derive the next frontier (Step 1). Close a\nsignificant stretch of the build with a progress summary — which waves ran, which\nchange-sets landed, what verify said, which generation steps interleaved, and\nany failed task left flagged for triage.\n\n## What the runner actually does today (do not overclaim)\n\nBe honest with the creator about the gap between this method and the runner:\n\n- **The runner enforces single-flight.** It refuses a run plan carrying more\n than one coding-agent task, refuses a second dispatch while one is active, and\n holds one workspace-mutation lock per background run. So a wave with\n parallelism degree > 1 is **not** realizable on today's runner — the wave\n **degrades to sequential single-flight dispatch** (repeated invocation of the\n build-dispatch contract, one task at a time, in frontier order). The frontier\n math, the readiness discipline, and the reconciliation are all still correct\n and useful sequentially — you just do not get concurrency yet.\n- **No overlap is attribution-safe today — not even a companion-generation\n step.** The generation endpoints are not coding-locked, but the coding\n change-set capture is a whole-worktree time-window diff, so a generation step\n writing files while a coding dispatch is capturing is misattributed to that\n run (Step 3's caveat). So the generation steps **also** serialize outside an\n active coding-capture window: their input-ready *ordering* holds, only the\n *concurrency* is deferred. Safe overlap of generation-with-coding, and\n coding-with-coding, both require git worktree-per-agent isolation.\n- **The concurrency this method describes is the declarative target** for a\n runner-serializer slice (multi-coding-agent run-completion serialization,\n git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock)\n — filed as runner tasks, **not** built by this scaffold playbook. Until they\n land, run the waves sequentially and do not claim a parallel run (or a\n generation-alongside-coding overlap) happened when it did not.\n\n## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)\n\nKeep this playbook at **scale-orchestration depth**. Explicitly **out of scope\nhere**:\n\n- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order\n the graph, or add tasks — the **build-decompose** playbook owns the task\n graph. You read it and schedule from it.\n- **The per-task dispatch contract.** You do NOT re-specify single-flight\n locking, context-pack composition, change-set capture, or the verify hook —\n the **build-dispatch** playbook owns \"how ONE task dispatches safely\", and\n each parallel slot **invokes** that contract. If you catch yourself describing\n how a single task captures its change-set, stop — that is the dispatch\n playbook.\n- **The runner-serializer mechanism.** The multi-coding-agent serializer, git\n worktree-per-agent provisioning, the run-outcome reconciler, and the cursor\n lock are **companion-runner mechanism**, filed as runner tasks — this\n declarative method does not build them.\n- **A priority / work-stealing scheduler + cost-optimal packing.** Deciding an\n optimal task ordering within a band, work-stealing across idle slots, backoff,\n and cost-optimal packing are a later depth phase — the v1 scaffold picks a\n small parallelism degree (or a module partition) and a simple frontier order.\n- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the v1\n disposition.\n- **Auto-executed reviewer checklist.** The scale-soundness checklist ships\n **declarative** — the deterministic typecheck gate runs automatically; nothing\n executes the checklist prose (rubric-only judge gates were retired at the\n flexible-intelligence hard cut). Do not assume it auto-ran.\n- **Schema / field authoring + code generation.** The **coding agents** author\n fields, schemas, ui-behavior, and code at dispatch time — never the\n orchestrator.\n\nIf you find yourself designing how ONE task dispatches safely rather than how\nMANY tasks are scheduled + reconciled, stop — that is the build-dispatch\nplaybook.\n\n## What you emit\n\n**No journey artifact.** This is a pure-orchestration playbook: the observable\nresult of the build — each task's **change-set** (files touched, attributed,\nsummarized) and **status** — is materialized by the runner on the dispatched\ntask rows (the build-dispatch playbook's mechanism), not authored here. A\nseparate schedule / wave-log artifact family is deliberately not added: the task\nrows already *are* the dispatch record and a second home for the same record\nwould drift (a typed wave-schedule / run-ledger contract is a filed later-phase\nitem). Use the configured host's actual authorization boundary and review its\nrecorded changes and verification outcomes. The approval declaration alone does\nnot authorize or gate dispatch.\n\n## References\n\n- A playbook's declared `approval` and failure policy gate nothing on a leaf run; they are read only\n at a composite lane's boundary, where they frame a decision for the person and revert nothing.\n\n## Reviewer checklist — `scale-schedule-sound`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is kept here, verbatim, minus the retired runner's closing sentence:\n\nJudge whether the SCALE orchestration ran the build soundly — the trust-but-verify reviewer pass over how MANY tasks were scheduled, parallelised, and reconciled, WITHOUT straying into how ONE task dispatches (that is the build-dispatch playbook's rubric) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task dispatched in a wave had ALL its prose prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP (the build stage ran against a missing prerequisite). A prerequisite whose run FAILED (its change-set flagged under keep_and_flag) does NOT satisfy the dependency — its dependents must stay blocked, and dispatching them anyway is a GAP. (2) PARALLELISM SAFETY / ATTRIBUTION — the concurrent coding runs in a wave were isolated so each run's change-set is cleanly attributable (files RUN_EXCLUSIVE / APPEARED_DURING_RUN per run), via git worktree-per-agent isolation OR a module/resource partition that puts every concurrent agent on a DISJOINT file set. Two concurrent coding agents mutating the SAME worktree — which makes every touched file BASELINE_DIRTY_AMBIGUOUS and destroys per-run attribution — is a GAP (the single-flight floor was bypassed without an isolation answer). Note the honest floor: the runner enforces single-flight today, so on the current runner a 'wave' degrades to SEQUENTIAL single-flight dispatch and this invariant reads whether the METHOD declared a sound isolation model, not whether concurrency actually ran. (3) COMPANION-GENERATION INTERLEAVE — the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) ran through their deterministic companion endpoints AFTER the resources / modules whose output they consume existed, at the right point in the schedule order; a generation step ordered before its inputs exist, or a missing generation step for authored surfaces, is a CONCERN; treating a deterministic generation step as a coding-agent dispatch (dispatching an agent for it) is a CONCERN. Note the honest floor: the generation steps do NOT take the coding single-flight lock, but the coding change-set capture is a whole-worktree time-window diff, so a generation step writing files WHILE a coding dispatch is capturing is misattributed to that coding run — so on today's runner the generation steps also serialize outside an active coding-capture window, and this invariant reads whether they ran at the right point in the ORDER, not whether they truly overlapped a coding run (safe overlap needs worktree isolation). (4) WAVE-COMPLETION RECONCILIATION — the next wave opened only after every task in the current frontier reached a terminal SUCCEEDED outcome (or was explicitly held as a blocked / flagged failure); advancing the schedule while a wave's tasks were still in-flight or with an unreconciled failure is a GAP (a downstream task could build on an unfinished prerequisite). (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task in a wave kept its captured change-set flagged for human triage (keep_and_flag), its already-dispatched siblings in the same wave were left to complete, and its DEPENDENTS in later waves stayed blocked until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP (F-5 workspace-safety violation). (6) BOUNDARY DISCIPLINE — the orchestration stays at SCALE depth: it derives ready-sets, schedules waves, sets the parallelism + isolation model, interleaves the companion-generation steps, and reconciles completion. It does NOT re-decompose the plan (the build-decompose playbook owns the task graph), does NOT re-specify the per-task dispatch mechanics (single-flight lock / context-pack / change-set capture / verify — the build-dispatch playbook owns those; the scale orchestrator INVOKES that contract per slot), and does NOT itself author schemas / fields / code (the coding agents do that at dispatch time). Evidence of re-decomposition, re-authoring the single-task dispatch contract, or the orchestrator authoring code itself is a CONCERN (scope creep out of the scale lane). (The checklist is declarative: nothing executes it; the current host's deterministic checks apply; the approval enum alone adds no gate.)\n",
23
+ "skillRefs": [],
29
24
  "skillBodyRefs": [],
30
25
  "contextSources": [],
31
26
  "draftableDocumentDefinitionRefs": [],
@@ -14,12 +14,12 @@ Read and apply these patterns from the application-developer point of view:
14
14
 
15
15
  ## What this step does
16
16
 
17
- The framework ships fourteen composition scenarios under `templates/saas/scenarios/`. Two of
17
+ The framework ships one composition scenario per folder under `templates/saas/scenarios/`. Two of
18
18
  them — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The
19
- other twelve give an application a marketing website, a documentation portal, a cron minion, a
20
- worker, a provider, a file-picker provider, a second website locale or another deployment
21
- environment, and until this step existed nothing in the journey decided whether an application
22
- needed any of them: they were reachable only by a person running `wildo compose`.
19
+ others give an application a marketing website, a documentation portal, a cron minion, a worker, a
20
+ provider, a file-picker provider, a second website locale, another deployment environment or the
21
+ optional 3D layout, and until this step existed nothing in the journey decided whether an
22
+ application needed any of them: they were reachable only by a person running `wildo compose`.
23
23
 
24
24
  This step records that decision as the `capability-composition` family: **one decision per
25
25
  scenario the framework ships**, each with a disposition, the closed basis it was derived from,
@@ -34,15 +34,12 @@ DECLARE:
34
34
  |---|---|---|
35
35
  | `add-website` | the market declares an inbound web channel (organic or paid search, content, owned or paid social); else a brand brief has landed; else the business model declares pricing plans | `market-snapshot.channels`, `brand-brief`, `business-model.plans` |
36
36
  | `add-technical-doc` | a targeted ICP (CORE or EXPANSION) is a legal entity; else a non-functional requirement declares PORTABILITY | `market-snapshot.icps`, `requirements.nonFunctional` |
37
+ | `add-locale` | a website is composed and the application configuration serves more than one language — one locale per language beyond the primary | `appPreferences.languages` in the application configuration (a host fact: no family declares languages, and the configuration already does) |
37
38
 
38
- Where no typed declaration can decide a scenario yet, the record says **DECLINED with the basis
39
+ Where no typed declaration can decide a scenario, the record says **DECLINED with the basis
39
40
  `NO_DECLARATION_DECIDES_IT` and names the declaration that would decide it** — a field for
40
- somebody to add, never a question for somebody to answer:
41
-
42
- - `add-minion`, `add-worker-node`, `add-worker-rust` — a typed declaration of scheduled or
43
- background execution on a feature draft or a requirement; the closed vocabularies carry none.
44
- - `add-locale` — a locale set the product serves; measured 2026-09-17, no family declares
45
- languages (a governed document's drafting locale is a different decision).
41
+ somebody to add, never a question for somebody to answer. Today the only such case is `add-locale`
42
+ when a website is composed but the host could not read the configuration's languages.
46
43
 
47
44
  Scenarios another step applies are recorded as **OWNED_BY_ANOTHER_STEP**, naming the owner, so
48
45
  the record stays total without claiming the application lacks them:
@@ -50,9 +47,11 @@ the record stays total without claiming the application lacks them:
50
47
  | scenario | owner |
51
48
  |---|---|
52
49
  | `add-module`, `add-resource` | `bottom_up.foundation` — the domain composition |
50
+ | `add-minion`, `add-worker-node`, `add-worker-rust` | `bottom_up.foundation` — one per surface the integration plan declares |
53
51
  | `add-custom-operation`, `add-website-section`, `add-marketing-page`, `add-file-picker-provider` | the build tasks that produce those artifacts (`bottom_up.build-decompose`) |
54
52
  | `add-provider` | the foundation's provider decision |
55
53
  | `add-environment` | the operator, at deployment (`wildo compose add-environment`) |
54
+ | `add-3d-layout` | the operator's opt-in (`wildo compose add-3d-layout`): nothing a product declares decides a rendering style, so the journey never adopts the optional 3D layout |
56
55
 
57
56
  ## Where it lands, and who reads it
58
57
 
@@ -74,7 +73,7 @@ re-running this step refines it. Nothing is re-asked because nothing was asked.
74
73
  ## What you emit
75
74
 
76
75
  - The **capability-composition** at `specifications/src/capability-composition/index.ts` —
77
- fourteen decisions, total over the scenarios the framework ships.
76
+ one decision per scenario, total over the scenarios the framework ships.
78
77
 
79
78
  ## Verification
80
79
 
@@ -90,6 +89,5 @@ This step is RUNNER-OWNED: the composition is derived by a function, and no mode
90
89
  at all. The two skills are named by ref rather than by path for the same reason the tool-less
91
90
  playbooks are (#1435) — a path is an instruction nothing can follow:
92
91
 
93
- - `journey-status` — the journey state, and the domain plan this step follows.
94
92
  - `config-saas` — the SaaS-config surface the applied scenarios append to
95
93
  (`applicationExtraServices`, the workspace members), which is what the foundation executor writes.
@@ -42,9 +42,8 @@
42
42
  ],
43
43
  "stepOutputs": [],
44
44
  "method": {
45
- "guidance": "# Capability Composition — Which Scenarios This Application Needs\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nThe framework ships fourteen composition scenarios under `templates/saas/scenarios/`. Two of\nthem — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The\nother twelve give an application a marketing website, a documentation portal, a cron minion, a\nworker, a provider, a file-picker provider, a second website locale or another deployment\nenvironment, and until this step existed nothing in the journey decided whether an application\nneeded any of them: they were reachable only by a person running `wildo compose`.\n\nThis step records that decision as the `capability-composition` family: **one decision per\nscenario the framework ships**, each with a disposition, the closed basis it was derived from,\nand a one-sentence detail naming the declaring entries.\n\n## It is derived, never asked\n\nNothing here is an interview. Every decision is read off what the application's own families\nDECLARE:\n\n| scenario | NEEDED when | read from |\n|---|---|---|\n| `add-website` | the market declares an inbound web channel (organic or paid search, content, owned or paid social); else a brand brief has landed; else the business model declares pricing plans | `market-snapshot.channels`, `brand-brief`, `business-model.plans` |\n| `add-technical-doc` | a targeted ICP (CORE or EXPANSION) is a legal entity; else a non-functional requirement declares PORTABILITY | `market-snapshot.icps`, `requirements.nonFunctional` |\n\nWhere no typed declaration can decide a scenario yet, the record says **DECLINED with the basis\n`NO_DECLARATION_DECIDES_IT` and names the declaration that would decide it** — a field for\nsomebody to add, never a question for somebody to answer:\n\n- `add-minion`, `add-worker-node`, `add-worker-rust` — a typed declaration of scheduled or\n background execution on a feature draft or a requirement; the closed vocabularies carry none.\n- `add-locale` — a locale set the product serves; measured 2026-09-17, no family declares\n languages (a governed document's drafting locale is a different decision).\n\nScenarios another step applies are recorded as **OWNED_BY_ANOTHER_STEP**, naming the owner, so\nthe record stays total without claiming the application lacks them:\n\n| scenario | owner |\n|---|---|\n| `add-module`, `add-resource` | `bottom_up.foundation` — the domain composition |\n| `add-custom-operation`, `add-website-section`, `add-marketing-page`, `add-file-picker-provider` | the build tasks that produce those artifacts (`bottom_up.build-decompose`) |\n| `add-provider` | the foundation's provider decision |\n| `add-environment` | the operator, at deployment (`wildo compose add-environment`) |\n\n## Where it lands, and who reads it\n\nThe family lands at `specifications/src/capability-composition/index.ts` and is wired onto the\n`capabilityComposition` companion-exports slot. `bottom_up.foundation` reads it there: the NEEDED\nscenarios are applied after the domain scenarios, with the application's own host facts (slug,\ndisplay name, public domain from its infrastructure environments, its port block), and the\nfoundation record names **every scenario applied and every scenario declined with the declaration\neach came from**. A package that already exists (`website/`, `technical-doc/`) is left alone and\nreported as already composed.\n\n## Read state first\n\nA composition landed before the market, the brand or the business model exists declines what\nnothing yet implies, and says so in each decision's detail. That is the honest first record, not a\nmistake: derived staleness marks the composition stale when any input family lands or changes, and\nre-running this step refines it. Nothing is re-asked because nothing was asked.\n\n## What you emit\n\n- The **capability-composition** at `specifications/src/capability-composition/index.ts` —\n fourteen decisions, total over the scenarios the framework ships.\n\n## Verification\n\n- The record is total: `validateCapabilityComposition` reports `SCENARIO_NOT_DECIDED` for any\n scenario the framework ships that the record never decided about, and\n `DISPOSITION_BASIS_MISMATCH` for a disposition whose basis contradicts it.\n- `rg -n \"disposition: CompositionDisposition.NEEDED\" specifications/src/capability-composition/index.ts`\n lists what the foundation will apply.\n\n## References — named by REF, because nothing here opens a file\n\nThis step is RUNNER-OWNED: the composition is derived by a function, and no model reads this method\nat all. The two skills are named by ref rather than by path for the same reason the tool-less\nplaybooks are (#1435) — a path is an instruction nothing can follow:\n\n- `journey-status` — the journey state, and the domain plan this step follows.\n- `config-saas` — the SaaS-config surface the applied scenarios append to\n (`applicationExtraServices`, the workspace members), which is what the foundation executor writes.\n",
45
+ "guidance": "# Capability Composition — Which Scenarios This Application Needs\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nThe framework ships one composition scenario per folder under `templates/saas/scenarios/`. Two of\nthem — `add-module` and `add-resource` — are applied by the foundation from the domain plan. The\nothers give an application a marketing website, a documentation portal, a cron minion, a worker, a\nprovider, a file-picker provider, a second website locale, another deployment environment or the\noptional 3D layout, and until this step existed nothing in the journey decided whether an\napplication needed any of them: they were reachable only by a person running `wildo compose`.\n\nThis step records that decision as the `capability-composition` family: **one decision per\nscenario the framework ships**, each with a disposition, the closed basis it was derived from,\nand a one-sentence detail naming the declaring entries.\n\n## It is derived, never asked\n\nNothing here is an interview. Every decision is read off what the application's own families\nDECLARE:\n\n| scenario | NEEDED when | read from |\n|---|---|---|\n| `add-website` | the market declares an inbound web channel (organic or paid search, content, owned or paid social); else a brand brief has landed; else the business model declares pricing plans | `market-snapshot.channels`, `brand-brief`, `business-model.plans` |\n| `add-technical-doc` | a targeted ICP (CORE or EXPANSION) is a legal entity; else a non-functional requirement declares PORTABILITY | `market-snapshot.icps`, `requirements.nonFunctional` |\n| `add-locale` | a website is composed and the application configuration serves more than one language — one locale per language beyond the primary | `appPreferences.languages` in the application configuration (a host fact: no family declares languages, and the configuration already does) |\n\nWhere no typed declaration can decide a scenario, the record says **DECLINED with the basis\n`NO_DECLARATION_DECIDES_IT` and names the declaration that would decide it** — a field for\nsomebody to add, never a question for somebody to answer. Today the only such case is `add-locale`\nwhen a website is composed but the host could not read the configuration's languages.\n\nScenarios another step applies are recorded as **OWNED_BY_ANOTHER_STEP**, naming the owner, so\nthe record stays total without claiming the application lacks them:\n\n| scenario | owner |\n|---|---|\n| `add-module`, `add-resource` | `bottom_up.foundation` — the domain composition |\n| `add-minion`, `add-worker-node`, `add-worker-rust` | `bottom_up.foundation` — one per surface the integration plan declares |\n| `add-custom-operation`, `add-website-section`, `add-marketing-page`, `add-file-picker-provider` | the build tasks that produce those artifacts (`bottom_up.build-decompose`) |\n| `add-provider` | the foundation's provider decision |\n| `add-environment` | the operator, at deployment (`wildo compose add-environment`) |\n| `add-3d-layout` | the operator's opt-in (`wildo compose add-3d-layout`): nothing a product declares decides a rendering style, so the journey never adopts the optional 3D layout |\n\n## Where it lands, and who reads it\n\nThe family lands at `specifications/src/capability-composition/index.ts` and is wired onto the\n`capabilityComposition` companion-exports slot. `bottom_up.foundation` reads it there: the NEEDED\nscenarios are applied after the domain scenarios, with the application's own host facts (slug,\ndisplay name, public domain from its infrastructure environments, its port block), and the\nfoundation record names **every scenario applied and every scenario declined with the declaration\neach came from**. A package that already exists (`website/`, `technical-doc/`) is left alone and\nreported as already composed.\n\n## Read state first\n\nA composition landed before the market, the brand or the business model exists declines what\nnothing yet implies, and says so in each decision's detail. That is the honest first record, not a\nmistake: derived staleness marks the composition stale when any input family lands or changes, and\nre-running this step refines it. Nothing is re-asked because nothing was asked.\n\n## What you emit\n\n- The **capability-composition** at `specifications/src/capability-composition/index.ts` —\n one decision per scenario, total over the scenarios the framework ships.\n\n## Verification\n\n- The record is total: `validateCapabilityComposition` reports `SCENARIO_NOT_DECIDED` for any\n scenario the framework ships that the record never decided about, and\n `DISPOSITION_BASIS_MISMATCH` for a disposition whose basis contradicts it.\n- `rg -n \"disposition: CompositionDisposition.NEEDED\" specifications/src/capability-composition/index.ts`\n lists what the foundation will apply.\n\n## References — named by REF, because nothing here opens a file\n\nThis step is RUNNER-OWNED: the composition is derived by a function, and no model reads this method\nat all. The two skills are named by ref rather than by path for the same reason the tool-less\nplaybooks are (#1435) — a path is an instruction nothing can follow:\n\n- `config-saas` — the SaaS-config surface the applied scenarios append to\n (`applicationExtraServices`, the workspace members), which is what the foundation executor writes.\n",
46
46
  "skillRefs": [
47
- "journey-status",
48
47
  "config-saas"
49
48
  ],
50
49
  "skillBodyRefs": [],
@@ -66,10 +66,28 @@ serves. For a re-derivation, name what placement or the build reported the plan
66
66
  not route — that is the whole objective. For placement, name the modules the plan
67
67
  declares and the audiences that reach them.
68
68
 
69
+ ## When the build sends the application back
70
+
71
+ The root re-opens this lane when the build lane's decomposer finds the conception unbuildable
72
+ (`conception-buildable` GAP, #1638). The round history names the criterion, and the objective you
73
+ are given carries the decomposer's reason. Revise the leaf that owns the faulted element, which is
74
+ usually the domain plan: a module, resource or relationship no build target can express, or a
75
+ reference another family makes to something the plan does not declare. A composition surface no
76
+ plan realises belongs to the surface plan it names. Do not re-derive the whole conception: the
77
+ leaves the fault does not touch are still right, and re-deriving them makes the build re-plan work
78
+ that was sound.
79
+
69
80
  ## When to stop
70
81
 
71
- Stop when the placement plan is on record: it is the decision this lane ends on. Stop
72
- also when nothing eligible advances the conception — the plan suspended on a
82
+ Stop when the placement plan is on record AND every surface the capability composition
83
+ decided is planned: the placement plan is the decision this lane ends on, but it depends
84
+ only on the domain plan, so it can land while the composition's surfaces are still
85
+ unplanned. A website or documentation portal the composition marks NEEDED, with no
86
+ website plan or documentation plan on record, is a surface the build decomposition will
87
+ emit no task for — and nothing downstream says so. Offer its plan before stopping. The
88
+ coherence report names the gap as `composition-surface-not-planned`.
89
+
90
+ Stop also when nothing eligible advances the conception — the plan suspended on a
73
91
  clarification, or an interview is unanswered — and say which.
74
92
 
75
93
  ## What the creator reviews
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "bottom_up.conception",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "phase": "bottom_up",
5
- "intent": "Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you: a family already on record is not re-derived unless the plan it was derived from has been re-derived in this run. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record: it is this lane's closing decision. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.",
5
+ "intent": "Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you: a family already on record is not re-derived unless the plan it was derived from has been re-derived in this run. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane's closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_valid",
@@ -50,16 +50,24 @@
50
50
  {
51
51
  "family": "placement-plan",
52
52
  "render": "map"
53
+ },
54
+ {
55
+ "family": "capability-composition"
56
+ },
57
+ {
58
+ "family": "website-plan",
59
+ "render": "map"
60
+ },
61
+ {
62
+ "family": "documentation-plan",
63
+ "render": "map"
53
64
  }
54
65
  ],
55
66
  "outputs": [],
56
67
  "stepOutputs": [],
57
68
  "method": {
58
- "guidance": "# The Conception Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that CONCEIVE the\napplication's structure — the domain plan, the panels' staffing, the foundation, the\nplacement plan — and it ends on the placement plan, which is the lane's closing decision.\n\n## The children, and why the order is not written here\n\n- **`bottom_up.domain-plan`** — modules, resources and relationships, from the\n requirements and the market. Asks the creator one question (tenancy) and may suspend\n mid-run on a clarification.\n- **`top_down.expert-personas`** — derives and accepts the expert charters the panels\n convene. Runner-owned, lands no family, never re-derives a committed charter, reports\n a role whose inputs have not landed as waiting.\n- **`bottom_up.capability-composition`** — which composition scenarios the\n application needs (a website, a technical-doc portal, workers, minions). Its record\n is what the foundation applies.\n- **`bottom_up.foundation`** — composes the application from the domain plan: the\n configuration, the module and resource slices, the environments. Runner-owned,\n idempotent (a byte-identical target is a skip; a collision refuses), asks the creator\n three questions.\n- **`bottom_up.experience-plan`**, **`bottom_up.website-plan`**,\n **`bottom_up.documentation-plan`** — what each surface the composition declared\n CONTAINS. Conception rather than build: the decomposer reads all three, so a surface\n planned after decomposition is one the build plan has no task for. An application that\n declared no website simply has no website plan, and nothing waits for one.\n- **`bottom_up.placement-plan`** — where every module lands in the application shell,\n decided by a panel (an information architect and a design-system guardian) over three\n candidates.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. The plan needs the requirements and the\nmarket; the personas need the vision and the market; the foundation and the placement\nneed the plan. Re-run the lane on an application whose plan exists and the first round\nalready offers the three that follow it.\n\n## Selecting the next children\n\n- **Missing beats present.** A plan or a placement already on record is not\n re-derived unless what it was derived from has been re-derived in this run.\n- **The runner-owned steps run once.** The foundation and the personas land nothing\n the runtime marks delivered, so they stay eligible; the round history is the record\n that they ran. Do not spend a round on either a second time.\n- **Independent children share a round.** The personas and the foundation both need\n only the plan and can run beside each other.\n- **A child waiting on the creator is not offered** — an unanswered interview, or a\n suspended clarification. Run everything else, and stop when nothing eligible advances\n the conception.\n\n## Composing an objective for a child\n\nFor the domain plan, name the requirements the plan must route and the market ICPs it\nserves. For a re-derivation, name what placement or the build reported the plan could\nnot route — that is the whole objective. For placement, name the modules the plan\ndeclares and the audiences that reach them.\n\n## When to stop\n\nStop when the placement plan is on record: it is the decision this lane ends on. Stop\nalso when nothing eligible advances the conception — the plan suspended on a\nclarification, or an interview is unanswered — and say which.\n\n## What the creator reviews\n\nThe domain plan and the placement plan, exactly as each leaf's own review guide says;\nthe composed application in the working tree, through `git status`; and the accepted\ncharters. The decision this lane ends on: the conception is accepted, or returned to\nthe domain plan with what could not be routed.\n",
59
- "skillRefs": [
60
- "journey-status",
61
- "journey-report"
62
- ],
69
+ "guidance": "# The Conception Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that CONCEIVE the\napplication's structure — the domain plan, the panels' staffing, the foundation, the\nplacement plan — and it ends on the placement plan, which is the lane's closing decision.\n\n## The children, and why the order is not written here\n\n- **`bottom_up.domain-plan`** — modules, resources and relationships, from the\n requirements and the market. Asks the creator one question (tenancy) and may suspend\n mid-run on a clarification.\n- **`top_down.expert-personas`** — derives and accepts the expert charters the panels\n convene. Runner-owned, lands no family, never re-derives a committed charter, reports\n a role whose inputs have not landed as waiting.\n- **`bottom_up.capability-composition`** — which composition scenarios the\n application needs (a website, a technical-doc portal, workers, minions). Its record\n is what the foundation applies.\n- **`bottom_up.foundation`** — composes the application from the domain plan: the\n configuration, the module and resource slices, the environments. Runner-owned,\n idempotent (a byte-identical target is a skip; a collision refuses), asks the creator\n three questions.\n- **`bottom_up.experience-plan`**, **`bottom_up.website-plan`**,\n **`bottom_up.documentation-plan`** — what each surface the composition declared\n CONTAINS. Conception rather than build: the decomposer reads all three, so a surface\n planned after decomposition is one the build plan has no task for. An application that\n declared no website simply has no website plan, and nothing waits for one.\n- **`bottom_up.placement-plan`** — where every module lands in the application shell,\n decided by a panel (an information architect and a design-system guardian) over three\n candidates.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. The plan needs the requirements and the\nmarket; the personas need the vision and the market; the foundation and the placement\nneed the plan. Re-run the lane on an application whose plan exists and the first round\nalready offers the three that follow it.\n\n## Selecting the next children\n\n- **Missing beats present.** A plan or a placement already on record is not\n re-derived unless what it was derived from has been re-derived in this run.\n- **The runner-owned steps run once.** The foundation and the personas land nothing\n the runtime marks delivered, so they stay eligible; the round history is the record\n that they ran. Do not spend a round on either a second time.\n- **Independent children share a round.** The personas and the foundation both need\n only the plan and can run beside each other.\n- **A child waiting on the creator is not offered** — an unanswered interview, or a\n suspended clarification. Run everything else, and stop when nothing eligible advances\n the conception.\n\n## Composing an objective for a child\n\nFor the domain plan, name the requirements the plan must route and the market ICPs it\nserves. For a re-derivation, name what placement or the build reported the plan could\nnot route — that is the whole objective. For placement, name the modules the plan\ndeclares and the audiences that reach them.\n\n## When the build sends the application back\n\nThe root re-opens this lane when the build lane's decomposer finds the conception unbuildable\n(`conception-buildable` GAP, #1638). The round history names the criterion, and the objective you\nare given carries the decomposer's reason. Revise the leaf that owns the faulted element, which is\nusually the domain plan: a module, resource or relationship no build target can express, or a\nreference another family makes to something the plan does not declare. A composition surface no\nplan realises belongs to the surface plan it names. Do not re-derive the whole conception: the\nleaves the fault does not touch are still right, and re-deriving them makes the build re-plan work\nthat was sound.\n\n## When to stop\n\nStop when the placement plan is on record AND every surface the capability composition\ndecided is planned: the placement plan is the decision this lane ends on, but it depends\nonly on the domain plan, so it can land while the composition's surfaces are still\nunplanned. A website or documentation portal the composition marks NEEDED, with no\nwebsite plan or documentation plan on record, is a surface the build decomposition will\nemit no task for — and nothing downstream says so. Offer its plan before stopping. The\ncoherence report names the gap as `composition-surface-not-planned`.\n\nStop also when nothing eligible advances the conception — the plan suspended on a\nclarification, or an interview is unanswered — and say which.\n\n## What the creator reviews\n\nThe domain plan and the placement plan, exactly as each leaf's own review guide says;\nthe composed application in the working tree, through `git status`; and the accepted\ncharters. The decision this lane ends on: the conception is accepted, or returned to\nthe domain plan with what could not be routed.\n",
70
+ "skillRefs": [],
63
71
  "skillBodyRefs": [],
64
72
  "contextSources": [],
65
73
  "draftableDocumentDefinitionRefs": [],
@@ -29,12 +29,14 @@ never written by a task.
29
29
 
30
30
  ## Step 1 — Read the capability composition FIRST
31
31
 
32
- Find the `add-technical-doc` decision.
33
-
34
- - **Declined**: land `disposition: NOT_APPLICABLE`, no chapters, and a `rationale` naming what the
35
- composition said. A complete answer — do not plan chapters for a portal the application will never
36
- compose.
37
- - **Needed**: `PLANNED`, and continue.
32
+ Find the `add-technical-doc` decision. This playbook runs only once the composition decides it is
33
+ **NEEDED**: its eligibility is gated on that decision, so a declined portal is never planned, and a
34
+ plan landed while it was needed is set aside for every reader if the composition later declines it.
35
+
36
+ - **Needed** (the normal case): `PLANNED`, and continue.
37
+ - **Declined** in the record you are given (it changed after you were started): land
38
+ `disposition: NOT_APPLICABLE`, no chapters, and a `rationale` naming what the composition said. Do not
39
+ plan chapters for a portal the application will never compose.
38
40
 
39
41
  ## Step 2 — Plan chapters from what the application ACTUALLY has
40
42
 
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "bottom_up.documentation-plan",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "bottom_up",
5
- "intent": "Documentation plan — decide WHICH CHAPTERS this application's documentation portal carries, what each one documents in THIS product, and who it is written for. Reads the capability composition first (an application whose composition declined `add-technical-doc` lands a NOT_APPLICABLE plan stating why), then the application's own specifications — its resources and their operations, its roles — and the requirements and feature drafts that say what a reader is trying to do. Every chapter names what in those specifications it documents, because the authoring skill forbids inventing a local source: a chapter grounded in nothing is one a coding agent would have to make up. Chapters are typed by the documentation engine's OWN vocabularies — its unit kinds and its reader audiences — so a landed plan speaks the language the portal's derivation already consumes. Produces the plan; the decomposer turns each chapter into a build task, and the companion's publication owns where it lands.",
5
+ "intent": "Documentation plan — decide WHICH CHAPTERS this application's documentation portal carries, what each one documents in THIS product, and who it is written for. Runs only once the capability composition decides `add-technical-doc` is NEEDED, then reads the application's own specifications — its resources and their operations, its roles — and the requirements and feature drafts that say what a reader is trying to do. Every chapter names what in those specifications it documents, because the authoring skill forbids inventing a local source: a chapter grounded in nothing is one a coding agent would have to make up. Chapters are typed by the documentation engine's OWN vocabularies — its unit kinds and its reader audiences — so a landed plan speaks the language the portal's derivation already consumes. Produces the plan; the decomposer turns each chapter into a build task, and the companion's publication owns where it lands.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -10,6 +10,14 @@
10
10
  "family": "capability-composition"
11
11
  }
12
12
  },
13
+ {
14
+ "kind": "artifact_decides",
15
+ "selector": {
16
+ "family": "capability-composition"
17
+ },
18
+ "decision": "add-technical-doc",
19
+ "equals": "NEEDED"
20
+ },
13
21
  {
14
22
  "kind": "artifact_exists",
15
23
  "selector": {
@@ -43,9 +51,8 @@
43
51
  ],
44
52
  "stepOutputs": [],
45
53
  "method": {
46
- "guidance": "# Documentation Plan — Which Chapters the Portal Carries\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## Where you are in the journey\n\nThe domain is planned and the application is being built. The framework's documentation engine\nalready derives resource-oriented pages from the specifications. What only this application can\nsupply is its own chapters — a cross-resource guide, an administrator's journey, a quickstart — and\nthose are published from two accepted files: this plan, and the chapter bodies written against it.\n\nYou produce the file that decides WHICH chapters exist: each one's ref, title, kind\nand audiences. You do not write the chapters: the decomposer turns each into a build task, whose\nagent authors the chapter's BODY in `specifications/src/technical-documentation/index.ts` under the\nsame `chapterRef`, and the companion's publication joins the two and publishes the result under\n`/guides/<slug>`. A body your plan does not declare is withheld from the portal and reported, so a\nchapter ref you drop or rename unpublishes the page written for it. The portal's generated tree is\nnever written by a task.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-technical-doc` decision.\n\n- **Declined**: land `disposition: NOT_APPLICABLE`, no chapters, and a `rationale` naming what the\n composition said. A complete answer — do not plan chapters for a portal the application will never\n compose.\n- **Needed**: `PLANNED`, and continue.\n\n## Step 2 — Plan chapters from what the application ACTUALLY has\n\nEvery chapter names, in `derivedFromRefs`, the application specifications it documents: resource\nrefs, operation refs and role refs, as those specifications authored them.\n\n(The governed documents an application publishes are NOT an input here: the family that holds them\nis the landed half of a producer/landed hop, and declaring it would be an input no playbook produces\n— the prompt would silently lose that section on every run. A chapter that must point a reader at\nthe privacy notice names it the way a reader reaches it, through the portal's own publication.) This\nis the field that keeps a chapter honest — the authoring contract forbids inventing a local source,\nso a chapter grounded in nothing is a chapter a coding agent would have to make up.\n\nRead the workspace, not only the decisions: a chapter about an operation the config does not declare\ndocuments a product that was planned rather than the one that exists.\n\n## Step 3 — Choose the KIND and the AUDIENCE from the engine's own vocabularies\n\nThese are not this plan's words. They are the documentation engine's, which is why a landed plan can\nbe consumed by the portal's derivation directly:\n\n| kind | when |\n|---|---|\n| `ORIENTATION` | where things are and what this product is — the way in |\n| `QUICKSTART` | the shortest path to a first real result |\n| `HOW_TO` | accomplishing one task somebody actually has |\n| `CONCEPT` | the idea behind a mechanism, when the how-to keeps needing it |\n| `REFERENCE` | the exhaustive surface; usually DERIVED already — author one only where the derived pages leave a gap |\n| `RUNBOOK` | an operational procedure, for the people who run it |\n| `TROUBLESHOOTING` | what goes wrong and what to do |\n| `CHANGE` | what moved between versions |\n\nAudiences: `ORGANIZATION_ADMINISTRATOR`, `ORGANIZATION_INTEGRATION_DEVELOPER`,\n`EXTERNAL_INTEGRATION_DEVELOPER`, `CONSUMING_INTERNAL_SERVICE`, `APPLICATION_OPERATIONS_STAFF`. At\nleast one per chapter: a chapter addressed to nobody is one the publication policy cannot route.\n\n**Consider a way in written for this product.** The portal always opens on its own generic Get started\npage and its page about what the application manages, so a plan with no `ORIENTATION` or\n`QUICKSTART` chapter is not refused — it is reported, because a first-time reader then meets this\nproduct only through generic pages. Plan one when the product has a first result worth walking to.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every chapter ref that still has a reason to exist — build\ntasks name them, and a moved ref orphans the task that produced its chapter.\n\n## What you emit\n\n- The **documentation plan** at `specifications/src/documentation-plan/index.ts` — a disposition\n with its rationale, and the chapters, each with its title, kind, audiences, purpose and the\n specifications it documents.\n\n## Verification\n\n- Every `derivedFromRefs` entry names something the application's specifications declare.\n- If no chapter is an `ORIENTATION` or a `QUICKSTART`, the rationale says why the generic Get started page is enough.\n- `rg -n \"chapterRef\" specifications/src/documentation-plan/index.ts | wc -l` — the number of chapter\n tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). One skill reaches this step as a BODY (`method.skillBodyRefs`):\n**`application-consumer-documentation-authoring`** — it defines what a source-grounded chapter IS\nand forbids inventing a local source, which is the rule this whole plan is built on.\n\nThe rest are named as contracts the coding agent opens when it writes each chapter:\n\n- `spec-resource-update` — the resource specifications a chapter documents, and what they guarantee.\n- `engine-product-definitions` — the product-level definitions a reader's orientation rests on.\n",
54
+ "guidance": "# Documentation Plan — Which Chapters the Portal Carries\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## Where you are in the journey\n\nThe domain is planned and the application is being built. The framework's documentation engine\nalready derives resource-oriented pages from the specifications. What only this application can\nsupply is its own chapters — a cross-resource guide, an administrator's journey, a quickstart — and\nthose are published from two accepted files: this plan, and the chapter bodies written against it.\n\nYou produce the file that decides WHICH chapters exist: each one's ref, title, kind\nand audiences. You do not write the chapters: the decomposer turns each into a build task, whose\nagent authors the chapter's BODY in `specifications/src/technical-documentation/index.ts` under the\nsame `chapterRef`, and the companion's publication joins the two and publishes the result under\n`/guides/<slug>`. A body your plan does not declare is withheld from the portal and reported, so a\nchapter ref you drop or rename unpublishes the page written for it. The portal's generated tree is\nnever written by a task.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-technical-doc` decision. This playbook runs only once the composition decides it is\n**NEEDED**: its eligibility is gated on that decision, so a declined portal is never planned, and a\nplan landed while it was needed is set aside for every reader if the composition later declines it.\n\n- **Needed** (the normal case): `PLANNED`, and continue.\n- **Declined** in the record you are given (it changed after you were started): land\n `disposition: NOT_APPLICABLE`, no chapters, and a `rationale` naming what the composition said. Do not\n plan chapters for a portal the application will never compose.\n\n## Step 2 — Plan chapters from what the application ACTUALLY has\n\nEvery chapter names, in `derivedFromRefs`, the application specifications it documents: resource\nrefs, operation refs and role refs, as those specifications authored them.\n\n(The governed documents an application publishes are NOT an input here: the family that holds them\nis the landed half of a producer/landed hop, and declaring it would be an input no playbook produces\n— the prompt would silently lose that section on every run. A chapter that must point a reader at\nthe privacy notice names it the way a reader reaches it, through the portal's own publication.) This\nis the field that keeps a chapter honest — the authoring contract forbids inventing a local source,\nso a chapter grounded in nothing is a chapter a coding agent would have to make up.\n\nRead the workspace, not only the decisions: a chapter about an operation the config does not declare\ndocuments a product that was planned rather than the one that exists.\n\n## Step 3 — Choose the KIND and the AUDIENCE from the engine's own vocabularies\n\nThese are not this plan's words. They are the documentation engine's, which is why a landed plan can\nbe consumed by the portal's derivation directly:\n\n| kind | when |\n|---|---|\n| `ORIENTATION` | where things are and what this product is — the way in |\n| `QUICKSTART` | the shortest path to a first real result |\n| `HOW_TO` | accomplishing one task somebody actually has |\n| `CONCEPT` | the idea behind a mechanism, when the how-to keeps needing it |\n| `REFERENCE` | the exhaustive surface; usually DERIVED already — author one only where the derived pages leave a gap |\n| `RUNBOOK` | an operational procedure, for the people who run it |\n| `TROUBLESHOOTING` | what goes wrong and what to do |\n| `CHANGE` | what moved between versions |\n\nAudiences: `ORGANIZATION_ADMINISTRATOR`, `ORGANIZATION_INTEGRATION_DEVELOPER`,\n`EXTERNAL_INTEGRATION_DEVELOPER`, `CONSUMING_INTERNAL_SERVICE`, `APPLICATION_OPERATIONS_STAFF`. At\nleast one per chapter: a chapter addressed to nobody is one the publication policy cannot route.\n\n**Consider a way in written for this product.** The portal always opens on its own generic Get started\npage and its page about what the application manages, so a plan with no `ORIENTATION` or\n`QUICKSTART` chapter is not refused — it is reported, because a first-time reader then meets this\nproduct only through generic pages. Plan one when the product has a first result worth walking to.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every chapter ref that still has a reason to exist — build\ntasks name them, and a moved ref orphans the task that produced its chapter.\n\n## What you emit\n\n- The **documentation plan** at `specifications/src/documentation-plan/index.ts` — a disposition\n with its rationale, and the chapters, each with its title, kind, audiences, purpose and the\n specifications it documents.\n\n## Verification\n\n- Every `derivedFromRefs` entry names something the application's specifications declare.\n- If no chapter is an `ORIENTATION` or a `QUICKSTART`, the rationale says why the generic Get started page is enough.\n- `rg -n \"chapterRef\" specifications/src/documentation-plan/index.ts | wc -l` — the number of chapter\n tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). One skill reaches this step as a BODY (`method.skillBodyRefs`):\n**`application-consumer-documentation-authoring`** — it defines what a source-grounded chapter IS\nand forbids inventing a local source, which is the rule this whole plan is built on.\n\nThe rest are named as contracts the coding agent opens when it writes each chapter:\n\n- `spec-resource-update` — the resource specifications a chapter documents, and what they guarantee.\n- `engine-product-definitions` — the product-level definitions a reader's orientation rests on.\n",
47
55
  "skillRefs": [
48
- "journey-status",
49
56
  "application-consumer-documentation-authoring",
50
57
  "spec-resource-update",
51
58
  "engine-product-definitions"
@@ -66,8 +66,8 @@ loop's** job, downstream of this plan.
66
66
  This playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting
67
67
  anything:
68
68
 
69
- 1. Read the current journey state and scope through the `journey-status` skill (it
70
- owns the read; do not re-derive it here). Confirm the top-down set is present
69
+ 1. Read the current journey state and scope from what this run is given — the loaded
70
+ specifications and the workspace sections of your brief — and do not re-derive it. Confirm the top-down set is present
71
71
  and approved, and check whether a `domain-plan` already
72
72
  exist from an earlier run (refine them, do not re-author — see below).
73
73
  2. Read the approved definition set. **Load-bearing** (these drive the
@@ -247,8 +247,6 @@ These are skill FOLDERS installed in the application, named so each piece of wor
247
247
  authoring contract a later coding agent can open. This step has no tools and does not open them;
248
248
  what reaches you is this method, your declared inputs, and the brief's own sections.
249
249
 
250
- - `journey-status` — read the current journey state and
251
- scope, and confirm the approved top-down set is in place to plan the domain from.
252
250
  - `resource-add-module` — the module-scaffolding vocabulary
253
251
  (what a module is across the project layout); keeps module boundaries idiomatic.
254
252
  - `resource-add-resource` — the resource vocabulary (what a