@wildo-ai/framework-knowledge 1.1.3 → 1.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (841) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +349 -17
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  6. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.loader.js +47 -1
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
  13. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  14. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
  15. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  25. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  26. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
  27. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  28. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  29. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  30. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
  31. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  32. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
  33. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  34. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
  35. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  36. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  41. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  44. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
  45. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
  47. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
  49. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  50. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
  51. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  52. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  53. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  54. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
  55. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  56. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  57. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
  60. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  61. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  63. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
  64. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  65. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  68. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  69. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  70. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  71. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  72. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  74. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
  76. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
  78. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  80. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  81. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  82. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
  84. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
  86. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  87. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
  88. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  89. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
  90. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  92. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
  94. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  95. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
  96. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  99. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
  100. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  101. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  103. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
  104. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  105. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
  112. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  113. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
  114. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
  116. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  117. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
  118. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  120. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  121. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  122. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  123. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  124. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  125. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
  126. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  127. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  128. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  129. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
  130. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  131. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  132. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  133. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
  134. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  135. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  136. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  137. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
  138. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  139. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
  140. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  141. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
  142. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  143. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
  144. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
  146. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  147. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  148. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  149. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  150. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  151. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
  152. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  153. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
  154. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
  156. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  157. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
  158. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  159. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
  160. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  161. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
  162. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  163. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  164. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  165. package/dist/knowledge/manifest.json +9 -8
  166. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  167. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  168. package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
  169. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
  170. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  171. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  172. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
  173. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
  174. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  175. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  176. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
  177. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
  178. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
  179. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
  180. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
  181. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
  182. package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
  183. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
  184. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
  185. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
  186. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
  187. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
  188. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
  189. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
  190. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
  191. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
  192. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
  193. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  194. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  195. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
  196. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  197. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
  198. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
  199. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
  200. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  201. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
  202. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  203. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
  204. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  205. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  206. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
  207. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  208. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  209. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  210. package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
  211. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
  212. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  213. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  214. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
  215. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  216. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  217. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  218. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
  219. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
  220. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
  221. package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
  222. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
  223. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  224. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
  225. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  226. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  227. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
  228. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
  229. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  230. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
  231. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  232. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  233. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
  234. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
  235. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  236. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
  237. package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
  238. package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
  239. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  240. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
  241. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  242. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
  243. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  244. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
  245. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  246. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
  247. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  248. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  249. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
  250. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
  251. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  252. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  253. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  254. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
  255. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
  256. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
  257. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  258. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  259. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  260. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
  261. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
  262. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
  263. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  264. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  265. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
  266. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
  267. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  268. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
  269. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  270. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  271. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  272. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  273. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  274. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  275. package/dist/knowledge/references/application-maturity.config.md +319 -0
  276. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  277. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  278. package/dist/knowledge/references/brand.asset.config.md +8 -16
  279. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  280. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  281. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  282. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  283. package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
  284. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  285. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  286. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  287. package/dist/knowledge/references/capability-composition.config.md +155 -0
  288. package/dist/knowledge/references/cli.market.utils.md +1 -0
  289. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  290. package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
  291. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  292. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  293. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  294. package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
  295. package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
  296. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
  297. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  298. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  299. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  300. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  301. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
  302. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
  303. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  304. package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
  305. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  306. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  307. package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
  308. package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
  309. package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
  310. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
  311. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
  312. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  313. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
  314. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
  315. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
  316. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
  317. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  318. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  319. package/dist/knowledge/references/experience-plan.config.md +311 -0
  320. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
  321. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  322. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
  323. package/dist/knowledge/references/integration-plan.config.md +185 -0
  324. package/dist/knowledge/references/market.alternative.config.md +1 -1
  325. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  326. package/dist/knowledge/references/market.channel.config.md +3 -3
  327. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  328. package/dist/knowledge/references/market.gain.config.md +1 -1
  329. package/dist/knowledge/references/market.icp.config.md +2 -2
  330. package/dist/knowledge/references/market.job.config.md +1 -1
  331. package/dist/knowledge/references/market.message-template.config.md +2 -2
  332. package/dist/knowledge/references/market.objection.config.md +1 -1
  333. package/dist/knowledge/references/market.pain.config.md +1 -1
  334. package/dist/knowledge/references/market.persona.config.md +2 -2
  335. package/dist/knowledge/references/market.proof.config.md +1 -1
  336. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  337. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  338. package/dist/knowledge/references/market.trigger.config.md +1 -1
  339. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  340. package/dist/knowledge/references/placement-plan.config.md +369 -0
  341. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  342. package/dist/knowledge/references/platform.config.backing-services.md +0 -21
  343. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  344. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  345. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  346. package/dist/knowledge/references/platform.config.saas.md +261 -9
  347. package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
  348. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  349. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  350. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  351. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  352. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  353. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  354. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  355. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  356. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
  357. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  358. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  359. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
  360. package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
  361. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  362. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
  363. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  364. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
  365. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  366. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  367. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
  368. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  369. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  370. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  371. package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
  372. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  373. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  374. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  375. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  376. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  377. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  378. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  379. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
  380. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  381. package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
  382. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  383. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  384. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  385. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  386. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  387. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  388. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  389. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  390. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  391. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  392. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  393. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  394. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
  395. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  396. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  397. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
  398. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
  399. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
  400. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  401. package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
  402. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  403. package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
  404. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  405. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
  406. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
  407. package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
  408. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  409. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
  410. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  411. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  412. package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
  413. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
  414. package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
  415. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  416. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  417. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  418. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  419. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  420. package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
  421. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  422. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  423. package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
  424. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  425. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  426. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
  427. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
  428. package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
  429. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
  430. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  431. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  432. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
  433. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  434. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  435. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  436. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  437. package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
  438. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
  439. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  440. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  441. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
  442. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  443. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  444. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  445. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
  446. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  447. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  448. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  449. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  450. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  451. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  452. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  453. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  454. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  455. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  456. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  457. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  458. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  459. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  460. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
  461. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
  462. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  463. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  464. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  465. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  466. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  467. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  468. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  469. package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
  470. package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
  471. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  472. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  473. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  474. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  475. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  476. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  477. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  478. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
  479. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
  480. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
  481. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  482. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
  483. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  484. package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
  485. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
  486. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  487. package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
  488. package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
  489. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  490. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
  491. package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
  492. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  493. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  494. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  495. package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
  496. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  497. package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
  498. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  499. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  500. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  501. package/dist/knowledge/references/website-plan.config.md +205 -0
  502. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  503. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  504. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  505. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
  506. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
  507. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
  508. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  509. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  510. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  511. package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
  512. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
  513. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
  514. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  515. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  516. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  517. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  518. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
  519. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
  520. package/dist/knowledge/references/zod.factories.address.md +118 -0
  521. package/dist/knowledge/references/zod.factories.code.md +2 -0
  522. package/dist/knowledge/references/zod.factories.duration.md +2 -0
  523. package/dist/knowledge/references/zod.factories.money.md +2 -0
  524. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  525. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  526. package/dist/knowledge/registries/framework-topics.json +1215 -11
  527. package/dist/knowledge/registries/playbooks.json +454 -50
  528. package/dist/knowledge/registries/source-tags.json +3153 -1043
  529. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  530. package/dist/knowledge/rules/live-context-door.md +108 -0
  531. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  532. package/dist/knowledge/skills/INDEX.md +46 -11
  533. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
  534. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  535. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  536. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
  537. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  538. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  539. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
  540. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
  541. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
  542. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
  543. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  544. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
  545. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  546. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  547. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  548. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
  549. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
  550. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  551. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  552. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
  553. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  554. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
  555. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  556. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  557. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  558. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
  559. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
  560. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
  561. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
  562. package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
  563. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
  564. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  565. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  566. package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
  567. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  568. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  569. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  570. package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
  571. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  572. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
  573. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  574. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  575. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
  576. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
  577. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  578. package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
  579. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
  580. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
  581. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  582. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
  583. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
  584. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  585. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
  586. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
  587. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  588. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  589. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  590. package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
  591. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  592. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  593. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  594. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  595. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
  596. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  597. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
  598. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  599. package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
  600. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
  601. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
  602. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
  603. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  604. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
  605. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  606. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
  607. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
  608. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
  609. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
  610. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  611. package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
  612. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  613. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
  614. package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
  615. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
  616. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  617. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  618. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  619. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  620. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
  621. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  622. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  623. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
  624. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
  625. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
  626. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
  627. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
  628. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
  629. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  630. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  631. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
  632. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  633. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
  634. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
  635. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  636. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  637. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  638. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  639. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
  640. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
  641. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
  642. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
  643. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
  644. package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
  645. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  646. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
  647. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  648. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  649. package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
  650. package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
  651. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
  652. package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
  653. package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
  654. package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
  655. package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
  656. package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
  657. package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
  658. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
  659. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  660. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  661. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
  662. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
  663. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  664. package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
  665. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  666. package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
  667. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
  668. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
  669. package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
  670. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
  671. package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
  672. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
  673. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
  674. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
  675. package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
  676. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
  677. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
  678. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  679. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
  680. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
  681. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
  682. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  683. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  684. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  685. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  686. package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
  687. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  688. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  689. package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
  690. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
  691. package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
  692. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
  693. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
  694. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  695. package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
  696. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  697. package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
  698. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  699. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  700. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  701. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
  702. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  703. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
  704. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
  705. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  706. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
  707. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
  708. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
  709. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
  710. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
  711. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  712. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  713. package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
  714. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
  715. package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
  716. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
  717. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  718. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  719. package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
  720. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
  721. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
  722. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
  723. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
  724. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
  725. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  726. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  727. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  728. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
  729. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  730. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
  731. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  732. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
  733. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  734. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
  735. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
  736. package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
  737. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
  738. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  739. package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
  740. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
  741. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
  742. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
  743. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
  744. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  745. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  746. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  747. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
  748. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
  749. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  750. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  751. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
  752. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  753. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  754. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
  755. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
  756. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  757. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  758. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
  759. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
  760. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  761. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
  762. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  763. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  764. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  765. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  766. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
  767. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
  768. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
  769. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
  770. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
  771. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  772. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
  773. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
  774. package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
  775. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  776. package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
  777. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  778. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  779. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  780. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
  781. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
  782. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  783. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
  784. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
  785. package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
  786. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  787. package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
  788. package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
  789. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  790. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
  791. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
  792. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
  793. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  794. package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
  795. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  796. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
  797. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
  798. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  799. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
  800. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  801. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  802. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
  803. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
  804. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
  805. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
  806. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
  807. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
  808. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
  809. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
  810. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
  811. package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
  812. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  813. package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
  814. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
  815. package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
  816. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
  817. package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
  818. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
  819. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
  820. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
  821. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
  822. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
  823. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
  824. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
  825. package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
  826. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
  827. package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
  828. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
  829. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
  830. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
  831. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
  832. package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
  833. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  834. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  835. package/dist/knowledge/topic-index.json +5335 -1010
  836. package/dist/tsconfig.build.tsbuildinfo +1 -1
  837. package/dist/tsconfig.tsbuildinfo +1 -1
  838. package/package.json +4 -4
  839. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  840. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  841. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -3,14 +3,7 @@
