@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
@@ -32,6 +32,9 @@
32
32
  },
33
33
  {
34
34
  "family": "brand-name-screening"
35
+ },
36
+ {
37
+ "family": "risk-register"
35
38
  }
36
39
  ],
37
40
  "outputs": [
@@ -43,9 +46,10 @@
43
46
  ],
44
47
  "stepOutputs": [],
45
48
  "method": {
46
- "guidance": "# Complete the risk register\n\nThe derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.\n\nThis step writes what they mean for this product and these users, and proposes the risks no derivation reaches.\n\n## You are drafting, not deciding\n\nA model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:\n\n- Write statements a reader can argue with. \"Personal data is processed by third parties\" is unarguable and says nothing; \"two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely\" is a claim someone can check and correct.\n- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.\n- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.\n\nAfter landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.\n\n## Two kinds of entry, and the difference is what may be believed\n\n**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.\n\n**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.\n\n### The brand name is a derived signal\n\n`application:brand-name-trademark-standing` says where the brand's chosen name stands\nagainst its minimal trademark screening. It is computed by matching the brand name to its\nscreened candidate. When the signal reports the exposure as PRESENT, complete it into a\n**SIGNAL_DERIVED** entry with that `signalRef`. Do not write a PROPOSED one: the standing is\nmeasured, and a later run re-derives it.\n\n- **kept despite a conflict**: name the conflicting marks and registers from the signal's\n detail and the screening in your brief. Say what the exposure means for THIS product: an\n opposition, a cease-and-desist, a forced rebrand after launch.\n- **screening incomplete**: name the jurisdictions or registers not covered, and say the\n name is not cleared there.\n- **conflict unacknowledged**: the screening now finds a conflict that nobody chose to keep\n (the brand was named before a re-screen found it). Say so. Do not describe it as the\n creator's decision, because it was not one.\n- **never screened**: say so plainly.\n\nA cleared name, or a line with no brand, needs no entry. Never weigh a present exposure as\n\"low\" on the grounds that a screening ran: a screening is not a clearance.\n\n## Weighting is two qualitative bands and NOTHING is multiplied\n\nLikelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.\n\nGround the bands in what is IMPLEMENTED, not in how the risk sounds. \"Impact HIGH because the erasure path is manual\" is grounded. \"Impact HIGH because data breaches are serious\" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.\n\nWhere the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.\n\n## The signals, and what to do when they are not all there\n\nThe derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.\n\nFour of them always arrive: three are read from the application's configuration (its capabilities, retention and provider hosting) and one from its specifications (the brand name's trademark standing). The ones that need every resource materialized — the personal-data inventory and its declaration gap, the MCP exposure and the chat-command exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.\n\nThe register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.\n\nDo not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.\n\n## What belongs to other mechanisms\n\n- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.\n- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.\n- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.\n- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.\n",
49
+ "guidance": "# Complete the risk register\n\nThe derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.\n\nThis step writes what they mean for this product and these users, and proposes the risks no derivation reaches.\n\n## You are drafting, not deciding\n\nA model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:\n\n- Write statements a reader can argue with. \"Personal data is processed by third parties\" is unarguable and says nothing; \"two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely\" is a claim someone can check and correct.\n- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.\n- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.\n\nAfter landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.\n\n## Two kinds of entry, and the difference is what may be believed\n\n**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.\n\n**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.\n\n### The brand name is a derived signal\n\n`application:brand-name-trademark-standing` says where the brand's chosen name stands\nagainst its minimal trademark screening. It is computed by matching the brand name to its\nscreened candidate. When the signal reports the exposure as PRESENT, complete it into a\n**SIGNAL_DERIVED** entry with that `signalRef`. Do not write a PROPOSED one: the standing is\nmeasured, and a later run re-derives it.\n\n- **kept despite a conflict**: name the conflicting marks and registers from the signal's\n detail and the screening in your brief. Say what the exposure means for THIS product: an\n opposition, a cease-and-desist, a forced rebrand after launch.\n- **screening incomplete**: name the jurisdictions or registers not covered, and say the\n name is not cleared there.\n- **conflict unacknowledged**: the screening now finds a conflict that nobody chose to keep\n (the brand was named before a re-screen found it). Say so. Do not describe it as the\n creator's decision, because it was not one.\n- **never screened**: say so plainly.\n\nA cleared name, or a line with no brand, needs no entry. Never weigh a present exposure as\n\"low\" on the grounds that a screening ran: a screening is not a clearance.\n\n## Weighting is two qualitative bands and NOTHING is multiplied\n\nLikelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.\n\nGround the bands in what is IMPLEMENTED, not in how the risk sounds. \"Impact HIGH because the erasure path is manual\" is grounded. \"Impact HIGH because data breaches are serious\" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.\n\nWhere the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.\n\n## The signals, and what to do when they are not all there\n\nThe derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.\n\nFour of them always arrive: three are read from the application's configuration (its capabilities, retention and provider hosting) and one from its specifications (the brand name's trademark standing). The ones that need every resource materialized — the personal-data inventory and its declaration gap, the MCP exposure and the chat-command exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.\n\nThe register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.\n\nDo not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.\n\n## What belongs to other mechanisms\n\n- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.\n- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.\n- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.\n- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.\n\n## Refine, don't re-author\n\nWhen a risk register is already on record, it is an input of this run: refine it. Keep every ref that still names\nthe same thing, because other artifacts and committed work name it: the audit plan, the evidence demands and the documents that cite an entry. Mint a new ref only for something\nthat did not exist before, and drop one only when its subject is gone. A reworded entry under a new ref reads\neverywhere downstream as one thing removed and another added (#3449).\n",
47
50
  "skillRefs": [],
48
51
  "skillBodyRefs": [],
52
+ "derivedFromAnswers": [],
49
53
  "contextSources": [
50
54
  "risk_signals"
51
55
  ],
@@ -70,10 +70,15 @@
70
70
  "ref": "delivery-pressure",
71
71
  "question": "Is there a date, an event, or a commitment the first release has to meet? Answer \"none\" if the plan is shaped by scope rather than by a deadline.",
72
72
  "kind": "free_text",
73
- "depth": "detail"
73
+ "depth": "detail",
74
+ "nonAnswers": [
75
+ "not_applicable",
76
+ "deferred"
77
+ ]
74
78
  }
75
79
  ]
76
80
  },
81
+ "derivedFromAnswers": [],
77
82
  "contextSources": [
78
83
  "market_fit_scores"
79
84
  ],
@@ -43,6 +43,17 @@ as they are; they will review them.
43
43
  If an answer says "propose it", the creator delegated that part: propose it from the services. If the
44
44
  interview says "none", write none — an empty list is an answer.
45
45
 
46
+ An answer left **NOT DECIDED YET** is not "none", and the method must not read as if it were. Say it is
47
+ owed in `owed`:
48
+
49
+ - `signatories` not decided yet → `owed` includes `QUALIFIED_DECISIONS`. Write only the decisions and
50
+ qualifications the creator's other answers name; never invent a qualified decision to fill the gap.
51
+ - `agent-work` not decided yet → `owed` includes `AGENT_WORK`. A step the client does still names
52
+ `CLIENT`; a step of the firm's work whose performer waits on that answer names **no** `performedBy` and
53
+ no `agentShape`. Never decide for the creator which work an agent does.
54
+
55
+ `owed` is empty when every answer was given.
56
+
46
57
  ## Step 1 — One service per thing the firm sells
47
58
 
48
59
  Each service is one entry in `services`:
@@ -70,7 +81,8 @@ service.
70
81
 
71
82
  ## Step 3 — The steps, and who carries each one
72
83
 
73
- Each step happens in one stage and is performed by exactly one of:
84
+ Each step happens in one stage and is performed by exactly one of (or, while `AGENT_WORK` is owed, by
85
+ none yet):
74
86
 
