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