@wildo-ai/framework-knowledge 1.1.5 → 1.1.7

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 (837) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +14 -0
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
  3. package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
  4. package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
  5. package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
  7. package/dist/{knowledge/skills/journey-run/references/framework-playbook-approval-policy.md → claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md} +10 -8
  8. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
  9. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
  10. package/dist/{knowledge/skills/journey-run → claude-marketplace/plugins/wildo}/references/expert-personas-and-deliberations.md +8 -8
  11. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
  12. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
  14. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
  15. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
  17. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
  18. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
  19. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
  20. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
  21. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  22. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  23. package/dist/esm/framework-knowledge.definitions.js +321 -11
  24. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +0 -3
  28. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +12 -2
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +33 -2
  32. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +8 -5
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +55 -10
  36. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -6
  40. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  42. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  43. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -6
  44. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  45. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  46. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
  47. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +0 -1
  48. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  49. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +2 -2
  50. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  51. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -4
  52. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  53. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +10 -3
  54. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
  55. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +7 -3
  56. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
  57. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +8 -3
  59. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +1 -1
  61. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +0 -1
  63. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +7 -3
  65. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +9 -4
  67. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +3 -2
  69. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +4 -3
  71. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +1 -1
  73. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +1 -3
  75. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  77. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
  79. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +10 -3
  81. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +8 -3
  83. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +12 -5
  85. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +33 -5
  87. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +1 -1
  89. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +1 -1
  90. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
  92. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
  93. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
  94. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
  95. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
  96. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
  97. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
  98. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -0
  99. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  100. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +1 -1
  101. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
  103. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
  104. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
  105. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
  106. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +1 -1
  107. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +1 -1
  108. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  109. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +1 -1
  110. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
  111. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
  113. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  114. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +1 -1
  115. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +1 -1
  116. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  117. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +1 -1
  118. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +1 -1
  119. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +1 -1
  121. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +1 -1
  122. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  123. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +1 -1
  124. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +1 -1
  125. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  126. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +1 -1
  127. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +1 -1
  128. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  129. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +36 -17
  130. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  131. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +67 -17
  132. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  133. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +1 -1
  134. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +1 -1
  135. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +45 -0
  137. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
  138. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
  139. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -0
  140. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +1 -1
  141. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  142. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +1 -1
  143. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  144. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +1 -1
  145. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  146. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  148. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  149. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +1 -1
  150. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +1 -1
  151. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  152. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +1 -1
  153. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +1 -1
  154. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +1 -1
  156. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +1 -1
  157. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  158. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +1 -1
  159. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +1 -1
  160. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  161. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +1 -1
  162. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  163. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  164. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  165. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +1 -1
  166. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  167. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -3
  168. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  169. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  170. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  171. package/dist/knowledge/manifest.json +8 -8
  172. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -3
  173. package/dist/knowledge/playbooks/bottom_up.build/method.md +4 -2
  174. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +31 -7
  175. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  176. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  177. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +134 -26
  178. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +7 -4
  179. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +84 -29
  180. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -7
  181. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +12 -23
  182. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -7
  183. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +12 -14
  184. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -2
  185. package/dist/knowledge/playbooks/bottom_up.conception/method.md +20 -2
  186. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +15 -7
  187. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +8 -6
  188. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +11 -4
  189. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +2 -4
  190. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
  191. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +18 -2
  192. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +1 -2
  193. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +2 -4
  194. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -5
  195. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +16 -2
  196. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +3 -3
  197. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +1 -3
  198. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +1 -2
  199. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +8 -7
  200. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +11 -4
  201. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +27 -5
  202. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +1 -4
  203. package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
  204. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
  205. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
  206. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -0
  207. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +112 -21
  208. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  209. package/dist/knowledge/playbooks/refinement.document-facts/method.md +7 -2
  210. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -4
  211. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
  212. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
  213. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +6 -0
  214. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
  215. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +0 -4
  216. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +1 -2
  217. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +1 -3
  218. package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -4
  219. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -2
  220. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +1 -3
  221. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +5 -3
  222. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +2 -4
  223. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +1 -3
  224. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +0 -4
  225. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +2 -4
  226. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -3
  227. package/dist/knowledge/playbooks/top_down.definition/method.md +7 -4
  228. package/dist/knowledge/playbooks/top_down.definition/playbook.json +52 -7
  229. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +1 -1
  230. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +2 -4
  231. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
  232. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
  233. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +0 -1
  234. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -1
  235. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -1
  236. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +2 -4
  237. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -2
  238. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +1 -1
  239. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
  240. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +17 -1
  241. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +2 -5
  242. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -3
  243. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +15 -7
  244. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +2 -4
  245. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -4
  246. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +1 -2
  247. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  248. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +12 -5
  249. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +212 -0
  250. package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
  251. package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
  252. package/dist/knowledge/references/build-plan.task-graph.config.md +71 -6
  253. package/dist/knowledge/references/capability-composition.config.md +20 -1
  254. package/dist/knowledge/references/cli.market.generate-command.md +18 -2
  255. package/dist/knowledge/references/engine.client-bundle.allow-list.md +7 -22
  256. package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
  257. package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
  258. package/dist/knowledge/references/example.backend.addon-wiring.module.md +5 -0
  259. package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
  260. package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
  261. package/dist/knowledge/references/example.config.app-shell.full.md +11 -0
  262. package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
  263. package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
  264. package/dist/knowledge/references/example.config.backend.required-floors.md +7 -0
  265. package/dist/knowledge/references/example.config.navigation.full.md +45 -2
  266. package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
  267. package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
  268. package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -0
  269. package/dist/knowledge/references/example.flows-actors.autonomous-agent.md +23 -0
  270. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
  271. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +26 -3
  272. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +1 -1
  273. package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
  274. package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
  275. package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
  276. package/dist/knowledge/references/example.infra.environment-config.local.md +14 -30
  277. package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
  278. package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
  279. package/dist/knowledge/references/example.module.companion-exports.full.md +8 -13
  280. package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
  281. package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
  282. package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
  283. package/dist/knowledge/references/example.provider.backend-module-shape.md +3 -0
  284. package/dist/knowledge/references/example.provider.frontend-app.module.md +9 -0
  285. package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
  286. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +14 -13
  287. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +18 -0
  288. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +11 -11
  289. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +5 -0
  290. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +2 -0
  291. package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
  292. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
  293. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +24 -6
  294. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +36 -25
  295. package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
  296. package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
  297. package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
  298. package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
  299. package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
  300. package/dist/knowledge/references/example.website.page.manifest.md +30 -0
  301. package/dist/knowledge/references/experience-plan.config.md +11 -4
  302. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +20 -0
  303. package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
  304. package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
  305. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
  306. package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
  307. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
  308. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
  309. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
  310. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +21 -0
  311. package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
  312. package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
  313. package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
  314. package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
  315. package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
  316. package/dist/knowledge/references/integration-plan.config.md +34 -2
  317. package/dist/knowledge/references/market.alternative.config.md +1 -1
  318. package/dist/knowledge/references/market.buying-journey.config.md +1 -1
  319. package/dist/knowledge/references/market.category.config.md +1 -1
  320. package/dist/knowledge/references/market.channel.config.md +1 -1
  321. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  322. package/dist/knowledge/references/market.gain.config.md +1 -1
  323. package/dist/knowledge/references/market.icp.config.md +1 -1
  324. package/dist/knowledge/references/market.job.config.md +1 -1
  325. package/dist/knowledge/references/market.message-template.config.md +1 -1
  326. package/dist/knowledge/references/market.objection.config.md +1 -1
  327. package/dist/knowledge/references/market.pain.config.md +1 -1
  328. package/dist/knowledge/references/market.persona.config.md +1 -1
  329. package/dist/knowledge/references/market.positioning.config.md +1 -1
  330. package/dist/knowledge/references/market.proof.config.md +1 -1
  331. package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
  332. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  333. package/dist/knowledge/references/market.trigger.config.md +1 -1
  334. package/dist/knowledge/references/placement-plan.config.md +7 -1
  335. package/dist/knowledge/references/platform.config.backing-services.md +15 -15
  336. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +57 -57
  337. package/dist/knowledge/references/presets.3d.focal-plane-settings.md +45 -0
  338. package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
  339. package/dist/knowledge/references/presets.3d.layout-contract.md +235 -0
  340. package/dist/knowledge/references/presets.3d.register-layout.md +100 -0
  341. package/dist/knowledge/references/presets.models.labelling.sections.md +5 -0
  342. package/dist/knowledge/references/presets.models.shell-region.md +47 -0
  343. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
  344. package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
  345. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
  346. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +7 -6
  347. package/dist/knowledge/references/saas.backend.compliance.governed-documents-pdf-template.md +370 -0
  348. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +7 -0
  349. package/dist/knowledge/references/saas.backend.domain-module.md +93 -15
  350. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
  351. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
  352. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +200 -0
  353. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +2 -0
  354. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +73 -0
  355. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +33 -9
  356. package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
  357. package/dist/knowledge/references/saas.backend.system-access-service.md +98 -0
  358. package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
  359. package/dist/knowledge/references/saas.config.providers.augmentations.md +61 -0
  360. package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
  361. package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -0
  362. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +56 -2
  363. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +2 -2
  364. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +253 -0
  365. package/dist/knowledge/references/saas.frontend.billing-context.md +25 -2
  366. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
  367. package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
  368. package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
  369. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
  370. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +7 -5
  371. package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
  372. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +17 -2
  373. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
  374. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
  375. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +9 -0
  376. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +100 -5
  377. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
  378. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +61 -0
  379. package/dist/knowledge/references/saas.market.generation-agent.md +0 -1
  380. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
  381. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
  382. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
  383. package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
  384. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
  385. package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
  386. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
  387. package/dist/knowledge/references/saas.models.audit.trail-config.md +15 -9
  388. package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
  389. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +8 -0
  390. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +54 -1
  391. package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
  392. package/dist/knowledge/references/saas.models.config.organization-types.md +74 -0
  393. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +31 -14
  394. package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
  395. package/dist/knowledge/references/saas.models.data-mode-read-list.md +4 -4
  396. package/dist/knowledge/references/saas.models.engine-capabilities.md +12 -0
  397. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +5 -1
  398. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
  399. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
  400. package/dist/knowledge/references/saas.models.external-data-pipeline.md +667 -6
  401. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +98 -0
  402. package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
  403. package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
  404. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
  405. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
  406. package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
  407. package/dist/knowledge/references/saas.models.http-api-binding.md +812 -29
  408. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
  409. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
  410. package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
  411. package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
  412. package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
  413. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +28 -0
  414. package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
  415. package/dist/knowledge/references/saas.models.navigation.layout.md +11 -7
  416. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +32 -23
  417. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +8 -4
  418. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +22 -20
  419. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +14 -0
  420. package/dist/knowledge/references/saas.models.notifications.targets.md +20 -12
  421. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +61 -34
  422. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +9 -0
  423. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
  424. package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
  425. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
  426. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
  427. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
  428. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
  429. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
  430. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
  431. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
  432. package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
  433. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
  434. package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
  435. package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
  436. package/dist/knowledge/references/saas.models.provider-capabilities.md +34 -0
  437. package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
  438. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
  439. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +61 -0
  440. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +98 -13
  441. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
  442. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -28
  443. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
  444. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +6 -0
  445. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +8 -0
  446. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -0
  447. package/dist/knowledge/references/saas.models.system-of-record-actions.md +226 -0
  448. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
  449. package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
  450. package/dist/knowledge/references/saas.models.systems-of-record.md +242 -7
  451. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
  452. package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
  453. package/dist/knowledge/references/saas.public-runtime.contract.md +75 -7
  454. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +20 -0
  455. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +106 -13
  456. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
  457. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
  458. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
  459. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
  460. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
  461. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +6 -4
  462. package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
  463. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +14 -2
  464. package/dist/knowledge/references/saas.specifications.processor-register.md +77 -0
  465. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
  466. package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
  467. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +112 -45
  468. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +13 -1
  469. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
  470. package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
  471. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
  472. package/dist/knowledge/references/saas.website.astro.bridge.md +32 -9
  473. package/dist/knowledge/references/saas.website.astro.head-renderer.md +1 -1
  474. package/dist/knowledge/references/saas.website.astro.label-loader.md +7 -4
  475. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +15 -15
  476. package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
  477. package/dist/knowledge/references/saas.website.blog.bridge.md +17 -4
  478. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
  479. package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
  480. package/dist/knowledge/references/saas.website.consent.banner.md +10 -10
  481. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -4
  482. package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
  483. package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
  484. package/dist/knowledge/references/saas.website.page-layout.component.md +5 -2
  485. package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
  486. package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
  487. package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
  488. package/dist/knowledge/references/saas.website.runtime.context.md +23 -4
  489. package/dist/knowledge/references/saas.website.sections.definition-schema.md +14 -7
  490. package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
  491. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
  492. package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
  493. package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
  494. package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
  495. package/dist/knowledge/references/website-plan.config.md +39 -6
  496. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +2 -1
  497. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +21 -0
  498. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +1 -2
  499. package/dist/knowledge/references/zod.decorators.file-schema.md +11 -10
  500. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +7 -4
  501. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +8 -2
  502. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +5 -1
  503. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +5 -1
  504. package/dist/knowledge/references/zod.factories.address.md +7 -7
  505. package/dist/knowledge/references/zod.factories.code.md +2 -2
  506. package/dist/knowledge/references/zod.factories.duration.md +4 -4
  507. package/dist/knowledge/references/zod.factories.money.md +3 -3
  508. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  509. package/dist/knowledge/registries/framework-topics.json +1248 -54
  510. package/dist/knowledge/registries/playbooks.json +81 -109
  511. package/dist/knowledge/registries/source-tags.json +3201 -1118
  512. package/dist/knowledge/rules/live-context-door.md +29 -0
  513. package/dist/knowledge/skills/INDEX.md +27 -24
  514. package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
  515. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
  516. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
  517. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
  518. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
  519. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
  520. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
  521. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
  522. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
  523. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +31 -0
  524. package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -0
  525. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +1 -0
  526. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +9 -0
  527. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
  528. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +94 -16
  529. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +21 -8
  530. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +7 -0
  531. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +13 -5
  532. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +30 -6
  533. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +160 -32
  534. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +20 -0
  535. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +14 -2
  536. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +88 -0
  537. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +112 -14
  538. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
  539. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
  540. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
  541. package/dist/knowledge/skills/config-app-shell/SKILL.md +21 -0
  542. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +2 -2
  543. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +279 -0
  544. package/dist/knowledge/skills/config-app-shell/references/framework-shell-region-markers-api.md +66 -0
  545. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -0
  546. package/dist/knowledge/skills/config-navigation/SKILL.md +114 -16
  547. package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
  548. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +11 -7
  549. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +29 -5
  550. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +40 -27
  551. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +22 -20
  552. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +112 -5
  553. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +10 -10
  554. package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
  555. package/dist/knowledge/skills/config-saas/SKILL.md +3 -1
  556. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +7 -0
  557. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +21 -11
  558. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +5 -1
  559. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +59 -9
  560. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +46 -0
  561. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +251 -12
  562. package/dist/knowledge/skills/config-saas-backend/SKILL.md +8 -0
  563. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +81 -0
  564. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +37 -15
  565. package/dist/knowledge/skills/configure-billing/SKILL.md +64 -24
  566. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +35 -2
  567. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +14 -0
  568. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +3 -0
  569. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +25 -2
  570. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +73 -1
  571. package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
  572. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +27 -12
  573. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +11 -2
  574. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +26 -2
  575. package/dist/knowledge/skills/email-add-template/SKILL.md +61 -24
  576. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +5 -2
  577. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
  578. package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
  579. package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
  580. package/dist/knowledge/skills/engine-component-registration/SKILL.md +1 -0
  581. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +6 -0
  582. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +27 -3
  583. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +180 -0
  584. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
  585. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
  586. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
  587. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
  588. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +31 -4
  589. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +26 -3
  590. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
  591. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
  592. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +202 -0
  593. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +93 -15
  594. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +96 -11
  595. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +2 -1
  596. package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
  597. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -0
  598. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -2
  599. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +14 -9
  600. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +1 -0
  601. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +1 -0
  602. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +5 -0
  603. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
  604. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +5 -0
  605. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +8 -1
  606. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +5 -0
  607. package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
  608. package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
  609. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
  610. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
  611. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
  612. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
  613. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
  614. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
  615. package/dist/knowledge/skills/infra-environment-config/SKILL.md +150 -44
  616. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +83 -74
  617. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +180 -0
  618. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +53 -0
  619. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
  620. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +245 -0
  621. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +108 -0
  622. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +259 -0
  623. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
  624. package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +43 -0
  625. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
  626. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +32 -1
  627. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +2 -1
  628. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +36 -4
  629. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +2 -1
  630. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  631. package/dist/knowledge/skills/market-alternatives/SKILL.md +3 -2
  632. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
  633. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
  634. package/dist/knowledge/skills/market-category/SKILL.md +2 -1
  635. package/dist/knowledge/skills/market-channels/SKILL.md +2 -1
  636. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +7 -4
  637. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +6 -4
  638. package/dist/knowledge/skills/market-generation-cli/SKILL.md +28 -13
  639. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +18 -3
  640. package/dist/knowledge/skills/market-icp/SKILL.md +2 -1
  641. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +4 -3
  642. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -1
  643. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  644. package/dist/knowledge/skills/market-persona/SKILL.md +2 -1
  645. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
  646. package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
  647. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +3 -2
  648. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
  649. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -0
  650. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +2 -1
  651. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +3 -2
  652. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +1 -0
  653. package/dist/knowledge/skills/minion-authoring/SKILL.md +5 -1
  654. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +143 -0
  655. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
  656. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
  657. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
  658. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
  659. package/dist/knowledge/skills/module-companion-exports/SKILL.md +17 -16
  660. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +6 -4
  661. package/dist/knowledge/skills/module-registration/SKILL.md +2 -1
  662. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +93 -15
  663. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +86 -1
  664. package/dist/knowledge/skills/module-relationships/SKILL.md +3 -2
  665. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
  666. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
  667. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
  668. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
  669. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
  670. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
  671. package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
  672. package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -33
  673. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +227 -0
  674. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
  675. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
  676. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -0
  677. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-allow-list-api.md +111 -0
  678. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
  679. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +132 -23
  680. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +399 -0
  681. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +29 -0
  682. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
  683. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
  684. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
  685. package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
  686. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
  687. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +75 -24
  688. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +3 -3
  689. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +61 -0
  690. package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
  691. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +17 -2
  692. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +15 -0
  693. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
  694. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +25 -0
  695. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +6 -0
  696. package/dist/knowledge/skills/resource-add-field/SKILL.md +1 -0
  697. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
  698. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +105 -6
  699. package/dist/knowledge/skills/resource-add-module/SKILL.md +1 -0
  700. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +2 -1
  701. package/dist/knowledge/skills/resource-add-resource/SKILL.md +3 -0
  702. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +124 -30
  703. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +1 -0
  704. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +8 -0
  705. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +9 -0
  706. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +17 -1
  707. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +124 -30
  708. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +7 -6
  709. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +142 -34
  710. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +98 -0
  711. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +86 -52
  712. package/dist/knowledge/skills/resource-custom-view/SKILL.md +1 -0
  713. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +100 -5
  714. package/dist/knowledge/skills/resource-external-data/SKILL.md +1026 -28
  715. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
  716. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
  717. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
  718. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +686 -11
  719. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +904 -31
  720. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +166 -6
  721. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
  722. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
  723. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
  724. package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
  725. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
  726. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
  727. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
  728. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
  729. package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
  730. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
  731. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -0
  732. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +1 -0
  733. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +12 -0
  734. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +186 -0
  735. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
  736. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
  737. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
  738. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
  739. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
  740. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
  741. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +2 -2
  742. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
  743. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +3 -1
  744. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +2 -1
  745. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +28 -0
  746. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +5 -1
  747. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +34 -30
  748. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +5 -1
  749. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +101 -42
  750. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +21 -0
  751. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +1 -2
  752. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +125 -6
  753. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +8 -2
  754. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
  755. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +61 -1
  756. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +110 -9
  757. package/dist/knowledge/skills/seeding-authoring/SKILL.md +1 -0
  758. package/dist/knowledge/skills/seeding-operations/SKILL.md +1 -0
  759. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +455 -0
  760. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
  761. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
  762. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
  763. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
  764. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
  765. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -0
  766. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +61 -0
  767. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
  768. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
  769. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +14 -16
  770. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +6 -4
  771. package/dist/knowledge/skills/spec-component-update/SKILL.md +1 -0
  772. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
  773. package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
  774. package/dist/knowledge/skills/spec-feature-update/SKILL.md +1 -0
  775. package/dist/knowledge/skills/spec-resource-update/SKILL.md +13 -0
  776. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +158 -46
  777. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
  778. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
  779. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +5 -1
  780. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +1 -0
  781. package/dist/knowledge/skills/views-app-level/SKILL.md +2 -1
  782. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +43 -1
  783. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
  784. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +5 -1
  785. package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
  786. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -0
  787. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +29 -6
  788. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
  789. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +17 -4
  790. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +23 -28
  791. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +7 -22
  792. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +167 -20
  793. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
  794. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +63 -6
  795. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
  796. package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
  797. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -2
  798. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -2
  799. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +2 -1
  800. package/dist/knowledge/skills/website-page-authoring/SKILL.md +117 -33
  801. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
  802. package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
  803. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
  804. package/dist/knowledge/skills/website-section-contact/SKILL.md +65 -36
  805. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -11
  806. package/dist/knowledge/skills/website-section-cta/SKILL.md +32 -22
  807. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -11
  808. package/dist/knowledge/skills/website-section-faq/SKILL.md +99 -63
  809. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -11
  810. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +27 -18
  811. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -11
  812. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +33 -22
  813. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -11
  814. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +31 -20
  815. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -11
  816. package/dist/knowledge/skills/website-section-hero/SKILL.md +65 -44
  817. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -11
  818. package/dist/knowledge/skills/website-section-pricing/SKILL.md +217 -200
  819. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -11
  820. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
  821. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +45 -34
  822. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -11
  823. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
  824. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
  825. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +30 -25
  826. package/dist/knowledge/skills/worker-authoring/SKILL.md +1 -0
  827. package/dist/knowledge/topic-index.json +5957 -1729
  828. package/dist/tsconfig.build.tsbuildinfo +1 -1
  829. package/dist/tsconfig.tsbuildinfo +1 -1
  830. package/package.json +4 -4
  831. package/dist/knowledge/skills/journey-approve/SKILL.md +0 -63
  832. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -77
  833. package/dist/knowledge/skills/journey-next/SKILL.md +0 -82
  834. package/dist/knowledge/skills/journey-report/SKILL.md +0 -56
  835. package/dist/knowledge/skills/journey-run/SKILL.md +0 -140
  836. package/dist/knowledge/skills/journey-status/SKILL.md +0 -60
  837. /package/dist/{knowledge/skills/journey-approve → claude-marketplace/plugins/wildo}/references/specification-family-map.md +0 -0
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "bottom_up.domain-plan",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "phase": "bottom_up",
5
5
  "intent": "Turn the approved definition set into one atomic, planning-depth domain output set: module decomposition with per-module resource inventory plus typed inter-resource relationship intents. The output remains staged until deterministic validation, semantic evaluation and distinct result authority complete.",