75
87
  | `performedBy` | means |
76
88
  |---|---|
@@ -139,6 +151,10 @@ the `holidays` as dates (`YYYY-MM-DD`). When the creator names a calendar ("Fren
139
151
  write out its dates for the current and next year. A decision with no deadline is allowed, and it is marked:
140
152
  the engine's default lapse and reminders apply.
141
153
 
154
+ When `working-hours` is NOT DECIDED YET, write no `reviewCalendar` and never invent one: give each deadline on
155
+ `elapsed` time, or leave it out. A business-time deadline needs the calendar the creator has not given, and the
156
+ method is refused with one.
157
+
142
158
  ## Step 5 — What the client receives, what is kept, and what it costs
143
159
 
144
160
  - `deliverables` — what a case produces for the client, at which stage, from which planned resource
@@ -175,6 +191,7 @@ One `ServiceMethod`. The schema refuses:
175
191
 
176
192
  - a step in a stage the service does not declare, and a deliverable at one;
177
193
  - an agent step without an `agentShape`, and any other step with one;
194
+ - a step with no `performedBy` when `owed` does not include `AGENT_WORK`;
178
195
  - a decision at a step the service does not declare;
179
196
  - an `owner` decision naming a qualification, a `role` or `assignee` decision naming none, and a
180
197
  qualification the method does not declare;
@@ -193,6 +210,7 @@ Fix the cause it names and answer again.
193
210
  - Every service's `purpose` says what the client gets.
194
211
  - Every decision the `signatories` answer named is a decision point, with the role, and the professional
195
212
  qualification when the answer named a profession.
213
+ - Every answer left not decided yet is in `owed`, and nothing it would have decided was invented.
196
214
  - No agent step decides anything a decision point decides.
197
215
  - Every `role` and `assignee` decision names a declared qualification; every qualification is used.
198
216
  - Every reviewer decision that keeps a client waiting has a deadline, or the creator said it has none.
@@ -39,7 +39,7 @@
39
39
  ],
40
40
  "stepOutputs": [],