3
3
  "version": "0.2.0",
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
- "functionalTopics": [
7
- "model_domain_graph"
8
- ],
9
6
  "preconditions": [
10
- {
11
- "kind": "phase_is",
12
- "phase": "bottom_up"
13
- },
14
7
  {
15
8
  "kind": "artifact_exists",
16
9
  "selector": {
@@ -30,7 +23,7 @@
30
23
  },
31
24
  {
32
25
  "family": "market-snapshot",
33
- "intent": "audience"
26
+ "intent": "value"
34
27
  },
35
28
  {
36
29
  "family": "feature-drafts"
@@ -40,24 +33,28 @@
40
33
  },
41
34
  {
42
35
  "family": "vision-brief"
36
+ },
37
+ {
38
+ "family": "domain-plan"
43
39
  }
44
40
  ],
45
41
  "outputs": [
46
42
  {
47
43
  "family": "domain-plan",
48
44
  "schemaRef": "saas-specifications:DomainPlanOutputSet",
49
- "placement": "specifications/src/domain-plan/",
50
- "description": "THE atomic domain plan: the module decomposition AND the inter-resource relationship drafts, one value, one landed file. (The former separate relationship-drafts family was collapsed into this output 2026-08-24 — the two were never independently meaningful, and the deterministic validator crosses them.) A working edit until a human commits it."
45
+ "description": "THE atomic domain plan: the module decomposition AND the inter-resource relationship drafts, one value, one landed file. (The former separate relationship-drafts family was collapsed into this output 2026-08-24 — the two were never independently meaningful, and the deterministic validator crosses them.) A working edit until it is committed."
51
46
  }
52
47
  ],
48
+ "stepOutputs": [],
53
49
  "method": {
54
- "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// TODO CLI COMMAND: wildo context journey-status\n// (read current journey scope + approved artifacts + any existing domain plan)\n// TODO CLI COMMAND: wildo context requirements\n// (read the functional / non-functional requirements to decompose)\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\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm the approved top-down set is in place to plan the domain from.\n- `.claude/skills/resource-add-module/SKILL.md` — the module-scaffolding vocabulary\n (what a module is across the project layout); keeps module boundaries idiomatic.\n- `.claude/skills/resource-add-resource/SKILL.md` — the resource vocabulary (what a\n resource is); keeps the per-module inventory idiomatic.\n- `.claude/skills/module-relationships/SKILL.md` — 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 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",
55
51
  "skillRefs": [
56
52
  "journey-status",
57
53
  "resource-add-module",
58
54
  "resource-add-resource",
59
55
  "module-relationships"
60
56
  ],
57
+ "skillBodyRefs": [],
61
58
  "elicitation": {
62
59
  "questions": [
63
60
  {
@@ -70,10 +67,14 @@
70
67
  ]
71
68
  }
72
69
  ]
73
- }
70
+ },
71
+ "contextSources": [],
72
+ "draftableDocumentDefinitionRefs": [],
73
+ "suspendsForClarification": true,
74
+ "briefAdequacyGate": false,
75
+ "briefAdequacyExcludedSources": []
74
76
  },