6
6
  "preconditions": [
@@ -47,9 +47,8 @@
47
47
  ],
48
48
  "stepOutputs": [],
49
49
  "method": {
50
- "guidance": "# Domain Plan — Definition Set → Modules + Resources + Relationships (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The decomposition heuristic, the resource-inventory convention, and\n> the relationship-intent shape below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of domain modelling (a full ERD, a\n> cardinality-to-FK solver and full domain-graph validation) is intentionally\n> shallow here and is deepened in a later phase; do\n> not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first bottom-up playbook** — the pivot from **product definition**\n(top-down: vision, market, requirements, roadmap, business model) to **project\ndefinition** (bottom-up: the app's modules, resources, and how they relate). It\nruns **only after** the exact\n`top_down-to-bottom_up.bootstrap-non-regulated@0.1.0` route has produced a\ndurable `top_down → bottom_up` transition-commit fact. That fact proves the\nroute-bound readiness, semantic decision, Authority Request/Decision and phase\neffect chain; it is not an arbitrary approval flag. The separate\n`phase_is bottom_up` predicate checks the current phase projection. You are not\nre-opening product questions here — you are turning the currently accepted\nproduct definition into the *shape of the software that delivers it*.\n\n## What this playbook does\n\nYou are the **domain architect**. This playbook reads the approved definition set\nand drafts the **domain plan**: the answer to *\"what modules does this app have,\nwhat resources live in each, and how do those resources relate?\"* You produce\n**two artifacts**:\n\n1. The **domain-plan** family — the **module decomposition** with a **per-module\n resource inventory**, authored as a collection of **ModuleBusinessSemantics\n drafts** (one per proposed module). Each module draft states its purpose, its\n business capability, its primary actors, and its resource inventory\n (`mainResources` — the semantic center of the module; `supportingResources` —\n resources that support without being the center). The resource inventory lives\n **inside** each module draft because an inventory is inherently *per module*.\n2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship\n intents**: for each durable association between two inventoried resources, the\n two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-many),\n and the **ownership direction** (which resource holds the reference). These are\n typed conceptual drafts — a relationship is not a module, so it earns its own\n family, and the build loop consumes it when it wires FK fields.\n\nThis is a **planning pass**. You name modules, the resources inside them, and how\nthey relate. You do **not** author schemas, resolve a cardinality intent into a\nconcrete foreign-key field, or generate any code — that is the **bottom-up build\nloop's** job, downstream of this plan.\n\n## Read state first — the definition set you read, the two artifacts you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the top-down set is present\n and approved, and check whether a `domain-plan` already\n exist from an earlier run (refine them, do not re-author — see below).\n2. Read the approved definition set. **Load-bearing** (these drive the\n decomposition): the **requirements** (`requirements` family — the functional and\n non-functional requirements the domain must satisfy), the capability-mapped\n **MarketSnapshot** (`market-snapshot` — the benefits wired to their delivering\n features, so you know what capability each feature carries), and the\n **feature-drafts** (the prose capability contracts — what each delivering\n feature actually is). **Contextual** (they shape emphasis, not the core\n decomposition): the **roadmap** (`roadmap` — the release phasing, so you can see\n which modules are MVP-critical vs later) and the **VisionSnapshot**\n (`vision-brief` — the product framing and differentiation).\n\n\nYou **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +\n`vision-brief`; you **write** the `domain-plan` families.\n\n## Step 1 — Derive the modules (the decomposition)\n\nA **module** is a bounded slice of the app that delivers a coherent business\ncapability. Derive modules by **clustering** the definition set, not by guessing:\n\n1. **Cluster requirements and features by capability.** Group the functional\n requirements and the feature-drafts that serve one coherent capability (e.g.\n \"everything about authoring and tracking tasks\", \"everything about billing and\n plans\"). Each tight cluster is a candidate module. A feature-draft and the\n requirements it realises usually land in the same module.\n2. **Name each module and state its semantics.** For each candidate module author a\n `ModuleBusinessSemantics` draft: a `relatedModuleId` (the id the module registry\n will use — it must be **distinct across all module drafts**; two modules sharing\n an id silently collide, since the registry addresses modules by id), a `purpose`\n (why the module exists, in plain language), a\n `businessCapability` (the capability it delivers), the `primaryActors` (the\n human/business actors that interact with it), and — optionally — a\n `businessDomain` (the larger bounded-context label) and `integrationSurfaces`\n (named surfaces the module participates in).\n3. **Keep modules justified.** Every module must earn its existence from\n requirements or features in the definition set. Do **not** invent a module the\n definition set does not call for — a speculative module is a coherence CONCERN\n (see the quality gate). Conversely, if a requirement or feature has no home\n module, you are missing a module (a coverage GAP).\n\nThe `resource-add-module` skill carries the module-scaffolding vocabulary (what a\nmodule is across the project layout); read it to keep module boundaries idiomatic.\n\n## Step 2 — Inventory the resources per module\n\nFor each module, list the **resources** (persisted entity types) it owns. The\ninventory is **two lists on the module draft**:\n\n- **`mainResources`** — the resources that form the semantic **center** of the\n module (the entities the module is *about*: a `tasks` module's `task`).\n- **`supportingResources`** — resources that **support** the module's capability\n without being its center (lookup tables, join/junction entities, per-entity\n settings). A resource that is the center of the module belongs in `mainResources`,\n not here.\n\nRules for a plausible inventory:\n\n- **Derive resources from the requirements + feature-drafts**, not from a blank\n page: a requirement that says \"users can label tasks\" implies a `task` resource\n and (probably) a `label` resource. The `resource-add-resource` skill carries the\n vocabulary for what a resource is; read it to keep the inventory idiomatic.\n- **Each resource is inventoried in exactly one module** as its `mainResource`. A\n resource that is genuinely shared across modules is a signal you either have the\n module boundary wrong or you need a relationship (Step 3), not the same main\n resource duplicated in two modules.\n- **Do not author fields or schemas here.** The inventory names the resource and\n says which module owns it. What fields the resource carries, its enums, its\n decorators — all of that is the **build loop's** job. If you catch yourself\n writing a field list, stop: that is out of this playbook's depth.\n\n## Step 3 — Draft the inter-resource relationships\n\nOnce the resources are inventoried, capture how they **relate**. For each durable\nassociation between two inventoried resources, author a **relationship draft** in\nthe relationship drafts (inside the domain-plan value) stating:\n\n- **The two ends** — the two resources that relate (both must be inventoried in\n some module's inventory from Step 2; a relationship to an un-inventoried resource\n is a coverage GAP).\n- **The cardinality intent** — one-to-one, one-to-many, or many-to-many. This is an\n *intent*, in prose; you are not resolving it into a foreign-key placement here.\n- **The ownership direction** — which resource conceptually **holds** the reference\n (e.g. \"a `task` belongs to a `project`\" → the `task` end holds the reference).\n This is the *intent* the build loop needs; it does **not** decide the physical FK\n holder (that resolution — FK holder from cardinality, discriminator relationships,\n conditional relationships — is the `module-relationships` skill's job at build\n time, **not** here).\n\nThe `module-relationships` skill carries the technical HOW of realising a\nrelationship (FK fields, cardinality-to-FK-holder resolution, conditional /\ndiscriminator relationships). Read it to keep your relationship *intents* aligned\nwith what the build loop can actually wire — but do **not** perform that wiring in\nthis planning pass.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not rename or re-decompose modules\n that are already correct. Only add a module, move a resource to a different\n module, or add/correct a relationship where the plan genuinely changed.\n- **Reuse existing module ids.** A module that already exists keeps its\n `relatedModuleId` — never mint a second id for the same module. Likewise, keep a\n resource's name stable across runs.\n- **Never orphan a relationship.** A relationship draft must name two resources\n that are actually inventoried in Step 2. If you move or rename a resource, follow\n it into every relationship draft that references it.\n\n## Executable semantic evaluation — `domain-plan-output-set-result`\n\nThe staged output set first passes deterministic structural validation: exact\nmodule/resource identities, typed relationship ends, unique ownership, and the\natomic manifest must all be valid. That is a non-bypassable eligibility floor,\nnot a semantic quality opinion.\n\nThe companion then executes the playbook's structured semantic Treatment over\nthe exact staged output-set artifact. Its six criteria remain distinct:\nrequirement coverage, feature coverage, module justification, inventory\nplausibility, relationship integrity, and planning-depth boundary discipline.\nEach criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the\nworst-verdict aggregation policy determines the Decision Rule consequence.\n\nA semantic PASS does **not** accept or publish the candidate. It transitions the\nresult Decision Point to `AUTHORITY_REQUIRED`; an explicit operator authority\ndecision is a separate later boundary. CONCERN or GAP requests revision,\nINDETERMINATE requests evidence, and evaluator or hard-floor failure blocks\nclosed. The evaluation path never mutates accepted specification heads.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **Schema / field authoring.** The inventory names resources and their owning\n module; it does **not** author fields, enums, decorators, or Zod schemas. That is\n the build loop. If you catch yourself writing a field list, stop.\n- **Cardinality-to-FK resolution.** A relationship draft states a cardinality\n *intent* and an ownership *intent* in prose. Resolving that into a physical\n foreign-key holder, a discriminator relationship, or a conditional relationship is\n the `module-relationships` skill's job **at build time**, not here.\n- **A full ERD / domain-graph solver.** Phases-of-a-graph, transitive dependency\n ordering, normalization analysis, and diagram generation are a later-phase\n concern. You draft modules, an inventory, and relationship intents — not a solved\n entity-relationship diagram.\n- **A full domain-graph solver.** The framework now ships a typed conceptual\n relationship-draft contract and deterministic structural validation for the\n atomic output set. It deliberately does not solve physical FK placement,\n normalization, graph execution order, discriminator relationships, or\n conditional relationships; those remain build-depth concerns.\n- **Code generation / module registration.** Scaffolding the module folders,\n registering the module across runtimes, generating resource files — all of that is\n the bottom-up build loop, downstream of this plan.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n- The **domain-plan** under `specifications/src/domain-plan/` — a\n collection of `ModuleBusinessSemantics` drafts: the module decomposition, each\n module carrying its purpose, business capability, primary actors, and its\n `mainResources` / `supportingResources` inventory.\n- The **relationship drafts** inside the landed `specifications/src/domain-plan/` value\n — the inter-resource relationship intents (two ends + cardinality intent +\n ownership direction) between inventoried resources.\n\nAfter deterministic validation and semantic PASS, the runtime creates a distinct\nresult-bound Authority Request for the exact staged output-set digest. The local\noperator's explicit interface response settles that request; transition authority\ncannot substitute for it. Only then may the atomic specification-family mutation\naccept both files together for consumption by the bottom-up build loop.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `journey-status` — read the current journey state and\n scope, and confirm the approved top-down set is in place to plan the domain from.\n- `resource-add-module` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `resource-add-resource` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `module-relationships` — the technical HOW of realising a\n relationship (FK fields, cardinality-to-FK-holder resolution, conditional /\n discriminator relationships) — consulted so relationship *intents* align with what\n the build loop can wire, NOT performed in this planning pass.\n",
50
+ "guidance": "# Domain Plan — Definition Set → Modules + Resources + Relationships (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to be\n> iterated. The decomposition heuristic, the resource-inventory convention, and\n> the relationship-intent shape below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of domain modelling (a full ERD, a\n> cardinality-to-FK solver and full domain-graph validation) is intentionally\n> shallow here and is deepened in a later phase; do\n> not perfect it in this playbook.\n\n## Where you are in the journey\n\nThis is the **first bottom-up playbook** — the pivot from **product definition**\n(top-down: vision, market, requirements, roadmap, business model) to **project\ndefinition** (bottom-up: the app's modules, resources, and how they relate). It\nruns **only after** the exact\n`top_down-to-bottom_up.bootstrap-non-regulated@0.1.0` route has produced a\ndurable `top_down → bottom_up` transition-commit fact. That fact proves the\nroute-bound readiness, semantic decision, Authority Request/Decision and phase\neffect chain; it is not an arbitrary approval flag. The separate\n`phase_is bottom_up` predicate checks the current phase projection. You are not\nre-opening product questions here — you are turning the currently accepted\nproduct definition into the *shape of the software that delivers it*.\n\n## What this playbook does\n\nYou are the **domain architect**. This playbook reads the approved definition set\nand drafts the **domain plan**: the answer to *\"what modules does this app have,\nwhat resources live in each, and how do those resources relate?\"* You produce\n**two artifacts**:\n\n1. The **domain-plan** family — the **module decomposition** with a **per-module\n resource inventory**, authored as a collection of **ModuleBusinessSemantics\n drafts** (one per proposed module). Each module draft states its purpose, its\n business capability, its primary actors, and its resource inventory\n (`mainResources` — the semantic center of the module; `supportingResources` —\n resources that support without being the center). The resource inventory lives\n **inside** each module draft because an inventory is inherently *per module*.\n2. The **relationship drafts** — carried INSIDE the same domain-plan value — the **inter-resource relationship\n intents**: for each durable association between two inventoried resources, the\n two ends, the **cardinality intent** (one-to-one / one-to-many / many-to-many),\n and the **ownership direction** (which resource holds the reference). These are\n typed conceptual drafts — a relationship is not a module, so it earns its own\n family, and the build loop consumes it when it wires FK fields.\n\nThis is a **planning pass**. You name modules, the resources inside them, and how\nthey relate. You do **not** author schemas, resolve a cardinality intent into a\nconcrete foreign-key field, or generate any code — that is the **bottom-up build\nloop's** job, downstream of this plan.\n\n## Read state first — the definition set you read, the two artifacts you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before drafting\nanything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the top-down set is present\n and approved, and check whether a `domain-plan` already\n exist from an earlier run (refine them, do not re-author — see below).\n2. Read the approved definition set. **Load-bearing** (these drive the\n decomposition): the **requirements** (`requirements` family — the functional and\n non-functional requirements the domain must satisfy), the capability-mapped\n **MarketSnapshot** (`market-snapshot` — the benefits wired to their delivering\n features, so you know what capability each feature carries), and the\n **feature-drafts** (the prose capability contracts — what each delivering\n feature actually is). **Contextual** (they shape emphasis, not the core\n decomposition): the **roadmap** (`roadmap` — the release phasing, so you can see\n which modules are MVP-critical vs later) and the **VisionSnapshot**\n (`vision-brief` — the product framing and differentiation).\n\n\nYou **read** `requirements` + `market-snapshot` + `feature-drafts` + `roadmap` +\n`vision-brief`; you **write** the `domain-plan` families.\n\n## Step 1 — Derive the modules (the decomposition)\n\nA **module** is a bounded slice of the app that delivers a coherent business\ncapability. Derive modules by **clustering** the definition set, not by guessing:\n\n1. **Cluster requirements and features by capability.** Group the functional\n requirements and the feature-drafts that serve one coherent capability (e.g.\n \"everything about authoring and tracking tasks\", \"everything about billing and\n plans\"). Each tight cluster is a candidate module. A feature-draft and the\n requirements it realises usually land in the same module.\n2. **Name each module and state its semantics.** For each candidate module author a\n `ModuleBusinessSemantics` draft: a `relatedModuleId` (the id the module registry\n will use — it must be **distinct across all module drafts**; two modules sharing\n an id silently collide, since the registry addresses modules by id), a `purpose`\n (why the module exists, in plain language), a\n `businessCapability` (the capability it delivers), the `primaryActors` (the\n human/business actors that interact with it), and — optionally — a\n `businessDomain` (the larger bounded-context label) and `integrationSurfaces`\n (named surfaces the module participates in).\n3. **Keep modules justified.** Every module must earn its existence from\n requirements or features in the definition set. Do **not** invent a module the\n definition set does not call for — a speculative module is a coherence CONCERN\n (see the quality gate). Conversely, if a requirement or feature has no home\n module, you are missing a module (a coverage GAP).\n\nThe `resource-add-module` skill carries the module-scaffolding vocabulary (what a\nmodule is across the project layout); read it to keep module boundaries idiomatic.\n\n## Step 2 — Inventory the resources per module\n\nFor each module, list the **resources** (persisted entity types) it owns. The\ninventory is **two lists on the module draft**:\n\n- **`mainResources`** — the resources that form the semantic **center** of the\n module (the entities the module is *about*: a `tasks` module's `task`).\n- **`supportingResources`** — resources that **support** the module's capability\n without being its center (lookup tables, join/junction entities, per-entity\n settings). A resource that is the center of the module belongs in `mainResources`,\n not here.\n\nRules for a plausible inventory:\n\n- **Derive resources from the requirements + feature-drafts**, not from a blank\n page: a requirement that says \"users can label tasks\" implies a `task` resource\n and (probably) a `label` resource. The `resource-add-resource` skill carries the\n vocabulary for what a resource is; read it to keep the inventory idiomatic.\n- **Each resource is inventoried in exactly one module** as its `mainResource`. A\n resource that is genuinely shared across modules is a signal you either have the\n module boundary wrong or you need a relationship (Step 3), not the same main\n resource duplicated in two modules.\n- **Do not author fields or schemas here.** The inventory names the resource and\n says which module owns it. What fields the resource carries, its enums, its\n decorators — all of that is the **build loop's** job. If you catch yourself\n writing a field list, stop: that is out of this playbook's depth.\n\n## Step 3 — Draft the inter-resource relationships\n\nOnce the resources are inventoried, capture how they **relate**. For each durable\nassociation between two inventoried resources, author a **relationship draft** in\nthe relationship drafts (inside the domain-plan value) stating:\n\n- **The two ends** — the two resources that relate (both must be inventoried in\n some module's inventory from Step 2; a relationship to an un-inventoried resource\n is a coverage GAP).\n- **The cardinality intent** — one-to-one, one-to-many, or many-to-many. This is an\n *intent*, in prose; you are not resolving it into a foreign-key placement here.\n- **The ownership direction** — which resource conceptually **holds** the reference\n (e.g. \"a `task` belongs to a `project`\" → the `task` end holds the reference).\n This is the *intent* the build loop needs; it does **not** decide the physical FK\n holder (that resolution — FK holder from cardinality, discriminator relationships,\n conditional relationships — is the `module-relationships` skill's job at build\n time, **not** here).\n\nThe `module-relationships` skill carries the technical HOW of realising a\nrelationship (FK fields, cardinality-to-FK-holder resolution, conditional /\ndiscriminator relationships). Read it to keep your relationship *intents* aligned\nwith what the build loop can actually wire — but do **not** perform that wiring in\nthis planning pass.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not rename or re-decompose modules\n that are already correct. Only add a module, move a resource to a different\n module, or add/correct a relationship where the plan genuinely changed.\n- **Reuse existing module ids.** A module that already exists keeps its\n `relatedModuleId` — never mint a second id for the same module. Likewise, keep a\n resource's name stable across runs.\n- **Never orphan a relationship.** A relationship draft must name two resources\n that are actually inventoried in Step 2. If you move or rename a resource, follow\n it into every relationship draft that references it.\n\n## Executable semantic evaluation — `domain-plan-output-set-result`\n\nThe staged output set first passes deterministic structural validation: exact\nmodule/resource identities, typed relationship ends, unique ownership, and the\natomic manifest must all be valid. That is a non-bypassable eligibility floor,\nnot a semantic quality opinion.\n\nThe companion then executes the playbook's structured semantic Treatment over\nthe exact staged output-set artifact. Its six criteria remain distinct:\nrequirement coverage, feature coverage, module justification, inventory\nplausibility, relationship integrity, and planning-depth boundary discipline.\nEach criterion produces PASS / CONCERN / GAP / INDETERMINATE evidence, and the\nworst-verdict aggregation policy determines the Decision Rule consequence.\n\nA semantic PASS does **not** accept or publish the candidate. It transitions the\nresult Decision Point to `AUTHORITY_REQUIRED`; an explicit operator authority\ndecision is a separate later boundary. CONCERN or GAP requests revision,\nINDETERMINATE requests evidence, and evaluator or hard-floor failure blocks\nclosed. The evaluation path never mutates accepted specification heads.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **Schema / field authoring.** The inventory names resources and their owning\n module; it does **not** author fields, enums, decorators, or Zod schemas. That is\n the build loop. If you catch yourself writing a field list, stop.\n- **Cardinality-to-FK resolution.** A relationship draft states a cardinality\n *intent* and an ownership *intent* in prose. Resolving that into a physical\n foreign-key holder, a discriminator relationship, or a conditional relationship is\n the `module-relationships` skill's job **at build time**, not here.\n- **A full ERD / domain-graph solver.** Phases-of-a-graph, transitive dependency\n ordering, normalization analysis, and diagram generation are a later-phase\n concern. You draft modules, an inventory, and relationship intents — not a solved\n entity-relationship diagram.\n- **A full domain-graph solver.** The framework now ships a typed conceptual\n relationship-draft contract and deterministic structural validation for the\n atomic output set. It deliberately does not solve physical FK placement,\n normalization, graph execution order, discriminator relationships, or\n conditional relationships; those remain build-depth concerns.\n- **Code generation / module registration.** Scaffolding the module folders,\n registering the module across runtimes, generating resource files — all of that is\n the bottom-up build loop, downstream of this plan.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n- The **domain-plan** under `specifications/src/domain-plan/` — a\n collection of `ModuleBusinessSemantics` drafts: the module decomposition, each\n module carrying its purpose, business capability, primary actors, and its\n `mainResources` / `supportingResources` inventory.\n- The **relationship drafts** inside the landed `specifications/src/domain-plan/` value\n — the inter-resource relationship intents (two ends + cardinality intent +\n ownership direction) between inventoried resources.\n\nAfter deterministic validation and semantic PASS, the runtime creates a distinct\nresult-bound Authority Request for the exact staged output-set digest. The local\noperator's explicit interface response settles that request; transition authority\ncannot substitute for it. Only then may the atomic specification-family mutation\naccept both files together for consumption by the bottom-up build loop.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `resource-add-module` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `resource-add-resource` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `module-relationships` — the technical HOW of realising a\n relationship (FK fields, cardinality-to-FK-holder resolution, conditional /\n discriminator relationships) — consulted so relationship *intents* align with what\n the build loop can wire, NOT performed in this planning pass.\n",
51
51
  "skillRefs": [
52
- "journey-status",
53
52
  "resource-add-module",
54
53
  "resource-add-resource",
55
54
  "module-relationships"
@@ -59,7 +58,7 @@
59
58
  "questions": [
60
59
  {
61
60
  "ref": "tenancy",
62
- "question": "How is this application's data partitioned? Answer `organizations` when users collaborate inside shared workspaces or teams (this enables the ORGANIZATIONS engine capability and scopes every resource to an organization), or `users` when every user's data is their own.",
61
+ "question": "Do people use this application together, in shared workspaces or teams, or does each person only see their own data? Choose organizations if they work together, users if each person's data is their own.",
63
62
  "kind": "choice",
64
63
  "options": [
65
64
  "organizations",
@@ -39,14 +39,30 @@ nothing reaches them. That is the one thing this plan refuses.
39
39
  | surface | what you decide | skill |
40
40
  |---|---|---|
41
41
  | `APP_SHELL` | which sidebar sections exist, what the top bar carries, the quick switcher's scope | `config-app-shell` |
42
- | `NAVIGATION` | the zones, and what each operation does to them — push, replace, overlay | `config-navigation` |
43
- | `DESIGN_SYSTEM` | the palette and typography, from the BRAND's visual tone — never invented here | `config-design-system` |
42
+ | `NAVIGATION` | the SHAPE the application navigates in — one thing at a time, list-and-detail, or a canvas with a floating detail — and then the zones and per-operation transitions that say it | `config-navigation` |
43
+ | `DESIGN_SYSTEM` | the palette and typography, from the BRAND's visual tone — never invented here. When the brief says the brand does not apply (an internal tool), keep the scaffold's neutral theme and do not propose this surface | `config-design-system` |
44
44
  | `GLOBAL_VIEWS` | which app-level views are registered as launcher entries | `views-app-level` |
45
45
 
46
46
  Each names the things the file gains (`declarationRefs`) — a sidebar section ref, a zone, a token.
47
47
  Never the file: `wildo init` writes all four, so a decision that names nothing was true before any
48
48
  task ran.
49
49
 
50
+ **`NAVIGATION` is a product decision before it is a configuration.** The scaffold's default — one
51
+ zone, a detail that replaces the list — is a real shape and it is right for some products and wrong
52
+ for others, and nothing about the domain plan reveals which. The question is *while a person is
53
+ reading one record, what else must stay on screen*, and its answer comes from the ICPs and the
54
+ jobs-to-be-done that are already decided (on an application with no market, from
55
+ the operating team and the work the vision and the requirements describe): users who triage a queue need the list to stay, users who
56
+ open one record and finish it do not, and a product whose main surface is a board or a map needs the
57
+ detail to float over it rather than take a share of it.
58
+
59
+ Decide it HERE, with the market and definition artifacts in front of you, and put the reasoning in
60
+ the surface's `rationale` — a later task reading only the layout cannot recover why that shape was
61
+ chosen, and the shape decides whether a detail needs its own page chrome, whether a list wants
62
+ selection affordances, and whether operations must be addressable. `config-navigation`
63
+ opens with that question, translates the product shapes into what to declare, and names the trade
64
+ that is hardest to reverse: content in an overlay has no URL, so nobody can link to it.
65
+
50
66
  ## Step 2 — Decide the surfaces
51
67
 
52
68
  A surface exists because a person has to do something the generated list and read cannot do. Six
@@ -41,9 +41,8 @@
41
41
  ],
42
42
  "stepOutputs": [],
43
43
  "method": {
44
- "guidance": "# Experience Plan — What This Application's Experience Is\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved: the modules, resources and relationships exist as decisions, and the\nframework generates a list and a read screen for every resource without being asked. You decide\n**what this application carries beyond that** — the surfaces a person actually works on — **how\nits shell, navigation and palette are composed**, and **the journey a new person takes**: the\nmoments the application recognises, and the guidance that gets them there.\n\nYou do not write any of it. `bottom_up.build-decompose` turns each entry here into a build task\nbound to the skill that authors it.\n\n## This is not the placement plan\n\nPlacement decides WHERE a decided subject sits — which settings category, which sidebar section.\nThis decides WHICH SURFACES EXIST. Run in that order: a placement of a view nobody proposed places\nnothing, and the placement plan is an input here so a proposed surface does not duplicate something\nthe shell already reaches.\n\n## Step 1 — Compose the configuration surfaces\n\n**At least one, and in practice always the shell.** An application whose navigation and app shell\nare left at the scaffold's defaults has no route to its own modules: the generated screens exist and\nnothing reaches them. That is the one thing this plan refuses.\n\n| surface | what you decide | skill |\n|---|---|---|\n| `APP_SHELL` | which sidebar sections exist, what the top bar carries, the quick switcher's scope | `config-app-shell` |\n| `NAVIGATION` | the zones, and what each operation does to them — push, replace, overlay | `config-navigation` |\n| `DESIGN_SYSTEM` | the palette and typography, from the BRAND's visual tone — never invented here | `config-design-system` |\n| `GLOBAL_VIEWS` | which app-level views are registered as launcher entries | `views-app-level` |\n\nEach names the things the file gains (`declarationRefs`) — a sidebar section ref, a zone, a token.\nNever the file: `wildo init` writes all four, so a decision that names nothing was true before any\ntask ran.\n\n## Step 2 — Decide the surfaces\n\nA surface exists because a person has to do something the generated list and read cannot do. Six\nkinds, each naming the skill that authors it:\n\n| kind | what it is | belongs to |\n|---|---|---|\n| `RESOURCE_COMPOSITE_VIEW` | a workspace composing several resources around one | a resource |\n| `RESOURCE_CUSTOM_VIEW` | a bespoke screen for one operation — a wizard, a rich read | a resource |\n| `RESOURCE_EXECUTION_VIEW` | drives a long-running execution and shows its progress | a resource |\n| `RESOURCE_CHART_VIEW` | a chart over one resource's rows | a resource |\n| `APPLICATION_VIEW` | an application-level view or dashboard — the home a person opens on | a module |\n| `CUSTOM_COMPONENT` | a component several surfaces reuse | a module |\n\nThe first four are declared in ONE resource's ui-behavior, so each names its resource; the last two\nbelong to their module and must not. The plan refuses both mistakes, in both directions.\n\n**Plan an application view.** An application with none opens on whatever the shell defaults to,\nwhich is nobody's decision.\n\n## Step 3 — Name the preset components each surface reuses\n\nThis is the field this plan exists for. The framework ships a component catalogue, and a coding\nagent that has not been told which components to reuse builds the surface out of raw elements —\nbypassing the theme, the surface policy and the accessibility behaviour every preset carries. Read\nthe catalogue (`frontend-component-catalog`) and name the components each surface is composed from.\n\nA `CUSTOM_COMPONENT` reuses nothing by definition: it IS the reusable thing.\n\n## Step 4 — Make every surface accountable\n\nEach carries `servesRefs`: the requirement, feature draft, roadmap phase or success criterion that\nasked for it. A surface accountable to nothing is one nobody asked for, and the plan reports it.\n\n## Step 5 — Plan the journey\n\nA new person arrives at an application they have never used. Decide what recognises their progress\nand what tells them what to do first. **Plan at least one of the two** — a plan with neither is\nreported, because a new person then meets a product that neither welcomes nor guides them. An\ninternal tool may rightly have neither; say so by leaving both empty on purpose.\n\n**Milestones** — the moments worth recognising: a person's first record of the thing the product is\nfor, a count that shows it is working for them, a moment a whole organization reaches together. Each\nnames its identifier as a slug (`first-deal-won`, declared `FIRST_DEAL_WON` in code), its module,\nthe resource whose operation earns it, and the moment in the person's own terms. How loudly each one\ncelebrates is decided when it is built, not here.\n\n**Guidance** — two shapes, and choosing between them is the decision:\n\n| kind | what it is | use it when |\n|---|---|---|\n| `ONBOARDING_DOCUMENT` | embedded on a screen — a welcome announcement, a getting-started stepper | the guidance belongs to a place, and should be there whenever that place is |\n| `GUIDANCE_FLOW` | triggered by an event — a banner after the first X, a tour, a one-question survey | the guidance belongs to a moment, and should appear once, right after something happened |\n\nFive rules decide whether planned guidance will ever be seen — plan against them:\n\n- **Only one triggered overlay shows at a time.** The others wait behind it until it is finished,\n skipped or dismissed, and a waiting one is dropped if the page reloads first — so a second flow\n planned on the same moment is often never seen. Give each flow its own moment.\n- **A flow shows once per person.** Guidance that should appear every time — an empty-list message —\n is not a flow; it belongs to the resource's own screen.\n- **A gate is a milestone the person already holds.** `gatedByMilestoneRefs` must name milestones\n earned BEFORE the flow's moment, never the one that same moment earns.\n- **Keep refs stable.** A guidance ref keys every person's saved progress; renaming it forgets it.\n- **A document names its host.** An `ONBOARDING_DOCUMENT` is seen only where a view embeds it, so it\n names that view in `hostViewRef` — a view you plan above, or one the application already has, and\n in either case a view of the document's OWN module: a document is declared by the module whose view\n shows it, and its build task writes only there. A flow names none: its trigger shows it.\n\nBoth carry `servesRefs`, like every surface.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every view ref that still has a reason to exist — build tasks\nname them, and a moved ref orphans the task that produced its surface. The same holds for milestone\nidentifiers and guidance refs, with one more reason: people's progress is stored against them.\n\n## What you emit\n\n- The **experience plan** at `specifications/src/experience-plan/index.ts` — the configuration\n surfaces this application composes, the views it carries — each with its kind, its home, what a\n person does on it, the presets it reuses and what it serves — and its journey: the milestones it\n recognises and the guidance toward them.\n\n## Verification\n\n- Every `moduleRef` and `resourceRef` names something the domain plan declares.\n- Every `reusesComponentRefs` entry names a component the catalogue carries.\n- `rg -n \"kind: ExperienceViewKind\" specifications/src/experience-plan/index.ts | wc -l` — the number\n of view tasks the build lane will emit.\n- Every `triggerResourceRef` names a resource the domain plan declares, and no two guidance flows are\n planned on the same moment.\n- Every `gatedByMilestoneRefs` entry names a planned milestone or one the application already declares.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and one reaches this step as a BODY\n(`method.skillBodyRefs`): **`frontend-component-catalog`**. That is not a convenience — naming the\npresets each surface reuses is this plan's whole point, and a model without the catalogue in front\nof it invents component names that resolve to nothing.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `views-composite-authoring` — what a composite view IS, so a planned one is one the build lane can author.\n- `resource-custom-view` — a custom view's shape and its binding.\n- `spec-composite-view-update` — the specification a composite view owes.\n- `views-add-composite-view`, `views-add-custom-view`, `views-execution-authoring`,\n `views-chart-authoring`, `views-app-level`, `engine-component-registration` — one per view KIND,\n bound to the emitted task by `EXPERIENCE_VIEW_SKILL_REF`.\n- `config-app-shell`, `config-navigation`, `config-design-system` — one per configuration SURFACE,\n bound by `EXPERIENCE_CONFIGURATION_SKILL_REF`.\n- `milestones-and-celebrations` — how a planned milestone is declared and celebrated, bound by\n `EXPERIENCE_MILESTONE_SKILL_REF`.\n- `guidance-onboarding-authoring` — how a planned document or flow is authored, bound by\n `EXPERIENCE_GUIDANCE_SKILL_REF`.\n",
44
+ "guidance": "# Experience Plan — What This Application's Experience Is\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved: the modules, resources and relationships exist as decisions, and the\nframework generates a list and a read screen for every resource without being asked. You decide\n**what this application carries beyond that** — the surfaces a person actually works on — **how\nits shell, navigation and palette are composed**, and **the journey a new person takes**: the\nmoments the application recognises, and the guidance that gets them there.\n\nYou do not write any of it. `bottom_up.build-decompose` turns each entry here into a build task\nbound to the skill that authors it.\n\n## This is not the placement plan\n\nPlacement decides WHERE a decided subject sits — which settings category, which sidebar section.\nThis decides WHICH SURFACES EXIST. Run in that order: a placement of a view nobody proposed places\nnothing, and the placement plan is an input here so a proposed surface does not duplicate something\nthe shell already reaches.\n\n## Step 1 — Compose the configuration surfaces\n\n**At least one, and in practice always the shell.** An application whose navigation and app shell\nare left at the scaffold's defaults has no route to its own modules: the generated screens exist and\nnothing reaches them. That is the one thing this plan refuses.\n\n| surface | what you decide | skill |\n|---|---|---|\n| `APP_SHELL` | which sidebar sections exist, what the top bar carries, the quick switcher's scope | `config-app-shell` |\n| `NAVIGATION` | the SHAPE the application navigates in — one thing at a time, list-and-detail, or a canvas with a floating detail — and then the zones and per-operation transitions that say it | `config-navigation` |\n| `DESIGN_SYSTEM` | the palette and typography, from the BRAND's visual tone — never invented here. When the brief says the brand does not apply (an internal tool), keep the scaffold's neutral theme and do not propose this surface | `config-design-system` |\n| `GLOBAL_VIEWS` | which app-level views are registered as launcher entries | `views-app-level` |\n\nEach names the things the file gains (`declarationRefs`) — a sidebar section ref, a zone, a token.\nNever the file: `wildo init` writes all four, so a decision that names nothing was true before any\ntask ran.\n\n**`NAVIGATION` is a product decision before it is a configuration.** The scaffold's default — one\nzone, a detail that replaces the list — is a real shape and it is right for some products and wrong\nfor others, and nothing about the domain plan reveals which. The question is *while a person is\nreading one record, what else must stay on screen*, and its answer comes from the ICPs and the\njobs-to-be-done that are already decided (on an application with no market, from\nthe operating team and the work the vision and the requirements describe): users who triage a queue need the list to stay, users who\nopen one record and finish it do not, and a product whose main surface is a board or a map needs the\ndetail to float over it rather than take a share of it.\n\nDecide it HERE, with the market and definition artifacts in front of you, and put the reasoning in\nthe surface's `rationale` — a later task reading only the layout cannot recover why that shape was\nchosen, and the shape decides whether a detail needs its own page chrome, whether a list wants\nselection affordances, and whether operations must be addressable. `config-navigation`\nopens with that question, translates the product shapes into what to declare, and names the trade\nthat is hardest to reverse: content in an overlay has no URL, so nobody can link to it.\n\n## Step 2 — Decide the surfaces\n\nA surface exists because a person has to do something the generated list and read cannot do. Six\nkinds, each naming the skill that authors it:\n\n| kind | what it is | belongs to |\n|---|---|---|\n| `RESOURCE_COMPOSITE_VIEW` | a workspace composing several resources around one | a resource |\n| `RESOURCE_CUSTOM_VIEW` | a bespoke screen for one operation — a wizard, a rich read | a resource |\n| `RESOURCE_EXECUTION_VIEW` | drives a long-running execution and shows its progress | a resource |\n| `RESOURCE_CHART_VIEW` | a chart over one resource's rows | a resource |\n| `APPLICATION_VIEW` | an application-level view or dashboard — the home a person opens on | a module |\n| `CUSTOM_COMPONENT` | a component several surfaces reuse | a module |\n\nThe first four are declared in ONE resource's ui-behavior, so each names its resource; the last two\nbelong to their module and must not. The plan refuses both mistakes, in both directions.\n\n**Plan an application view.** An application with none opens on whatever the shell defaults to,\nwhich is nobody's decision.\n\n## Step 3 — Name the preset components each surface reuses\n\nThis is the field this plan exists for. The framework ships a component catalogue, and a coding\nagent that has not been told which components to reuse builds the surface out of raw elements —\nbypassing the theme, the surface policy and the accessibility behaviour every preset carries. Read\nthe catalogue (`frontend-component-catalog`) and name the components each surface is composed from.\n\nA `CUSTOM_COMPONENT` reuses nothing by definition: it IS the reusable thing.\n\n## Step 4 — Make every surface accountable\n\nEach carries `servesRefs`: the requirement, feature draft, roadmap phase or success criterion that\nasked for it. A surface accountable to nothing is one nobody asked for, and the plan reports it.\n\n## Step 5 — Plan the journey\n\nA new person arrives at an application they have never used. Decide what recognises their progress\nand what tells them what to do first. **Plan at least one of the two** — a plan with neither is\nreported, because a new person then meets a product that neither welcomes nor guides them. An\ninternal tool may rightly have neither; say so by leaving both empty on purpose.\n\n**Milestones** — the moments worth recognising: a person's first record of the thing the product is\nfor, a count that shows it is working for them, a moment a whole organization reaches together. Each\nnames its identifier as a slug (`first-deal-won`, declared `FIRST_DEAL_WON` in code), its module,\nthe resource whose operation earns it, and the moment in the person's own terms. How loudly each one\ncelebrates is decided when it is built, not here.\n\n**Guidance** — two shapes, and choosing between them is the decision:\n\n| kind | what it is | use it when |\n|---|---|---|\n| `ONBOARDING_DOCUMENT` | embedded on a screen — a welcome announcement, a getting-started stepper | the guidance belongs to a place, and should be there whenever that place is |\n| `GUIDANCE_FLOW` | triggered by an event — a banner after the first X, a tour, a one-question survey | the guidance belongs to a moment, and should appear once, right after something happened |\n\nFive rules decide whether planned guidance will ever be seen — plan against them:\n\n- **Only one triggered overlay shows at a time.** The others wait behind it until it is finished,\n skipped or dismissed, and a waiting one is dropped if the page reloads first — so a second flow\n planned on the same moment is often never seen. Give each flow its own moment.\n- **A flow shows once per person.** Guidance that should appear every time — an empty-list message —\n is not a flow; it belongs to the resource's own screen.\n- **A gate is a milestone the person already holds.** `gatedByMilestoneRefs` must name milestones\n earned BEFORE the flow's moment, never the one that same moment earns.\n- **Keep refs stable.** A guidance ref keys every person's saved progress; renaming it forgets it.\n- **A document names its host.** An `ONBOARDING_DOCUMENT` is seen only where a view embeds it, so it\n names that view in `hostViewRef` — a view you plan above, or one the application already has, and\n in either case a view of the document's OWN module: a document is declared by the module whose view\n shows it, and its build task writes only there. A flow names none: its trigger shows it.\n\nBoth carry `servesRefs`, like every surface.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every view ref that still has a reason to exist — build tasks\nname them, and a moved ref orphans the task that produced its surface. The same holds for milestone\nidentifiers and guidance refs, with one more reason: people's progress is stored against them.\n\n## What you emit\n\n- The **experience plan** at `specifications/src/experience-plan/index.ts` — the configuration\n surfaces this application composes, the views it carries — each with its kind, its home, what a\n person does on it, the presets it reuses and what it serves — and its journey: the milestones it\n recognises and the guidance toward them.\n\n## Verification\n\n- Every `moduleRef` and `resourceRef` names something the domain plan declares.\n- Every `reusesComponentRefs` entry names a component the catalogue carries.\n- `rg -n \"kind: ExperienceViewKind\" specifications/src/experience-plan/index.ts | wc -l` — the number\n of view tasks the build lane will emit.\n- Every `triggerResourceRef` names a resource the domain plan declares, and no two guidance flows are\n planned on the same moment.\n- Every `gatedByMilestoneRefs` entry names a planned milestone or one the application already declares.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and one reaches this step as a BODY\n(`method.skillBodyRefs`): **`frontend-component-catalog`**. That is not a convenience — naming the\npresets each surface reuses is this plan's whole point, and a model without the catalogue in front\nof it invents component names that resolve to nothing.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `views-composite-authoring` — what a composite view IS, so a planned one is one the build lane can author.\n- `resource-custom-view` — a custom view's shape and its binding.\n- `spec-composite-view-update` — the specification a composite view owes.\n- `views-add-composite-view`, `views-add-custom-view`, `views-execution-authoring`,\n `views-chart-authoring`, `views-app-level`, `engine-component-registration` — one per view KIND,\n bound to the emitted task by `EXPERIENCE_VIEW_SKILL_REF`.\n- `config-app-shell`, `config-navigation`, `config-design-system` — one per configuration SURFACE,\n bound by `EXPERIENCE_CONFIGURATION_SKILL_REF`.\n- `milestones-and-celebrations` — how a planned milestone is declared and celebrated, bound by\n `EXPERIENCE_MILESTONE_SKILL_REF`.\n- `guidance-onboarding-authoring` — how a planned document or flow is authored, bound by\n `EXPERIENCE_GUIDANCE_SKILL_REF`.\n",
45
45
  "skillRefs": [
46
- "journey-status",
47
46
  "frontend-component-catalog",
48
47
  "views-composite-authoring",
49
48
  "resource-custom-view",
@@ -84,8 +84,8 @@ expect initial scaffolding to merge around it. For an existing application, keep
84
84
  its source and use the documented repair/composition paths; never scaffold over it.
85
85
  Then:
86
86
 
87
- 1. Read the current journey state and scope through the `journey-status` skill (it
88
- owns the read; do not re-derive it here). Confirm the domain plan is present and
87
+ 1. Read the current journey state and scope from what this run is given — the loaded
88
+ specifications and the workspace sections of your brief — and do not re-derive it. Confirm the domain plan is present and
89
89
  approved, and check whether a `./wildo.saas.config.ts` already exists from an
90
90
  earlier run (refine it, do not re-author — see below).
91
91
  2. Read the **domain plan** (`domain-plan` family — the modules to register + their
@@ -380,8 +380,6 @@ with authored resources, operations, UX, and integrations.
380
380
 
381
381
  ## References
382
382
 
383
- - `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,
384
- and confirm the approved domain plan + vision brief are in place to configure from.
385
383
  - `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring
386
384
  surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.
387
385
  - `.claude/skills/module-registration/SKILL.md` — register each domain-plan module
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "bottom_up.foundation",
3
- "version": "0.2.4",
3
+ "version": "0.2.5",
4
4
  "phase": "bottom_up",
5
5
  "intent": "Bottom-up foundation — turn the approved domain plan and top-down definitions into a configured, bootable application skeleton. For a fresh application, use wildo init in an empty destination before refining its generated configuration; preserve existing projects and use their repair/composition paths. Author capabilities, modules and providers from the approved plan, verify application knowledge delivery (wildo assets sync refreshes installed assets), then run wildo setup --non-interactive and wildo local init with their prerequisites. These tools exist; their successful invocation and postconditions must be observed in the current run. The registered foundation executor composes module/resource shells and tenancy configuration; it does not run this full init/assets/setup sequence. This methodology states the prerequisites and postconditions to fulfil around that execution. It emits no artifact: the deliverable is the application source, configured module registrations and verified initialization. Record the reasons for configuration choices beside those choices. Runs after the domain plan is approved in the bottom_up phase; business resource implementation belongs to the later build work.",
6
6
  "preconditions": [
@@ -46,9 +46,8 @@
46
46
  "outputs": [],
47
47
  "stepOutputs": [],
48
48
  "method": {
49
- "guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis method composes existing tooling: `wildo init` creates the SaaS skeleton and\nattempts knowledge delivery, `wildo assets sync` refreshes that knowledge, and\n`wildo setup --non-interactive` followed by `wildo local init` configures and verifies\nthe local environment. It is guidance consumed by the application-creation lane,\nnot an automatically executed CLI script. The registered foundation executor composes\nmodule and resource shells and tenancy configuration from the domain plan; it does\nnot execute this full init/assets/setup sequence. Fulfil those prerequisites and\npostconditions separately and record actual command outcomes. Tool availability\nalone does not prove that a foundation run succeeded.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_expected vision-brief` — mean the journey\nhas entered the build-shaping phase and the load-bearing artifact is present: the\n**domain plan**, whose modules are registered and whose tenancy decides two of the three\nderived capabilities. The vision is SEQUENCING here rather than readiness (#1434): nothing\nin this playbook reads its content, and it is enforced harder upstream — the market\nsnapshot and the requirements both gate on it, and the domain plan gates on those. The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. First inspect the destination: create\na fresh skeleton with `wildo init` in an empty directory, or preserve the existing\napplication. Then perform the configuration-authoring and bring-up steps below.\nThe method describes their order; it does not itself execute the commands.\n\n1. **The engine capabilities are DERIVED for you**, from the approved domain plan's tenancy and the\n business model's revenue model. You do not choose them — see \"Engine capabilities\" below.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after the skeleton is present, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Record the compliance declarations you were given** — the operating entity and\n the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.\n See `config-saas` and its `references/compliance-declarations.md`.\n5. **Verify and bring up the configured project** — check the existing skeleton\n and knowledge delivery, run `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. Deterministic composition may create\nresource shells from the domain plan. Business-specific fields, processing, UI behavior,\nviews and navigation are the downstream build work; a generated shell does not\ncomplete that work.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything, inspect the target directory. For a new application, run `wildo init`\nin an empty destination first, then refine its generated configuration from the\napproved plan. Do not write the planned config into an empty destination and then\nexpect initial scaffolding to merge around it. For an existing application, keep\nits source and use the documented repair/composition paths; never scaffold over it.\nThen:\n\n1. Read the current journey state and scope through the `journey-status` skill (it\n owns the read; do not re-derive it here). Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory). The executor also reads the landed **business model** if there is\n one, for the billing capability alone; it may legitimately be absent, per the top-down\n phase-gate's optional posture.\n\n **Nothing else is read.** This list used to continue with the market snapshot (\"its ICPs sharpen\n capability selection\"), the requirements and the roadmap (\"which modules are MVP-critical, so you\n enable what the first release needs\"). None of the three reaches the executor, and none ever did\n (#1434). They are no longer declared as inputs either, so the declaration and the prose now say\n the same thing.\n\n// Operator affordances (the executor itself is handed the domain-plan VALUE directly):\n// `wildo context journey` — the eligibility board, runs in flight\n// `wildo context info specification-artifacts` — per-family landed state and rendered content\n\nThe executor **reads** `domain-plan` (handed to it, relationship drafts included) and the landed\n`business-model`; it **writes** `./wildo.saas.config.ts` and the materialized skeleton — app files,\ncommitted to git, which is where the record of what was decided lives.\n\nThis line used to name six families (#1434). Four of them reached nothing.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations, billing,\nnotifications, audit trails, and so on). **THE EXECUTOR DERIVES THEM. Nothing here chooses one.**\n\nExactly three are derivable today, and each from one declared value:\n\n| capability | derived from |\n|---|---|\n| `ORGANIZATIONS` | the domain plan's `tenancy` is `organizations` |\n| `EMAIL_TRANSACTIONAL` | the same — tenant invitations send mail |\n| `BILLING` | the business model's revenue model charges users |\n\n**Compliance constraints do NOT select a capability, and this method said for months that they were\n\"the primary driver\".** They are not, and the reason is recorded where the derivation lives\n(`FOUNDATION_CAPABILITY_BASIS`, which is TOTAL over the capability vocabulary and names why each\nremaining one is underivable). The clearest case is the one this method used to point at: where an\naudit trail must LIVE — a ledger, a SIEM — is an operator decision about retention and independence\nrather than a product fact, and leaving that capability out removes no control objective, because\nassurance reads the application's own audit store.\n\nA capability nothing derives is not enabled by guessing. It is enabled deliberately, later, by\nwhoever decides it — which is why the basis map records a reason per capability instead of a\nquestion.\n\nHistorical note, kept because it is the defect rather than a detail (#1434): this section described a\nderivation the runtime cannot perform — four steps of \"walk the constraints\", \"treat these as\nsharpeners\", \"every enabled capability must trace to a compliance constraint\" — and a reader believed\ncompliance constraints shaped the foundation. Nothing walked anything. The market snapshot, the\nrequirements and the roadmap were declared inputs of this playbook for the same reason and reached\nthe same nobody; they are no longer declared.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`. The executor writes that block; read the skill when you need to understand\nwhat an enabled capability means, not to decide one.\n\n## Step 1b — Apply the capability composition's optional packages\n\nWhen a `capability-composition` has landed (`bottom_up.capability-composition`), the executor\napplies every scenario it marks NEEDED after the domain scenarios below — the marketing website\n(`add-website`) and the documentation portal (`add-technical-doc`) today — with the application's\nown host facts: its slug and display name from `wildo.saas.config.ts`, the public domain from its\ninfrastructure environments (a remote one first, `localhost` when none declares one), and its port\nblock (website = app port + 1, docs = app port + 2, the convention the dogfood applications use).\nA package whose workspace already exists is left alone and reported as already composed. The run\nrecord names **every scenario applied and every scenario declined with the declaration each came\nfrom** (`compositionScenarios`), so a reader sees why the application has a website — or why not —\nwithout re-deriving it.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\nThe skeleton supplies the root workspaces and registry structure; declaring a\nmodule in configuration alone does not implement its package or contributions.\n\n1. **Declare each approved module at the SaaS root.** Use `config-saas` for the\n module's application configuration and preserve existing module identifiers.\n2. **Materialize and register module shells.** Use the delivered module-composition\n scenario and `module-registration` guidance to create the corresponding shared,\n backend and frontend contributions. Inspect the resulting registry exports;\n `config sync` is not a substitute for authored module implementation. At foundation\n depth the shells must load; business-specific resource behavior remains the build\n loop's work.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces). A value the vendor issues per deployment — an OAuth client ID, a\nfrontend SDK DSN — is authored in each environment's\n`./infrastructure/<env>/wildo.infra.<env>.config.ts > providerConfigurations` instead (the\n`infra-environment-config` skill):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n**The choice itself is the creator's, and the interview carries it.** Billing and SMS are\nthe two capabilities whose every provider needs an account, so the executor cannot pick one:\nit reads the `billing-provider` and `sms-provider` answers from the dossier, declares the chosen\nprovider in the backend scope, selects it as primary and enables the capability. The provider's\nrequired credentials are recorded on the run result as OWED — the application boots, and the\nprovider answers once an operator sets them. Answering `none` — the interview requires an answer to\nevery question, so \"decide later\" is an option — leaves the capability owed exactly as before. The\noptions are the engine providers serving the capability plus `none`; the interview validator refuses\nanything else before the run starts. Email is the exception the executor decides itself: it has a\ncredential-free development substitute (`email-preview`) and needs no choice.\n\n## Step 4 — Record the compliance declarations (only what you were told)\n\nThe creator answered `operating-entity` and `operating-jurisdictions`. Write those answers\ninto `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.\n\n- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is\n independently declarable, so a creator who named the company and not its lawful bases\n gets `legalEntityName` and `registeredAddress` written and the rest left absent. A\n missing part is reported downstream as outstanding; it does not block anything here.\n- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and\n above all not a lawful basis — that is a legal determination, and `CONSENT` in\n particular would tell a person their data rests on an agreement they could withdraw.\n A produced privacy notice quotes these as fact. An absent declaration is reported as an\n open gap a reader can see; an invented one is published.\n- **Omit the key entirely when you were told nothing.** Absence means \"nobody answered\",\n which is the honest state and the one every consumer already renders correctly. An\n empty object is refused by the schema precisely because it would satisfy the field while\n disclosing nothing.\n- **A jurisdiction needs its `basis`.** \"eu\" alone does not say whether you are established\n there, sell there, or hold data about people there, and those imply different obligations.\n If the creator gave a place without a reason, record neither — ask, or leave it out.\n\nThis step CANNOT fail the run. If the creator answered nothing, write nothing and continue:\nthe application boots, and the gap is visible where it matters rather than here.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\n## Step 5 — Verify materialization and bring up the environment\n\nRun the existing commands from the intended application root with their documented\nprerequisites. Keep application structure, delivered knowledge and running services\nas separately verified results.\n\n1. **Verify the skeleton.** A fresh project starts with `wildo init` in an empty\n destination before the configuration-authoring steps above. Check `frontend/`,\n `shared-lib/`, `backend-api/`, `specifications/` and the generated configuration.\n On a repeat run, preserve existing source; use init's repair path or the relevant\n composition scenario instead of regenerating the project as a new application.\n\n2. **Verify application knowledge delivery.** Init attempts delivery from the\n installed packages and reports delivered or skipped assets. If dependency\n installation was skipped or a package is unavailable, install the required\n packages, then refresh the supported skills/rules and framework assets:\n\n ```bash\n wildo assets sync\n ```\n\n <!-- fwk-provenance-waiver: the command below is named in order to be REFUSED — `wildo fwk` needs a framework workspace and errors inside a generated application, which is exactly why an agent that might reach for it has to recognise the name; translating it away would leave the prohibition with nothing to prohibit. -->\n Read the result and inspect the delivered application guidance. Do not assume\n arbitrary agents/hooks are installed, and do not substitute a framework-developer\n delivery flow for this one — this command is how an application receives them.\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\n5. **Know what a PostgreSQL store owes — and that you do not write its baseline here.** Read the\n store selection you authored in the infra env config:\n\n ```bash\n rg -n \"applicationDatabase\" infrastructure/*/wildo.infra.*.config.ts\n ```\n\n Absent, or MongoDB: there is nothing to do — a collection exists on first write, there is no\n plan, and no migration is ever owed.\n\n `engine: DatabaseEngine.POSTGRESQL`: nothing creates a table implicitly, so until the INITIAL\n migration exists the backend refuses to boot on every table it declares. Do NOT accept a baseline\n with `wildo db diff --update-lockfile`: that writes the lockfile and NO migration, so it records a\n plan whose tables were never created and the boot gate still refuses.\n\n The build loop owns that migration. For an application that declares PostgreSQL and has no\n `backend-api/migrations/schema-plan.lock.json`, the dispatch host derives a `database-migrations`\n step; it runs `wildo db generate`, which, with no lockfile, renders the whole model as the initial\n migration and writes the baseline in the same invocation. The two are one change and are committed\n together. It needs a built `backend-api` (the plan is computed by importing the compiled backend\n registry), so report the store you found and leave the migration to that step.\n\nReport the status of each bring-up step to the creator from its real exit and\npostcondition results. A skipped knowledge delivery or unsuccessful initialization\nis not completion, even when source files exist.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module since the last run,\n reflect it (register the module) — do not re-derive the whole configuration from\n scratch. The delta is visible in `git diff` on the config, which is the record. A new\n compliance constraint does NOT enable a capability here; see Step 1 for why.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis 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 foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. Existing command permission and effect boundaries apply independently\nof this reviewer checklist.\n\n## Scaffold-depth boundary\n\nKeep this playbook at foundation depth. Explicitly **out of scope here**:\n\n- **Implementing replacement CLI tooling.** Use the existing init, asset delivery,\n setup and local initialization owners. If a command fails, retain its diagnostic\n evidence and resolve the prerequisite or concrete defect rather than inventing\n another materializer inside the application.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities. The foundation executor can materialize resource shells\n and scope them to the chosen tenancy. Filling those shells with business-specific\n fields, rules, UI behavior, views and navigation belongs to the later build work.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — deeper capability modelling belongs to a dedicated later pass,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and scope,\n and confirm the approved domain plan + vision brief are in place to configure from.\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is maintained here as guidance against the current tooling:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — materialize a fresh skeleton in an empty destination (or preserve an existing project) → refine config and module registrations → verify knowledge delivery → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth: deterministic resource shells are allowed, but business-specific fields, processing, UI behavior, views and navigation belong to later build work. Use the existing init/assets owners; do not replace them. Headless setup and local init run once their prerequisites are satisfied. This reviewer checklist is declarative; creator approval is the trust floor.\n",
49
+ "guidance": "# Foundation — Domain Plan → Configured, Bootable App Skeleton (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis method composes existing tooling: `wildo init` creates the SaaS skeleton and\nattempts knowledge delivery, `wildo assets sync` refreshes that knowledge, and\n`wildo setup --non-interactive` followed by `wildo local init` configures and verifies\nthe local environment. It is guidance consumed by the application-creation lane,\nnot an automatically executed CLI script. The registered foundation executor composes\nmodule and resource shells and tenancy configuration from the domain plan; it does\nnot execute this full init/assets/setup sequence. Fulfil those prerequisites and\npostconditions separately and record actual command outcomes. Tool availability\nalone does not prove that a foundation run succeeded.\n\n## Where you are in the journey\n\nThis is the **foundation** playbook — the point in the **bottom-up** phase where\nthe *plan* becomes a *bootable app*. It runs **after** the `bottom_up.domain-plan`\nplaybook produced (and the creator approved) the **domain plan**: the module\ndecomposition, the per-module resource inventory, and the inter-resource\nrelationship intents. Its preconditions — `phase_is bottom_up` and\n`artifact_exists domain-plan` and `artifact_expected vision-brief` — mean the journey\nhas entered the build-shaping phase and the load-bearing artifact is present: the\n**domain plan**, whose modules are registered and whose tenancy decides two of the three\nderived capabilities. The vision is SEQUENCING here rather than readiness (#1434): nothing\nin this playbook reads its content, and it is enforced harder upstream — the market\nsnapshot and the requirements both gate on it, and the domain plan gates on those. The\nroute-bound `transition_committed` fact that authorized and applied crossing from top-down into\nbottom-up was the domain-plan playbook's duty (it is the first bottom-up playbook);\nyou do not re-cross that boundary — the domain plan's existence already sits behind\nit.\n\nYou are not re-opening the domain plan here — you are turning an *approved* plan\ninto the *configured application skeleton the build loop then fills in*.\n\n## What this playbook does\n\nYou are the **foundation engineer**. This playbook reads the approved domain plan\nand the vision brief, then configures and brings up the application skeleton so the\nbuild loop has a real workspace to author into. First inspect the destination: create\na fresh skeleton with `wildo init` in an empty directory, or preserve the existing\napplication. Then perform the configuration-authoring and bring-up steps below.\nThe method describes their order; it does not itself execute the commands.\n\n1. **The engine capabilities are DERIVED for you**, from the approved domain plan's tenancy and the\n business model's revenue model. You do not choose them — see \"Engine capabilities\" below.\n2. **Declare the domain-plan's modules** at the SaaS root (they are registered across\n the runtimes after the skeleton is present, so it boots with them).\n3. **Select the providers** the enabled capabilities need.\n4. **Record the compliance declarations you were given** — the operating entity and\n the jurisdictions, from the elicitation answers, into `./wildo.saas.config.ts`.\n See `config-saas` and its `references/compliance-declarations.md`.\n5. **Verify and bring up the configured project** — check the existing skeleton\n and knowledge delivery, run `wildo setup --non-interactive`, then `wildo local init`.\n\nYou emit **no artifact**. The deliverable is the app itself: `./wildo.saas.config.ts`,\nthe materialized skeleton, and a verified local initialization. Record *why* each\ncapability, module and provider was chosen in the config's own comments, where the\nnext reader of that file will find it.\n\nThis is a **foundation pass**. You enable capabilities, declare modules as shells,\nselect providers, and bring the skeleton up. Deterministic composition may create\nresource shells from the domain plan. Business-specific fields, processing, UI behavior,\nviews and navigation are the downstream build work; a generated shell does not\ncomplete that work.\n\n## Read state first — the artifacts you read, the files you write\n\nThis playbook is **idempotent** and, on a re-run, a *refinement*. Before configuring\nanything, inspect the target directory. For a new application, run `wildo init`\nin an empty destination first, then refine its generated configuration from the\napproved plan. Do not write the planned config into an empty destination and then\nexpect initial scaffolding to merge around it. For an existing application, keep\nits source and use the documented repair/composition paths; never scaffold over it.\nThen:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it. Confirm the domain plan is present and\n approved, and check whether a `./wildo.saas.config.ts` already exists from an\n earlier run (refine it, do not re-author — see below).\n2. Read the **domain plan** (`domain-plan` family — the modules to register + their\n resource inventory). The executor also reads the landed **business model** if there is\n one, for the billing capability alone; it may legitimately be absent, per the top-down\n phase-gate's optional posture.\n\n **Nothing else is read.** This list used to continue with the market snapshot (\"its ICPs sharpen\n capability selection\"), the requirements and the roadmap (\"which modules are MVP-critical, so you\n enable what the first release needs\"). None of the three reaches the executor, and none ever did\n (#1434). They are no longer declared as inputs either, so the declaration and the prose now say\n the same thing.\n\n// Operator affordances (the executor itself is handed the domain-plan VALUE directly):\n// `wildo context journey` — the eligibility board, runs in flight\n// `wildo context info specification-artifacts` — per-family landed state and rendered content\n\nThe executor **reads** `domain-plan` (handed to it, relationship drafts included) and the landed\n`business-model`; it **writes** `./wildo.saas.config.ts` and the materialized skeleton — app files,\ncommitted to git, which is where the record of what was decided lives.\n\nThis line used to name six families (#1434). Four of them reached nothing.\n\n## Step 1 — Derive and enable the engine capabilities\n\nEngine capabilities are the framework surfaces the app turns on (organizations, billing,\nnotifications, audit trails, and so on). **THE EXECUTOR DERIVES THEM. Nothing here chooses one.**\n\nExactly three are derivable today, and each from one declared value:\n\n| capability | derived from |\n|---|---|\n| `ORGANIZATIONS` | the domain plan's `tenancy` is `organizations` |\n| `EMAIL_TRANSACTIONAL` | the same — tenant invitations send mail |\n| `BILLING` | the business model's revenue model charges users |\n\n**Compliance constraints do NOT select a capability, and this method said for months that they were\n\"the primary driver\".** They are not, and the reason is recorded where the derivation lives\n(`FOUNDATION_CAPABILITY_BASIS`, which is TOTAL over the capability vocabulary and names why each\nremaining one is underivable). The clearest case is the one this method used to point at: where an\naudit trail must LIVE — a ledger, a SIEM — is an operator decision about retention and independence\nrather than a product fact, and leaving that capability out removes no control objective, because\nassurance reads the application's own audit store.\n\nA capability nothing derives is not enabled by guessing. It is enabled deliberately, later, by\nwhoever decides it — which is why the basis map records a reason per capability instead of a\nquestion.\n\nHistorical note, kept because it is the defect rather than a detail (#1434): this section described a\nderivation the runtime cannot perform — four steps of \"walk the constraints\", \"treat these as\nsharpeners\", \"every enabled capability must trace to a compliance constraint\" — and a reader believed\ncompliance constraints shaped the foundation. Nothing walked anything. The market snapshot, the\nrequirements and the roadmap were declared inputs of this playbook for the same reason and reached\nthe same nobody; they are no longer declared.\n\nThe `config-saas` skill carries the vocabulary for the `engineCapabilities` block of\n`./wildo.saas.config.ts`. The executor writes that block; read the skill when you need to understand\nwhat an enabled capability means, not to decide one.\n\n## Step 1b — Apply the capability composition's optional packages\n\nWhen a `capability-composition` has landed (`bottom_up.capability-composition`), the executor\napplies every scenario it marks NEEDED after the domain scenarios below — the marketing website\n(`add-website`) and the documentation portal (`add-technical-doc`) today — with the application's\nown host facts: its slug and display name from `wildo.saas.config.ts`, the public domain from its\ninfrastructure environments (a remote one first, `localhost` when none declares one), and its port\nblock (website = app port + 1, docs = app port + 2, the convention the dogfood applications use).\nA package whose workspace already exists is left alone and reported as already composed. The run\nrecord names **every scenario applied and every scenario declined with the declaration each came\nfrom** (`compositionScenarios`), so a reader sees why the application has a website — or why not —\nwithout re-deriving it.\n\n## Step 2 — Declare the domain-plan's modules (register across runtimes after materialization)\n\nThe skeleton supplies the root workspaces and registry structure; declaring a\nmodule in configuration alone does not implement its package or contributions.\n\n1. **Declare each approved module at the SaaS root.** Use `config-saas` for the\n module's application configuration and preserve existing module identifiers.\n2. **Materialize and register module shells.** Use the delivered module-composition\n scenario and `module-registration` guidance to create the corresponding shared,\n backend and frontend contributions. Inspect the resulting registry exports;\n `config sync` is not a substitute for authored module implementation. At foundation\n depth the shells must load; business-specific resource behavior remains the build\n loop's work.\n3. **Declare every domain-plan module — and no more.** A module the domain plan named\n that is missing from the config is a GAP; a module in the config the domain plan did\n not name is an unjustified-module CONCERN. Record the declared modules (each traced\n to its domain-plan module) as a comment beside it in the config.\n\n**Do not author the resources here.** The domain plan's per-module resource inventory\ntells you *what* resources each module will own, but authoring their schemas, fields,\nand config is the **build loop's** job. If you catch yourself writing a resource\nschema, stop: that is out of this playbook's depth.\n\n## Step 3 — Select the providers\n\nEnabled capabilities that reach an external service need a **provider** (billing → a\npayment provider; notifications/email → an email provider; file storage → an object\nstore). For each such capability, select and wire the provider scope +\n`providerConfigurations` in `./wildo.saas.config.ts` (the `config-saas` skill covers\nthe provider surfaces). A value the vendor issues per deployment — an OAuth client ID, a\nfrontend SDK DSN — is authored in each environment's\n`./infrastructure/<env>/wildo.infra.<env>.config.ts > providerConfigurations` instead (the\n`infra-environment-config` skill):\n\n- **Every provider matches a declared capability.** A provider wired for no enabled\n capability is a CONCERN; an enabled capability that needs a provider with none\n selected is a GAP.\n- **Do not seed secrets here.** Provider *selection* (which provider, which scope) is\n foundation; the per-environment secret material is seeded by the deterministic\n bring-up / environment step, not authored inline. Record the selected providers\n (each matched to its capability) as a comment beside it in the config.\n\n**The choice itself is the creator's, and the interview carries it.** Billing and SMS are\nthe two capabilities whose every provider needs an account, so the executor cannot pick one:\nit reads the `billing-provider` and `sms-provider` answers from the dossier, declares the chosen\nprovider in the backend scope, selects it as primary and enables the capability. The provider's\nrequired credentials are recorded on the run result as OWED — the application boots, and the\nprovider answers once an operator sets them. Answering `none` — the interview requires an answer to\nevery question, so \"decide later\" is an option — leaves the capability owed exactly as before. The\noptions are the engine providers serving the capability plus `none`; the interview validator refuses\nanything else before the run starts. Email is the exception the executor decides itself: it has a\ncredential-free development substitute (`email-preview`) and needs no choice.\n\n## Step 4 — Record the compliance declarations (only what you were told)\n\nThe creator answered `operating-entity` and `operating-jurisdictions`. Write those answers\ninto `operatorComplianceIdentity` and `operatingJurisdictions`, and **nothing else**.\n\n- **Record the PART you were given.** Every part of `operatorComplianceIdentity` is\n independently declarable, so a creator who named the company and not its lawful bases\n gets `legalEntityName` and `registeredAddress` written and the rest left absent. A\n missing part is reported downstream as outstanding; it does not block anything here.\n- **NEVER invent one.** Not a company name, not an address, not a privacy contact, and\n above all not a lawful basis — that is a legal determination, and `CONSENT` in\n particular would tell a person their data rests on an agreement they could withdraw.\n A produced privacy notice quotes these as fact. An absent declaration is reported as an\n open gap a reader can see; an invented one is published.\n- **Omit the key entirely when you were told nothing.** Absence means \"nobody answered\",\n which is the honest state and the one every consumer already renders correctly. An\n empty object is refused by the schema precisely because it would satisfy the field while\n disclosing nothing.\n- **A jurisdiction needs its `basis`.** \"eu\" alone does not say whether you are established\n there, sell there, or hold data about people there, and those imply different obligations.\n If the creator gave a place without a reason, record neither — ask, or leave it out.\n\nThis step CANNOT fail the run. If the creator answered nothing, write nothing and continue:\nthe application boots, and the gap is visible where it matters rather than here.\n\n(A `foundation-manifest` artifact was declared here until 2026-08-25 and is now\nretired with the app-creation verification/digest aspect. It was a bookkeeping record\nof decisions the config already carries — deleting it costs no fact about the app.)\n\n## Step 5 — Verify materialization and bring up the environment\n\nRun the existing commands from the intended application root with their documented\nprerequisites. Keep application structure, delivered knowledge and running services\nas separately verified results.\n\n1. **Verify the skeleton.** A fresh project starts with `wildo init` in an empty\n destination before the configuration-authoring steps above. Check `frontend/`,\n `shared-lib/`, `backend-api/`, `specifications/` and the generated configuration.\n On a repeat run, preserve existing source; use init's repair path or the relevant\n composition scenario instead of regenerating the project as a new application.\n\n2. **Verify application knowledge delivery.** Init attempts delivery from the\n installed packages and reports delivered or skipped assets. If dependency\n installation was skipped or a package is unavailable, install the required\n packages, then refresh the supported skills/rules and framework assets:\n\n ```bash\n wildo assets sync\n ```\n\n <!-- fwk-provenance-waiver: the command below is named in order to be REFUSED — `wildo fwk` needs a framework workspace and errors inside a generated application, which is exactly why an agent that might reach for it has to recognise the name; translating it away would leave the prohibition with nothing to prohibit. -->\n Read the result and inspect the delivered application guidance. Do not assume\n arbitrary agents/hooks are installed, and do not substitute a framework-developer\n delivery flow for this one — this command is how an application receives them.\n\n3. **Run setup** — configure the app from the authored `./wildo.saas.config.ts` and\n the `./infrastructure/` env configs (the `infra-environment-config` skill owns the\n typed infra env files; the `local-environment-bootstrap` skill owns the `wildo`\n lifecycle). Headless setup is registered and fail-closed on the administrator seed\n environment variables; it mints the environment generation without placeholders.\n\n ```bash\n wildo setup --non-interactive\n ```\n\n4. **Initialize and verify the project** — run the registered convergence journey.\n It regenerates artifacts, starts and readiness-gates backing services, reconciles\n platform Mongo state and credentials, starts native platform services, registers the\n app once, emits all runtime projections, and executes a signed managed-config read.\n\n ```bash\n wildo local init\n ```\n\n5. **Know what a PostgreSQL store owes — and that you do not write its baseline here.** Read the\n store selection you authored in the infra env config:\n\n ```bash\n rg -n \"applicationDatabase\" infrastructure/*/wildo.infra.*.config.ts\n ```\n\n Absent, or MongoDB: there is nothing to do — a collection exists on first write, there is no\n plan, and no migration is ever owed.\n\n `engine: DatabaseEngine.POSTGRESQL`: nothing creates a table implicitly, so until the INITIAL\n migration exists the backend refuses to boot on every table it declares. Do NOT accept a baseline\n with `wildo db diff --update-lockfile`: that writes the lockfile and NO migration, so it records a\n plan whose tables were never created and the boot gate still refuses.\n\n The build loop owns that migration. For an application that declares PostgreSQL and has no\n `backend-api/migrations/schema-plan.lock.json`, the dispatch host derives a `database-migrations`\n step; it runs `wildo db generate`, which, with no lockfile, renders the whole model as the initial\n migration and writes the baseline in the same invocation. The two are one change and are committed\n together. It needs a built `backend-api` (the plan is computed by importing the compiled backend\n registry), so report the store you found and leave the migration to that step.\n\nReport the status of each bring-up step to the creator from its real exit and\npostcondition results. A skipped knowledge delivery or unsuccessful initialization\nis not completion, even when source files exist.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** On a re-run, do not disable a capability, drop a module,\n or re-select a provider that is already correct. Only enable a newly-justified\n capability, register a newly-added domain-plan module, or correct a provider where\n the definition set genuinely changed.\n- **Reuse existing module ids and provider scopes.** A module already registered keeps\n its id; a provider already selected keeps its scope — never mint a second one for the\n same module/capability.\n- **Follow the definition set.** If the domain plan added a module since the last run,\n reflect it (register the module) — do not re-derive the whole configuration from\n scratch. The delta is visible in `git diff` on the config, which is the record. A new\n compliance constraint does NOT enable a capability here; see Step 1 for why.\n\n## Quality gate — `foundation-configured-coherently` (declarative at scaffold depth)\n\nThe foundation is checked against the `foundation-configured-coherently` **reviewer\nchecklist** (see the end of this method): five invariants (capability derivation, module registration, provider coverage,\nsequence order, and foundation-depth boundary discipline), each marked PASS / CONCERN /\nGAP.\n\nThis 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 foundation today is the\ncreator's `approve_result` review of the produced config and the bring-up result. There is\nintentionally **no deterministic gate**: config validation is a `wildo` CLI concern\n(`config sync` / validate), not a validator in the journey-artifact schemaRef\nvocabulary. Existing command permission and effect boundaries apply independently\nof this reviewer checklist.\n\n## Scaffold-depth boundary\n\nKeep this playbook at foundation depth. Explicitly **out of scope here**:\n\n- **Implementing replacement CLI tooling.** Use the existing init, asset delivery,\n setup and local initialization owners. If a command fails, retain its diagnostic\n evidence and resolve the prerequisite or concrete defect rather than inventing\n another materializer inside the application.\n- **Resource / field / schema authoring.** The config declares modules as shells and\n enables capabilities. The foundation executor can materialize resource shells\n and scope them to the chosen tenancy. Filling those shells with business-specific\n fields, rules, UI behavior, views and navigation belongs to the later build work.\n- **Re-introducing a foundation artifact.** The `foundation-manifest` family was\n retired on 2026-08-25 with the app-creation verification/digest aspect. Do **NOT**\n reshape `_core` to bring it back: the config file and its git history already carry\n every decision it recorded.\n- **Deep capability / provider modelling.** A defended capability-selection model\n (per-compliance-regime obligation → capability mapping, provider cost/feature\n matrices, multi-provider fallback) is a later depth pass. You derive capabilities\n from the definition set with the v1 heuristic above — not a solved obligation graph.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at scaffold\ndepth — deeper capability modelling belongs to a dedicated later pass,\nholistically.\n\n## What you emit\n\n- The authored **`./wildo.saas.config.ts`** (an app file) — the enabled engine\n capabilities, the registered modules, and the selected providers — plus the\n registered module shells across the runtimes and the\n brought-up skeleton.\n- The **bring-up result** reported to the creator: the status of each step, taken from\n its real exit/postcondition rather than from intent. This is a report, not a stored\n artifact — nothing reads it back.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's foundation, which the bottom-up build loop then fills in\nwith authored resources, operations, UX, and integrations.\n\n## References\n\n- `.claude/skills/config-saas/SKILL.md` — the `./wildo.saas.config.ts` authoring\n surface: `engineCapabilities`, `modules`, provider scopes, and `providerConfigurations`.\n- `.claude/skills/module-registration/SKILL.md` — register each domain-plan module\n across the shared / frontend / backend registries so the skeleton boots with it\n (distinct from `config-saas`, which only declares module existence at the root).\n- `.claude/skills/infra-environment-config/SKILL.md` — the typed `./infrastructure/`\n environment configs (backing services, public domain, service auth) the bring-up needs.\n- `.claude/skills/local-environment-bootstrap/SKILL.md` — the `wildo` lifecycle\n (`setup`, `local init`, `local reinit`, `local dev`) for deterministic initialization,\n repair, clean-room recovery, and runtime start.\n\n## Reviewer checklist — `foundation-configured-coherently`\n\nFormerly authored as an `llm_judge` quality gate; the generic rubric-only gate kind was retired at the flexible-intelligence hard cut (judgment now runs only through a compiled Evaluation Treatment). The checklist itself is creator-facing review guidance and is maintained here as guidance against the current tooling:\n\nJudge whether the authored foundation (the ./wildo.saas.config.ts composition + the materialized skeleton) is a coherent realisation of the approved domain plan and the top-down definition set. Assess five invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) CAPABILITY DERIVATION — every enabled engine capability traces to a compliance/vision, business-model, market, or domain-plan need; unjustified capabilities are a CONCERN and missing required capabilities are a GAP. (2) MODULE REGISTRATION — every approved domain-plan module is declared and registered across runtimes; missing modules are a GAP and extra modules are a CONCERN. (3) PROVIDER COVERAGE — every provider serves a declared capability and every provider-backed capability has a provider. (4) SEQUENCE ORDER AND PROOF — materialize a fresh skeleton in an empty destination (or preserve an existing project) → refine config and module registrations → verify knowledge delivery → wildo setup --non-interactive → wildo local init. Treat setup intent, container health, or an initialization marker as insufficient: local init must reach its signed managed-config-read postcondition. (5) BOUNDARY DISCIPLINE — stay at foundation depth: deterministic resource shells are allowed, but business-specific fields, processing, UI behavior, views and navigation belong to later build work. Use the existing init/assets owners; do not replace them. Headless setup and local init run once their prerequisites are satisfied. This reviewer checklist is declarative; creator approval is the trust floor.\n",
50
50
  "skillRefs": [
51
- "journey-status",
52
51
  "config-saas",
53
52
  "module-registration",
54
53
  "infra-environment-config",
@@ -60,12 +59,16 @@
60
59
  "questions": [
61
60
  {
62
61
  "ref": "primary-scope",
63
- "question": "What is the application's tenancy model? Answer `organizations` when users collaborate inside shared workspaces/teams (this enables the ORGANIZATIONS engine capability), or `users` when every user's data is their own.",
62
+ "question": "Do people use this application together, in shared workspaces or teams, or does each person only see their own data? Choose organizations if they work together, users if each person's data is their own.",
64
63
  "kind": "choice",
65
64
  "options": [
66
65
  "organizations",
67
66
  "users"
68
- ]
67
+ ],
68
+ "sameDecisionAs": {
69
+ "playbookRef": "bottom_up.domain-plan",
70
+ "questionRef": "tenancy"
71
+ }
69
72
  },
70
73
  {
71
74
  "ref": "operating-entity",
@@ -91,6 +91,18 @@ one declaration written twice, and the plan refuses it.
91
91
  **A minion's or a worker's own providers are not here.** Those are declared on that surface's own
92
92
  `providers` block and belong to the task that builds it.
93
93
 
94
+ ## Step 4b — Say whether work arrives by email
95
+
96
+ Declare an `inboundChannels` entry with `channel: email` only when the product ACTS on messages people
97
+ send it — a firm whose clients email documents to their matter, a support desk that turns a message
98
+ into a ticket. Its `purpose` says what arrives and what the application does with it; `servesRefs`
99
+ names what asked for it.
100
+
101
+ This declaration is what switches the receiving capability on: the foundation derives `EMAIL_INBOUND`
102
+ from it and records the provider it is owed, so nobody is asked. Do not declare it because the product
103
+ SENDS email — sending is another capability — and never declare a webhook: a signed delivery from
104
+ another system is derived for that delivery, not planned.
105
+
94
106
  ## Step 5 — Make every surface accountable
95
107
 
96
108
  Each worker and minion carries `servesRefs`: the requirement, feature draft, roadmap phase or
@@ -105,8 +117,8 @@ build tasks name them, and a moved ref orphans the task that produced its packag
105
117
  ## What you emit
106
118
 
107
119
  - The **integration plan** at `specifications/src/integration-plan/index.ts` — the workers, the
108
- minions and the provider bindings this application carries, with the rationale for the shape as a
109
- whole.
120
+ minions, the provider bindings and the inbound channels this application carries, with the
121
+ rationale for the shape as a whole.
110
122
 
111
123
  ## Verification
112
124
 
@@ -136,3 +148,5 @@ The rest are the contracts the CODING AGENT opens when it builds each task:
136
148
  what you want is DATA rather than a provider call.
137
149
  - `configure-billing` — the worked five-surface chain for the provider binding most applications
138
150
  need first.
151
+ - `inbound-channels` — what a declared inbound channel becomes: the handler that decides what a
152
+ message causes, the sender assurance it requires, and whether it answers.
@@ -38,16 +38,16 @@
38
38
  ],
39
39
  "stepOutputs": [],
40
40
  "method": {
41
- "guidance": "# Integration Plan — What Runs Beside the Backend\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved and the requirements are written. You decide **what this application\nruns that is not a request** — its workers and its cron minions — and **what it reaches out to** —\nthe providers it binds, and where.\n\nYou do not write any of it. The foundation composes each package, and\n`bottom_up.build-decompose` turns each entry here into a build task bound to the skill that authors\nit.\n\n## Most applications declare nothing here, and that is an answer\n\nThere is no minimum. An application with no worker, no minion and no extra provider binding is the\nordinary case, and a plan that says so — with a rationale saying why — is complete. Inventing a\nworker to fill a collection composes a package nobody maintains.\n\n## Step 1 — Worker or minion? One question settles it\n\nThis is the distinction the whole plan turns on, and planning one as the other produces either a\npackage that never runs or one that runs with nothing to contain it.\n\n| | **worker** | **minion** |\n|---|---|---|\n| what starts it | the backend calls it | the clock |\n| how it is reached | HTTP routes it registers | nothing reaches it |\n| its authority | the caller's | a containment whitelist of its own |\n| plan it when | work cannot finish inside a request | something must happen because time passed |\n\nA nightly sweep is a minion. A slow import the user triggers is a worker. A nightly sweep that the\nbackend also triggers on demand is **both**, and they are two entries.\n\n## The refs carry a prefix, and the schema refuses one that does not\n\nA worker is `worker-<slug>` and a minion is `minion-<slug>`. You supply the SLUG; the runtime stamps\nthe prefix. Keep the slug kebab-case and starting with a LETTER: a ref beginning with a digit parses\nhere and is then refused when the foundation derives the package's identifiers from it.\n\n## Step 2 — Plan each worker\n\n- **`runtime`** — `NODE` unless the work is CPU-bound enough that the choice is the reason the\n worker exists. Rust is a cargo crate: no shared-lib, no pnpm workspace member, a different\n bootstrap. Choose it deliberately or choose Node.\n- **`purpose`** — what the backend delegates, and **why that cannot happen inside a request**. The\n second half is what a reader checks the decision against.\n- **`jobRefs`** — the routes the entry registers, which is what the backend calls. At least one, and\n **not the worker's own name**: `worker-imports` exposing only `imports` says nothing about what is\n delegated, and the plan reports it.\n\n## Step 3 — Plan each minion, and name its containment\n\n- **`purpose`** — what happens because time passed.\n- **`behaviorRefs`** — the named behaviours the tick performs.\n- **`readsResourceRefs` / `writesResourceRefs`** — **the containment decision, and this is why a\n minion is planned rather than left to the coding agent.** A minion's `resourceAccess` whitelist\n starts DENY-ALL, each named resource must separately opt in, and an empty whitelist logs a soft\n warning and **keeps running** — so a minion whose access nobody decided looks healthy and touches\n nothing. Name the decided resources its tick reads and the ones it writes.\n\n**No schedule here.** The plan says what happens because time passed, never how often: a cadence is\nan operational decision, and the minion's own build task sets it beside the whitelist it must widen\nanyway.\n\n## Step 4 — Bind the providers\n\nOne entry per provider per **scope** — the runtime owner whose declaration it lands in:\n\n| scope | the owner | what the binding is |\n|---|---|---|\n| `BACKEND` | the backend service | a package installed in the backend and scoped to it |\n| `COMPANION` | the dev companion | the same act, in the companion's scope |\n| `FRONTEND_APP` | the application frontend | a browser-bound provider module |\n| `WEBSITE` | the marketing site | the same, on the website's frontend service |\n\nThe same provider on two scopes is legitimate and common; the same provider twice on ONE scope is\none declaration written twice, and the plan refuses it.\n\n**A minion's or a worker's own providers are not here.** Those are declared on that surface's own\n`providers` block and belong to the task that builds it.\n\n## Step 5 — Make every surface accountable\n\nEach worker and minion carries `servesRefs`: the requirement, feature draft, roadmap phase or\nsuccess criterion that asked for it. A background process accountable to nothing is one nobody\nasked for, and the plan reports it.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every worker and minion ref that still has a reason to exist —\nbuild tasks name them, and a moved ref orphans the task that produced its package.\n\n## What you emit\n\n- The **integration plan** at `specifications/src/integration-plan/index.ts` — the workers, the\n minions and the provider bindings this application carries, with the rationale for the shape as a\n whole.\n\n## Verification\n\n- Every `readsResourceRefs` / `writesResourceRefs` entry names a resource the domain plan declares.\n- No worker's only `jobRefs` entry repeats its own name.\n- `rg -n \"workerRef|minionRef\" specifications/src/integration-plan/index.ts | wc -l` — the number of\n packages the foundation will compose.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and two reach this step as BODIES\n(`method.skillBodyRefs`): **`worker-authoring`** and **`minion-authoring`**. That is not a\nconvenience — step 1's question is a runtime contract, and step 3's containment chain has three\nparts of which two live outside the minion's own package, so neither is answerable from memory.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `provider-backend-package` — installing and scoping a provider on a backend-side owner, bound to\n the emitted task by `INTEGRATION_PROVIDER_BINDING_SKILL_REF` for the `BACKEND` and `COMPANION`\n scopes.\n- `provider-frontend-file-picker` — the frontend provider-module mechanism, bound for the\n `FRONTEND_APP` and `WEBSITE` scopes.\n- `provider-operation-calls` — how a bound provider's operations are actually called, which is what\n makes a binding worth having.\n- `resource-external-data` — the other way to reach another system: read-through or pipeline, when\n what you want is DATA rather than a provider call.\n- `configure-billing` — the worked five-surface chain for the provider binding most applications\n need first.\n",
41
+ "guidance": "# Integration Plan — What Runs Beside the Backend\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe domain plan is approved and the requirements are written. You decide **what this application\nruns that is not a request** — its workers and its cron minions — and **what it reaches out to** —\nthe providers it binds, and where.\n\nYou do not write any of it. The foundation composes each package, and\n`bottom_up.build-decompose` turns each entry here into a build task bound to the skill that authors\nit.\n\n## Most applications declare nothing here, and that is an answer\n\nThere is no minimum. An application with no worker, no minion and no extra provider binding is the\nordinary case, and a plan that says so — with a rationale saying why — is complete. Inventing a\nworker to fill a collection composes a package nobody maintains.\n\n## Step 1 — Worker or minion? One question settles it\n\nThis is the distinction the whole plan turns on, and planning one as the other produces either a\npackage that never runs or one that runs with nothing to contain it.\n\n| | **worker** | **minion** |\n|---|---|---|\n| what starts it | the backend calls it | the clock |\n| how it is reached | HTTP routes it registers | nothing reaches it |\n| its authority | the caller's | a containment whitelist of its own |\n| plan it when | work cannot finish inside a request | something must happen because time passed |\n\nA nightly sweep is a minion. A slow import the user triggers is a worker. A nightly sweep that the\nbackend also triggers on demand is **both**, and they are two entries.\n\n## The refs carry a prefix, and the schema refuses one that does not\n\nA worker is `worker-<slug>` and a minion is `minion-<slug>`. You supply the SLUG; the runtime stamps\nthe prefix. Keep the slug kebab-case and starting with a LETTER: a ref beginning with a digit parses\nhere and is then refused when the foundation derives the package's identifiers from it.\n\n## Step 2 — Plan each worker\n\n- **`runtime`** — `NODE` unless the work is CPU-bound enough that the choice is the reason the\n worker exists. Rust is a cargo crate: no shared-lib, no pnpm workspace member, a different\n bootstrap. Choose it deliberately or choose Node.\n- **`purpose`** — what the backend delegates, and **why that cannot happen inside a request**. The\n second half is what a reader checks the decision against.\n- **`jobRefs`** — the routes the entry registers, which is what the backend calls. At least one, and\n **not the worker's own name**: `worker-imports` exposing only `imports` says nothing about what is\n delegated, and the plan reports it.\n\n## Step 3 — Plan each minion, and name its containment\n\n- **`purpose`** — what happens because time passed.\n- **`behaviorRefs`** — the named behaviours the tick performs.\n- **`readsResourceRefs` / `writesResourceRefs`** — **the containment decision, and this is why a\n minion is planned rather than left to the coding agent.** A minion's `resourceAccess` whitelist\n starts DENY-ALL, each named resource must separately opt in, and an empty whitelist logs a soft\n warning and **keeps running** — so a minion whose access nobody decided looks healthy and touches\n nothing. Name the decided resources its tick reads and the ones it writes.\n\n**No schedule here.** The plan says what happens because time passed, never how often: a cadence is\nan operational decision, and the minion's own build task sets it beside the whitelist it must widen\nanyway.\n\n## Step 4 — Bind the providers\n\nOne entry per provider per **scope** — the runtime owner whose declaration it lands in:\n\n| scope | the owner | what the binding is |\n|---|---|---|\n| `BACKEND` | the backend service | a package installed in the backend and scoped to it |\n| `COMPANION` | the dev companion | the same act, in the companion's scope |\n| `FRONTEND_APP` | the application frontend | a browser-bound provider module |\n| `WEBSITE` | the marketing site | the same, on the website's frontend service |\n\nThe same provider on two scopes is legitimate and common; the same provider twice on ONE scope is\none declaration written twice, and the plan refuses it.\n\n**A minion's or a worker's own providers are not here.** Those are declared on that surface's own\n`providers` block and belong to the task that builds it.\n\n## Step 4b — Say whether work arrives by email\n\nDeclare an `inboundChannels` entry with `channel: email` only when the product ACTS on messages people\nsend it — a firm whose clients email documents to their matter, a support desk that turns a message\ninto a ticket. Its `purpose` says what arrives and what the application does with it; `servesRefs`\nnames what asked for it.\n\nThis declaration is what switches the receiving capability on: the foundation derives `EMAIL_INBOUND`\nfrom it and records the provider it is owed, so nobody is asked. Do not declare it because the product\nSENDS email — sending is another capability — and never declare a webhook: a signed delivery from\nanother system is derived for that delivery, not planned.\n\n## Step 5 — Make every surface accountable\n\nEach worker and minion carries `servesRefs`: the requirement, feature draft, roadmap phase or\nsuccess criterion that asked for it. A background process accountable to nothing is one nobody\nasked for, and the plan reports it.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every worker and minion ref that still has a reason to exist —\nbuild tasks name them, and a moved ref orphans the task that produced its package.\n\n## What you emit\n\n- The **integration plan** at `specifications/src/integration-plan/index.ts` — the workers, the\n minions, the provider bindings and the inbound channels this application carries, with the\n rationale for the shape as a whole.\n\n## Verification\n\n- Every `readsResourceRefs` / `writesResourceRefs` entry names a resource the domain plan declares.\n- No worker's only `jobRefs` entry repeats its own name.\n- `rg -n \"workerRef|minionRef\" specifications/src/integration-plan/index.ts | wc -l` — the number of\n packages the foundation will compose.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem, so a path here would be an instruction answered from\nrecollection (#1435). Each skill is named by its REF, and two reach this step as BODIES\n(`method.skillBodyRefs`): **`worker-authoring`** and **`minion-authoring`**. That is not a\nconvenience — step 1's question is a runtime contract, and step 3's containment chain has three\nparts of which two live outside the minion's own package, so neither is answerable from memory.\n\nThe rest are the contracts the CODING AGENT opens when it builds each task:\n\n- `provider-backend-package` — installing and scoping a provider on a backend-side owner, bound to\n the emitted task by `INTEGRATION_PROVIDER_BINDING_SKILL_REF` for the `BACKEND` and `COMPANION`\n scopes.\n- `provider-frontend-file-picker` — the frontend provider-module mechanism, bound for the\n `FRONTEND_APP` and `WEBSITE` scopes.\n- `provider-operation-calls` — how a bound provider's operations are actually called, which is what\n makes a binding worth having.\n- `resource-external-data` — the other way to reach another system: read-through or pipeline, when\n what you want is DATA rather than a provider call.\n- `configure-billing` — the worked five-surface chain for the provider binding most applications\n need first.\n- `inbound-channels` — what a declared inbound channel becomes: the handler that decides what a\n message causes, the sender assurance it requires, and whether it answers.\n",
42
42
  "skillRefs": [
43
- "journey-status",
44
43
  "worker-authoring",
45
44
  "minion-authoring",
46
45
  "provider-backend-package",
47
46
  "provider-frontend-file-picker",
48
47
  "provider-operation-calls",
49
48
  "resource-external-data",
50
- "configure-billing"
49
+ "configure-billing",
50
+ "inbound-channels"
51
51
  ],
52
52
  "skillBodyRefs": [
53
53
  "worker-authoring",
@@ -51,9 +51,7 @@
51
51
  "stepOutputs": [],
52
52
  "method": {
53
53
  "guidance": "# Maturity Reading — Where This Application Stands\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nThe build lane ends on four typechecks and a migration-drift probe, and its own method says it \"does\nnot boot the application, run its test suite\". Nothing related what was BUILT to what the\napplication's requirements ASKED FOR.\n\nThis step records that relation as the `application-maturity` family: **one row per requirement the\napplication declares**, the evidence that exists for it, and the stage that follows.\n\n## There is no \"done\", and that is the design\n\nThe highest stage does not mean finished. It means that today, every requirement has the strongest\nevidence this framework can produce for it — and the next requirement somebody writes lowers the\nreading again, with no code change anywhere. That is what the measurement is FOR.\n\nSo nothing in the lane may gate on this family, and no other step may read a stage as permission.\n\n## It is derived, never judged\n\nNothing here is an opinion, and no model produces it. Each row's level is reached by a measurement:\n\n| level | reached when | measured from |\n|---|---|---|\n| `UNADDRESSED` | nothing the application decided points at the requirement | the decided-element graph |\n| `DECIDED` | a decided element links to it — a feature draft, an experience surface, a worker, a build task | inbound links on the same graph |\n| `BUILT` | a build task addressing it has LANDED | the landing probe, over committed bytes |\n| `VERIFIED` | that landed task's declared product was PROVEN | the same probe, minus what it could not verify |\n| `OBSERVED` | something watched the running application do it | runtime observations |\n\nThe ladder is ordered, and the stage is the highest one whose threshold the population meets. The\ndefault threshold is **every requirement at that level** — one number, and not a guess: a share\nbelow 1 would be an invented tolerance, and this family measures rather than flatters.\n\n## The denominator is the requirements family, and nothing else\n\nEvery row comes from `requirements`, functional and non-functional, in its own order. Not the\nrequirements that happen to be referenced somewhere, not a count of build tasks, not a share of\nfiles. A requirement nothing addresses is a ROW at `UNADDRESSED` — visible, counted, and lowering\nthe reading.\n\nThat is the difference between a measurement and a file count: a denominator you choose yourself is\nnot a measurement at all.\n\n## A family that addresses requirements joins on its own\n\n\"Which elements address this requirement\" is read from the decided-element graph's inbound links, so\nevery family that declares an edge to `requirements.functional` or `requirements.non-functional`\nalready contributes — and one that declares such an edge tomorrow contributes without this method,\nor the derivation, knowing it exists.\n\n## What the reading says that a number cannot\n\nThree findings, and each names the application rather than the artifact:\n\n- a requirement **nothing addresses** — the reading's whole point;\n- a requirement whose build work **landed and could not be proven**, so its evidence stops at\n `BUILT`. A task that declares no product cannot be probed, and that is a known, deliberate state\n rather than a failure;\n- **no runtime observation exists at all**, which today is true of every application. The finding\n names what would fill it — an engine-behaviour e2e scenario that names the requirement it\n exercises — rather than leaving the top of the ladder quietly empty.\n\n## What you emit\n\n- The **maturity reading** at `specifications/src/application-maturity/index.ts`. It is landed by\n the runner, not written by hand.\n\n## Verification\n\n- The row count equals the number of requirements the application declares.\n- Every `requirementRef` names a requirement in the `requirements` family.\n- `rg -c \"UNADDRESSED\" specifications/src/application-maturity/index.ts` — how many requirements\n nothing has picked up yet.\n",
54
- "skillRefs": [
55
- "journey-status"
56
- ],
54
+ "skillRefs": [],
57
55
  "skillBodyRefs": [],
58
56
  "contextSources": [],
59
57
  "draftableDocumentDefinitionRefs": [],
@@ -32,8 +32,7 @@
32
32
  "skillRefs": [
33
33
  "settings-placement-authoring",
34
34
  "config-app-shell",
35
- "config-navigation",
36
- "journey-status"
35
+ "config-navigation"
37
36
  ],
38
37
  "skillBodyRefs": [],
39
38
  "contextSources": [
@@ -26,13 +26,14 @@ same capability composition you read here.
26
26
 
27
27
  ## Step 1 — Read the capability composition FIRST
28
28
 
29
- Find the `add-website` decision.
30
-
31
- - **Declined** (or owned by nothing, or absent from the record): land a plan with
32
- `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. That
33
- is a complete answer. Do not plan a site the application will never compose — the pages would
34
- become tasks with nowhere to write.
35
- - **Needed**: `disposition: PLANNED`, and continue.
29
+ Find the `add-website` decision. This playbook runs only once the composition decides it is
30
+ **NEEDED**: its eligibility is gated on that decision, so a declined website is never planned, and a
31
+ plan landed while it was needed is set aside for every reader if the composition later declines it.
32
+
33
+ - **Needed** (the normal case): `disposition: PLANNED`, and continue.
34
+ - **Declined** in the record you are given (it changed after you were started): land a plan with
35
+ `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not
36
+ plan a site the application will never compose — the pages would become tasks with nowhere to write.
36
37
 
37
38
  ## Step 2 — Decide the pages, from what the product actually declares
38
39
 
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "bottom_up.website-plan",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "bottom_up",
5
- "intent": "Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has, what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Reads the capability composition FIRST: an application whose composition declined a website lands a NOT_APPLICABLE plan stating why, which is a complete answer rather than an empty artifact. A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.",
5
+ "intent": "Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has, what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Runs only once the capability composition decides the website is NEEDED (a declined website is never planned, and a plan landed before a later decline is set aside). A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -10,6 +10,14 @@
10
10
  "family": "capability-composition"
11
11
  }
12
12
  },
13
+ {
14
+ "kind": "artifact_decides",
15
+ "selector": {
16
+ "family": "capability-composition"
17
+ },
18
+ "decision": "add-website",
19
+ "equals": "NEEDED"
20
+ },
13
21
  {
14
22
  "kind": "artifact_exists",
15
23
  "selector": {
@@ -47,9 +55,8 @@
47
55
  ],
48
56
  "stepOutputs": [],
49
57
  "method": {
50
- "guidance": "# Website Plan — What the Marketing Site Says\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision.\n\n- **Declined** (or owned by nothing, or absent from the record): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. That\n is a complete answer. Do not plan a site the application will never compose — the pages would\n become tasks with nowhere to write.\n- **Needed**: `disposition: PLANNED`, and continue.\n\n## Step 2 — Decide the pages, from what the product actually declares\n\nA page exists because something the application declared needs a place to be said. Derive first,\nand invent nothing:\n\n| page | exists when |\n|---|---|\n| the landing page | always — it is the origin every canonical URL derives from |\n| a pricing page | the business model declares pricing plans |\n| a features page | the market snapshot carries benefits worth arguing one at a time |\n| a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered\n sections.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Every page opens on a `HERO`, and exactly one page reads as the landing page.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
58
+ "guidance": "# Website Plan — What the Marketing Site Says\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision. This playbook runs only once the composition decides it is\n**NEEDED**: its eligibility is gated on that decision, so a declined website is never planned, and a\nplan landed while it was needed is set aside for every reader if the composition later declines it.\n\n- **Needed** (the normal case): `disposition: PLANNED`, and continue.\n- **Declined** in the record you are given (it changed after you were started): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not\n plan a site the application will never compose — the pages would become tasks with nowhere to write.\n\n## Step 2 — Decide the pages, from what the product actually declares\n\nA page exists because something the application declared needs a place to be said. Derive first,\nand invent nothing:\n\n| page | exists when |\n|---|---|\n| the landing page | always — it is the origin every canonical URL derives from |\n| a pricing page | the business model declares pricing plans |\n| a features page | the market snapshot carries benefits worth arguing one at a time |\n| a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered\n sections.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Every page opens on a `HERO`, and exactly one page reads as the landing page.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
51
59
  "skillRefs": [
52
- "journey-status",
53
60
  "website-page-authoring",
54
61
  "website-navigation-authoring",
55
62
  "website-seo-aeo-geo",