41
41
  "method": {
42
- "guidance": "# Service Method — How the Firm Works\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this playbook does\n\nYou are writing down the firm's **method**: the services it sells to its clients and, for each, how a\ncase is worked. The output is one `ServiceMethod`. It is the one place the method is written down; the\ndomain plan, the roles and the build plan derive from it, so a method that is vague here is an\napplication that is vague everywhere.\n\nA firm is not a product its users drive alone. A case is opened for a client, agents and the firm's\npeople work it, a qualified person takes the decisions that carry the firm's responsibility, and the\nclient receives something at the end. Write that down, case by case.\n\n## What the creator decides, and what you draft\n\nThe interview has four questions:\n\n- **`services`** — what the firm sells, what starts a case and what ends it.\n- **`signatories`** — which decisions only a qualified person may take, and what that person must be.\n- **`agent-work`** — which work in a case the creator wants agents to do.\n- **`working-hours`** — where and when the firm's reviewers work.\n\nAn answer the creator gave is theirs: build on it, do not second-guess it. An answer recorded as an\nASSUMPTION (proposed, because the creator did not know or chose a quick interview) is a proposal: use it,\nand keep anything resting on it easy to revise. `agent-work` and `working-hours` are usually assumptions.\n\nEverything else you DRAFT from those answers, the vision and the market: the stages, the steps, the\ndeliverables, the evidence retention, the correction reasons. Draft them so the creator can accept them\nas they are; they will review them.\n\nIf an answer says \"propose it\", the creator delegated that part: propose it from the services. If the\ninterview says \"none\", write none — an empty list is an answer.\n\n## Step 1 — One service per thing the firm sells\n\nEach service is one entry in `services`:\n\n- `serviceRef` — a kebab-case key (`month-end-close`, `annual-audit`). Later families name it.\n- `label` — what the firm calls it.\n- `purpose` — what the CLIENT gets, in one sentence. Not what the firm does: \"the client's books closed\n every month, reconciled and signed off\", not \"we reconcile bank lines\".\n\nTwo services the creator described as one are one service. Do not split a service to look thorough.\n\n## Step 2 — The case, and its stages\n\n`case` is the unit of work a service is delivered in: one close, one audit engagement, one filing.\n\n- `caseRef` — the PLANNED RESOURCE whose rows are the cases, in the domain plan's naming (plural,\n kebab-case: `closes`, `audit-engagements`). The domain plan inventories it and the build plan makes it\n the work unit, the record every model call on the case is costed to.\n- `opensWhen` / `closesWhen` — the events, in the creator's words.\n\n`stages` are the states a case moves through, in order, first stage first. Each has a `meaning`: what is\ntrue of a case in that stage. Include the stage a case returns to when something surfaces after it was\nfinished (\"reopened\") when the creator's work has one. Stage refs are kebab-case and unique within the\nservice.\n\n## Step 3 — The steps, and who carries each one\n\nEach step happens in one stage and is performed by exactly one of:\n\n| `performedBy` | means |\n|---|---|\n| `AGENT` | an agent of the application does it. Say how it runs in `agentShape` |\n| `PERSON` | one of the firm's people does it |\n| `CLIENT` | the client does it (sends documents, answers a question) |\n\nAn agent step names its `agentShape`, and no other step does:\n\n- `AUTONOMOUS` — it runs on its own, on a schedule or an event (reconciling every night, reading every\n document that arrives);\n- `CHAT_ASSISTANT` — a person talks to it and it proposes;\n- `INVOKED` — another part of the application calls it;\n- `FLOW_STEP` — it is one step of a declared flow the application runs.\n\nGive work to an agent where it relieves the firm's people of reading, matching and drafting. **Never\ngive an agent a decision a qualified person must take**: an agent proposes, and the decision point in\nStep 4 is where the person decides.\n\n`readsRefs` and `producesRefs` name the planned resources a step reads and writes, in the domain plan's\nnaming. They are what lets the domain plan know a step needs a resource. Leave them empty rather than\ninventing a resource no requirement implies.\n\n## Step 4 — The decision points: who decides, on what ground, by when\n\nA decision point is where the case waits for a person. Each sits at one step (`stepRef`) and says in\n`decides` what is decided. Then three choices, and they are the heart of this artifact.\n\n**Who decides (`route`):**\n\n| `route` | when |\n|---|---|\n| `owner` | the person whose own work raised it confirms it (accepting what an assistant proposed to them). Nobody vets the owner, so it takes no qualification |\n| `role` | anyone holding a role may decide (any qualified accountant serving the client) |\n| `assignee` | one named person decides (the client's engagement partner). Say who in `assignee`, in the firm's words |\n\n**On what ground (`qualificationRef`):** every `role` and `assignee` decision names a qualification from\n`qualifications`, and an `owner` decision names none. A qualification says:\n\n- `role` — the role the person holds for the client, as the role table keys it\n (`ORG_QUALIFIED_ACCOUNTANT`). It says what the client ENTRUSTED the firm with.\n- `heldBy` — whose people hold that role: `FIRM` when the firm's people take the decision for the client\n (almost always: the qualified accountant, the engagement partner), `CLIENT` when the client's own staff\n take it in their organization (the client's finance director approving a deliverable). A firm-held role\n reaches the firm's people through the relationship the firm serves its clients through, so the build\n confers it there; `ORG_REPRESENTATIVE` is conferred by that relationship already. A role is always one\n a member of an organization holds: never an application role (`APP_…`), and a firm-held role is never\n the client's administration (`ORG_OWNER`, `ORG_ADMIN`), which no relationship may confer.\n- `professionalQualificationKind` — set ONLY when the PERSON must also hold a verified professional\n qualification (a chartered accountant, a licensed engineer). It follows the person, and lapses with\n their licence. The value is a kebab-case kind (`chartered-accountant`) the application declares in its\n `professionalQualificationKinds`; name the kind you need, and the build declares it.\n\nUse the creator's `signatories` answer to choose. A decision the creator tied to a profession (\"a\nchartered accountant\") needs both the role and the professional qualification. A decision tied to a\nposition (\"the engagement partner\") is an `assignee` decision with the role. A review any expert serving\nthe client may do is a `role` decision whose qualification names the role alone. Most decisions need\nonly a role; the professional-qualifications skill shown to you explains the mechanisms and how they\ncombine.\n\n**By when (`decisionDeadline`):** a review that keeps a client waiting says when it is due, as an\nISO-8601 duration (`PT9H`, `P2D`) counted on `basis`: `calendar` (the firm's working hours) or `elapsed`\n(around the clock). A business-time deadline needs `reviewCalendar`, built from the `working-hours`\nanswer: the `timeZone` (an IANA name), the `workingDays`, the `workingHours` (`HH:MM` from and to) and\nthe `holidays` as dates (`YYYY-MM-DD`). When the creator names a calendar (\"French public holidays\"),\nwrite out its dates for the current and next year. A decision with no deadline is allowed, and it is marked:\nthe engine's default lapse and reminders apply.\n\n## Step 5 — What the client receives, what is kept, and what it costs\n\n- `deliverables` — what a case produces for the client, at which stage, from which planned resource\n (`fromResourceRef`). A close report, an audit opinion, a filed return.\n- `evidenceRetention` — how long the case's evidence is kept: a `retentionClass` and its `ground`.\n Records the law requires the firm to keep (accounting documents, working papers) are\n `BUSINESS_RECORDS`; say the ground in plain words and name the jurisdiction the vision gives. You\n state the firm's obligation as you understand it; the compliance lane governs the retention period.\n- `pricing` — `PER_CASE` when each case is billed, `INCLUDED_IN_PLAN` when a subscription covers it,\n `BILLED_OUTSIDE` when the firm bills from its own tools. Read it off the business model when one is on\n record: a plan priced `per_usage` whose `usageUnit` is this service's case (\"close\") makes the service\n `PER_CASE`; a subscription plan that covers the service makes it `INCLUDED_IN_PLAN`. With no business\n model, `BILLED_OUTSIDE`, which commits the application to nothing. A service `PER_CASE` is billed one\n metered unit when its case closes, once per case however often it is reopened; the build records it.\n An internal tool has no billing at all, whatever a business model or a feature line brings: price\n every service `BILLED_OUTSIDE` there. The coherence report names a price per case on such an\n application as the method's gap, and no build can record it.\n\n## Step 6 — How the client takes part, and why a person corrects an agent\n\n- `clientParticipation` — one paragraph: what the client provides, what they answer, what they read.\n- `correctionReasons` — when agents do work a person reviews, the short list of reasons a person gives\n for correcting it (`wrong_account`, `missing_evidence`). Each `reasonCode` is lowercase snake_case.\n They let the firm see why agent work is corrected. Five to eight reasons, specific to the work.\n\n## Refine, don't re-author\n\nWhen a method is already on record, refine it. Keep every ref that still names the same thing, because\nlater families name them; change the content, not the identity.\n\n## What you emit\n\nOne `ServiceMethod`. The schema refuses:\n\n- a step in a stage the service does not declare, and a deliverable at one;\n- an agent step without an `agentShape`, and any other step with one;\n- a decision at a step the service does not declare;\n- an `owner` decision naming a qualification, a `role` or `assignee` decision naming none, and a\n qualification the method does not declare;\n- one resource kept in two retention classes, because two services name it as their evidence;\n- an `assignee` decision with no `assignee`, and an `assignee` on any other decision;\n- a business-time deadline with no `reviewCalendar`, and a deadline that is not a positive duration\n in weeks, days, hours, minutes or seconds (`PT8H`, `P2D`; no years or months);\n- a qualification on a role no member of an organization holds (an application role, an inbound\n handler's, a capability lent through a relationship), and a firm-held one on `ORG_OWNER` or `ORG_ADMIN`;\n- any ref declared twice.\n\nFix the cause it names and answer again.\n\n## Verification\n\n- Every service's `purpose` says what the client gets.\n- Every decision the `signatories` answer named is a decision point, with the role, and the professional\n qualification when the answer named a profession.\n- No agent step decides anything a decision point decides.\n- Every `role` and `assignee` decision names a declared qualification; every qualification is used.\n- Every reviewer decision that keeps a client waiting has a deadline, or the creator said it has none.\n",
42
+ "guidance": "# Service Method — How the Firm Works\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this playbook does\n\nYou are writing down the firm's **method**: the services it sells to its clients and, for each, how a\ncase is worked. The output is one `ServiceMethod`. It is the one place the method is written down; the\ndomain plan, the roles and the build plan derive from it, so a method that is vague here is an\napplication that is vague everywhere.\n\nA firm is not a product its users drive alone. A case is opened for a client, agents and the firm's\npeople work it, a qualified person takes the decisions that carry the firm's responsibility, and the\nclient receives something at the end. Write that down, case by case.\n\n## What the creator decides, and what you draft\n\nThe interview has four questions:\n\n- **`services`** — what the firm sells, what starts a case and what ends it.\n- **`signatories`** — which decisions only a qualified person may take, and what that person must be.\n- **`agent-work`** — which work in a case the creator wants agents to do.\n- **`working-hours`** — where and when the firm's reviewers work.\n\nAn answer the creator gave is theirs: build on it, do not second-guess it. An answer recorded as an\nASSUMPTION (proposed, because the creator did not know or chose a quick interview) is a proposal: use it,\nand keep anything resting on it easy to revise. `agent-work` and `working-hours` are usually assumptions.\n\nEverything else you DRAFT from those answers, the vision and the market: the stages, the steps, the\ndeliverables, the evidence retention, the correction reasons. Draft them so the creator can accept them\nas they are; they will review them.\n\nIf an answer says \"propose it\", the creator delegated that part: propose it from the services. If the\ninterview says \"none\", write none — an empty list is an answer.\n\nAn answer left **NOT DECIDED YET** is not \"none\", and the method must not read as if it were. Say it is\nowed in `owed`:\n\n- `signatories` not decided yet → `owed` includes `QUALIFIED_DECISIONS`. Write only the decisions and\n qualifications the creator's other answers name; never invent a qualified decision to fill the gap.\n- `agent-work` not decided yet → `owed` includes `AGENT_WORK`. A step the client does still names\n `CLIENT`; a step of the firm's work whose performer waits on that answer names **no** `performedBy` and\n no `agentShape`. Never decide for the creator which work an agent does.\n\n`owed` is empty when every answer was given.\n\n## Step 1 — One service per thing the firm sells\n\nEach service is one entry in `services`:\n\n- `serviceRef` — a kebab-case key (`month-end-close`, `annual-audit`). Later families name it.\n- `label` — what the firm calls it.\n- `purpose` — what the CLIENT gets, in one sentence. Not what the firm does: \"the client's books closed\n every month, reconciled and signed off\", not \"we reconcile bank lines\".\n\nTwo services the creator described as one are one service. Do not split a service to look thorough.\n\n## Step 2 — The case, and its stages\n\n`case` is the unit of work a service is delivered in: one close, one audit engagement, one filing.\n\n- `caseRef` — the PLANNED RESOURCE whose rows are the cases, in the domain plan's naming (plural,\n kebab-case: `closes`, `audit-engagements`). The domain plan inventories it and the build plan makes it\n the work unit, the record every model call on the case is costed to.\n- `opensWhen` / `closesWhen` — the events, in the creator's words.\n\n`stages` are the states a case moves through, in order, first stage first. Each has a `meaning`: what is\ntrue of a case in that stage. Include the stage a case returns to when something surfaces after it was\nfinished (\"reopened\") when the creator's work has one. Stage refs are kebab-case and unique within the\nservice.\n\n## Step 3 — The steps, and who carries each one\n\nEach step happens in one stage and is performed by exactly one of (or, while `AGENT_WORK` is owed, by\nnone yet):\n\n| `performedBy` | means |\n|---|---|\n| `AGENT` | an agent of the application does it. Say how it runs in `agentShape` |\n| `PERSON` | one of the firm's people does it |\n| `CLIENT` | the client does it (sends documents, answers a question) |\n\nAn agent step names its `agentShape`, and no other step does:\n\n- `AUTONOMOUS` — it runs on its own, on a schedule or an event (reconciling every night, reading every\n document that arrives);\n- `CHAT_ASSISTANT` — a person talks to it and it proposes;\n- `INVOKED` — another part of the application calls it;\n- `FLOW_STEP` — it is one step of a declared flow the application runs.\n\nGive work to an agent where it relieves the firm's people of reading, matching and drafting. **Never\ngive an agent a decision a qualified person must take**: an agent proposes, and the decision point in\nStep 4 is where the person decides.\n\n`readsRefs` and `producesRefs` name the planned resources a step reads and writes, in the domain plan's\nnaming. They are what lets the domain plan know a step needs a resource. Leave them empty rather than\ninventing a resource no requirement implies.\n\n## Step 4 — The decision points: who decides, on what ground, by when\n\nA decision point is where the case waits for a person. Each sits at one step (`stepRef`) and says in\n`decides` what is decided. Then three choices, and they are the heart of this artifact.\n\n**Who decides (`route`):**\n\n| `route` | when |\n|---|---|\n| `owner` | the person whose own work raised it confirms it (accepting what an assistant proposed to them). Nobody vets the owner, so it takes no qualification |\n| `role` | anyone holding a role may decide (any qualified accountant serving the client) |\n| `assignee` | one named person decides (the client's engagement partner). Say who in `assignee`, in the firm's words |\n\n**On what ground (`qualificationRef`):** every `role` and `assignee` decision names a qualification from\n`qualifications`, and an `owner` decision names none. A qualification says:\n\n- `role` — the role the person holds for the client, as the role table keys it\n (`ORG_QUALIFIED_ACCOUNTANT`). It says what the client ENTRUSTED the firm with.\n- `heldBy` — whose people hold that role: `FIRM` when the firm's people take the decision for the client\n (almost always: the qualified accountant, the engagement partner), `CLIENT` when the client's own staff\n take it in their organization (the client's finance director approving a deliverable). A firm-held role\n reaches the firm's people through the relationship the firm serves its clients through, so the build\n confers it there; `ORG_REPRESENTATIVE` is conferred by that relationship already. A role is always one\n a member of an organization holds: never an application role (`APP_…`), and a firm-held role is never\n the client's administration (`ORG_OWNER`, `ORG_ADMIN`), which no relationship may confer.\n- `professionalQualificationKind` — set ONLY when the PERSON must also hold a verified professional\n qualification (a chartered accountant, a licensed engineer). It follows the person, and lapses with\n their licence. The value is a kebab-case kind (`chartered-accountant`) the application declares in its\n `professionalQualificationKinds`; name the kind you need, and the build declares it.\n\nUse the creator's `signatories` answer to choose. A decision the creator tied to a profession (\"a\nchartered accountant\") needs both the role and the professional qualification. A decision tied to a\nposition (\"the engagement partner\") is an `assignee` decision with the role. A review any expert serving\nthe client may do is a `role` decision whose qualification names the role alone. Most decisions need\nonly a role; the professional-qualifications skill shown to you explains the mechanisms and how they\ncombine.\n\n**By when (`decisionDeadline`):** a review that keeps a client waiting says when it is due, as an\nISO-8601 duration (`PT9H`, `P2D`) counted on `basis`: `calendar` (the firm's working hours) or `elapsed`\n(around the clock). A business-time deadline needs `reviewCalendar`, built from the `working-hours`\nanswer: the `timeZone` (an IANA name), the `workingDays`, the `workingHours` (`HH:MM` from and to) and\nthe `holidays` as dates (`YYYY-MM-DD`). When the creator names a calendar (\"French public holidays\"),\nwrite out its dates for the current and next year. A decision with no deadline is allowed, and it is marked:\nthe engine's default lapse and reminders apply.\n\nWhen `working-hours` is NOT DECIDED YET, write no `reviewCalendar` and never invent one: give each deadline on\n`elapsed` time, or leave it out. A business-time deadline needs the calendar the creator has not given, and the\nmethod is refused with one.\n\n## Step 5 — What the client receives, what is kept, and what it costs\n\n- `deliverables` — what a case produces for the client, at which stage, from which planned resource\n (`fromResourceRef`). A close report, an audit opinion, a filed return.\n- `evidenceRetention` — how long the case's evidence is kept: a `retentionClass` and its `ground`.\n Records the law requires the firm to keep (accounting documents, working papers) are\n `BUSINESS_RECORDS`; say the ground in plain words and name the jurisdiction the vision gives. You\n state the firm's obligation as you understand it; the compliance lane governs the retention period.\n- `pricing` — `PER_CASE` when each case is billed, `INCLUDED_IN_PLAN` when a subscription covers it,\n `BILLED_OUTSIDE` when the firm bills from its own tools. Read it off the business model when one is on\n record: a plan priced `per_usage` whose `usageUnit` is this service's case (\"close\") makes the service\n `PER_CASE`; a subscription plan that covers the service makes it `INCLUDED_IN_PLAN`. With no business\n model, `BILLED_OUTSIDE`, which commits the application to nothing. A service `PER_CASE` is billed one\n metered unit when its case closes, once per case however often it is reopened; the build records it.\n An internal tool has no billing at all, whatever a business model or a feature line brings: price\n every service `BILLED_OUTSIDE` there. The coherence report names a price per case on such an\n application as the method's gap, and no build can record it.\n\n## Step 6 — How the client takes part, and why a person corrects an agent\n\n- `clientParticipation` — one paragraph: what the client provides, what they answer, what they read.\n- `correctionReasons` — when agents do work a person reviews, the short list of reasons a person gives\n for correcting it (`wrong_account`, `missing_evidence`). Each `reasonCode` is lowercase snake_case.\n They let the firm see why agent work is corrected. Five to eight reasons, specific to the work.\n\n## Refine, don't re-author\n\nWhen a method is already on record, refine it. Keep every ref that still names the same thing, because\nlater families name them; change the content, not the identity.\n\n## What you emit\n\nOne `ServiceMethod`. The schema refuses:\n\n- a step in a stage the service does not declare, and a deliverable at one;\n- an agent step without an `agentShape`, and any other step with one;\n- a step with no `performedBy` when `owed` does not include `AGENT_WORK`;\n- a decision at a step the service does not declare;\n- an `owner` decision naming a qualification, a `role` or `assignee` decision naming none, and a\n qualification the method does not declare;\n- one resource kept in two retention classes, because two services name it as their evidence;\n- an `assignee` decision with no `assignee`, and an `assignee` on any other decision;\n- a business-time deadline with no `reviewCalendar`, and a deadline that is not a positive duration\n in weeks, days, hours, minutes or seconds (`PT8H`, `P2D`; no years or months);\n- a qualification on a role no member of an organization holds (an application role, an inbound\n handler's, a capability lent through a relationship), and a firm-held one on `ORG_OWNER` or `ORG_ADMIN`;\n- any ref declared twice.\n\nFix the cause it names and answer again.\n\n## Verification\n\n- Every service's `purpose` says what the client gets.\n- Every decision the `signatories` answer named is a decision point, with the role, and the professional\n qualification when the answer named a profession.\n- Every answer left not decided yet is in `owed`, and nothing it would have decided was invented.\n- No agent step decides anything a decision point decides.\n- Every `role` and `assignee` decision names a declared qualification; every qualification is used.\n- Every reviewer decision that keeps a client waiting has a deadline, or the creator said it has none.\n",
43
43
  "skillRefs": [
44
44
  "professional-qualifications",
45
45
  "flows-actors-autonomous-agents",
@@ -65,22 +65,34 @@
65
65
  "question": "Which decisions in a case must a qualified person of the firm take, and what must they be? Name the decision and the role or professional qualification (\"posting to the client's books: a chartered accountant\"; \"signing the period off: the client's engagement partner\"). Answer \"none\" if no decision needs a qualified person.",
66
66
  "kind": "free_text",
67
67
  "depth": "essential",
68
- "regulatedDomain": true
68
+ "regulatedDomain": true,
69
+ "nonAnswers": [
70
+ "not_applicable",
71
+ "deferred"
72
+ ]
69
73
  },
70
74
  {
71
75
  "ref": "agent-work",
72
76
  "question": "Which work in a case would you like agents to do for the firm's people — reading documents, reconciling, drafting, answering the client? Answer \"propose it\" to have it proposed from the services, or \"none\".",
73
77
  "kind": "free_text",
74
- "depth": "detail"
78
+ "depth": "detail",
79
+ "nonAnswers": [
80
+ "not_applicable",
81
+ "deferred"
82
+ ]
75
83
  },
76
84
  {
77
85
  "ref": "working-hours",
78
86
  "question": "Where do the firm's reviewers work, and when? Give the time zone and the working hours (\"Europe/Paris, 9:00 to 18:00, French public holidays\"). Deadlines on a decision are counted in these hours.",
79
87
  "kind": "free_text",
80
- "depth": "detail"
88
+ "depth": "detail",
89
+ "nonAnswers": [
90
+ "deferred"
91
+ ]
81
92
  }
82
93
  ]