75
77
  "executor": "companion_agent",
76
- "qualityGates": [],
77
78
  "approval": "approve_result",
78
79
  "budget": {
79
80
  "maxRuns": 3
@@ -0,0 +1,165 @@
1
+ # Experience Plan — What This Application's Experience Is
2
+
3
+ ### Target Application Framing
4
+
5
+ This knowledge is for configuring behavior in the target application.
6
+ Wildo is the framework surface being used, not the product being built.
7
+
8
+ Read and apply these patterns from the application-developer point of view:
9
+
10
+ - how the application should configure the relevant app-level file
11
+ - how the application should use framework-provided factories, enums, and helpers
12
+ - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
+
14
+
15
+ ## Where you are in the journey
16
+
17
+ The domain plan is approved: the modules, resources and relationships exist as decisions, and the
18
+ framework generates a list and a read screen for every resource without being asked. You decide
19
+ **what this application carries beyond that** — the surfaces a person actually works on — **how
20
+ its shell, navigation and palette are composed**, and **the journey a new person takes**: the
21
+ moments the application recognises, and the guidance that gets them there.
22
+
23
+ You do not write any of it. `bottom_up.build-decompose` turns each entry here into a build task
24
+ bound to the skill that authors it.
25
+
26
+ ## This is not the placement plan
27
+
28
+ Placement decides WHERE a decided subject sits — which settings category, which sidebar section.
29
+ This decides WHICH SURFACES EXIST. Run in that order: a placement of a view nobody proposed places
30
+ nothing, and the placement plan is an input here so a proposed surface does not duplicate something
31
+ the shell already reaches.
32
+
33
+ ## Step 1 — Compose the configuration surfaces
34
+
35
+ **At least one, and in practice always the shell.** An application whose navigation and app shell
36
+ are left at the scaffold's defaults has no route to its own modules: the generated screens exist and
37
+ nothing reaches them. That is the one thing this plan refuses.
38
+
39
+ | surface | what you decide | skill |
40
+ |---|---|---|
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` |
44
+ | `GLOBAL_VIEWS` | which app-level views are registered as launcher entries | `views-app-level` |
45
+
46
+ Each names the things the file gains (`declarationRefs`) — a sidebar section ref, a zone, a token.
47
+ Never the file: `wildo init` writes all four, so a decision that names nothing was true before any
48
+ task ran.
49
+
50
+ ## Step 2 — Decide the surfaces
51
+
52
+ A surface exists because a person has to do something the generated list and read cannot do. Six
53
+ kinds, each naming the skill that authors it:
54
+
55
+ | kind | what it is | belongs to |
56
+ |---|---|---|
57
+ | `RESOURCE_COMPOSITE_VIEW` | a workspace composing several resources around one | a resource |
58
+ | `RESOURCE_CUSTOM_VIEW` | a bespoke screen for one operation — a wizard, a rich read | a resource |
59
+ | `RESOURCE_EXECUTION_VIEW` | drives a long-running execution and shows its progress | a resource |
60
+ | `RESOURCE_CHART_VIEW` | a chart over one resource's rows | a resource |
61
+ | `APPLICATION_VIEW` | an application-level view or dashboard — the home a person opens on | a module |
62
+ | `CUSTOM_COMPONENT` | a component several surfaces reuse | a module |
63
+
64
+ The first four are declared in ONE resource's ui-behavior, so each names its resource; the last two
65
+ belong to their module and must not. The plan refuses both mistakes, in both directions.
66
+
67
+ **Plan an application view.** An application with none opens on whatever the shell defaults to,
68
+ which is nobody's decision.
69
+
70
+ ## Step 3 — Name the preset components each surface reuses
71
+
72
+ This is the field this plan exists for. The framework ships a component catalogue, and a coding
73
+ agent that has not been told which components to reuse builds the surface out of raw elements —
74
+ bypassing the theme, the surface policy and the accessibility behaviour every preset carries. Read
75
+ the catalogue (`frontend-component-catalog`) and name the components each surface is composed from.
76
+
77
+ A `CUSTOM_COMPONENT` reuses nothing by definition: it IS the reusable thing.
78
+
79
+ ## Step 4 — Make every surface accountable
80
+
81
+ Each carries `servesRefs`: the requirement, feature draft, roadmap phase or success criterion that
82
+ asked for it. A surface accountable to nothing is one nobody asked for, and the plan reports it.
83
+
84
+ ## Step 5 — Plan the journey
85
+
86
+ A new person arrives at an application they have never used. Decide what recognises their progress
87
+ and what tells them what to do first. **Plan at least one of the two** — a plan with neither is
88
+ reported, because a new person then meets a product that neither welcomes nor guides them. An
89
+ internal tool may rightly have neither; say so by leaving both empty on purpose.
90
+
91
+ **Milestones** — the moments worth recognising: a person's first record of the thing the product is
92
+ for, a count that shows it is working for them, a moment a whole organization reaches together. Each
93
+ names its identifier as a slug (`first-deal-won`, declared `FIRST_DEAL_WON` in code), its module,
94
+ the resource whose operation earns it, and the moment in the person's own terms. How loudly each one
95
+ celebrates is decided when it is built, not here.
96
+
97
+ **Guidance** — two shapes, and choosing between them is the decision:
98
+
99
+ | kind | what it is | use it when |
100
+ |---|---|---|
101
+ | `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 |
102
+ | `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 |
103
+
104
+ Five rules decide whether planned guidance will ever be seen — plan against them:
105
+
106
+ - **Only one triggered overlay shows at a time.** The others wait behind it until it is finished,
107
+ skipped or dismissed, and a waiting one is dropped if the page reloads first — so a second flow
108
+ planned on the same moment is often never seen. Give each flow its own moment.
109
+ - **A flow shows once per person.** Guidance that should appear every time — an empty-list message —
110
+ is not a flow; it belongs to the resource's own screen.
111
+ - **A gate is a milestone the person already holds.** `gatedByMilestoneRefs` must name milestones
112
+ earned BEFORE the flow's moment, never the one that same moment earns.
113
+ - **Keep refs stable.** A guidance ref keys every person's saved progress; renaming it forgets it.
114
+ - **A document names its host.** An `ONBOARDING_DOCUMENT` is seen only where a view embeds it, so it
115
+ names that view in `hostViewRef` — a view you plan above, or one the application already has, and
116
+ in either case a view of the document's OWN module: a document is declared by the module whose view
117
+ shows it, and its build task writes only there. A flow names none: its trigger shows it.
118
+
119
+ Both carry `servesRefs`, like every surface.
120
+
121
+ ## Refine, don't re-author
122
+
123
+ Your own prior plan is an input. Keep every view ref that still has a reason to exist — build tasks
124
+ name them, and a moved ref orphans the task that produced its surface. The same holds for milestone
125
+ identifiers and guidance refs, with one more reason: people's progress is stored against them.
126
+
127
+ ## What you emit
128
+
129
+ - The **experience plan** at `specifications/src/experience-plan/index.ts` — the configuration
130
+ surfaces this application composes, the views it carries — each with its kind, its home, what a
131
+ person does on it, the presets it reuses and what it serves — and its journey: the milestones it
132
+ recognises and the guidance toward them.
133
+
134
+ ## Verification
135
+
136
+ - Every `moduleRef` and `resourceRef` names something the domain plan declares.
137
+ - Every `reusesComponentRefs` entry names a component the catalogue carries.
138
+ - `rg -n "kind: ExperienceViewKind" specifications/src/experience-plan/index.ts | wc -l` — the number
139
+ of view tasks the build lane will emit.
140
+ - Every `triggerResourceRef` names a resource the domain plan declares, and no two guidance flows are
141
+ planned on the same moment.
142
+ - Every `gatedByMilestoneRefs` entry names a planned milestone or one the application already declares.
143
+
144
+ ## References — named by REF, because this step cannot open a file
145
+
146
+ A structured generation has no filesystem, so a path here would be an instruction answered from
147
+ recollection (#1435). Each skill is named by its REF, and one reaches this step as a BODY
148
+ (`method.skillBodyRefs`): **`frontend-component-catalog`**. That is not a convenience — naming the
149
+ presets each surface reuses is this plan's whole point, and a model without the catalogue in front
150
+ of it invents component names that resolve to nothing.
151
+
152
+ The rest are the contracts the CODING AGENT opens when it builds each task:
153
+
154
+ - `views-composite-authoring` — what a composite view IS, so a planned one is one the build lane can author.
155
+ - `resource-custom-view` — a custom view's shape and its binding.
156
+ - `spec-composite-view-update` — the specification a composite view owes.
157
+ - `views-add-composite-view`, `views-add-custom-view`, `views-execution-authoring`,
158
+ `views-chart-authoring`, `views-app-level`, `engine-component-registration` — one per view KIND,
159
+ bound to the emitted task by `EXPERIENCE_VIEW_SKILL_REF`.
160
+ - `config-app-shell`, `config-navigation`, `config-design-system` — one per configuration SURFACE,
161
+ bound by `EXPERIENCE_CONFIGURATION_SKILL_REF`.
162
+ - `milestones-and-celebrations` — how a planned milestone is declared and celebrated, bound by
163
+ `EXPERIENCE_MILESTONE_SKILL_REF`.
164
+ - `guidance-onboarding-authoring` — how a planned document or flow is authored, bound by
165
+ `EXPERIENCE_GUIDANCE_SKILL_REF`.
@@ -0,0 +1,74 @@
1
+ {
2
+ "ref": "bottom_up.experience-plan",
3
+ "version": "0.2.0",
4
+ "phase": "bottom_up",
5
+ "intent": "User-experience composition — decide WHAT THIS APPLICATION'S EXPERIENCE IS beyond the screens the framework generates for each resource: which composite, custom, execution and chart views it carries and on which resource, which application-level views and dashboards it opens on, which custom components several views reuse, how its navigation, app shell, design system and global views are composed, and the JOURNEY a new person takes — the milestones it recognises and the onboarding documents and guidance flows that get a person there. Reads the domain plan (the modules, resources and relationships that exist), the requirements and feature drafts (what somebody asked for), the placement plan (where decided subjects already sit) and the brand (the visual tone the design system applies). Every view names the PRESET COMPONENTS it reuses, from the framework's own catalogue, because a coding agent with no catalogue in front of it builds custom surfaces out of raw elements and bypasses the theme, the surface policy and the accessibility behaviour every preset carries. Produces the plan; the decomposer turns it into build tasks, each bound to the skill the view's kind, the configuration's surface, the milestone or the guidance kind names.",
6
+ "preconditions": [
7
+ {
8
+ "kind": "artifact_exists",
9
+ "selector": {
10
+ "family": "domain-plan"
11
+ }
12
+ }
13
+ ],
14
+ "inputs": [
15
+ {
16
+ "family": "domain-plan"
17
+ },
18
+ {
19
+ "family": "requirements"
20
+ },
21
+ {
22
+ "family": "feature-drafts"
23
+ },
24
+ {
25
+ "family": "placement-plan",
26
+ "render": "map"
27
+ },
28
+ {
29
+ "family": "brand-brief"
30
+ },
31
+ {
32
+ "family": "experience-plan"
33
+ }
34
+ ],
35
+ "outputs": [
36
+ {
37
+ "family": "experience-plan",
38
+ "schemaRef": "saas-specifications:ExperiencePlan",
39
+ "description": "The application's experience: the views it carries beyond the generated screens — each with its kind (which names the skill that authors it), the module and resource it belongs to, what a person does on it, the preset components it reuses and what it is accountable to — the application-wide configuration surfaces it composes, each naming what that file gains and why, and its journey: the milestones it recognises (identifier, module, the resource that earns each, the moment) and the guidance toward them (onboarding documents and guidance flows, the milestones each waits for)."
40
+ }
41
+ ],
42
+ "stepOutputs": [],
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",
45
+ "skillRefs": [
46
+ "journey-status",
47
+ "frontend-component-catalog",
48
+ "views-composite-authoring",
49
+ "resource-custom-view",
50
+ "spec-composite-view-update",
51
+ "config-navigation",
52
+ "config-app-shell",
53
+ "config-design-system",
54
+ "milestones-and-celebrations",
55
+ "guidance-onboarding-authoring"
56
+ ],
57
+ "skillBodyRefs": [
58
+ "frontend-component-catalog"
59
+ ],
60
+ "contextSources": [
61
+ "workspace_truth"
62
+ ],
63
+ "draftableDocumentDefinitionRefs": [],
64
+ "suspendsForClarification": false,
65
+ "briefAdequacyGate": false,
66
+ "briefAdequacyExcludedSources": []
67
+ },
68
+ "executor": "companion_agent",
69
+ "approval": "approve_result",
70
+ "budget": {
71
+ "maxRuns": 3
72
+ },
73
+ "onFailure": "keep_and_flag"
74
+ }