@wildo-ai/framework-knowledge 1.1.11 → 1.1.13

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 (812) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +4 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
  5. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
  6. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +3 -3
  7. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
  8. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
  9. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
  10. package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
  11. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  12. package/dist/esm/framework-knowledge.definitions.js +180 -32
  13. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  14. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  15. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  16. package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
  17. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
  18. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -1
  19. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  20. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  21. package/dist/esm/index.d.ts.map +1 -1
  22. package/dist/esm/index.js.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
  24. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -12
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +7 -4
  31. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +76 -14
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
  35. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -15
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
  41. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  43. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
  45. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
  47. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  49. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +35 -14
  50. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  51. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +16 -8
  52. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  53. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +19 -8
  54. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  55. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +30 -3
  56. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  57. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +87 -16
  58. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  61. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
  62. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
  63. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
  64. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
  65. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +5 -1
  66. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +3 -2
  68. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  69. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  71. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
  72. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
  74. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
  76. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
  78. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  82. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  83. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +3 -5
  84. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  85. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
  86. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
  88. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  89. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +8 -6
  91. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
  93. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +8 -1
  95. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  96. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +4 -1
  99. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +11 -3
  101. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  103. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
  104. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
  107. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
  109. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
  111. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
  113. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +36 -13
  115. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  116. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +8 -2
  117. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  118. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -1
  119. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +4 -1
  121. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +34 -6
  123. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  124. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +5 -2
  125. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  126. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +4 -3
  127. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  128. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  129. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
  130. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  131. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
  132. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  133. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +39 -29
  134. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  135. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  136. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  137. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +8 -3
  138. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  139. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -7
  140. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  141. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  142. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  143. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  144. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  145. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  146. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  147. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  148. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +2 -2
  149. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  150. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  151. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  152. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  153. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
  154. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  156. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
  157. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  158. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -7
  159. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  160. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +12 -14
  161. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  162. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +3 -0
  163. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  164. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
  165. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  166. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
  167. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  168. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +2 -1
  169. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  170. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +4 -1
  171. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
  172. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
  173. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
  174. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
  175. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  176. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +4 -2
  177. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  178. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +34 -1
  179. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  180. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +35 -17
  181. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  182. package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
  183. package/dist/esm/source-anchor-grammar.js.map +1 -1
  184. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  185. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  186. package/dist/knowledge/manifest.json +7 -7
  187. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
  188. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
  189. package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
  190. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
  191. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  192. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  193. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +439 -27
  194. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
  195. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
  196. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
  197. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
  198. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
  199. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
  200. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
  201. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
  202. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  203. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  204. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +104 -2
  205. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
  206. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
  207. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
  208. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
  209. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -8
  210. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
  211. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
  212. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +19 -2
  213. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
  214. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +34 -0
  215. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
  216. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
  217. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
  218. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
  219. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
  220. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
  221. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
  222. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -6
  223. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
  224. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
  225. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
  226. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +56 -5
  227. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
  228. package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
  229. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
  230. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
  231. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
  232. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  233. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  234. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -3
  235. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
  236. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
  237. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  238. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  239. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
  240. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
  241. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
  242. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  243. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  244. package/dist/knowledge/playbooks/top_down.business-model/method.md +43 -11
  245. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
  246. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
  247. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
  248. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
  249. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +3 -3
  250. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
  251. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
  252. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
  253. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
  254. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
  255. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
  256. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
  257. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
  258. package/dist/knowledge/playbooks/top_down.definition/method.md +3 -1
  259. package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
  260. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
  261. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
  262. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
  263. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
  264. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
  265. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
  266. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
  267. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
  268. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  269. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  270. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -0
  271. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +14 -0
  272. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +11 -7
  273. package/dist/knowledge/playbooks/top_down.risk-register/method.md +7 -0
  274. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
  275. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
  276. package/dist/knowledge/playbooks/top_down.service-method/method.md +19 -1
  277. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
  278. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
  279. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
  280. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
  281. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
  282. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +17 -2
  283. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
  284. package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
  285. package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
  286. package/dist/knowledge/references/application-maturity.config.md +70 -1
  287. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
  288. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
  289. package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
  290. package/dist/knowledge/references/brand.name-screening.config.md +30 -3
  291. package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
  292. package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
  293. package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
  294. package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
  295. package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
  296. package/dist/knowledge/references/companion.market.generation-service.md +46 -5
  297. package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
  298. package/dist/knowledge/references/companion.technical-doc.service.md +195 -63
  299. package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
  300. package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
  301. package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
  302. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
  303. package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
  304. package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
  305. package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
  306. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +4 -2
  307. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
  308. package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
  309. package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
  310. package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
  311. package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
  312. package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
  313. package/dist/knowledge/references/example.provider.backend-module-shape.md +28 -4
  314. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
  315. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +21 -0
  316. package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
  317. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
  318. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +37 -2
  319. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
  320. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
  321. package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
  322. package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
  323. package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
  324. package/dist/knowledge/references/example.website.demo.complete-items.md +3 -3
  325. package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
  326. package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
  327. package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
  328. package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
  329. package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
  330. package/dist/knowledge/references/example.website.section.stats.md +1 -1
  331. package/dist/knowledge/references/experience-plan.config.md +111 -1
  332. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
  333. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
  334. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
  335. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
  336. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
  337. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
  338. package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
  339. package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
  340. package/dist/knowledge/references/integration-plan.config.md +7 -7
  341. package/dist/knowledge/references/placement-plan.config.md +19 -0
  342. package/dist/knowledge/references/platform.config.backing-services.md +9 -11
  343. package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
  344. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
  345. package/dist/knowledge/references/platform.config.infrastructure-host.md +1 -1
  346. package/dist/knowledge/references/platform.config.platform-key-management.md +89 -10
  347. package/dist/knowledge/references/platform.config.saas.md +20 -18
  348. package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
  349. package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
  350. package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
  351. package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
  352. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +3 -3
  353. package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
  354. package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
  355. package/dist/knowledge/references/requirements.engine-substance.md +38 -0
  356. package/dist/knowledge/references/requirements.functional-requirement.config.md +11 -0
  357. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +15 -4
  358. package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
  359. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +49 -2
  360. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
  361. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
  362. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
  363. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
  364. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
  365. package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
  366. package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
  367. package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
  368. package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
  369. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
  370. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
  371. package/dist/knowledge/references/saas.backend.domain-module.md +30 -1
  372. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
  373. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
  374. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +435 -2
  375. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
  376. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
  377. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
  378. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
  379. package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
  380. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
  381. package/dist/knowledge/references/saas.backend.system-access-service.md +159 -4
  382. package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
  383. package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
  384. package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
  385. package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
  386. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
  387. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
  388. package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
  389. package/dist/knowledge/references/saas.frontend.chart-dashboard.md +133 -0
  390. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
  391. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
  392. package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
  393. package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
  394. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
  395. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
  396. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
  397. package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
  398. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
  399. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
  400. package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
  401. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
  402. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
  403. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
  404. package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
  405. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
  406. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
  407. package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
  408. package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
  409. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
  410. package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
  411. package/dist/knowledge/references/saas.models.chart-dashboard-tile-sizes.md +40 -0
  412. package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
  413. package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
  414. package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
  415. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
  416. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
  417. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
  418. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
  419. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
  420. package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
  421. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
  422. package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
  423. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
  424. package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
  425. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails-environment.md +52 -0
  426. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
  427. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
  428. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
  429. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
  430. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
  431. package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
  432. package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
  433. package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
  434. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
  435. package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
  436. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
  437. package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
  438. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
  439. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
  440. package/dist/knowledge/references/saas.models.organization-dashboard-layout.md +61 -0
  441. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
  442. package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
  443. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
  444. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
  445. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
  446. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
  447. package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
  448. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
  449. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
  450. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
  451. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
  452. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
  453. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +2 -0
  454. package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
  455. package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
  456. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
  457. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -0
  458. package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
  459. package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
  460. package/dist/knowledge/references/saas.models.representative-activity.md +4 -0
  461. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
  462. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
  463. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
  464. package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
  465. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
  466. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +38 -0
  467. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
  468. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
  469. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
  470. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
  471. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
  472. package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
  473. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
  474. package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -2
  475. package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
  476. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +3 -1
  477. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
  478. package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
  479. package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
  480. package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
  481. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
  482. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -2
  483. package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
  484. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +6 -2
  485. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
  486. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
  487. package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
  488. package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
  489. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
  490. package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
  491. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
  492. package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
  493. package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
  494. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
  495. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
  496. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
  497. package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
  498. package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
  499. package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
  500. package/dist/knowledge/references/service-method.config.md +35 -2
  501. package/dist/knowledge/references/vision.constraint.config.md +4 -2
  502. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
  503. package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
  504. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
  505. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
  506. package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
  507. package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
  508. package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
  509. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
  510. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
  511. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
  512. package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
  513. package/dist/knowledge/references/zod.factories.code.md +4 -4
  514. package/dist/knowledge/references/zod.factories.duration.md +4 -4
  515. package/dist/knowledge/references/zod.factories.money.md +4 -4
  516. package/dist/knowledge/references/zod.factories.phone.md +4 -4
  517. package/dist/knowledge/references/zod.factories.year-month.md +79 -0
  518. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  519. package/dist/knowledge/registries/framework-topics.json +455 -2
  520. package/dist/knowledge/registries/playbooks.json +51 -39
  521. package/dist/knowledge/registries/source-tags.json +2505 -1627
  522. package/dist/knowledge/rules/database-migration-obligation.md +6 -7
  523. package/dist/knowledge/rules/live-context-door.md +1 -1
  524. package/dist/knowledge/skills/INDEX.md +3 -1
  525. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
  526. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
  527. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
  528. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
  529. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
  530. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
  531. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -11
  532. package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
  533. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +13 -11
  534. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
  535. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
  536. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
  537. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +46 -2
  538. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
  539. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
  540. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +12 -5
  541. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
  542. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
  543. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
  544. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
  545. package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
  546. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +2 -2
  547. package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
  548. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
  549. package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
  550. package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +90 -0
  551. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +4 -2
  552. package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
  553. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
  554. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +3 -0
  555. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
  556. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
  557. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
  558. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
  559. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
  560. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
  561. package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
  562. package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
  563. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +4 -0
  564. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
  565. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
  566. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
  567. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
  568. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
  569. package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
  570. package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
  571. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
  572. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
  573. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -11
  574. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
  575. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -9
  576. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +240 -9
  577. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
  578. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
  579. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
  580. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
  581. package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
  582. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
  583. package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
  584. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +20 -0
  585. package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
  586. package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
  587. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
  588. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
  589. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
  590. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
  591. package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +78 -0
  592. package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
  593. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
  594. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +3 -2
  595. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
  596. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
  597. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
  598. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +13 -3
  599. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
  600. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -11
  601. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
  602. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
  603. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +188 -10
  604. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
  605. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
  606. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
  607. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +3 -3
  608. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
  609. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +447 -8
  610. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
  611. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
  612. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
  613. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +13 -3
  614. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
  615. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
  616. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +13 -3
  617. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
  618. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
  619. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -1
  620. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +6 -5
  621. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +50 -14
  622. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
  623. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
  624. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
  625. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
  626. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
  627. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
  628. package/dist/knowledge/skills/inbound-channels/SKILL.md +31 -9
  629. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
  630. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
  631. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
  632. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
  633. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
  634. package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
  635. package/dist/knowledge/skills/infra-environment-config/SKILL.md +149 -77
  636. package/dist/knowledge/skills/infra-environment-config/references/framework-agent-content-guardrails-environment-api.md +67 -0
  637. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
  638. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +133 -8
  639. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +1 -1
  640. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +89 -10
  641. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
  642. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
  643. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
  644. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
  645. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
  646. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +3 -3
  647. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
  648. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
  649. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
  650. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +24 -2
  651. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
  652. package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
  653. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
  654. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
  655. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
  656. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
  657. package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
  658. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
  659. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
  660. package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
  661. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
  662. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
  663. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
  664. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
  665. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
  666. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
  667. package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -15
  668. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
  669. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
  670. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
  671. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +8 -1
  672. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
  673. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -0
  674. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
  675. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
  676. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +11 -6
  677. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
  678. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
  679. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
  680. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
  681. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
  682. package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
  683. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
  684. package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
  685. package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
  686. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +107 -42
  687. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
  688. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
  689. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
  690. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
  691. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +34 -7
  692. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
  693. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
  694. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +140 -58
  695. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +28 -2
  696. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
  697. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +5 -4
  698. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
  699. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
  700. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
  701. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
  702. package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
  703. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
  704. package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
  705. package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
  706. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
  707. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
  708. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
  709. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
  710. package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
  711. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
  712. package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
  713. package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
  714. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +26 -5
  715. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
  716. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
  717. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
  718. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
  719. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
  720. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
  721. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +18 -2
  722. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
  723. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
  724. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
  725. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
  726. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +21 -0
  727. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
  728. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
  729. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
  730. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
  731. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
  732. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
  733. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
  734. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
  735. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
  736. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
  737. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
  738. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
  739. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -0
  740. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
  741. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
  742. package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
  743. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
  744. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +66 -3
  745. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
  746. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
  747. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
  748. package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
  749. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +83 -16
  750. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
  751. package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
  752. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +9 -2
  753. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
  754. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
  755. package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
  756. package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
  757. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
  758. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
  759. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
  760. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
  761. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
  762. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
  763. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +21 -2
  764. package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
  765. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +121 -75
  766. package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
  767. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +100 -71
  768. package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
  769. package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
  770. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
  771. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
  772. package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
  773. package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
  774. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +36 -5
  775. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
  776. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +4 -0
  777. package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +371 -0
  778. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
  779. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
  780. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
  781. package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
  782. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
  783. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
  784. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
  785. package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
  786. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
  787. package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
  788. package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
  789. package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
  790. package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
  791. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
  792. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
  793. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
  794. package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
  795. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
  796. package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
  797. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
  798. package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
  799. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
  800. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
  801. package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
  802. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
  803. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
  804. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
  805. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
  806. package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
  807. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
  808. package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
  809. package/dist/knowledge/topic-index.json +2422 -723
  810. package/dist/tsconfig.build.tsbuildinfo +1 -1
  811. package/package.json +6 -6
  812. package/dist/tsconfig.tsbuildinfo +0 -1
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.integration-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,4BAA4B;IACnC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,+yBAA+yB;IACzzB,eAAe,EAAE;QACf;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,sJAAsJ,EAAE;QAC1L,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,+DAA+D,EAAE;QACrG,EAAE,QAAQ,EAAE,aAAa,EAAE,IAAI,EAAE,wFAAwF,EAAE;QAC3H,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,wJAAwJ,EAAE;QACxM,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,oLAAoL,EAAE;KAC7N;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,kBAAkB;YAC5B,WAAW,EAAE,qCAAqC;YAClD,aAAa,EAAE,4cAA4c;SAC5d;KACF;IACD,QAAQ,EAAE;QACR;;;;;;;;;;WAUG;QACH,gBAAgB,EAAE,CAAC,iBAAiB,EAAE,mBAAmB,CAAC;QAC1D;;;;;;WAMG;QACH,eAAe,EAAE,CAAC,kBAAkB,EAAE,kBAAkB,CAAC;QACzD,WAAW,EAAE;YACX,kBAAkB;YAClB,kBAAkB;YAClB,0BAA0B;YAC1B,+BAA+B;YAC/B,0BAA0B;YAC1B,wBAAwB;YACxB,mBAAmB;YACnB,kBAAkB;SACnB;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The background-execution and external-reach leaf (#1495). `add-minion`, `add-worker-node`,\n * `add-worker-rust`, `add-provider` and `add-file-picker-provider` all shipped as scenarios, and\n * the decomposer was told to plan \"workers / minions and other auxiliary execution surfaces\" and\n * \"providers, external connectors, billing wiring\" — with no product kind for any of them and,\n * measured 2026-09-22, ZERO worker and minion skills in the catalog. Nothing in the journey could\n * give an application a background worker, a cron minion or a provider binding.\n *\n * It produces the integration plan. Two consumers read it, and the split is the point:\n *\n * - `bottom_up.foundation` composes the PACKAGE — one `add-worker-node`, `add-worker-rust` or\n * `add-minion` per surface, fanned out exactly as modules and resources are fanned out of the\n * domain plan. That is why the capability composition reports those three scenarios as owned by\n * the foundation rather than as undecidable, which is what they read until this family existed.\n * - `bottom_up.build-decompose` emits the WORK — one task per worker, minion and provider binding,\n * each bound to its skill through the three total maps in `_core`, and one per inbound channel\n * producing its handler, which the dispatch routes to `inbound-channels` from the product (#1832).\n *\n * The build plan keeps ONE producer, which is what makes landing decidable (#895).\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.integration-plan\",\n \"version\": \"0.2.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Background execution and external reach — decide WHAT RUNS BESIDE THE BACKEND and WHAT THIS APPLICATION REACHES OUT TO: which workers exist and on which runtime, which cron minions wake on their own and exactly which resources each one may read and write, and which providers are bound into which runtime owner's scope. Reads the requirements and feature drafts (what somebody asked for, including the work that cannot happen inside a request), the domain plan (the resources a minion's containment whitelist names) and the roadmap (what is owed when). Every surface names what it is accountable to, because a process nobody asked for is a process nobody maintains. Produces the plan; the foundation composes each package and the decomposer emits the work, each task bound to the skill its runtime or scope names.\",\n \"preconditions\": [\n /*\n * The DOMAIN PLAN is what a minion's containment is OVER: `readsResourceRefs` and\n * `writesResourceRefs` name decided resources, and a whitelist naming resources nobody decided\n * contains nothing. Its CONTENT is read, so `artifact_exists` is the honest strength (#1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"requirements\", \"//\": \"What somebody asked the application to do — including the work that cannot happen inside a request, which is the only honest reason a worker exists.\" },\n { \"family\": \"feature-drafts\", \"//\": \"The drafted features whose work a background surface carries.\" },\n { \"family\": \"domain-plan\", \"//\": \"The resources a minion's containment whitelist names, and the modules a worker serves.\" },\n { \"family\": \"roadmap\", \"render\": \"map\", \"//\": \"When each phase is owed, so a surface is planned against the phase that needs it. A MAP: the phases' own rationale is not this method's input (#1424).\" },\n { \"family\": \"integration-plan\", \"//\": \"Its own family: its method refines its own prior output and keeps its worker and minion refs, which build tasks name (#1430). Input, not precondition: a first run stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"integration-plan\",\n \"schemaRef\": \"saas-specifications:IntegrationPlan\",\n \"description\": \"What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), and the providers it binds into each runtime owner's scope. Every collection may be empty, and saying so is an answer.\"\n }\n ],\n \"method\": {\n /*\n * WORKSPACE_TRUTH — this method plans against CODE as well as against decisions: which workers\n * and minions the application ALREADY carries (its `applicationWorkers` / `applicationMinions`\n * buckets), and which providers its scopes already name. A plan proposing a worker the tree\n * already has emits a task that composes a package twice.\n *\n * PROVIDER_REGISTRY (#2025) — the provider modules the registry OFFERS. Since the catalogue was\n * archived (#2019) a vendor reaches an application only by being installed from the registry, so\n * the workspace alone shows what is installed and nothing that could be added: an OCR or Teams need\n * was planned against nothing, or against a vendor recalled from training that no module provides.\n */\n \"contextSources\": [\"workspace_truth\", \"provider_registry\"],\n /*\n * TWO bodies reach this step (#1435), and they are the two the plan's central decisions depend\n * on: whether a surface is a worker or a minion, and what a minion's containment must name.\n * Both are impossible to decide from recollection — the difference is a runtime contract, and\n * the containment chain has three parts of which two are outside the minion's own package.\n * Every other skill is a contract the CODING AGENT opens when it builds the task.\n */\n \"skillBodyRefs\": [\"worker-authoring\", \"minion-authoring\"],\n \"skillRefs\": [\n \"worker-authoring\",\n \"minion-authoring\",\n \"provider-backend-package\",\n \"provider-frontend-file-picker\",\n \"provider-operation-calls\",\n \"resource-external-data\",\n \"configure-billing\",\n \"inbound-channels\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.integration-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,4BAA4B;IACnC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,+yBAA+yB;IACzzB,eAAe,EAAE;QACf;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,sJAAsJ,EAAE;QAC1L,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,+DAA+D,EAAE;QACrG,EAAE,QAAQ,EAAE,aAAa,EAAE,IAAI,EAAE,wFAAwF,EAAE;QAC3H,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,wJAAwJ,EAAE;QACxM,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,oLAAoL,EAAE;KAC7N;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,kBAAkB;YAC5B,WAAW,EAAE,qCAAqC;YAClD,aAAa,EAAE,4cAA4c;SAC5d;KACF;IACD,QAAQ,EAAE;QACR;;;;;;;;;;WAUG;QACH,gBAAgB,EAAE,CAAC,iBAAiB,EAAE,mBAAmB,CAAC;QAC1D;;;;;;WAMG;QACH,eAAe,EAAE,CAAC,kBAAkB,EAAE,kBAAkB,CAAC;QACzD,WAAW,EAAE;YACX,kBAAkB;YAClB,kBAAkB;YAClB,0BAA0B;YAC1B,+BAA+B;YAC/B,0BAA0B;YAC1B,wBAAwB;YACxB,mBAAmB;YACnB,kBAAkB;SACnB;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The background-execution and external-reach leaf (#1495). `add-minion`, `add-worker-node`,\n * `add-worker-rust`, `add-provider` and `add-file-picker-provider` all shipped as scenarios, and\n * the decomposer was told to plan \"workers / minions and other auxiliary execution surfaces\" and\n * \"providers, external connectors, billing wiring\" — with no product kind for any of them and,\n * measured 2026-09-22, ZERO worker and minion skills in the catalog. Nothing in the journey could\n * give an application a background worker, a cron minion or a provider binding.\n *\n * It produces the integration plan. Two consumers read it, and the split is the point:\n *\n * - `bottom_up.foundation` composes the PACKAGE — one `add-worker-node`, `add-worker-rust` or\n * `add-minion` per surface, fanned out exactly as modules and resources are fanned out of the\n * domain plan. That is why the capability composition reports those three scenarios as owned by\n * the foundation rather than as undecidable, which is what they read until this family existed.\n * - `bottom_up.build-decompose` emits the WORK — one task per worker, minion and provider binding,\n * each bound to its skill through the three total maps in `_core`, and one per inbound channel\n * producing its handler, which the dispatch routes to `inbound-channels` from the product (#1832).\n *\n * The build plan keeps ONE producer, which is what makes landing decidable (#895).\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.integration-plan\",\n \"version\": \"0.2.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Background execution and external reach — decide WHAT RUNS BESIDE THE BACKEND and WHAT THIS APPLICATION REACHES OUT TO: which workers exist and on which runtime, which cron minions wake on their own and exactly which resources each one may read and write, and which providers are bound into which runtime owner's scope. Reads the requirements and feature drafts (what somebody asked for, including the work that cannot happen inside a request), the domain plan (the resources a minion's containment whitelist names) and the roadmap (what is owed when). Every surface names what it is accountable to, because a process nobody asked for is a process nobody maintains. Produces the plan; the foundation composes each package and the decomposer emits the work, each task bound to the skill its runtime or scope names.\",\n \"preconditions\": [\n /*\n * The DOMAIN PLAN is what a minion's containment is OVER: `readsResourceRefs` and\n * `writesResourceRefs` name decided resources, and a whitelist naming resources nobody decided\n * contains nothing. Its CONTENT is read, so `artifact_exists` is the honest strength (#1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"requirements\", \"//\": \"What somebody asked the application to do — including the work that cannot happen inside a request, which is the only honest reason a worker exists.\" },\n { \"family\": \"feature-drafts\", \"//\": \"The drafted features whose work a background surface carries.\" },\n { \"family\": \"domain-plan\", \"//\": \"The resources a minion's containment whitelist names, and the modules a worker serves.\" },\n { \"family\": \"roadmap\", \"render\": \"map\", \"//\": \"When each phase is owed, so a surface is planned against the phase that needs it. A MAP: the phases' own rationale is not this method's input (#1424).\" },\n { \"family\": \"integration-plan\", \"//\": \"Its own family: its method refines its own prior output and keeps its worker and minion refs, which build tasks name (#1430). Input, not precondition: a first run stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"integration-plan\",\n \"schemaRef\": \"saas-specifications:IntegrationPlan\",\n \"description\": \"What this application runs beside its backend and what it reaches out to: its workers (each with its runtime, what the backend delegates to it, the routes it registers and what it is accountable to), its cron minions (each with what happens because time passed, its named behaviours, and exactly which resources its tick reads and writes), and the providers it binds into each runtime owner's scope. Every collection may be empty, and saying so is an answer.\"\n }\n ],\n \"method\": {\n /*\n * WORKSPACE_TRUTH — this method plans against CODE as well as against decisions: which workers\n * and minions the application ALREADY carries (its `applicationWorkers` / `applicationMinions`\n * buckets), and which providers its scopes already name. A plan proposing a worker the tree\n * already has emits a task that composes a package twice.\n *\n * PROVIDER_REGISTRY (#2025) — the provider modules the registry OFFERS. Since the catalogue was\n * archived (#2019) a vendor reaches an application only by being installed from the registry, so\n * the workspace alone shows what is installed and nothing that could be added: an OCR or Teams need\n * was planned against nothing, or against a vendor recalled from training that no module provides.\n */\n \"contextSources\": [\"workspace_truth\", \"provider_registry\"],\n /*\n * TWO bodies reach this step (#1435), and they are the two the plan's central decisions depend\n * on: whether a surface is a worker or a minion, and what a minion's containment must name.\n * Both are impossible to decide from recollection — the difference is a runtime contract, and\n * the containment chain has three parts of which two are outside the minion's own package.\n * Every other skill is a contract the CODING AGENT opens when it builds the task.\n */\n \"skillBodyRefs\": [\"worker-authoring\", \"minion-authoring\"],\n \"skillRefs\": [\n \"worker-authoring\",\n \"minion-authoring\",\n \"provider-backend-package\",\n \"provider-frontend-file-picker\",\n \"provider-operation-calls\",\n \"resource-external-data\",\n \"configure-billing\",\n \"inbound-channels\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -20,9 +20,9 @@
20
20
  */
21
21
  export declare const playbookDefinition: {
22
22
  readonly ref: "bottom_up.maturity-reading";
23
- readonly version: "0.1.0";
23
+ readonly version: "0.2.0";
24
24
  readonly phase: "bottom_up";
25
- readonly intent: "Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED in committed bytes, a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.";
25
+ readonly intent: "Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED (its product is in the working tree and something checked it), a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.";
26
26
  readonly preconditions: readonly [{
27
27
  readonly kind: "artifact_exists";
28
28
  readonly selector: {
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.maturity-reading/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgDrB,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.maturity-reading/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgDrB,CAAC"}
@@ -20,9 +20,9 @@
20
20
  */
21
21
  export const playbookDefinition = {
22
22
  "ref": "bottom_up.maturity-reading",
23
- "version": "0.1.0",
23
+ "version": "0.2.0",
24
24
  "phase": "bottom_up",
25
- "intent": "Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED in committed bytes, a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.",
25
+ "intent": "Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED (its product is in the working tree and something checked it), a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.",
26
26
  "preconditions": [
27
27
  /*
28
28
  * The REQUIREMENTS are the denominator, and a reading with no denominator is not a weaker
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.maturity-reading/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,4BAA4B;IACnC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,y8BAAy8B;IACn9B,eAAe,EAAE;QACf;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD;;;;;;;;;OASG;IACH,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC7C,EAAE,QAAQ,EAAE,gBAAgB,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC/C,EAAE,QAAQ,EAAE,YAAY,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC3C,EAAE,QAAQ,EAAE,iBAAiB,EAAE,QAAQ,EAAE,KAAK,EAAE;QAChD,EAAE,QAAQ,EAAE,kBAAkB,EAAE,QAAQ,EAAE,KAAK,EAAE;QACjD,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE;QACxC,EAAE,QAAQ,EAAE,sBAAsB,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,wHAAwH,EAAE;KACtL;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,sBAAsB;YAChC,WAAW,EAAE,yCAAyC;YACtD,aAAa,EAAE,uTAAuT;SACvU;KACF;IACD,QAAQ,EAAE;QACR,WAAW,EAAE,EACZ;KACF;IACD,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * A RUNNER-OWNED step, like `bottom_up.capability-composition` and `bottom_up.foundation` (#1496):\n * the run short-circuits into the companion's maturity executor before any brief is composed,\n * because the reading is a PURE FUNCTION — `deriveApplicationMaturity` walks the requirements\n * family, the decided-element graph's inbound links and the build plan's landing probe. A model\n * asked where an application stands would ANSWER, and nothing could check the answer, which is the\n * one thing this family exists to prevent.\n *\n * It declares its `outputs` because the family IS landed through the generic renderer, so the\n * coherence report and the workbench have a producer to read. It carries no evaluation treatment:\n * there is no judgement in it to judge, only a measurement whose validator reports what the\n * APPLICATION lacks rather than what the artifact got wrong.\n *\n * **Not a gate, and nothing downstream may treat it as one.** Paul, 2026-09-22: *\"there are no\n * 'Done' for an app, there are a measurement face to requirements, with some stage.\"* The highest\n * stage says only that every requirement currently has the strongest evidence this framework can\n * produce; the next requirement lowers it again.\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.maturity-reading\",\n \"version\": \"0.1.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED in committed bytes, a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.\",\n \"preconditions\": [\n /*\n * The REQUIREMENTS are the denominator, and a reading with no denominator is not a weaker\n * reading — it is a different statement (\"nothing has been asked of this application yet\").\n * `artifact_exists` because the CONTENT is read: the rows ARE its entries (#1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"requirements\" } }\n ],\n /*\n * Every family the derivation reads, declared so derived-staleness compares them: the reading goes\n * stale when any decided element that could address a requirement changes. `render: 'map'` on each\n * — the executor reads the VALUES itself through the artifact state, and no brief is composed for\n * this step, so a full render would reach nothing (#1434's lesson).\n *\n * The list is the families that declare an edge to a requirement TODAY. It is not how the\n * derivation finds them — that is the decided-element graph, which a family declaring such an edge\n * tomorrow joins without this file changing — so a missing entry costs staleness, never coverage.\n */\n \"inputs\": [\n { \"family\": \"requirements\", \"render\": \"map\" },\n { \"family\": \"feature-drafts\", \"render\": \"map\" },\n { \"family\": \"build-plan\", \"render\": \"map\" },\n { \"family\": \"experience-plan\", \"render\": \"map\" },\n { \"family\": \"integration-plan\", \"render\": \"map\" },\n { \"family\": \"roadmap\", \"render\": \"map\" },\n { \"family\": \"application-maturity\", \"render\": \"map\", \"//\": \"Its own family: the reading it replaces. Input, not precondition — a first run, with no prior reading, stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"application-maturity\",\n \"schemaRef\": \"saas-specifications:ApplicationMaturity\",\n \"description\": \"Where the application stands against its own requirements: one row per requirement with the evidence level it has reached and the elements, landed tasks, proven tasks and runtime observations that carry it, the thresholds the reading was scored against, and the stage that follows. A reading, never a verdict.\"\n }\n ],\n \"method\": {\n \"skillRefs\": [\n ]\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 5\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.maturity-reading/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,4BAA4B;IACnC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,o/BAAo/B;IAC9/B,eAAe,EAAE;QACf;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE,EAAE;KACxE;IACD;;;;;;;;;OASG;IACH,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,cAAc,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC7C,EAAE,QAAQ,EAAE,gBAAgB,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC/C,EAAE,QAAQ,EAAE,YAAY,EAAE,QAAQ,EAAE,KAAK,EAAE;QAC3C,EAAE,QAAQ,EAAE,iBAAiB,EAAE,QAAQ,EAAE,KAAK,EAAE;QAChD,EAAE,QAAQ,EAAE,kBAAkB,EAAE,QAAQ,EAAE,KAAK,EAAE;QACjD,EAAE,QAAQ,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE;QACxC,EAAE,QAAQ,EAAE,sBAAsB,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,wHAAwH,EAAE;KACtL;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,sBAAsB;YAChC,WAAW,EAAE,yCAAyC;YACtD,aAAa,EAAE,uTAAuT;SACvU;KACF;IACD,QAAQ,EAAE;QACR,WAAW,EAAE,EACZ;KACF;IACD,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * A RUNNER-OWNED step, like `bottom_up.capability-composition` and `bottom_up.foundation` (#1496):\n * the run short-circuits into the companion's maturity executor before any brief is composed,\n * because the reading is a PURE FUNCTION — `deriveApplicationMaturity` walks the requirements\n * family, the decided-element graph's inbound links and the build plan's landing probe. A model\n * asked where an application stands would ANSWER, and nothing could check the answer, which is the\n * one thing this family exists to prevent.\n *\n * It declares its `outputs` because the family IS landed through the generic renderer, so the\n * coherence report and the workbench have a producer to read. It carries no evaluation treatment:\n * there is no judgement in it to judge, only a measurement whose validator reports what the\n * APPLICATION lacks rather than what the artifact got wrong.\n *\n * **Not a gate, and nothing downstream may treat it as one.** Paul, 2026-09-22: *\"there are no\n * 'Done' for an app, there are a measurement face to requirements, with some stage.\"* The highest\n * stage says only that every requirement currently has the strongest evidence this framework can\n * produce; the next requirement lowers it again.\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.maturity-reading\",\n \"version\": \"0.2.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Maturity reading — measure WHERE THIS APPLICATION STANDS against its own requirements, and record it as the `application-maturity` family: one row per requirement the application declares, the evidence that exists for it, and the stage that follows. DERIVED, never judged. Each row's level is reached by a measurement — a decided element that points at the requirement (a feature draft, an experience surface, a worker, a build task), a build task addressing it that has LANDED (its product is in the working tree and something checked it), a landed task whose declared product was PROVEN, or a runtime observation of the running application. The denominator is the requirements family itself, total and in its own order, so a requirement nothing addresses is a row rather than an omission and adding one lowers the reading with no code change. This is a MEASUREMENT and never a gate: there is no 'done' for an application, and the stage moves in both directions as the application and its requirements change.\",\n \"preconditions\": [\n /*\n * The REQUIREMENTS are the denominator, and a reading with no denominator is not a weaker\n * reading — it is a different statement (\"nothing has been asked of this application yet\").\n * `artifact_exists` because the CONTENT is read: the rows ARE its entries (#1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"requirements\" } }\n ],\n /*\n * Every family the derivation reads, declared so derived-staleness compares them: the reading goes\n * stale when any decided element that could address a requirement changes. `render: 'map'` on each\n * — the executor reads the VALUES itself through the artifact state, and no brief is composed for\n * this step, so a full render would reach nothing (#1434's lesson).\n *\n * The list is the families that declare an edge to a requirement TODAY. It is not how the\n * derivation finds them — that is the decided-element graph, which a family declaring such an edge\n * tomorrow joins without this file changing — so a missing entry costs staleness, never coverage.\n */\n \"inputs\": [\n { \"family\": \"requirements\", \"render\": \"map\" },\n { \"family\": \"feature-drafts\", \"render\": \"map\" },\n { \"family\": \"build-plan\", \"render\": \"map\" },\n { \"family\": \"experience-plan\", \"render\": \"map\" },\n { \"family\": \"integration-plan\", \"render\": \"map\" },\n { \"family\": \"roadmap\", \"render\": \"map\" },\n { \"family\": \"application-maturity\", \"render\": \"map\", \"//\": \"Its own family: the reading it replaces. Input, not precondition — a first run, with no prior reading, stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"application-maturity\",\n \"schemaRef\": \"saas-specifications:ApplicationMaturity\",\n \"description\": \"Where the application stands against its own requirements: one row per requirement with the evidence level it has reached and the elements, landed tasks, proven tasks and runtime observations that carry it, the thresholds the reading was scored against, and the stage that follows. A reading, never a verdict.\"\n }\n ],\n \"method\": {\n \"skillRefs\": [\n ]\n },\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 5\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -7,7 +7,7 @@
7
7
  */
8
8
  export declare const playbookDefinition: {
9
9
  readonly ref: "bottom_up.placement-plan";
10
- readonly version: "0.1.5";
10
+ readonly version: "0.1.8";
11
11
  readonly phase: "bottom_up";
12
12
  readonly intent: "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean), the requirements (which tasks matter), the customer profile (who the customers are, which decides whether an enterprise destination belongs at all) and what the creator stated about the user groups, and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches, through the `settings-placement-authoring` skill for the settings rail and the `config-app-shell` skill for the sidebar, command palette and user menu. A sidebar group or a sidebar or palette decision may name the roles it is shown to (`requiredRoles`), when one audience only opens it. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.";
13
13
  readonly preconditions: readonly [{
@@ -27,6 +27,10 @@ export declare const playbookDefinition: {
27
27
  }, {
28
28
  readonly family: "vision-brief";
29
29
  readonly "//": "What the product is and who it serves, which a placement must fit.";
30
+ }, {
31
+ readonly family: "experience-plan";
32
+ readonly aspects: readonly ["experience-plan.view"];
33
+ readonly "//": "The views the experience plan decided, when it has run (#3066): a business concept held in two resources has ONE sidebar entry, the application view whose entryForResourceRefs names them, and placement puts THAT view on the sidebar by its slug. An input, never a precondition: placement may run first, and then names the concept view by its concept slug, which the experience plan reuses.";
30
34
  }];
31
35
  readonly outputs: readonly [{
32
36
  readonly family: "placement-plan";
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+CrB,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgDrB,CAAC"}
@@ -7,7 +7,7 @@
7
7
  */
8
8
  export const playbookDefinition = {
9
9
  "ref": "bottom_up.placement-plan",
10
- "version": "0.1.5",
10
+ "version": "0.1.8",
11
11
  "phase": "bottom_up",
12
12
  "intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean), the requirements (which tasks matter), the customer profile (who the customers are, which decides whether an enterprise destination belongs at all) and what the creator stated about the user groups, and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches, through the `settings-placement-authoring` skill for the settings rail and the `config-app-shell` skill for the sidebar, command palette and user menu. A sidebar group or a sidebar or palette decision may name the roles it is shown to (`requiredRoles`), when one audience only opens it. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
13
13
  "preconditions": [
@@ -17,7 +17,8 @@ export const playbookDefinition = {
17
17
  { "family": "domain-plan" },
18
18
  { "family": "requirements" },
19
19
  { "family": "market-snapshot", "aspects": ["market.icp", "market.persona"], "//": "The customer profile the fit test reads (#2502): company size, the tools they run, their technical staff. Without it one run declined single sign-on for a five-person trade firm and another, from the same inputs, placed it." },
20
- { "family": "vision-brief", "//": "What the product is and who it serves, which a placement must fit." }
20
+ { "family": "vision-brief", "//": "What the product is and who it serves, which a placement must fit." },
21
+ { "family": "experience-plan", "aspects": ["experience-plan.view"], "//": "The views the experience plan decided, when it has run (#3066): a business concept held in two resources has ONE sidebar entry, the application view whose entryForResourceRefs names them, and placement puts THAT view on the sidebar by its slug. An input, never a precondition: placement may run first, and then names the concept view by its concept slug, which the experience plan reuses." }
21
22
  ],
22
23
  "outputs": [
23
24
  {
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,0BAA0B;IACjC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,s3DAAs3D;IACh4D,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,iBAAiB,EAAE,SAAS,EAAE,CAAC,YAAY,EAAE,gBAAgB,CAAC,EAAE,IAAI,EAAE,iOAAiO,EAAE;QACrT,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,oEAAoE,EAAE;KACzG;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,gBAAgB;YAC1B,WAAW,EAAE,mCAAmC;YAChD,aAAa,EAAE,g9DAAg9D;SACh+D;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,qVAAqV;QACzW,sBAAsB,EAAE,oIAAoI;QAC5J,uBAAuB,EAAE,uPAAuP;QAChR,gBAAgB,EAAE,CAAC,iBAAiB,EAAE,sBAAsB,EAAE,6BAA6B,CAAC;QAC5F,WAAW,EAAE;YACX,8BAA8B;YAC9B,kBAAkB;YAClB,mBAAmB;SACpB;QACD,gBAAgB,EAAE,4pBAA4pB;QAC9qB,cAAc,EAAE;YACd,YAAY,EAAE,0BAA0B;YACxC,kBAAkB,EAAE,CAAC,uBAAuB,EAAE,wBAAwB,CAAC;YACvE,oBAAoB,EAAE,wBAAwB;YAC9C,sBAAsB,EAAE,uBAAuB;YAC/C,gBAAgB,EAAE,CAAC;SACpB;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * Placement is a DECISION the creator should not have to make. This playbook\n * produces it as an artifact, with a per-decision rationale, so a later reader\n * can ask \"why is this here?\" without re-deriving the answer.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.placement-plan\",\n \"version\": \"0.1.5\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean), the requirements (which tasks matter), the customer profile (who the customers are, which decides whether an enterprise destination belongs at all) and what the creator stated about the user groups, and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches, through the `settings-placement-authoring` skill for the settings rail and the `config-app-shell` skill for the sidebar, command palette and user menu. A sidebar group or a sidebar or palette decision may name the roles it is shown to (`requiredRoles`), when one audience only opens it. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"requirements\" },\n { \"family\": \"market-snapshot\", \"aspects\": [\"market.icp\", \"market.persona\"], \"//\": \"The customer profile the fit test reads (#2502): company size, the tools they run, their technical staff. Without it one run declined single sign-on for a five-person trade firm and another, from the same inputs, placed it.\" },\n { \"family\": \"vision-brief\", \"//\": \"What the product is and who it serves, which a placement must fit.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"placement-plan\",\n \"schemaRef\": \"saas-specifications:PlacementPlan\",\n \"description\": \"The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for, and the semantic authority currently supplies ENGINE_SETTINGS_DESTINATION_REFS for ENGINE_SETTINGS_DESTINATION. Unknown settings references are errors and missing settings decisions are warnings. This does not establish coverage for resource operations or application views: those kinds need their own supplied catalogues. A caller supplying no catalogue receives no coverage result, not a clean coverage result. The plan carries no file path, config key or label string — those belong to the coding task that authors the config.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"WORKSPACE_TRUTH — placement is decided against what EXISTS: the real engine settings destinations, the real resources and their operations, and the shell surfaces the application already has. A planner working from the definition artifacts alone invents destination refs that resolve to nothing, and every decision it emits is unplaceable.\",\n \"//contextSources2502\": \"CREATOR_STATED_FACTS — the user groups and the devices they use, which order the sidebar for the group that opens it most (#2502).\",\n \"//contextSources2502b\": \"APPLICATION_ENABLED_SURFACE — what the configuration switches on (capabilities, billing, sign-in methods), the capability leg of the fit test, dated by the configuration so a placement is offered again when SSO or billing is switched on (#2502).\",\n \"contextSources\": [\"workspace_truth\", \"creator_stated_facts\", \"application_enabled_surface\"],\n \"skillRefs\": [\n \"settings-placement-authoring\",\n \"config-app-shell\",\n \"config-navigation\",\n ],\n \"//deliberation\": \"Placement is DECIDED BY A PANEL, not elicited from the creator: the arrangement that is right for an application has several defensible answers, and the creator is the person least equipped to choose between them before the app exists. The information-architect OWNS the domain (so it derives the rubric); the design-system-guardian sits as the coherence memory, because where a thing goes must not fork the pattern the shipped surfaces already taught users. Three candidates, because the criteria trade off against each other — first-run discoverability, the daily-use path, and category convention pull in different directions and a single pass silently picks one.\",\n \"deliberation\": {\n \"workDomain\": \"information_architecture\",\n \"reviewerRoleRefs\": [\"information-architect\", \"design-system-guardian\"],\n \"coordinatorRoleRef\": \"design-system-guardian\",\n \"rubricDeriverRoleRef\": \"information-architect\",\n \"candidateCount\": 3\n }\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.placement-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,0BAA0B;IACjC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,s3DAAs3D;IACh4D,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;KACvE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,iBAAiB,EAAE,SAAS,EAAE,CAAC,YAAY,EAAE,gBAAgB,CAAC,EAAE,IAAI,EAAE,iOAAiO,EAAE;QACrT,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,oEAAoE,EAAE;QACxG,EAAE,QAAQ,EAAE,iBAAiB,EAAE,SAAS,EAAE,CAAC,sBAAsB,CAAC,EAAE,IAAI,EAAE,sYAAsY,EAAE;KACnd;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,gBAAgB;YAC1B,WAAW,EAAE,mCAAmC;YAChD,aAAa,EAAE,g9DAAg9D;SACh+D;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,qVAAqV;QACzW,sBAAsB,EAAE,oIAAoI;QAC5J,uBAAuB,EAAE,uPAAuP;QAChR,gBAAgB,EAAE,CAAC,iBAAiB,EAAE,sBAAsB,EAAE,6BAA6B,CAAC;QAC5F,WAAW,EAAE;YACX,8BAA8B;YAC9B,kBAAkB;YAClB,mBAAmB;SACpB;QACD,gBAAgB,EAAE,4pBAA4pB;QAC9qB,cAAc,EAAE;YACd,YAAY,EAAE,0BAA0B;YACxC,kBAAkB,EAAE,CAAC,uBAAuB,EAAE,wBAAwB,CAAC;YACvE,oBAAoB,EAAE,wBAAwB;YAC9C,sBAAsB,EAAE,uBAAuB;YAC/C,gBAAgB,EAAE,CAAC;SACpB;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * Placement is a DECISION the creator should not have to make. This playbook\n * produces it as an artifact, with a per-decision rationale, so a later reader\n * can ask \"why is this here?\" without re-deriving the answer.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.placement-plan\",\n \"version\": \"0.1.8\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean), the requirements (which tasks matter), the customer profile (who the customers are, which decides whether an enterprise destination belongs at all) and what the creator stated about the user groups, and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches, through the `settings-placement-authoring` skill for the settings rail and the `config-app-shell` skill for the sidebar, command palette and user menu. A sidebar group or a sidebar or palette decision may name the roles it is shown to (`requiredRoles`), when one audience only opens it. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"requirements\" },\n { \"family\": \"market-snapshot\", \"aspects\": [\"market.icp\", \"market.persona\"], \"//\": \"The customer profile the fit test reads (#2502): company size, the tools they run, their technical staff. Without it one run declined single sign-on for a five-person trade firm and another, from the same inputs, placed it.\" },\n { \"family\": \"vision-brief\", \"//\": \"What the product is and who it serves, which a placement must fit.\" },\n { \"family\": \"experience-plan\", \"aspects\": [\"experience-plan.view\"], \"//\": \"The views the experience plan decided, when it has run (#3066): a business concept held in two resources has ONE sidebar entry, the application view whose entryForResourceRefs names them, and placement puts THAT view on the sidebar by its slug. An input, never a precondition: placement may run first, and then names the concept view by its concept slug, which the experience plan reuses.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"placement-plan\",\n \"schemaRef\": \"saas-specifications:PlacementPlan\",\n \"description\": \"The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run per SUBJECT KIND and only for the kinds a caller supplies a catalog for, and the semantic authority currently supplies ENGINE_SETTINGS_DESTINATION_REFS for ENGINE_SETTINGS_DESTINATION. Unknown settings references are errors and missing settings decisions are warnings. This does not establish coverage for resource operations or application views: those kinds need their own supplied catalogues. A caller supplying no catalogue receives no coverage result, not a clean coverage result. The plan carries no file path, config key or label string — those belong to the coding task that authors the config.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"WORKSPACE_TRUTH — placement is decided against what EXISTS: the real engine settings destinations, the real resources and their operations, and the shell surfaces the application already has. A planner working from the definition artifacts alone invents destination refs that resolve to nothing, and every decision it emits is unplaceable.\",\n \"//contextSources2502\": \"CREATOR_STATED_FACTS — the user groups and the devices they use, which order the sidebar for the group that opens it most (#2502).\",\n \"//contextSources2502b\": \"APPLICATION_ENABLED_SURFACE — what the configuration switches on (capabilities, billing, sign-in methods), the capability leg of the fit test, dated by the configuration so a placement is offered again when SSO or billing is switched on (#2502).\",\n \"contextSources\": [\"workspace_truth\", \"creator_stated_facts\", \"application_enabled_surface\"],\n \"skillRefs\": [\n \"settings-placement-authoring\",\n \"config-app-shell\",\n \"config-navigation\",\n ],\n \"//deliberation\": \"Placement is DECIDED BY A PANEL, not elicited from the creator: the arrangement that is right for an application has several defensible answers, and the creator is the person least equipped to choose between them before the app exists. The information-architect OWNS the domain (so it derives the rubric); the design-system-guardian sits as the coherence memory, because where a thing goes must not fork the pattern the shipped surfaces already taught users. Three candidates, because the criteria trade off against each other — first-run discoverability, the daily-use path, and category convention pull in different directions and a single pass silently picks one.\",\n \"deliberation\": {\n \"workDomain\": \"information_architecture\",\n \"reviewerRoleRefs\": [\"information-architect\", \"design-system-guardian\"],\n \"coordinatorRoleRef\": \"design-system-guardian\",\n \"rubricDeriverRoleRef\": \"information-architect\",\n \"candidateCount\": 3\n }\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.website-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsFrB,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.website-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsFrB,CAAC"}
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.website-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,wBAAwB;IAC/B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,gkDAAgkD;IAC1kD,eAAe,EAAE;QACf;;;;;WAKG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE;QACjF;;;;WAIG;QACH,EAAE,MAAM,EAAE,kBAAkB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE,UAAU,EAAE,aAAa,EAAE,QAAQ,EAAE,QAAQ,EAAE;QACjI;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,iBAAiB,EAAE,EAAE;KAC3E;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,wBAAwB,EAAE,IAAI,EAAE,8EAA8E,EAAE;QAC5H,EAAE,QAAQ,EAAE,iBAAiB,EAAE,IAAI,EAAE,+GAA+G,EAAE;QACtJ,EAAE,QAAQ,EAAE,aAAa,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,6LAA6L,EAAE;QACjP,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,+GAA+G,EAAE;QACrJ,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,4GAA4G,EAAE;QAChJ,EAAE,QAAQ,EAAE,SAAS,EAAE,IAAI,EAAE,qMAAqM,EAAE;QACpO,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,gVAAgV,EAAE;QACpX,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,sOAAsO,EAAE;QAC5Q,EAAE,QAAQ,EAAE,aAAa,EAAE,SAAS,EAAE,CAAC,sBAAsB,EAAE,uBAAuB,CAAC,EAAE,IAAI,EAAE,2MAA2M,EAAE;QAC5S,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,iIAAiI,EAAE;QACzK,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,gLAAgL,EAAE;KACrN;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,cAAc;YACxB,WAAW,EAAE,iCAAiC;YAC9C,aAAa,EAAE,sbAAsb;SACtc;KACF;IACD,QAAQ,EAAE;QACR;;;;;;WAMG;QACH;;;;;WAKG;QACH,gBAAgB,EAAE,CAAC,mBAAmB,CAAC;QACvC;;;;;WAKG;QACH,eAAe,EAAE,CAAC,wBAAwB,CAAC;QAC3C,WAAW,EAAE;YACX,wBAAwB;YACxB,8BAA8B;YAC9B,uBAAuB;YACvB,qBAAqB;YACrB,oBAAoB;YACpB,sCAAsC;YACtC,8BAA8B;YAC9B,sBAAsB;YACtB,4BAA4B;SAC7B;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The website lane's one leaf (#1492). It reads the market snapshot the top-down lane produced —\n * positioning, ICPs, tones of voice, proofs, objections, benefits — the brand brief and the\n * business model's pricing plans, and decides WHAT THE MARKETING SITE SAYS: its pages, their\n * sections in reading order, and the market entries each section draws on.\n *\n * It does NOT write the site. `bottom_up.build-decompose` turns each page into a `WEBSITE_PAGE`\n * task and each section into a `WEBSITE_SECTION` task bound to the skill that section's KIND names,\n * because the build plan has ONE producer and a second would destroy the first's output (#895).\n *\n * The `website-*` skills the framework ships were named by NO playbook until this one — the\n * largest finished asset in the catalog with no door. The site-level ones are this method's\n * `skillRefs`; the section skills are reached through `WEBSITE_SECTION_SKILL_REF`, which is total\n * over the section vocabulary, so a kind added without its skill does not compile.\n *\n * The plan is held to a truth bar (the method's Step 4): every capability, figure and name on the\n * site is something the application declares. The marketing material cannot settle that on its own,\n * so the plan also reads what the application declares about itself: its roadmap and requirements\n * (what is built, what is next), its document facts (retention, recipients and their regions, the\n * rights it honours) and its integration plan.\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.website-plan\",\n \"version\": \"0.5.1\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has and the KIND of each (home, product overview, product area, solution by role / industry / use case / company size, pricing, contact, company, security, blog — the kind derives its route, its menu placement and its essential sections), what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Runs only once the capability composition decides the website is NEEDED (a declined website is never planned, and a plan landed before a later decline is set aside). A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact, the problem, how it works, the product shown, paths by audience, comparison, facts in figures, integrations, latest posts, roadmap) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Every capability, figure and name the plan asks a section to state must be one the application declares (its roadmap, requirements, document facts and integration plan), never a claim the marketing material makes alone. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.\",\n \"preconditions\": [\n /*\n * The COMPOSITION is the readiness gate, and its CONTENT is what this method reads first: it\n * decides whether the application has a website at all, and this plan's disposition follows it.\n * `artifact_exists` rather than `artifact_expected` for exactly that reason — the content is\n * read, so the strength is honest (the audit's own distinction, #1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"capability-composition\" } },\n /*\n * And what it DECIDED (#1606): the plan is only worth producing when the composition says the\n * application has a website. Before this gate the playbook ran anyway, only to land NOT_APPLICABLE.\n * A plan landed while the website was needed is set aside for every reader if it is later declined.\n */\n { \"kind\": \"artifact_decides\", \"selector\": { \"family\": \"capability-composition\" }, \"decision\": \"add-website\", \"equals\": \"NEEDED\" },\n /*\n * The market snapshot is the SUBSTANCE. A site planned without it would be a model inventing\n * claims about a product nobody positioned, which is the one thing every method in this lane\n * refuses.\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"market-snapshot\" } }\n ],\n \"inputs\": [\n { \"family\": \"capability-composition\", \"//\": \"Whether this application has a website, and the declaration that decided it.\" },\n { \"family\": \"market-snapshot\", \"//\": \"The substance of every section: benefits, proofs, objections, jobs, pains, ICPs, tones of voice, positioning.\" },\n { \"family\": \"brand-brief\", \"render\": \"map\", \"//\": \"Whether the product has a name and a visual tone to present. The plan needs to know it EXISTS and who it addresses; the site's own chrome is authored by the build tasks (#1424's reading).\" },\n { \"family\": \"business-model\", \"//\": \"The pricing plans a PRICING section presents — a pricing page with no plan behind it is a page about nothing.\" },\n { \"family\": \"vision-brief\", \"//\": \"The product's own one-liner and differentiation, which a hero states before any market entry qualifies it.\" },\n { \"family\": \"roadmap\", \"//\": \"What is built now and what comes next or later, in the roadmap's own horizons: a ROADMAP section states them, and a capability not built yet is planned there, never as shipped. Absent is skipped.\" },\n { \"family\": \"requirements\", \"//\": \"What the product is committed to DO (#2507), so a section states a capability the requirements back rather than one the market snapshot wishes for. A section that says what the product does cites the requirement its claim rests on; a market benefit alone says what a buyer wants, never that the product delivers it. Absent is skipped.\" },\n { \"family\": \"document-facts\", \"//\": \"How the application actually behaves with data — what it keeps and for how long, who receives it and where, which rights it honours — derived from its own declarations. The source of a security page's figures. Absent is skipped.\" },\n { \"family\": \"domain-plan\", \"aspects\": [\"domain-plan.resource\", \"domain-plan.lifecycle\"], \"//\": \"The application's resources and their lifecycles, so a section's demo names a resource the application has (`demo.resourceRef`) and a status demo shows states its lifecycle declares. Absent is skipped.\" },\n { \"family\": \"integration-plan\", \"//\": \"The providers, channels and protocols the application declares, so an INTEGRATIONS section names only those. Absent is skipped.\" },\n { \"family\": \"website-plan\", \"//\": \"Its own family: its method refines its own prior output and keeps its page refs, so it must be GIVEN that output (#1430). Input, not precondition: a first run stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"website-plan\",\n \"schemaRef\": \"saas-specifications:WebsitePlan\",\n \"description\": \"What the marketing site says: a disposition (PLANNED, or NOT_APPLICABLE when the capability composition declined a website) with its rationale, and — when planned — the pages in navigation order, each with its purpose, the ICPs it is written for, its tone of voice, and its sections in reading order. Each section carries its KIND (which names the skill that authors it), what it does for the reader, and the market entries it draws on.\"\n }\n ],\n \"method\": {\n /*\n * MARKET_FIT_SCORES — the same computation `top_down.value-proposition` consumes, and for the\n * same reason: which benefits a page should lead with is a question about fit per ICP, and a\n * structured generation has no tools to compute it. The source renders the matrix beside each\n * benefit's authored Kano category, so the plan orders sections on a measurement rather than on\n * the model's impression of one (#1435).\n */\n /*\n * Deliberately NOT `compliance_primary_facts`: that source refuses to compose when the backend cannot be\n * introspected (it fails rather than let a governed document degrade to prose), and the website plan may run\n * before a backend exists. A site plan must never be blocked on it. The `document-facts` input carries the same\n * derived facts and is simply skipped when absent.\n */\n \"contextSources\": [\"market_fit_scores\"],\n /*\n * ONE body reaches this step (#1435): `website-page-authoring` says what a page IS in this engine\n * — a manifest, a route adapter, a sections file and a label pack the build fails closed on — and\n * a plan that contradicts it plans pages nothing can author. Every other skill below is a contract\n * the CODING AGENT opens when it builds the task, so its body would be brief weight here.\n */\n \"skillBodyRefs\": [\"website-page-authoring\"],\n \"skillRefs\": [\n \"website-page-authoring\",\n \"website-navigation-authoring\",\n \"website-motion-design\",\n \"website-seo-aeo-geo\",\n \"website-label-pack\",\n \"website-marketing-metadata-extension\",\n \"market-positioning-authoring\",\n \"market-tone-of-voice\",\n \"market-proof-and-objection\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.website-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,KAAK,EAAE,wBAAwB;IAC/B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,gkDAAgkD;IAC1kD,eAAe,EAAE;QACf;;;;;WAKG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE;QACjF;;;;WAIG;QACH,EAAE,MAAM,EAAE,kBAAkB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE,UAAU,EAAE,aAAa,EAAE,QAAQ,EAAE,QAAQ,EAAE;QACjI;;;;WAIG;QACH,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,iBAAiB,EAAE,EAAE;KAC3E;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,wBAAwB,EAAE,IAAI,EAAE,8EAA8E,EAAE;QAC5H,EAAE,QAAQ,EAAE,iBAAiB,EAAE,IAAI,EAAE,+GAA+G,EAAE;QACtJ,EAAE,QAAQ,EAAE,aAAa,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,6LAA6L,EAAE;QACjP,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,+GAA+G,EAAE;QACrJ,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,4GAA4G,EAAE;QAChJ,EAAE,QAAQ,EAAE,SAAS,EAAE,IAAI,EAAE,qMAAqM,EAAE;QACpO,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,gVAAgV,EAAE;QACpX,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,sOAAsO,EAAE;QAC5Q,EAAE,QAAQ,EAAE,aAAa,EAAE,SAAS,EAAE,CAAC,sBAAsB,EAAE,uBAAuB,CAAC,EAAE,IAAI,EAAE,2MAA2M,EAAE;QAC5S,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,iIAAiI,EAAE;QACzK,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,gLAAgL,EAAE;KACrN;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,cAAc;YACxB,WAAW,EAAE,iCAAiC;YAC9C,aAAa,EAAE,sbAAsb;SACtc;KACF;IACD,QAAQ,EAAE;QACR;;;;;;WAMG;QACH;;;;;WAKG;QACH,gBAAgB,EAAE,CAAC,mBAAmB,CAAC;QACvC;;;;;WAKG;QACH,eAAe,EAAE,CAAC,wBAAwB,CAAC;QAC3C,WAAW,EAAE;YACX,wBAAwB;YACxB,8BAA8B;YAC9B,uBAAuB;YACvB,qBAAqB;YACrB,oBAAoB;YACpB,sCAAsC;YACtC,8BAA8B;YAC9B,sBAAsB;YACtB,4BAA4B;SAC7B;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The website lane's one leaf (#1492). It reads the market snapshot the top-down lane produced —\n * positioning, ICPs, tones of voice, proofs, objections, benefits — the brand brief and the\n * business model's pricing plans, and decides WHAT THE MARKETING SITE SAYS: its pages, their\n * sections in reading order, and the market entries each section draws on.\n *\n * It does NOT write the site. `bottom_up.build-decompose` turns each page into a `WEBSITE_PAGE`\n * task and each section into a `WEBSITE_SECTION` task bound to the skill that section's KIND names,\n * because the build plan has ONE producer and a second would destroy the first's output (#895).\n *\n * The `website-*` skills the framework ships were named by NO playbook until this one — the\n * largest finished asset in the catalog with no door. The site-level ones are this method's\n * `skillRefs`; the section skills are reached through `WEBSITE_SECTION_SKILL_REF`, which is total\n * over the section vocabulary, so a kind added without its skill does not compile.\n *\n * The plan is held to a truth bar (the method's Step 4): every capability, figure and name on the\n * site is something the application declares. The marketing material cannot settle that on its own,\n * so the plan also reads what the application declares about itself: its roadmap and requirements\n * (what is built, what is next), its document facts (retention, recipients and their regions, the\n * rights it honours) and its integration plan.\n */\nexport const playbookDefinition = {\n \"ref\": \"bottom_up.website-plan\",\n \"version\": \"0.5.1\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has and the KIND of each (home, product overview, product area, solution by role / industry / use case / company size, pricing, contact, company, security, blog — the kind derives its route, its menu placement and its essential sections), what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Runs only once the capability composition decides the website is NEEDED (a declined website is never planned, and a plan landed before a later decline is set aside). A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact, the problem, how it works, the product shown, paths by audience, comparison, facts in figures, integrations, latest posts, roadmap) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Every capability, figure and name the plan asks a section to state must be one the application declares (its roadmap, requirements, document facts and integration plan), never a claim the marketing material makes alone. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.\",\n \"preconditions\": [\n /*\n * The COMPOSITION is the readiness gate, and its CONTENT is what this method reads first: it\n * decides whether the application has a website at all, and this plan's disposition follows it.\n * `artifact_exists` rather than `artifact_expected` for exactly that reason — the content is\n * read, so the strength is honest (the audit's own distinction, #1434).\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"capability-composition\" } },\n /*\n * And what it DECIDED (#1606): the plan is only worth producing when the composition says the\n * application has a website. Before this gate the playbook ran anyway, only to land NOT_APPLICABLE.\n * A plan landed while the website was needed is set aside for every reader if it is later declined.\n */\n { \"kind\": \"artifact_decides\", \"selector\": { \"family\": \"capability-composition\" }, \"decision\": \"add-website\", \"equals\": \"NEEDED\" },\n /*\n * The market snapshot is the SUBSTANCE. A site planned without it would be a model inventing\n * claims about a product nobody positioned, which is the one thing every method in this lane\n * refuses.\n */\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"market-snapshot\" } }\n ],\n \"inputs\": [\n { \"family\": \"capability-composition\", \"//\": \"Whether this application has a website, and the declaration that decided it.\" },\n { \"family\": \"market-snapshot\", \"//\": \"The substance of every section: benefits, proofs, objections, jobs, pains, ICPs, tones of voice, positioning.\" },\n { \"family\": \"brand-brief\", \"render\": \"map\", \"//\": \"Whether the product has a name and a visual tone to present. The plan needs to know it EXISTS and who it addresses; the site's own chrome is authored by the build tasks (#1424's reading).\" },\n { \"family\": \"business-model\", \"//\": \"The pricing plans a PRICING section presents — a pricing page with no plan behind it is a page about nothing.\" },\n { \"family\": \"vision-brief\", \"//\": \"The product's own one-liner and differentiation, which a hero states before any market entry qualifies it.\" },\n { \"family\": \"roadmap\", \"//\": \"What is built now and what comes next or later, in the roadmap's own horizons: a ROADMAP section states them, and a capability not built yet is planned there, never as shipped. Absent is skipped.\" },\n { \"family\": \"requirements\", \"//\": \"What the product is committed to DO (#2507), so a section states a capability the requirements back rather than one the market snapshot wishes for. A section that says what the product does cites the requirement its claim rests on; a market benefit alone says what a buyer wants, never that the product delivers it. Absent is skipped.\" },\n { \"family\": \"document-facts\", \"//\": \"How the application actually behaves with data — what it keeps and for how long, who receives it and where, which rights it honours — derived from its own declarations. The source of a security page's figures. Absent is skipped.\" },\n { \"family\": \"domain-plan\", \"aspects\": [\"domain-plan.resource\", \"domain-plan.lifecycle\"], \"//\": \"The application's resources and their lifecycles, so a section's demo names a resource the application has (`demo.resourceRef`) and a status demo shows states its lifecycle declares. Absent is skipped.\" },\n { \"family\": \"integration-plan\", \"//\": \"The providers, channels and protocols the application declares, so an INTEGRATIONS section names only those. Absent is skipped.\" },\n { \"family\": \"website-plan\", \"//\": \"Its own family: its method refines its own prior output and keeps its page refs, so it must be GIVEN that output (#1430). Input, not precondition: a first run stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"website-plan\",\n \"schemaRef\": \"saas-specifications:WebsitePlan\",\n \"description\": \"What the marketing site says: a disposition (PLANNED, or NOT_APPLICABLE when the capability composition declined a website) with its rationale, and — when planned — the pages in navigation order, each with its purpose, the ICPs it is written for, its tone of voice, and its sections in reading order. Each section carries its KIND (which names the skill that authors it), what it does for the reader, and the market entries it draws on.\"\n }\n ],\n \"method\": {\n /*\n * MARKET_FIT_SCORES — the same computation `top_down.value-proposition` consumes, and for the\n * same reason: which benefits a page should lead with is a question about fit per ICP, and a\n * structured generation has no tools to compute it. The source renders the matrix beside each\n * benefit's authored Kano category, so the plan orders sections on a measurement rather than on\n * the model's impression of one (#1435).\n */\n /*\n * Deliberately NOT `compliance_primary_facts`: that source refuses to compose when the backend cannot be\n * introspected (it fails rather than let a governed document degrade to prose), and the website plan may run\n * before a backend exists. A site plan must never be blocked on it. The `document-facts` input carries the same\n * derived facts and is simply skipped when absent.\n */\n \"contextSources\": [\"market_fit_scores\"],\n /*\n * ONE body reaches this step (#1435): `website-page-authoring` says what a page IS in this engine\n * — a manifest, a route adapter, a sections file and a label pack the build fails closed on — and\n * a plan that contradicts it plans pages nothing can author. Every other skill below is a contract\n * the CODING AGENT opens when it builds the task, so its body would be brief weight here.\n */\n \"skillBodyRefs\": [\"website-page-authoring\"],\n \"skillRefs\": [\n \"website-page-authoring\",\n \"website-navigation-authoring\",\n \"website-motion-design\",\n \"website-seo-aeo-geo\",\n \"website-label-pack\",\n \"website-marketing-metadata-extension\",\n \"market-positioning-authoring\",\n \"market-tone-of-voice\",\n \"market-proof-and-objection\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -11,9 +11,10 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase } from '@wildo-ai/saas-spe
11
11
  *
12
12
  * ## It admits LANES, and the waterfall is the lanes' own preconditions
13
13
  *
14
- * | lane | opens when |
14
+ * | child | opens when |
15
15
  * |---|---|
16
- * | `top_down.definition` | always — it starts at the vision interview, so a fresh application begins here |
16
+ * | `top_down.vision-elicitation` | always — a leaf, not a lane: the vision interview, so a fresh application begins here |
17
+ * | `top_down.definition` | a VALID vision |
17
18
  * | `cross_cutting.compliance` | a VALID vision — so it plays BESIDE the definition rather than after it |
18
19
  * | `bottom_up.conception` | valid requirements + market snapshot, the definition lane's landings |
19
20
  * | `bottom_up.build` | a valid domain plan + placement plan, the conception lane's landings |
@@ -22,6 +23,30 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase } from '@wildo-ai/saas-spe
22
23
  * tree after every round, and that IS the waterfall — which is also what makes the root re-runnable on
23
24
  * an application at any stage: whatever is on record satisfies the gates of whatever is not.
24
25
  *
26
+ * ## The vision lands in a round of its own, so the definition and compliance start together (#3386)
27
+ *
28
+ * The vision is the one family both early lanes need, and until #3386 it was written INSIDE the definition
29
+ * lane. A round waits for its lanes, so compliance (gated on the vision) could not be offered until the
30
+ * whole definition had returned: 24 minutes of market, requirements and roadmap on run 42120979649, while
31
+ * regime research needed only the vision, which was on record minutes in.
32
+ *
33
+ * So the root admits the interview itself, and the definition lane gates on a valid vision. On a fresh
34
+ * application the interview is then the ONLY thing eligible, by preconditions rather than by the selector's
35
+ * judgement; the round after it offers the definition and compliance lanes, whose write scopes are disjoint
36
+ * since #3362, so they share it. Nothing but the interview writes the vision, so no later landing of the
37
+ * definition re-stales the compliance lane's research (`compliance-posture-catalog.test.ts` pins the single
38
+ * writer; `creation-root-vision-round…test.ts` pins the rounds).
39
+ *
40
+ * Rejected: letting the root re-select mid-round once the vision lands inside a running definition lane.
41
+ * It needs the runtime to start a lane while a round is in flight, which nothing else needs, and it is
42
+ * correct only as fast as the selector notices. Lifting the interview needs no measurement to be right.
43
+ *
44
+ * The definition lane still ADMITS the interview, for two reasons: a re-answered interview is a REFRESH it
45
+ * may run when it is driven on its own, and the creation timeline attributes a playbook to the phase whose
46
+ * lane reaches it (`classifyPlaybookRefsByJourneyPhase`), so the vision stays definition work. Two admitters
47
+ * cannot land it twice in one round: both write the vision, so the disjointness admission never pairs them,
48
+ * and inside the lane a vision landed by the root is CURRENT and withheld.
49
+ *
25
50
  * ## Depth 3, because the deepest path is root → lane → umbrella → leaves
26
51
  *
27
52
  * A composite child is WITHHELD when `depth + 1` reaches the ceiling, and the ceiling is the tightest
@@ -30,15 +55,25 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase } from '@wildo-ai/saas-spe
30
55
  * `2` would silently withhold `top_down.market-analysis` from inside the definition lane and the
31
56
  * market snapshot would never land; declaring more would permit a level nothing in the catalog has.
32
57
  *
33
- * ## Two lanes CANNOT share a round, and that is correct rather than a limitation
58
+ * ## Two lanes per round (#3384), the build always one of them while it can dispatch
59
+ *
60
+ * The disjointness admission resolves a child's write scope transitively through `admits`. Until #3362
61
+ * the definition lane claimed `vision-brief` (through `vision-elicitation`) and the compliance lane
62
+ * claimed it too (through `compliance-posture`, which recorded the regimes ON the vision), so the two
63
+ * could never share a round. The posture now lands in its own `compliance-posture` family, so a round
64
+ * runs two lanes whose write scopes are disjoint, and an overlapping pair is refused by the admission
65
+ * and re-selected next round.
66
+ *
67
+ * A round waits for both of its lanes, so pairing matters most for the BUILD: one lane per round left
68
+ * it idle while the compliance lane ran (reference run 42218788356: 32 of 98 tasks landed, 27 ready, 40
69
+ * idle minutes).
34
70
  *
35
- * The disjointness admission resolves a child's write scope transitively through `admits`, so the
36
- * definition lane claims `vision-brief` (through `vision-elicitation`) and the compliance lane claims
37
- * it too (through `compliance-posture`, which records the applicable regimes ON the vision). They
38
- * overlap, so the admission runs them in successive rounds instead of concurrently — a refused child
39
- * is not lost, it was never marked delivered and is re-selected next round against the sibling's
40
- * landing. "Beside" therefore means *interleaved across rounds of one root run*, never *in the same
41
- * round*, and the compliance lane's own gate is what lets it start before the definition finishes.
71
+ * What the admission refuses is two lanes that WRITE the same family; a lane may read what the other
72
+ * rewrites. So compliance pairs with any lane, the definition pairs with the conception or the build, and
73
+ * only the conception and the build never pair (both admit the staffing step). A lane reading a family
74
+ * its partner rewrites reads it as it stood when its leaf ran: the build's decomposer reads the compliance
75
+ * posture, and a posture landed beside it makes the plan a REFRESH for a later round, which is the same
76
+ * catch-up any landing in an earlier round already gets.
42
77
  *
43
78
  * ## It ends on the MATURITY READING, which is a stage and never a "done"
44
79
  *
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/cross_cutting.application-creation/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,8BAA8B,EAC9B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiEG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqH9B,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/cross_cutting.application-creation/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,8BAA8B,EAC9B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoGG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0H9B,CAAC"}
@@ -11,9 +11,10 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-sp
11
11
  *
12
12
  * ## It admits LANES, and the waterfall is the lanes' own preconditions
13
13
  *
14
- * | lane | opens when |
14
+ * | child | opens when |
15
15
  * |---|---|
16
- * | `top_down.definition` | always — it starts at the vision interview, so a fresh application begins here |
16
+ * | `top_down.vision-elicitation` | always — a leaf, not a lane: the vision interview, so a fresh application begins here |
17
+ * | `top_down.definition` | a VALID vision |
17
18
  * | `cross_cutting.compliance` | a VALID vision — so it plays BESIDE the definition rather than after it |
18
19
  * | `bottom_up.conception` | valid requirements + market snapshot, the definition lane's landings |
19
20
  * | `bottom_up.build` | a valid domain plan + placement plan, the conception lane's landings |
@@ -22,6 +23,30 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-sp
22
23
  * tree after every round, and that IS the waterfall — which is also what makes the root re-runnable on
23
24
  * an application at any stage: whatever is on record satisfies the gates of whatever is not.
24
25
  *
26
+ * ## The vision lands in a round of its own, so the definition and compliance start together (#3386)
27
+ *
28
+ * The vision is the one family both early lanes need, and until #3386 it was written INSIDE the definition
29
+ * lane. A round waits for its lanes, so compliance (gated on the vision) could not be offered until the
30
+ * whole definition had returned: 24 minutes of market, requirements and roadmap on run 42120979649, while
31
+ * regime research needed only the vision, which was on record minutes in.
32
+ *
33
+ * So the root admits the interview itself, and the definition lane gates on a valid vision. On a fresh
34
+ * application the interview is then the ONLY thing eligible, by preconditions rather than by the selector's
35
+ * judgement; the round after it offers the definition and compliance lanes, whose write scopes are disjoint
36
+ * since #3362, so they share it. Nothing but the interview writes the vision, so no later landing of the
37
+ * definition re-stales the compliance lane's research (`compliance-posture-catalog.test.ts` pins the single
38
+ * writer; `creation-root-vision-round…test.ts` pins the rounds).
39
+ *
40
+ * Rejected: letting the root re-select mid-round once the vision lands inside a running definition lane.
41
+ * It needs the runtime to start a lane while a round is in flight, which nothing else needs, and it is
42
+ * correct only as fast as the selector notices. Lifting the interview needs no measurement to be right.
43
+ *
44
+ * The definition lane still ADMITS the interview, for two reasons: a re-answered interview is a REFRESH it
45
+ * may run when it is driven on its own, and the creation timeline attributes a playbook to the phase whose
46
+ * lane reaches it (`classifyPlaybookRefsByJourneyPhase`), so the vision stays definition work. Two admitters
47
+ * cannot land it twice in one round: both write the vision, so the disjointness admission never pairs them,
48
+ * and inside the lane a vision landed by the root is CURRENT and withheld.
49
+ *
25
50
  * ## Depth 3, because the deepest path is root → lane → umbrella → leaves
26
51
  *
27
52
  * A composite child is WITHHELD when `depth + 1` reaches the ceiling, and the ceiling is the tightest
@@ -30,15 +55,25 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-sp
30
55
  * `2` would silently withhold `top_down.market-analysis` from inside the definition lane and the
31
56
  * market snapshot would never land; declaring more would permit a level nothing in the catalog has.
32
57
  *
33
- * ## Two lanes CANNOT share a round, and that is correct rather than a limitation
58
+ * ## Two lanes per round (#3384), the build always one of them while it can dispatch
59
+ *
60
+ * The disjointness admission resolves a child's write scope transitively through `admits`. Until #3362
61
+ * the definition lane claimed `vision-brief` (through `vision-elicitation`) and the compliance lane
62
+ * claimed it too (through `compliance-posture`, which recorded the regimes ON the vision), so the two
63
+ * could never share a round. The posture now lands in its own `compliance-posture` family, so a round
64
+ * runs two lanes whose write scopes are disjoint, and an overlapping pair is refused by the admission
65
+ * and re-selected next round.
66
+ *
67
+ * A round waits for both of its lanes, so pairing matters most for the BUILD: one lane per round left
68
+ * it idle while the compliance lane ran (reference run 42218788356: 32 of 98 tasks landed, 27 ready, 40
69
+ * idle minutes).
34
70
  *
35
- * The disjointness admission resolves a child's write scope transitively through `admits`, so the
36
- * definition lane claims `vision-brief` (through `vision-elicitation`) and the compliance lane claims
37
- * it too (through `compliance-posture`, which records the applicable regimes ON the vision). They
38
- * overlap, so the admission runs them in successive rounds instead of concurrently — a refused child
39
- * is not lost, it was never marked delivered and is re-selected next round against the sibling's
40
- * landing. "Beside" therefore means *interleaved across rounds of one root run*, never *in the same
41
- * round*, and the compliance lane's own gate is what lets it start before the definition finishes.
71
+ * What the admission refuses is two lanes that WRITE the same family; a lane may read what the other
72
+ * rewrites. So compliance pairs with any lane, the definition pairs with the conception or the build, and
73
+ * only the conception and the build never pair (both admit the staffing step). A lane reading a family
74
+ * its partner rewrites reads it as it stood when its leaf ran: the build's decomposer reads the compliance
75
+ * posture, and a posture landed beside it makes the plan a REFRESH for a later round, which is the same
76
+ * catch-up any landing in an earlier round already gets.
42
77
  *
43
78
  * ## It ends on the MATURITY READING, which is a stage and never a "done"
44
79
  *
@@ -68,9 +103,9 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-sp
68
103
  */
69
104
  export const playbookDefinition = {
70
105
  ref: 'cross_cutting.application-creation',
71
- version: '0.1.0',
106
+ version: '0.3.0',
72
107
  phase: MetaWorkflow_Phase.CROSS_CUTTING,
73
- intent: 'Create the application: drive the definition (vision, market, requirements, capabilities, business model, roadmap, phase gate), the compliance posture and its governed documents, the conception (domain plan, foundation, placement) and the build (decompose, dispatch, assemble) as four LANES, each of which drives its own leaves. An umbrella over umbrellas: it authors nothing itself, and the order between the lanes is decided by their own preconditions against the working tree rather than declared here — the definition lane opens on a fresh application, compliance opens on a valid vision and runs beside it, conception opens once requirements and the market snapshot are on record, the build once the domain and placement plans are. Select the lane that can advance the application FURTHEST from what is on record, and prefer a lane that is waiting on nothing to one waiting on the creator. A lane is a long run: expect one lane per round, and do not re-select a lane that has just landed its families. STOP when no lane can advance the application — that is a STAGE the maturity reading names, never a finished application.',
108
+ intent: 'Create the application: elicit the vision, then drive the definition (market, requirements, capabilities, business model, roadmap, phase gate), the compliance posture and its governed documents, the conception (domain plan, foundation, placement) and the build (decompose, dispatch, assemble) as four LANES, each of which drives its own leaves. An umbrella over umbrellas: it authors nothing itself, and the order between the lanes is decided by their own preconditions against the working tree rather than declared here — on a fresh application only the vision interview can run, and it runs alone; the definition and compliance lanes both open on a valid vision and run side by side, conception opens once requirements and the market snapshot are on record, the build once the domain and placement plans are. Select up to TWO lanes per round whose work does not overlap: while the build lane can dispatch a task, it is always one of them, and the other is the lane that can advance the application furthest (compliance pairs with any lane). Prefer a lane that is waiting on nothing to one waiting on the creator. Do not re-select a lane that has just landed its families, except the build lane while tasks remain to dispatch. STOP when no lane can advance the application — that is a STAGE the maturity reading names, never a finished application.',
74
109
  // None. The root must be eligible on an empty application: that is the whole point of a ref that
75
110
  // means "create the application". Every gate below it is a lane's own.
76
111
  preconditions: [],
@@ -81,6 +116,7 @@ export const playbookDefinition = {
81
116
  */
82
117
  inputs: [
83
118
  { family: 'vision-brief' },
119
+ { family: 'compliance-posture', render: MetaWorkflow_InputRender.MAP },
84
120
  { family: 'market-snapshot', render: MetaWorkflow_InputRender.MAP },
85
121
  { family: 'requirements', render: MetaWorkflow_InputRender.MAP },
86
122
  { family: 'roadmap', render: MetaWorkflow_InputRender.MAP },
@@ -105,21 +141,22 @@ export const playbookDefinition = {
105
141
  'bottom_up.conception',
106
142
  'cross_cutting.compliance',
107
143
  'top_down.definition',
144
+ // A LEAF beside the lanes (#3386): the vision lands in its own round, so the two lanes that need it start together.
145
+ 'top_down.vision-elicitation',
108
146
  ],
109
147
  /*
110
148
  * Each lane is itself a bounded run, so this count is rounds-of-lanes, not rounds-of-work: four
111
- * lanes, plus the rounds where one lane is re-selected after another unblocked it (compliance's
112
- * document half after conception lands the domain plan; the build lane after a coherence gap
113
- * re-opens conception). Ten is headroom over the six a straight-through creation needs.
149
+ * lanes and the vision round, plus the rounds where one lane is re-selected after another unblocked it
150
+ * (compliance's document half after conception lands the domain plan; the build lane after a coherence
151
+ * gap re-opens conception). Ten is headroom over the seven a straight-through creation needs.
114
152
  */
115
153
  maximumIterations: 10,
116
154
  /*
117
- * ONE lane per round. Not a safety bound — the disjointness admission already refuses an overlap
118
- * — but an honest one: the definition and compliance lanes overlap on `vision-brief` and the
119
- * other pairs are strictly sequential, so a wider round would propose lanes that are dropped and
120
- * re-selected, spending a selection to learn what this declaration already knows.
155
+ * TWO lanes per round (#3384). Not a safety bound: the disjointness admission refuses a pair that
156
+ * writes a common family. Two rather than three: a round waits for its slowest lane, and the coding
157
+ * runs of the build share the machine with whatever runs beside them.
121
158
  */
122
- maximumLanesPerIteration: 1,
159
+ maximumLanesPerIteration: 2,
123
160
  /*
124
161
  * Three levels below this one: a lane, an umbrella inside it, and the umbrella's leaves. See the
125
162
  * depth note above — `2` would silently withhold the market umbrella from inside the definition
@@ -140,7 +177,10 @@ export const playbookDefinition = {
140
177
  * Across lanes (#1627): the definition lane exports its phase gate's verdict, and a GAP on
141
178
  * compliance presence is the compliance lane's to answer. The compliance lane is re-offered with
142
179
  * the criterion named in the round history, and its own selector picks the leaf. GAP only, as in
143
- * the lane: CONCERN is advice and INDETERMINATE is missing evidence.
180
+ * the lane: CONCERN is advice and INDETERMINATE is missing evidence. Since #3362 the posture the
181
+ * compliance lane lands is in its own family, which the gate does not read, so the GAP does not
182
+ * clear: it is the one-shot signal "run the compliance lane", fired once per settlement of the
183
+ * definition lane, and a compliance lane whose leaves have landed answers it with nothing to do.
144
184
  */
145
185
  reopenOnVerdict: [
146
186
  {