83
94
  },
95
+ "derivedFromAnswers": [],
84
96
  "contextSources": [],
85
97
  "draftableDocumentDefinitionRefs": [],
86
98
  "suspendsForClarification": false,
@@ -122,8 +122,11 @@ Then sharpen:
122
122
  Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or
123
123
  benefit still points at orphans the downstream ref (the validator catches
124
124
  this as `ORPHAN_REF`, but honest refinement should not create the orphan).
125
- If a slice from the market pass is genuinely wrong, fix it at its source
126
- slice, do not paper over it in the value-prop layer.
125
+ Only your slices land (the benefits, the tones of voice and the positionings,
126
+ #3403): an edit to any other part of the snapshot is replaced by its current
127
+ value. If a slice from the market pass is genuinely wrong, say so in your
128
+ rationale for the snapshot's producer to correct; do not paper over it in the
129
+ value-prop layer.
127
130
 
128
131
  ## Quality gate
129
132
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.value-proposition",
3
- "version": "0.1.1",
3
+ "version": "0.2.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Top-down value-proposition / positioning: sharpen the product's value proposition on an EXISTING MarketSnapshot — the weighted benefits (relieves/creates/advances edges, Kano category per ICP), the tones of voice, and the per-ICP positioning pillars — framed by the product VisionSnapshot's differentiation. Runs after market-analysis (which produced the broad snapshot) and refines the same market-snapshot artifact; it does NOT create a new family (benefits, tone-of-voice, and positioning all live inside MarketSnapshot). Emits the refined MarketSnapshot validated by validateMarketSnapshot, consumed downstream by capability-map (benefits -> deliveredByFeatureRefs) and the refinement/coverage playbooks. v1 scaffold methodology — the FIT/Kano scoring precision and positioning rigor are iterated in a later depth phase, not here.",
6
6
  "preconditions": [
@@ -23,12 +23,17 @@
23
23
  {
24
24
  "family": "market-snapshot",
25
25
  "schemaRef": "saas-specifications:MarketSnapshot",
26
- "description": "The SAME MarketSnapshot, refined so its value-proposition slices are sharp: benefits with weighted relieves/creates/advances edges and per-ICP Kano categories, the tones of voice, and one positioning pillar per targeted ICP. Validated by validateMarketSnapshot; feeds capability-map and refinement."
26
+ "description": "The SAME MarketSnapshot, refined so its value-proposition slices are sharp: benefits with weighted relieves/creates/advances edges and per-ICP Kano categories, the tones of voice, and one positioning pillar per targeted ICP. Validated by validateMarketSnapshot; feeds capability-map and refinement.",
27
+ "aspects": [
28
+ "market.benefit",
29
+ "market.tone-of-voice",
30
+ "market.positioning"
31
+ ]
27
32
  }
28
33
  ],
29
34
  "stepOutputs": [],
30
35
  "method": {
31
- "guidance": "# Value Proposition & Positioning — Sharpen Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The refinement order, the benefit-weighting posture, and the\n> \"sharpen vs. leave\" rules below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of the value-proposition work (quantified\n> FIT / Kano scoring precision, positioning rigor) is intentionally shallow\n> here and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **positioning strategist**. Market-analysis already produced the\n**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your\none job is to **sharpen the value-proposition slices of that same snapshot**:\nthe benefits, the tones of voice, and the per-ICP positioning pillars, framed\nby the product's **VisionSnapshot** differentiation. You do not create a new\nartifact family — benefits, tone-of-voice, and positioning all live *inside*\n`MarketSnapshot`. You read the existing snapshot, tighten these three slices,\nand re-emit the same snapshot.\n\nThis is a **focused refinement pass**, distinct from market-analysis (which\ndoes the broad initial market sweep). Where market-analysis lays down the\nwhole snapshot at a first-pass depth, you come back over the value-proposition\nslices specifically and make them sharp, consistent with each other, and true\nto the vision.\n\nThe three slices you own, in dependency order (later slices reference earlier\nrefs, and all reference the jobs/pains/gains the market pass already authored):\n\n1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),\n each a *weighted* set of edges: the pains it **relieves**, the gains it\n **creates**, and the jobs it **advances**, every edge carrying a `degree`\n (1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on\n `importanceByICP`: a per-ICP `weight` plus a **Kano category** from the\n `BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks\n the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),\n plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can\n matter differently to different segments. Benefits reference the\n pains/gains/jobs the market pass authored — never weight against a\n pain/gain/job that does not exist. (`market-add-feature-benefit`)\n - **Structural constraint (the U8 seam):** every benefit carries a\n non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.\n At this top-down phase there is no feature registry yet, so these are\n **forward-reference** feature refs; the `ORPHAN_REF` resolution check is\n skipped until a feature set exists. **Wiring benefits to real spec-first\n feature drafts is the capability-map playbook's job (U8), not yours** —\n do not invent the feature registry here. Keep the refs you inherit;\n leave a placeholder ref only where the market pass already did.\n2. **Tones of voice** — the named brand voices the product speaks in\n (`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;\n each positioning and message template later speaks in one of them.\n (`market-tone-of-voice`)\n3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):\n author **one positioning entry per ICP the product actually targets**\n (priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**\n (`valuePillars`) — the sharp claims that separate the product from the\n alternatives. Each pillar hangs off the weighted benefits above (it traces\n back to `FeatureBenefitRef[]`) and is framed by the vision's\n differentiation. (`market-positioning-authoring`)\n\nSharpen only the slices the product's stage warrants. A snapshot whose\nbenefits carry honest relieves/creates/advances weighting with per-ICP Kano\ncategories, at least one tone of voice, and one positioning entry (with its\nvalue pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the\nweighting and the pillar prose is additive.\n\n## Frame everything by the vision\n\nThe **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.\nRead its mission, its problem framing, and its success criteria before you\nweight a single benefit. A benefit's weight, a Kano category, and a positioning\npillar are only *right* if they express the product's actual differentiation —\nwhat the vision says makes this product worth building over the alternatives.\nWhen a benefit or pillar cannot be traced back to the vision's differentiation,\nthat is a signal to either sharpen the vision link or drop the claim, not to\ninvent a promise the product does not stand behind.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is at\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook refines in place — you read it, sharpen the value-proposition slices,\nand write the same artifact back. When the product's definition later\nstabilises, the snapshot is what seeds the durable market specification under\n`./specifications/` — but at this phase it is a journey artifact, not yet app\nsource.\n\n## Refine, don't re-author — read state first\n\nThis playbook is **idempotent** and, by construction, a *refinement*: a\nMarketSnapshot must already exist (the `artifact_exists` precondition enforces\nit). Before sharpening anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which scope\n the value proposition must hold *for*.\n2. Read the existing MarketSnapshot at this playbook's placement path and the\n VisionSnapshot at the `vision-brief` placement, so you sharpen against the\n real market intent and the real differentiation, not from scratch.\n\n\nThen sharpen:\n\n- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that\n are already sharp and vision-true. Only add/correct where the current\n steering notes, the vision, or benefit-weight inconsistencies call for it.\n- **Never orphan a ref.** A positioning names an ICP and its pillars name\n benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.\n Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or\n benefit still points at orphans the downstream ref (the validator catches\n this as `ORPHAN_REF`, but honest refinement should not create the orphan).\n If a slice from the market pass is genuinely wrong, fix it at its source\n slice, do not paper over it in the value-prop layer.\n\n## Quality gate\n\nYour re-emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\nvalue-proposition invariants it enforces are mostly **`ERROR`-severity hard\nfailures** — the snapshot does not advance until they clear:\n\n- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has\n no `MarketPositioning`. This is the headline gap this playbook closes: a\n targeted ICP without a positioning is a *hard failure*, not a warning.\n (`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)\n- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a\n `kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have\n claim needs a job to anchor against.\n- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both\n claim `THRESHOLD` for the same (icp, job); only one must-have per job.\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must stay deliverable (see the U8 seam above).\n- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or\n benefit naming a missing pain/gain/job. (Feature-ref orphans are only\n checked once a feature registry is passed — not at this phase.)\n\n`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`\n(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice\npast its review cadence). Read `market-snapshot-validation` for the full issue\ncatalogue and emit a clean snapshot the first time.\n\nBeyond the deterministic gate, the advisory judge reads the landed snapshot against\nthree criteria — vision-framed benefits, positioning coverage, and refinement rather\nthan re-authoring — and its verdicts reach the creator's review as notes. A verdict\nnever refuses a landing.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Quantified FIT / Kano scoring precision** — the deterministic FIT scorer has\n already been run for you and its per-ICP scores arrive in\n the declared `market_fit_scores` context section of your brief; `market-scoring-interpretation` is how to\n READ them. At scaffold depth you consume them to sanity-check benefit weighting\n and Kano assignment, never to drive a precise prioritization model, and you never\n restate or estimate a score. The prioritization seam stays pluggable (the\n capability-map playbook owns wiring FIT scores into feature drafts). Do not\n build a scoring model here.\n- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a\n full competitive positioning matrix, message-market-fit testing, or\n A/B-tested copy is later-phase work.\n- **Message-template rendering** — this playbook stops at the value-proposition\n slices (benefits / tone / pillars). Turning them into reusable message\n templates stays with the market-analysis playbook's `market_message_templates`\n slice.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nThe SAME MarketSnapshot at `specifications/src/market/index.ts`,\nwith its value-proposition slices sharpened: weighted benefits with per-ICP\nKano categories, the tones of voice, and one positioning entry (with its 2–4\nvalue pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's\ndifferentiation — passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's refined market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `market-add-feature-benefit` — author the benefit\n claims and their relieves/creates/advances weighting and per-ICP Kano\n categories.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-positioning-authoring` — author the per-ICP\n positioning entries and their 2–4 value pillars.\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting and Kano\n assignment (scaffold depth — sanity-check, not a scoring model).\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
36
+ "guidance": "# Value Proposition & Positioning — Sharpen Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The refinement order, the benefit-weighting posture, and the\n> \"sharpen vs. leave\" rules below are deliberately explicit so they can be\n> tuned against real runs — treat them as a starting rubric, not a frozen\n> contract. The *analytical depth* of the value-proposition work (quantified\n> FIT / Kano scoring precision, positioning rigor) is intentionally shallow\n> here and is deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **positioning strategist**. Market-analysis already produced the\n**MarketSnapshot** — the category, ICPs, personas, and jobs/pains/gains. Your\none job is to **sharpen the value-proposition slices of that same snapshot**:\nthe benefits, the tones of voice, and the per-ICP positioning pillars, framed\nby the product's **VisionSnapshot** differentiation. You do not create a new\nartifact family — benefits, tone-of-voice, and positioning all live *inside*\n`MarketSnapshot`. You read the existing snapshot, tighten these three slices,\nand re-emit the same snapshot.\n\nThis is a **focused refinement pass**, distinct from market-analysis (which\ndoes the broad initial market sweep). Where market-analysis lays down the\nwhole snapshot at a first-pass depth, you come back over the value-proposition\nslices specifically and make them sharp, consistent with each other, and true\nto the vision.\n\nThe three slices you own, in dependency order (later slices reference earlier\nrefs, and all reference the jobs/pains/gains the market pass already authored):\n\n1. **Benefits** — the outcome claims the product delivers (`FeatureBenefit`),\n each a *weighted* set of edges: the pains it **relieves**, the gains it\n **creates**, and the jobs it **advances**, every edge carrying a `degree`\n (1..10) the FIT scorer multiplies by the ICP's own edge weight. Layer on\n `importanceByICP`: a per-ICP `weight` plus a **Kano category** from the\n `BenefitKanoCategory` enum — `THRESHOLD` (a must-have; its absence breaks\n the deal), `PERFORMANCE` (more is better), `DELIGHTER` (unexpected upside),\n plus `INDIFFERENT` / `REVERSE` for completeness — so the same benefit can\n matter differently to different segments. Benefits reference the\n pains/gains/jobs the market pass authored — never weight against a\n pain/gain/job that does not exist. (`market-add-feature-benefit`)\n - **Structural constraint (the U8 seam):** every benefit carries a\n non-empty `deliveredByFeatureRefs[]` — a benefit must be *deliverable*.\n At this top-down phase there is no feature registry yet, so these are\n **forward-reference** feature refs; the `ORPHAN_REF` resolution check is\n skipped until a feature set exists. **Wiring benefits to real spec-first\n feature drafts is the capability-map playbook's job (U8), not yours** —\n do not invent the feature registry here. Keep the refs you inherit;\n leave a placeholder ref only where the market pass already did.\n2. **Tones of voice** — the named brand voices the product speaks in\n (`ToneOfVoice`, addressed by `ToneOfVoiceRef`). Keep them few and distinct;\n each positioning and message template later speaks in one of them.\n (`market-tone-of-voice`)\n3. **Positioning** — the per-ICP marketing-truth promise (`MarketPositioning`):\n author **one positioning entry per ICP the product actually targets**\n (priority `CORE` or `EXPANSION`), each carrying **2–4 value pillars**\n (`valuePillars`) — the sharp claims that separate the product from the\n alternatives. Each pillar hangs off the weighted benefits above (it traces\n back to `FeatureBenefitRef[]`) and is framed by the vision's\n differentiation. (`market-positioning-authoring`)\n\nSharpen only the slices the product's stage warrants. A snapshot whose\nbenefits carry honest relieves/creates/advances weighting with per-ICP Kano\ncategories, at least one tone of voice, and one positioning entry (with its\nvalue pillars) per `CORE`/`EXPANSION` ICP is a legitimate v1; the depth of the\nweighting and the pillar prose is additive.\n\n## Frame everything by the vision\n\nThe **VisionSnapshot** (`vision-brief` family) is your differentiation anchor.\nRead its mission, its problem framing, and its success criteria before you\nweight a single benefit. A benefit's weight, a Kano category, and a positioning\npillar are only *right* if they express the product's actual differentiation —\nwhat the vision says makes this product worth building over the alternatives.\nWhen a benefit or pillar cannot be traced back to the vision's differentiation,\nthat is a signal to either sharpen the vision link or drop the claim, not to\ninvent a promise the product does not stand behind.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is at\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook refines in place — you read it, sharpen the value-proposition slices,\nand write the same artifact back. When the product's definition later\nstabilises, the snapshot is what seeds the durable market specification under\n`./specifications/` — but at this phase it is a journey artifact, not yet app\nsource.\n\n## Refine, don't re-author — read state first\n\nThis playbook is **idempotent** and, by construction, a *refinement*: a\nMarketSnapshot must already exist (the `artifact_exists` precondition enforces\nit). Before sharpening anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which scope\n the value proposition must hold *for*.\n2. Read the existing MarketSnapshot at this playbook's placement path and the\n VisionSnapshot at the `vision-brief` placement, so you sharpen against the\n real market intent and the real differentiation, not from scratch.\n\n\nThen sharpen:\n\n- **Keep what still holds.** Do not rewrite benefits, tones, or pillars that\n are already sharp and vision-true. Only add/correct where the current\n steering notes, the vision, or benefit-weight inconsistencies call for it.\n- **Never orphan a ref.** A positioning names an ICP and its pillars name\n benefits; a benefit names the pains/gains/jobs it relieves/creates/advances.\n Dropping an ICP, pain, gain, job, or benefit that a positioning, pillar, or\n benefit still points at orphans the downstream ref (the validator catches\n this as `ORPHAN_REF`, but honest refinement should not create the orphan).\n Only your slices land (the benefits, the tones of voice and the positionings,\n #3403): an edit to any other part of the snapshot is replaced by its current\n value. If a slice from the market pass is genuinely wrong, say so in your\n rationale for the snapshot's producer to correct; do not paper over it in the\n value-prop layer.\n\n## Quality gate\n\nYour re-emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\nvalue-proposition invariants it enforces are mostly **`ERROR`-severity hard\nfailures** — the snapshot does not advance until they clear:\n\n- **`MISSING_POSITIONING_FOR_ICP` (ERROR)** — a `CORE` or `EXPANSION` ICP has\n no `MarketPositioning`. This is the headline gap this playbook closes: a\n targeted ICP without a positioning is a *hard failure*, not a warning.\n (`EXPLORATORY` / `DEFERRED` / `ANTI_TARGET` ICPs are exempt.)\n- **`THRESHOLD_BENEFIT_WITHOUT_JOB` (ERROR)** — a benefit carries a\n `kanoCategory: THRESHOLD` entry but its `advances[]` is empty; a must-have\n claim needs a job to anchor against.\n- **`MULTIPLE_THRESHOLDS_PER_ICP_JOB` (ERROR)** — two distinct benefits both\n claim `THRESHOLD` for the same (icp, job); only one must-have per job.\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must stay deliverable (see the U8 seam above).\n- **`ORPHAN_REF` (ERROR)** — a positioning naming a missing ICP, a pillar or\n benefit naming a missing pain/gain/job. (Feature-ref orphans are only\n checked once a feature registry is passed — not at this phase.)\n\n`WARN`-severity issues do not block but should be resolved: `DUPLICATE_EDGE_PER_ENTITY`\n(a duplicate `(benefit, icp)` importance edge) and `STALE_AUTHORED` (a slice\npast its review cadence). Read `market-snapshot-validation` for the full issue\ncatalogue and emit a clean snapshot the first time.\n\nBeyond the deterministic gate, the advisory judge reads the landed snapshot against\nthree criteria — vision-framed benefits, positioning coverage, and refinement rather\nthan re-authoring — and its verdicts reach the creator's review as notes. A verdict\nnever refuses a landing.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Quantified FIT / Kano scoring precision** — the deterministic FIT scorer has\n already been run for you and its per-ICP scores arrive in\n the declared `market_fit_scores` context section of your brief; `market-scoring-interpretation` is how to\n READ them. At scaffold depth you consume them to sanity-check benefit weighting\n and Kano assignment, never to drive a precise prioritization model, and you never\n restate or estimate a score. The prioritization seam stays pluggable (the\n capability-map playbook owns wiring FIT scores into feature drafts). Do not\n build a scoring model here.\n- **Positioning rigor** — a pillar captures *the* sharp per-ICP promise; a\n full competitive positioning matrix, message-market-fit testing, or\n A/B-tested copy is later-phase work.\n- **Message-template rendering** — this playbook stops at the value-proposition\n slices (benefits / tone / pillars). Turning them into reusable message\n templates stays with the market-analysis playbook's `market_message_templates`\n slice.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nThe SAME MarketSnapshot at `specifications/src/market/index.ts`,\nwith its value-proposition slices sharpened: weighted benefits with per-ICP\nKano categories, the tones of voice, and one positioning entry (with its 2–4\nvalue pillars) per `CORE`/`EXPANSION` ICP — all framed by the vision's\ndifferentiation — passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's refined market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `market-add-feature-benefit` — author the benefit\n claims and their relieves/creates/advances weighting and per-ICP Kano\n categories.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-positioning-authoring` — author the per-ICP\n positioning entries and their 2–4 value pillars.\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting and Kano\n assignment (scaffold depth — sanity-check, not a scoring model).\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
32
37
  "skillRefs": [
33
38
  "market-add-feature-benefit",
34
39
  "market-positioning-authoring",
@@ -37,6 +42,7 @@
37
42
  "market-snapshot-validation"
38
43
  ],
39
44
  "skillBodyRefs": [],
45
+ "derivedFromAnswers": [],
40
46
  "contextSources": [
41
47
  "market_fit_scores"
42
48
  ],
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-vision-elicitation-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/vision-coherence-and-readiness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"instruction":"Assess whether the validated vision is internally coherent, grounded in the creator input carried in this brief, non-vacuous for the current horizon, and explicit about important uncertainty. Do not reward polished prose that lacks a real problem, mission, observable success basis or binding constraints. Separate severities by CONSEQUENCE: limited repairable drift from the creator input is a CONCERN; a substituted product, audience or constraint set — or an internal contradiction — is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Usable WITH REVISION: grounded in the creator input overall, but carrying limited repairable drift (an embellished emphasis, a missing secondary element, weak evidence, or explicit material uncertainty) that revision can fix without re-eliciting the creator.","GAP":"NOT usable as direction: a foundational vision element is missing, the candidate contradicts itself, or it substitutes a DIFFERENT product, audience or binding-constraint set than the creator input states.","INDETERMINATE":"The creator input or candidate evidence needed to decide this criterion is absent or insufficient.","PASS":"The candidate is valid, internally coherent, grounded in the creator input, and sufficient to guide the current horizon."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/vision-elicitation","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.vision-elicitation"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-vision-elicitation-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/vision-coherence-and-readiness","criterionVersion":4,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"instruction":"Assess whether the validated vision is internally coherent, grounded in the creator input carried in this brief, non-vacuous for the current horizon, and explicit about important uncertainty. Do not reward polished prose that lacks a real problem, mission, observable success basis or binding constraints. Read each creator answer WITH its standing: an answer marked ASSUMED was proposed for the creator and never stated by them, so the vision must present it as an assumption or working hypothesis. Labelling it so is correct and never drift; presenting an ASSUMED answer as the creator's own statement is drift, and so is labelling a DECIDED answer as an assumption. A problem, mission or set of success criteria the creator left NOT DECIDED YET is correctly absent: its absence is never drift, and filling it in from other answers is. A regulated-domain question the creator left NOT DECIDED YET must appear as a compliance constraint stating that open question; leaving it out, which reads as 'no', or stating it as settled either way is drift. Separate severities by CONSEQUENCE: limited repairable drift from the creator input is a CONCERN; a substituted product, audience or constraint set — or an internal contradiction — is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Usable WITH REVISION: grounded in the creator input overall, but carrying limited repairable drift (an embellished emphasis, a missing secondary element, weak evidence, or explicit material uncertainty) that revision can fix without re-eliciting the creator.","GAP":"NOT usable as direction: a foundational vision element is missing, the candidate contradicts itself, or it substitutes a DIFFERENT product, audience or binding-constraint set than the creator input states.","INDETERMINATE":"The creator input or candidate evidence needed to decide this criterion is absent or insufficient.","PASS":"The candidate is valid, internally coherent, grounded in the creator input, and sufficient to guide the current horizon."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/vision-elicitation","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.vision-elicitation"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-vision-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/vision-coherence-and-readiness"],"requirementRef":"application-creation:authority-requirement/vision-elicitation-result","requirementVersion":1,"riskClassRef":"application-creation:risk/foundational-vision-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/vision-elicitation","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/vision-elicitation-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/vision-elicitation","policyVersion":1},"decisionPointRef":"application-creation:decision-point/vision-elicitation-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/vision-elicitation-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/vision-elicitation","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/vision-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/foundational-vision-change","triggerRefs":["application-creation:trigger/vision-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-vision-elicitation-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/vision-coherence-and-readiness"],"hardFloorRef":"application-creation:hard-floor/vision-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/vision-elicitation-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/vision-elicitation","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-vision-elicitation-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/vision-coherence-and-readiness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"instruction":"Assess whether the validated vision is internally coherent, grounded in the creator input carried in this brief, non-vacuous for the current horizon, and explicit about important uncertainty. Do not reward polished prose that lacks a real problem, mission, observable success basis or binding constraints. Separate severities by CONSEQUENCE: limited repairable drift from the creator input is a CONCERN; a substituted product, audience or constraint set — or an internal contradiction — is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Usable WITH REVISION: grounded in the creator input overall, but carrying limited repairable drift (an embellished emphasis, a missing secondary element, weak evidence, or explicit material uncertainty) that revision can fix without re-eliciting the creator.","GAP":"NOT usable as direction: a foundational vision element is missing, the candidate contradicts itself, or it substitutes a DIFFERENT product, audience or binding-constraint set than the creator input states.","INDETERMINATE":"The creator input or candidate evidence needed to decide this criterion is absent or insufficient.","PASS":"The candidate is valid, internally coherent, grounded in the creator input, and sufficient to guide the current horizon."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/vision-elicitation","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.vision-elicitation"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/vision-elicitation","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-vision-input-and-candidate","criterionRef":"application-creation:criterion/vision-coherence-and-readiness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-bootstrap-and-candidate"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-vision-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/vision-coherence-and-readiness"],"requirementRef":"application-creation:authority-requirement/vision-elicitation-result","requirementVersion":1,"riskClassRef":"application-creation:risk/foundational-vision-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/vision-elicitation","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/vision-elicitation-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/vision-elicitation","policyVersion":1},"decisionPointRef":"application-creation:decision-point/vision-elicitation-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/vision-elicitation-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/vision-elicitation","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/vision-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/foundational-vision-change","triggerRefs":["application-creation:trigger/vision-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-vision-elicitation-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/vision-coherence-and-readiness"],"hardFloorRef":"application-creation:hard-floor/vision-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/vision-elicitation-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/vision-elicitation","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-vision-elicitation-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/vision-coherence-and-readiness","criterionVersion":4,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1}],"instruction":"Assess whether the validated vision is internally coherent, grounded in the creator input carried in this brief, non-vacuous for the current horizon, and explicit about important uncertainty. Do not reward polished prose that lacks a real problem, mission, observable success basis or binding constraints. Read each creator answer WITH its standing: an answer marked ASSUMED was proposed for the creator and never stated by them, so the vision must present it as an assumption or working hypothesis. Labelling it so is correct and never drift; presenting an ASSUMED answer as the creator's own statement is drift, and so is labelling a DECIDED answer as an assumption. A problem, mission or set of success criteria the creator left NOT DECIDED YET is correctly absent: its absence is never drift, and filling it in from other answers is. A regulated-domain question the creator left NOT DECIDED YET must appear as a compliance constraint stating that open question; leaving it out, which reads as 'no', or stating it as settled either way is drift. Separate severities by CONSEQUENCE: limited repairable drift from the creator input is a CONCERN; a substituted product, audience or constraint set — or an internal contradiction — is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Usable WITH REVISION: grounded in the creator input overall, but carrying limited repairable drift (an embellished emphasis, a missing secondary element, weak evidence, or explicit material uncertainty) that revision can fix without re-eliciting the creator.","GAP":"NOT usable as direction: a foundational vision element is missing, the candidate contradicts itself, or it substitutes a DIFFERENT product, audience or binding-constraint set than the creator input states.","INDETERMINATE":"The creator input or candidate evidence needed to decide this criterion is absent or insufficient.","PASS":"The candidate is valid, internally coherent, grounded in the creator input, and sufficient to guide the current horizon."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/vision-elicitation","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.vision-elicitation"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/vision-elicitation","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-vision-input-and-candidate","criterionRef":"application-creation:criterion/vision-coherence-and-readiness","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/vision-coherence-and-readiness","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-bootstrap-and-candidate"}],"schemaVersion":1}
@@ -114,6 +114,16 @@ questions:
114
114
  per-regime obligation model (control catalogs, data-flow / residency
115
115
  matrices) is the compliance-posture step's job, not yours. Getting the
116
116
  compliance *seam* named here is what lets that later step engage.
117
+ - **A regulated-domain question left NOT DECIDED YET is an open compliance
118
+ constraint.** When the creator left one of the five regulated-domain
119
+ questions (children's or specially protected data, financial services,
120
+ healthcare, legal or compliance decisions, public sector or critical
121
+ infrastructure) not decided yet, record a `kind: compliance` constraint
122
+ whose statement names the OPEN QUESTION and what it decides ("Whether the
123
+ application will process health or clinical data is not decided yet; it
124
+ decides whether health-data rules apply."), with the creator's reason as
125
+ its rationale when they gave one. Never leave it out, which a later step
126
+ reads as "no", and never answer it either way from the other answers.
117
127
 
118
128
  ### The product's shape: workflow, users, boundary
119
129
 
@@ -127,7 +137,8 @@ Carry them into the snapshot in the creator's own terms:
127
137
 
128
138
  - the workflow's stages, in order, in the idea's `description`;
129
139
  - the user groups, what each does, and their devices, in the problem's "who is affected" (and in the
130
- idea when the product's shape depends on them, such as work done in the field on a phone);
140
+ idea when the product's shape depends on them, such as work done in the field on a phone; in the
141
+ idea's `description` when the creator left the problem not decided yet, so they are never lost);
131
142
  - each scope boundary as a `constraint` of kind `business`, stated as an exclusion ("Invoicing is out
132
143
  of scope: customers keep their accounting tool"), with the creator's reason as its rationale.
133
144
 
@@ -142,8 +153,12 @@ A single `VisionSnapshot`:
142
153
  otherwise).
143
154
  - `idea` — the required anchor (`oneLiner`, `description`, optional `notes`).
144
155
  - `problem` / `mission` — the optional singletons, present only if elicited.
156
+ When the creator left the problem statement or the mission NOT DECIDED YET,
157
+ emit that singleton as `null`; never fill it from the other answers.
145
158
  - `successCriteria[]` — each with a stable kebab-case `ref` prefixed
146
- `success-criterion-`, unique across the set.
159
+ `success-criterion-`, unique across the set. Empty when the creator left the
160
+ success criteria not decided yet: an empty set is honest, and the validator
161
+ WARNs on it so it stays visible.
147
162
  - `constraints[]` — each with a stable kebab-case `ref` prefixed `constraint-`,
148
163
  unique across the set, and a `kind`.
149
164