@wildo-ai/framework-knowledge 1.1.4 → 1.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (848) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +227 -6
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  6. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.loader.js +47 -1
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  10. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  11. package/dist/esm/index.d.ts.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  13. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
  17. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  18. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
  19. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  20. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
  21. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
  23. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
  25. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
  27. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  31. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  32. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
  33. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  36. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
  37. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  38. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
  39. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  40. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
  41. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  42. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  43. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
  45. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  47. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  48. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
  49. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  50. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
  51. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
  53. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
  55. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  56. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
  57. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  58. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  59. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  60. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
  61. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  62. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  63. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
  65. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
  67. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  68. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
  69. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  70. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
  71. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  72. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
  73. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  74. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  75. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  76. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  77. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  78. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  79. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  81. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  82. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
  83. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
  85. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  87. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  88. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  89. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  90. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
  91. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
  93. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
  95. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
  97. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  99. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
  101. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
  103. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
  105. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
  107. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  108. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
  109. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  110. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
  111. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
  113. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  114. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
  115. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  116. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
  117. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  118. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
  119. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
  121. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  122. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
  123. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  124. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
  125. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  126. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  127. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  128. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  129. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  130. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  131. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  132. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
  133. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  134. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  135. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  136. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
  137. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  138. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  139. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  140. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
  141. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  142. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  143. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  144. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
  145. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  146. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
  147. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  148. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
  149. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  150. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
  151. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  152. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
  153. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  154. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  155. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  156. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  157. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  158. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
  159. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  160. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
  161. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  162. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
  163. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  164. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
  165. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  166. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
  167. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  168. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
  169. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  170. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  171. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  172. package/dist/knowledge/manifest.json +9 -8
  173. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  174. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  175. package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
  176. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
  177. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  178. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  179. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
  180. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
  181. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  182. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  183. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
  184. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
  185. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
  186. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
  187. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
  188. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
  189. package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
  190. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
  191. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
  192. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
  193. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
  194. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
  195. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
  196. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
  197. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
  198. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
  199. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
  200. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  201. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  202. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
  203. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  204. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
  205. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
  206. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
  207. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  208. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
  209. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  210. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
  211. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  212. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  213. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
  214. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  215. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  216. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  217. package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
  218. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
  219. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  220. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  221. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
  222. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  223. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  224. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  225. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
  226. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
  227. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
  228. package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
  229. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
  230. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  231. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
  232. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  233. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  234. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
  235. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
  236. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  237. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
  238. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  239. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  240. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
  241. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
  242. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  243. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
  244. package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
  245. package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
  246. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  247. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
  248. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  249. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
  250. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  251. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
  252. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  253. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
  254. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  255. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  256. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
  257. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
  258. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  259. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  260. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  261. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
  262. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
  263. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
  264. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  265. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  266. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  267. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
  268. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
  269. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
  270. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  271. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  272. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
  273. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
  274. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  275. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
  276. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  277. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  278. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  279. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  280. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  281. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  282. package/dist/knowledge/references/application-maturity.config.md +319 -0
  283. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  284. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  285. package/dist/knowledge/references/brand.asset.config.md +8 -16
  286. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  287. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  288. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  289. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  290. package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
  291. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  292. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  293. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  294. package/dist/knowledge/references/capability-composition.config.md +155 -0
  295. package/dist/knowledge/references/cli.market.utils.md +1 -0
  296. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  297. package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
  298. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  299. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  300. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  301. package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
  302. package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
  303. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
  304. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  305. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  306. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  307. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  308. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
  309. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
  310. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  311. package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
  312. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  313. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  314. package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
  315. package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
  316. package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
  317. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
  318. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
  319. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  320. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
  321. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
  322. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
  323. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
  324. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  325. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  326. package/dist/knowledge/references/experience-plan.config.md +311 -0
  327. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
  328. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  329. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
  330. package/dist/knowledge/references/integration-plan.config.md +185 -0
  331. package/dist/knowledge/references/market.alternative.config.md +1 -1
  332. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  333. package/dist/knowledge/references/market.channel.config.md +3 -3
  334. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  335. package/dist/knowledge/references/market.gain.config.md +1 -1
  336. package/dist/knowledge/references/market.icp.config.md +2 -2
  337. package/dist/knowledge/references/market.job.config.md +1 -1
  338. package/dist/knowledge/references/market.message-template.config.md +2 -2
  339. package/dist/knowledge/references/market.objection.config.md +1 -1
  340. package/dist/knowledge/references/market.pain.config.md +1 -1
  341. package/dist/knowledge/references/market.persona.config.md +2 -2
  342. package/dist/knowledge/references/market.proof.config.md +1 -1
  343. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  344. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  345. package/dist/knowledge/references/market.trigger.config.md +1 -1
  346. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  347. package/dist/knowledge/references/placement-plan.config.md +369 -0
  348. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  349. package/dist/knowledge/references/platform.config.backing-services.md +0 -21
  350. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  351. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  352. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  353. package/dist/knowledge/references/platform.config.saas.md +261 -9
  354. package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
  355. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  356. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  357. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  358. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  359. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  360. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  361. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  362. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  363. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
  364. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  365. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  366. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
  367. package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
  368. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  369. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
  370. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  371. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
  372. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  373. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  374. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
  375. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  376. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  377. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  378. package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
  379. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  380. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  381. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  382. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  383. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  384. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  385. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  386. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
  387. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  388. package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
  389. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  390. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  391. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  392. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  393. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  394. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  395. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  396. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  397. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  398. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  399. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  400. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  401. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
  402. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  403. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  404. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
  405. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
  406. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
  407. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  408. package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
  409. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  410. package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
  411. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  412. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
  413. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
  414. package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
  415. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  416. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
  417. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  418. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  419. package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
  420. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
  421. package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
  422. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  423. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  424. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  425. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  426. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  427. package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
  428. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  429. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  430. package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
  431. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  432. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  433. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
  434. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
  435. package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
  436. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
  437. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  438. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  439. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
  440. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  441. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  442. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  443. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  444. package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
  445. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
  446. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  447. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  448. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
  449. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  450. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  451. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  452. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
  453. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  454. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  455. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  456. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  457. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  458. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  459. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  460. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  461. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  462. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  463. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  464. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  465. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  466. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  467. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
  468. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
  469. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  470. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  471. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  472. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  473. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  474. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  475. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  476. package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
  477. package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
  478. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  479. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  480. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  481. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  482. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  483. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  484. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  485. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
  486. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
  487. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
  488. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  489. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
  490. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  491. package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
  492. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
  493. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  494. package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
  495. package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
  496. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  497. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
  498. package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
  499. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  500. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  501. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  502. package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
  503. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  504. package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
  505. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  506. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  507. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  508. package/dist/knowledge/references/website-plan.config.md +205 -0
  509. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  510. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  511. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  512. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
  513. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
  514. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
  515. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  516. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  517. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  518. package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
  519. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
  520. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
  521. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  522. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  523. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  524. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  525. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
  526. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
  527. package/dist/knowledge/references/zod.factories.address.md +118 -0
  528. package/dist/knowledge/references/zod.factories.code.md +2 -0
  529. package/dist/knowledge/references/zod.factories.duration.md +2 -0
  530. package/dist/knowledge/references/zod.factories.money.md +2 -0
  531. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  532. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  533. package/dist/knowledge/registries/framework-topics.json +1215 -11
  534. package/dist/knowledge/registries/playbooks.json +454 -50
  535. package/dist/knowledge/registries/source-tags.json +3153 -1043
  536. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  537. package/dist/knowledge/rules/live-context-door.md +108 -0
  538. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  539. package/dist/knowledge/skills/INDEX.md +46 -11
  540. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
  541. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  542. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  543. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
  544. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  545. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  546. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
  547. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
  548. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
  549. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
  550. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  551. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
  552. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  553. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  554. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  555. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
  556. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
  557. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  558. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  559. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
  560. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  561. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
  562. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  563. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  564. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  565. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
  566. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
  567. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
  568. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
  569. package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
  570. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
  571. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  572. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  573. package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
  574. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  575. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  576. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  577. package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
  578. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  579. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
  580. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  581. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  582. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
  583. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
  584. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  585. package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
  586. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
  587. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
  588. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  589. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
  590. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
  591. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  592. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
  593. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
  594. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  595. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  596. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  597. package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
  598. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  599. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  600. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  601. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  602. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
  603. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  604. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
  605. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  606. package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
  607. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
  608. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
  609. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
  610. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  611. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
  612. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  613. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
  614. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
  615. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
  616. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
  617. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  618. package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
  619. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  620. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
  621. package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
  622. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
  623. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  624. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  625. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  626. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  627. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
  628. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  629. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  630. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
  631. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
  632. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
  633. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
  634. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
  635. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
  636. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  637. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  638. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
  639. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  640. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
  641. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
  642. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  643. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  644. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  645. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  646. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
  647. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
  648. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
  649. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
  650. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
  651. package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
  652. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  653. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
  654. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  655. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  656. package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
  657. package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
  658. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
  659. package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
  660. package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
  661. package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
  662. package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
  663. package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
  664. package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
  665. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
  666. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  667. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  668. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
  669. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
  670. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  671. package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
  672. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  673. package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
  674. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
  675. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
  676. package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
  677. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
  678. package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
  679. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
  680. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
  681. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
  682. package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
  683. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
  684. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
  685. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  686. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
  687. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
  688. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
  689. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  690. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  691. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  692. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  693. package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
  694. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  695. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  696. package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
  697. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
  698. package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
  699. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
  700. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
  701. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  702. package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
  703. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  704. package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
  705. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  706. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  707. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  708. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
  709. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  710. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
  711. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
  712. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  713. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
  714. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
  715. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
  716. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
  717. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
  718. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  719. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  720. package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
  721. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
  722. package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
  723. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
  724. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  725. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  726. package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
  727. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
  728. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
  729. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
  730. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
  731. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
  732. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  733. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  734. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  735. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
  736. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  737. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
  738. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  739. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
  740. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  741. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
  742. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
  743. package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
  744. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
  745. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  746. package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
  747. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
  748. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
  749. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
  750. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
  751. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  752. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  753. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  754. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
  755. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
  756. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  757. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  758. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
  759. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  760. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  761. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
  762. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
  763. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  764. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  765. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
  766. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
  767. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  768. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
  769. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  770. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  771. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  772. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  773. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
  774. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
  775. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
  776. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
  777. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
  778. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  779. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
  780. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
  781. package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
  782. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  783. package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
  784. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  785. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  786. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  787. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
  788. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
  789. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  790. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
  791. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
  792. package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
  793. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  794. package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
  795. package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
  796. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  797. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
  798. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
  799. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
  800. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  801. package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
  802. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  803. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
  804. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
  805. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  806. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
  807. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  808. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  809. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
  810. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
  811. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
  812. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
  813. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
  814. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
  815. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
  816. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
  817. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
  818. package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
  819. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  820. package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
  821. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
  822. package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
  823. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
  824. package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
  825. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
  826. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
  827. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
  828. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
  829. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
  830. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
  831. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
  832. package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
  833. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
  834. package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
  835. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
  836. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
  837. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
  838. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
  839. package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
  840. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  841. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  842. package/dist/knowledge/topic-index.json +5335 -1010
  843. package/dist/tsconfig.build.tsbuildinfo +1 -1
  844. package/dist/tsconfig.tsbuildinfo +1 -1
  845. package/package.json +4 -4
  846. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  847. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  848. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -1,14 +1,9 @@
1
1
  {
2
2
  "ref": "top_down.brand-identity",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "phase": "top_down",
5
5
  "intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name, the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "top_down"
11
- },
12
7
  {
13
8
  "kind": "artifact_exists",
14
9
  "selector": {
@@ -23,22 +18,28 @@
23
18
  {
24
19
  "family": "market-snapshot",
25
20
  "intent": "voice"
21
+ },
22
+ {
23
+ "family": "brand-brief"
26
24
  }
27
25
  ],
28
26
  "outputs": [
29
27
  {
30
28
  "family": "brand-brief",
31
29
  "schemaRef": "saas-specifications:BrandSnapshot",
32
- "placement": ".wildo-saas/journey/<journeyId>/brand-brief/",
33
30
  "description": "The visual-identity artifact — one BrandSnapshot per product (name + logo direction + visual tone; resolvedAssets left empty for the companion logo step to populate). Read by the companion logo generation step (which produces the master + derived assets) and, via resolvedAssets, by every downstream logo/favicon/brand-image consumer. Validated by validateBrandSnapshot."
34
31
  }
35
32
  ],
33
+ "stepOutputs": [],
36
34
  "method": {
37
- "guidance": "# Brand Identity — Interview 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 question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the vision to derive symbolism/tone)\n// TODO CLI COMMAND: wildo context brand-brief (read the existing brand brief, if any, to refine it)\n\n## References\n\n- `.claude/skills/brand-logo-authoring/SKILL.md` — the field contracts for the\n `BrandSnapshot` (name / logoDirection / visualTone), the mark-type selection\n table, background derivation-safety, and deriving the visual tone from the\n market voice.\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n whether a `vision-brief` / `brand-brief` already exists.\n",
35
+ "guidance": "# Brand Identity — Interview 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 question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity interviewer**. Your job is to draw the product's\nVISUAL identity out of the creator and capture it as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## The elicitation posture\n\n- **Interview, do not fill a form.** The typed questions on this playbook\n (`method.elicitation`) are your backbone, not your ceiling. Ask them in a\n natural order, reflect each answer back in one line, and let the creator\n correct you before moving on.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**; the\n logo direction and visual tone are OPTIONAL and elicited progressively. If the\n creator can only name the brand today, capture it, note what is still open,\n and stop — the snapshot persists as partially-directed and this playbook can\n resume. Never invent a mark direction the creator did not give you.\n- **One product, one brand.** The snapshot is a single aggregate — one name,\n one logo direction, one visual tone. If the creator describes two brands,\n stop and ask which one this journey is for.\n\n## What you elicit — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next. A brand without a name has nothing\n for a mark to render; do not proceed until you have it.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — pick the archetype. **Default to `COMBINATION_MARK`** (symbol +\n wordmark) — it is the only archetype that natively yields BOTH a header\n lockup and a square symbol for favicons/app-icons. Reach for `WORDMARK`\n (text-only) only when the brand is genuinely wordmark-only; warn the creator\n that a wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases).\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea**.\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable).\n - `backgroundTreatment` — keep `TRANSPARENT_ISOLATED` (the default and the\n only treatment that rasterizes losslessly into every derived asset). A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice: 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and optional hex `colorSeeds` pinned only\n when the brand has already committed to anchors that must agree with the\n design system.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present only if elicited.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-eliciting it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n- `journey-status` — reads the current journey state and whether a\n `vision-brief` / `brand-brief` already exists. That is a READ a tool-using\n agent performs; you receive its answer as your declared inputs instead, so\n you never need to consult the skill itself.\n",
38
36
  "skillRefs": [
39
37
  "journey-status",
40
38
  "brand-logo-authoring"
41
39
  ],
40
+ "skillBodyRefs": [
41
+ "brand-logo-authoring"
42
+ ],
42
43
  "elicitation": {
43
44
  "questions": [
44
45
  {
@@ -111,17 +112,14 @@
111
112
  "kind": "free_text"
112
113
  }
113
114
  ]
114
- }
115
+ },
116
+ "contextSources": [],
117
+ "draftableDocumentDefinitionRefs": [],
118
+ "suspendsForClarification": false,
119
+ "briefAdequacyGate": true,
120
+ "briefAdequacyExcludedSources": []
115
121
  },
116
122
  "executor": "companion_agent",
117
- "qualityGates": [
118
- {
119
- "ref": "brand-snapshot-valid",
120
- "kind": "deterministic_validator",
121
- "validatorRef": "saas-specifications:validateBrandSnapshot",
122
- "required": true
123
- }
124
- ],
125
123
  "approval": "approve_result",
126
124
  "budget": {
127
125
  "maxRuns": 3
@@ -3,12 +3,7 @@
3
3
  "version": "0.1.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "top_down"
11
- },
12
7
  {
13
8
  "kind": "artifact_valid",
14
9
  "selector": {
@@ -44,15 +39,16 @@
44
39
  {
45
40
  "family": "business-model",
46
41
  "schemaRef": "saas-specifications:BusinessModelLiteSnapshot",
47
- "placement": "specifications/src/business-model/",
48
42
  "description": "A validated revenue-model classification plus at least one pricing plan, each cross-linked to the market ICPs it targets and the requirements it unlocks."
49
43
  }
50
44
  ],
45
+ "stepOutputs": [],
51
46
  "method": {
52
47
  "guidance": "# Business Model — Commercial Intent 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.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **At least one plan.** A business model with no plans carries no information a\n reader could act on. If the creator sells exactly one thing, that is one plan,\n fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] Every `pricePoint` traces to something the creator actually wrote.\n- [ ] Every plan traces to a tier they described. No tier count was rounded up.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
53
48
  "skillRefs": [
54
49
  "journey-status"
55
50
  ],
51
+ "skillBodyRefs": [],
56
52
  "elicitation": {
57
53
  "questions": [
58
54
  {
@@ -89,17 +85,14 @@
89
85
  "kind": "free_text"
90
86
  }
91
87
  ]
92
- }
88
+ },
89
+ "contextSources": [],
90
+ "draftableDocumentDefinitionRefs": [],
91
+ "suspendsForClarification": false,
92
+ "briefAdequacyGate": false,
93
+ "briefAdequacyExcludedSources": []
93
94
  },
94
95
  "executor": "companion_agent",
95
- "qualityGates": [
96
- {
97
- "ref": "business-model-valid",
98
- "kind": "deterministic_validator",
99
- "validatorRef": "saas-specifications:validateBusinessModelLiteSnapshot",
100
- "required": true
101
- }
102
- ],
103
96
  "approval": "approve_result",
104
97
  "budget": {
105
98
  "maxRuns": 3
@@ -40,13 +40,10 @@ exist yet?** — and then record the answer in two places:
40
40
  (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —
41
41
  all in prose). These are **spec-first**: you author them BEFORE the runtime
42
42
  `FeatureDefinition` exists; the factory injects the `ref` later from the
43
- runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). The
44
- cross-registry validators are deliberately **fail-soft while the feature
45
- registry is empty** — so authoring the spec before the code does NOT
46
- crash-loop the app. (`spec-feature-update`)
43
+ runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.
47
44
 
48
- Then you **prioritize** the resulting feature set with a FIT-scoring + Kano
49
- step — kept pluggable and versioned (see "The scoring seam" below).
45
+ Then you **assess fit** for the resulting feature set with a FIT-scoring + Kano
46
+ step — kept pluggable and versioned (see "The scoring seam" below). This does not set build priority.
50
47
 
51
48
  This is a **focused pivot pass**, distinct from value-proposition sharpening
52
49
  (which weighted the benefits) and from scope/roadmap (which slots the features
@@ -68,8 +65,6 @@ anything:
68
65
  real market intent, the real requirements, and the real differentiation — not
69
66
  from scratch.
70
67
 
71
- // TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
72
- // TODO CLI COMMAND: wildo context market-snapshot (read the benefits to map + any existing feature edges)
73
68
 
74
69
  You **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**
75
70
  the refined `market-snapshot` (edge wired) and the `feature-drafts` family (the
@@ -103,9 +98,7 @@ For each benefit in the snapshot:
103
98
  wire `codeHandling` (it links a spec back to a runtime enum member +
104
99
  collection entry that does not exist yet at this phase) — the code-handling
105
100
  provenance is added when the feature is actually built, not now.
106
- `spec-feature-update` is the field-shape authority for a feature spec; here
107
- you use its prose surface only. Keep it a *capability contract*, not an
108
- implementation. (`spec-feature-update`)
101
+ Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.
109
102
  5. **Trace to requirements + vision.** A feature only earns its place if it
110
103
  delivers a benefit that traces to the vision's differentiation AND satisfies
111
104
  real requirements. When a benefit's delivering feature has no requirement
@@ -133,9 +126,12 @@ The scoring / prioritization methodology is expected to change substantially in
133
126
  later phase, so this playbook references the scoring *interface* (via the
134
127
  `market-scoring-interpretation` skill) and consumes its output; it does **not**
135
128
  re-implement the scoring math and does **not** hard-couple to any specific scoring
136
- function (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). Treat
137
- the scorer as a swappable black box: feed it the snapshot, read back the per-ICP
138
- FIT scores + Kano categories, and use them to sanity-check the capability set. If
129
+ function (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). You do
130
+ not run the scorer and must not estimate its output: the per-ICP FIT scores are
131
+ computed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each
132
+ benefit's authored Kano category. Read them there and use them to sanity-check the
133
+ capability set — a `0` carrying a stated reason is structural (an anti-target, or no
134
+ benefit covering that ICP), not a measurement of poor fit. If
139
135
  you find yourself hand-writing a scoring formula, tuning weights to hit a target
140
136
  result, or building an actual build-order prioritization model, **stop** — that is
141
137
  the depth phase's job, and hard-coding it here would break the pluggability
@@ -153,36 +149,17 @@ no draft.
153
149
  benefit appeared, or a draft is genuinely wrong.
154
150
  - **Never orphan a ref.** A benefit points at feature refs; those refs must have
155
151
  a draft (for new features) or a real registry entry (once code exists).
156
- Removing a feature that a benefit still delivers, or a draft a benefit still
157
- points at, orphans the edge. Feature-ref orphans are only resolution-checked
158
- once a feature registry is passed to the validator (not at this phase — the
159
- registry is empty and the check is fail-soft), so honest refinement must not
160
- create the orphan in the first place.
152
+ The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.
161
153
  - **One capability, one ref.** When two benefits are delivered by the same
162
154
  capability, they share the feature ref — do not fork it.
163
155
 
164
156
  ## Quality gate
165
157
 
166
- The refined MarketSnapshot is checked by the deterministic `market-snapshot-valid`
167
- gate (`validateMarketSnapshot`) before anything downstream consumes it. The
168
- capability-mapping invariants it enforces:
158
+ Validate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.
169
159
 
170
- - **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`
171
- is empty; every benefit must be deliverable. This is the headline check this
172
- playbook clears.
173
- - **`ORPHAN_REF` (ERROR)** — a benefit naming a missing pain/gain/job (feature-ref
174
- orphans are only checked once a feature registry is passed — not at this phase).
175
- - The value-proposition invariants inherited from the prior pass
176
- (`MISSING_POSITIONING_FOR_ICP`, `THRESHOLD_BENEFIT_WITHOUT_JOB`,
177
- `MULTIPLE_THRESHOLDS_PER_ICP_JOB`) still apply — do not regress them.
160
+ A draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.
178
161
 
179
- Read `market-snapshot-validation` for the full issue catalogue.
180
-
181
- The `feature-drafts` family has **no snapshot-level deterministic gate at this
182
- phase** — the only feature-spec validator is per-item and needs a ref-bearing
183
- config, which a spec-first draft deliberately omits. Author each draft to the
184
- `spec-feature-update` skill's contract (which carries the per-draft validity
185
- check); the collection-level gate is a filed depth-phase item (see below).
162
+ Validation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.
186
163
 
187
164
  ## Scaffold-depth boundary (deferred to a later depth phase)
188
165
 
@@ -196,11 +173,6 @@ Keep this playbook at scaffold depth. Explicitly **out of scope here**:
196
173
  - **Deep feature-spec drafts.** A draft here is a first-cut capability contract
197
174
  (purpose / roles / use-when). Rich operation inventories, interaction
198
175
  semantics, and UX are the bottom-up build phase's job, not the capability map.
199
- - **A snapshot-level `feature-drafts` validator.** No deterministic validator
200
- exists yet for a *collection* of spec-first drafts (the per-item
201
- `validateFeatureSpecification` needs a ref, which drafts omit). Authoring the
202
- collection-level gate — and deciding whether draft prioritization output is
203
- itself a gated artifact — is depth-phase work.
204
176
  - **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and
205
177
  jobs but NOT market pains/gains, so the "this requirement delivers
206
178
  `gain-X`" trace that would let capability mapping run benefit → requirement →
@@ -215,10 +187,10 @@ scaffold depth — depth is a dedicated later pass done once, holistically.
215
187
 
216
188
  Two artifacts for this journey:
217
189
 
218
- 1. The SAME **MarketSnapshot** at `.wildo-saas/journey/<journeyId>/market-snapshot/`,
190
+ 1. The SAME **MarketSnapshot** at `specifications/src/market/index.ts`,
219
191
  with every benefit's `deliveredByFeatureRefs` edge wired to its delivering
220
192
  feature(s), passing the `market-snapshot-valid` gate.
221
- 2. The **feature-drafts** at `.wildo-saas/journey/<journeyId>/feature-drafts/` —
193
+ 2. The **feature-drafts** at `specifications/src/feature-drafts/index.ts` —
222
194
  one spec-first `FeatureSpecificationDraft` per new delivering feature.
223
195
 
224
196
  The creator reviews the result (approval posture `approve_result`) before it is
@@ -226,14 +198,18 @@ accepted as the journey's capability map.
226
198
 
227
199
  ## References
228
200
 
229
- - `.claude/skills/journey-status/SKILL.md` — read the current journey state and
201
+ These are skill FOLDERS installed in the application, named so each piece of work has an
202
+ authoring contract a later coding agent can open. This step has no tools and does not open them;
203
+ what reaches you is this method, your declared inputs, and the brief's own sections.
204
+
205
+ - `journey-status` — read the current journey state and
230
206
  scope, and confirm a `market-snapshot` already exists to map from.
231
- - `.claude/skills/market-add-feature-benefit/SKILL.md` — author/adjust the benefit
207
+ - `market-add-feature-benefit` — author/adjust the benefit
232
208
  claims and wire their `deliveredByFeatureRefs` edges.
233
- - `.claude/skills/spec-feature-update/SKILL.md` — author the spec-first
209
+ - `spec-feature-update` — author the spec-first
234
210
  `FeatureSpecificationDraft`(s) for the new delivering features.
235
- - `.claude/skills/market-scoring-interpretation/SKILL.md` — the FIT/Kano scoring
211
+ - `market-scoring-interpretation` — the FIT/Kano scoring
236
212
  interface: interpret the deterministic scorer's ranking to sanity-check the
237
213
  capability set (pluggable seam — consume it, do not re-implement it).
238
- - `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation issue
214
+ - `market-snapshot-validation` — the full validation issue
239
215
  catalogue the quality gate enforces.
@@ -3,12 +3,7 @@
3
3
  "version": "0.1.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Map accepted market benefits and requirements to coherent product capabilities, atomically refining the market benefit-to-feature edges and producing ref-less feature specification drafts. FIT/Kano remains a pluggable fit signal, never an implicit build-order ranking.",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "top_down"
11
- },
12
7
  {
13
8
  "kind": "artifact_valid",
14
9
  "selector": {
@@ -37,41 +32,43 @@
37
32
  },
38
33
  {
39
34
  "family": "vision-brief"
35
+ },
36
+ {
37
+ "family": "feature-drafts"
40
38
  }
41
39
  ],
42
40
  "outputs": [
43
41
  {
44
42
  "family": "market-snapshot",
45
43
  "schemaRef": "saas-specifications:MarketSnapshot",
46
- "placement": ".wildo-saas/journey/<journeyId>/market-snapshot/",
47
44
  "description": "The same market snapshot, refined so every benefit names its delivering feature refs."
48
45
  },
49
46
  {
50
47
  "family": "feature-drafts",
51
48
  "schemaRef": "saas-specifications:FeatureSpecificationDrafts",
52
- "placement": ".wildo-saas/journey/<journeyId>/feature-drafts/",
53
49
  "description": "A collection of runner-addressed, ref-less FeatureSpecificationDraft payloads for capabilities without runtime definitions."
54
50
  }
55
51
  ],
52
+ "stepOutputs": [],
56
53
  "method": {
57
- "guidance": "# Capability Map — Benefit → Feature Pivot 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 be\n> iterated. The mapping order, the draft-authoring posture, and the\n> prioritization rubric below are deliberately explicit so they can be tuned\n> against real runs — treat them as a starting rubric, not a frozen contract.\n> The *analytical depth* of the capability work (quantified FIT / Kano scoring\n> precision, a real prioritization model) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **capability architect**. This playbook is the **pivot**: it turns\nthe *value proposition* (what the product promises the market) into *product\ncapability* (the features that actually deliver those promises). Value-proposition\nsharpening already produced a **MarketSnapshot** whose benefits carry weighted\nrelieves/creates/advances edges and per-ICP Kano categories. Your one job is to\nanswer, for every benefit: **which feature delivers this, and does that feature\nexist yet?** — and then record the answer in two places:\n\n1. **The benefit → feature edge** — on the SAME MarketSnapshot, wire every\n benefit's `deliveredByFeatureRefs[]` to the feature(s) that deliver it. This\n edge is the authoritative capability-mapping link (`FeatureBenefitConfig.\n deliveredByFeatureRefs`, required and non-empty): a benefit that is not\n deliverable by any feature is not a real capability. (`market-add-feature-benefit`)\n2. **The spec-first feature drafts** — for every feature the map introduces that\n has **no code registry entry yet**, author a `FeatureSpecificationDraft`\n (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —\n all in prose). These are **spec-first**: you author them BEFORE the runtime\n `FeatureDefinition` exists; the factory injects the `ref` later from the\n runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). The\n cross-registry validators are deliberately **fail-soft while the feature\n registry is empty** — so authoring the spec before the code does NOT\n crash-loop the app. (`spec-feature-update`)\n\nThen you **prioritize** the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below).\n\nThis is a **focused pivot pass**, distinct from value-proposition sharpening\n(which weighted the benefits) and from scope/roadmap (which slots the features\ninto releases). Where value-proposition made the benefits sharp, you make each\nbenefit *deliverable* and give every new capability its first spec.\n\n## Read state first — the two families you read, the two you write\n\nThis playbook is **idempotent** and a *refinement*: a MarketSnapshot must\nalready exist (the `artifact_exists` precondition enforces it). Before mapping\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here).\n2. Read the existing **MarketSnapshot** (the benefits and their weighting),\n the **requirements** (`requirements` family — the functional/non-functional\n requirements the features must satisfy), and the **VisionSnapshot**\n (`vision-brief` — the differentiation anchor). You map capability against the\n real market intent, the real requirements, and the real differentiation — not\n from scratch.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context market-snapshot (read the benefits to map + any existing feature edges)\n\nYou **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**\nthe refined `market-snapshot` (edge wired) and the `feature-drafts` family (the\nnew drafts).\n\n## The mapping loop (benefit by benefit)\n\nFor each benefit in the snapshot:\n\n1. **Identify the delivering feature(s).** Ask what capability the product must\n have for this benefit's claim to be true. Prefer *one clear feature per\n benefit*; a benefit may legitimately need more than one, and one feature may\n deliver several benefits.\n2. **Reuse before you create.** If a delivering feature already appears on\n another benefit's `deliveredByFeatureRefs`, or already has a draft from an\n earlier run, **reuse that same feature ref** — never mint a second ref for the\n same capability. Reusing refs is what keeps the map coherent and lets the\n downstream scope/roadmap playbook slot each feature exactly once.\n3. **Wire the edge.** Add the feature ref(s) to the benefit's\n `deliveredByFeatureRefs[]`. Every benefit must end with a non-empty edge —\n the gate fails a benefit with an empty `deliveredByFeatureRefs` as\n `EMPTY_BENEFIT_DELIVERED_BY` (ERROR).\n4. **Draft the new feature (spec-first).** If the feature is new (no code\n registry entry, no prior draft), author its `FeatureSpecificationDraft` into\n the `feature-drafts` family. A draft is the **prose subset** of a feature\n spec: a business-language `purpose`, its `businessRole` / optional\n `lifecycleRole`, `useWhen` / `avoidWhen`, optional `businessConstraints`, and\n the `availabilityRole` (how the feature gates / packages). **Author ONLY these\n prose fields.** Do NOT author a `ref` — the factory injects it later from the\n runtime feature identifier, which is why a draft is authored ref-less. Do NOT\n wire `codeHandling` (it links a spec back to a runtime enum member +\n collection entry that does not exist yet at this phase) — the code-handling\n provenance is added when the feature is actually built, not now.\n `spec-feature-update` is the field-shape authority for a feature spec; here\n you use its prose surface only. Keep it a *capability contract*, not an\n implementation. (`spec-feature-update`)\n5. **Trace to requirements + vision.** A feature only earns its place if it\n delivers a benefit that traces to the vision's differentiation AND satisfies\n real requirements. When a benefit's delivering feature has no requirement\n behind it, that is a signal to either add the requirement upstream or drop the\n claim — not to invent a feature the product does not need.\n\n## The scoring seam — FIT + Kano, kept PLUGGABLE and VERSIONED\n\nAssess the mapped capability set with a **FIT-scoring + Kano** step, and let that\nassessment inform how the capabilities get prioritized.\n\n**FIT is a fit signal, NOT a priority ranking — do not conflate them.**\n`computeFeatureFitScoreForICP` answers one narrow question: *how well does this\nfeature serve this ICP* on a deterministic 0–100 scale (edge `degree` × the ICP's\nown edge weight). It deliberately does NOT answer \"which feature do we build\nfirst\" — that is prioritization, a separate, deferred concern. Combine the FIT\nscore with the per-ICP Kano category (`THRESHOLD` = table-stakes, `PERFORMANCE` =\nmore-is-better, `DELIGHTER` = upside) to read *table-stakes vs. upside per\nsegment* — a fit judgement, not a build-order. Bending the FIT score into a\nbuild-order ranking yields wrong answers (this is the locked FIT-vs-priority\nvocabulary the `market-scoring-interpretation` skill enforces).\n\n**This step is a pluggable, versioned interface — bind to it, never embed it.**\nThe scoring / prioritization methodology is expected to change substantially in a\nlater phase, so this playbook references the scoring *interface* (via the\n`market-scoring-interpretation` skill) and consumes its output; it does **not**\nre-implement the scoring math and does **not** hard-couple to any specific scoring\nfunction (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). Treat\nthe scorer as a swappable black box: feed it the snapshot, read back the per-ICP\nFIT scores + Kano categories, and use them to sanity-check the capability set. If\nyou find yourself hand-writing a scoring formula, tuning weights to hit a target\nresult, or building an actual build-order prioritization model, **stop** — that is\nthe depth phase's job, and hard-coding it here would break the pluggability\ncontract (OQ-6).\n\nAt scaffold depth this is a *fit sanity check on the capability set*, not a\ndefended prioritization. The headline gap it surfaces: a table-stakes capability\n(a `THRESHOLD` benefit for a `CORE`/`EXPANSION` ICP) whose delivering feature has\nno draft.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite edges or drafts that are already\n correct. Only add/correct where a benefit lacks a delivering feature, a new\n benefit appeared, or a draft is genuinely wrong.\n- **Never orphan a ref.** A benefit points at feature refs; those refs must have\n a draft (for new features) or a real registry entry (once code exists).\n Removing a feature that a benefit still delivers, or a draft a benefit still\n points at, orphans the edge. Feature-ref orphans are only resolution-checked\n once a feature registry is passed to the validator (not at this phase — the\n registry is empty and the check is fail-soft), so honest refinement must not\n create the orphan in the first place.\n- **One capability, one ref.** When two benefits are delivered by the same\n capability, they share the feature ref — do not fork it.\n\n## Quality gate\n\nThe refined MarketSnapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\ncapability-mapping invariants it enforces:\n\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must be deliverable. This is the headline check this\n playbook clears.\n- **`ORPHAN_REF` (ERROR)** — a benefit naming a missing pain/gain/job (feature-ref\n orphans are only checked once a feature registry is passed — not at this phase).\n- The value-proposition invariants inherited from the prior pass\n (`MISSING_POSITIONING_FOR_ICP`, `THRESHOLD_BENEFIT_WITHOUT_JOB`,\n `MULTIPLE_THRESHOLDS_PER_ICP_JOB`) still apply — do not regress them.\n\nRead `market-snapshot-validation` for the full issue catalogue.\n\nThe `feature-drafts` family has **no snapshot-level deterministic gate at this\nphase** — the only feature-spec validator is per-item and needs a ref-bearing\nconfig, which a spec-first draft deliberately omits. Author each draft to the\n`spec-feature-update` skill's contract (which carries the per-draft validity\ncheck); the collection-level gate is a filed depth-phase item (see below).\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **A real prioritization model.** The FIT/Kano step here is a *fit* sanity\n check, not a defended, weighted, capacity-fitted *prioritization* (RICE/WSJF\n and the like are later-phase — and FIT is not priority, see the scoring seam).\n The scoring seam stays pluggable — do NOT build or tune a scoring or\n build-order model in this playbook.\n- **Deep feature-spec drafts.** A draft here is a first-cut capability contract\n (purpose / roles / use-when). Rich operation inventories, interaction\n semantics, and UX are the bottom-up build phase's job, not the capability map.\n- **A snapshot-level `feature-drafts` validator.** No deterministic validator\n exists yet for a *collection* of spec-first drafts (the per-item\n `validateFeatureSpecification` needs a ref, which drafts omit). Authoring the\n collection-level gate — and deciding whether draft prioritization output is\n itself a gated artifact — is depth-phase work.\n- **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and\n jobs but NOT market pains/gains, so the \"this requirement delivers\n `gain-X`\" trace that would let capability mapping run benefit → requirement →\n feature *deterministically* is lossy (expressible only in prose). Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase\n question — do NOT reshape the requirements contract here.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n1. The SAME **MarketSnapshot** at `.wildo-saas/journey/<journeyId>/market-snapshot/`,\n with every benefit's `deliveredByFeatureRefs` edge wired to its delivering\n feature(s), passing the `market-snapshot-valid` gate.\n2. The **feature-drafts** at `.wildo-saas/journey/<journeyId>/feature-drafts/` —\n one spec-first `FeatureSpecificationDraft` per new delivering feature.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's capability map.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm a `market-snapshot` already exists to map from.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `.claude/skills/spec-feature-update/SKILL.md` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — the FIT/Kano scoring\n interface: interpret the deterministic scorer's ranking to sanity-check the\n capability set (pluggable seam — consume it, do not re-implement it).\n- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation issue\n catalogue the quality gate enforces.\n",
54
+ "guidance": "# Capability Map — Benefit → Feature Pivot 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 be\n> iterated. The mapping order, the draft-authoring posture, and the\n> prioritization rubric below are deliberately explicit so they can be tuned\n> against real runs — treat them as a starting rubric, not a frozen contract.\n> The *analytical depth* of the capability work (quantified FIT / Kano scoring\n> precision, a real prioritization model) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **capability architect**. This playbook is the **pivot**: it turns\nthe *value proposition* (what the product promises the market) into *product\ncapability* (the features that actually deliver those promises). Value-proposition\nsharpening already produced a **MarketSnapshot** whose benefits carry weighted\nrelieves/creates/advances edges and per-ICP Kano categories. Your one job is to\nanswer, for every benefit: **which feature delivers this, and does that feature\nexist yet?** — and then record the answer in two places:\n\n1. **The benefit → feature edge** — on the SAME MarketSnapshot, wire every\n benefit's `deliveredByFeatureRefs[]` to the feature(s) that deliver it. This\n edge is the authoritative capability-mapping link (`FeatureBenefitConfig.\n deliveredByFeatureRefs`, required and non-empty): a benefit that is not\n deliverable by any feature is not a real capability. (`market-add-feature-benefit`)\n2. **The spec-first feature drafts** — for every feature the map introduces that\n has **no code registry entry yet**, author a `FeatureSpecificationDraft`\n (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —\n all in prose). These are **spec-first**: you author them BEFORE the runtime\n `FeatureDefinition` exists; the factory injects the `ref` later from the\n runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.\n\nThen you **assess fit** for the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below). This does not set build priority.\n\nThis is a **focused pivot pass**, distinct from value-proposition sharpening\n(which weighted the benefits) and from scope/roadmap (which slots the features\ninto releases). Where value-proposition made the benefits sharp, you make each\nbenefit *deliverable* and give every new capability its first spec.\n\n## Read state first — the two families you read, the two you write\n\nThis playbook is **idempotent** and a *refinement*: a MarketSnapshot must\nalready exist (the `artifact_exists` precondition enforces it). Before mapping\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here).\n2. Read the existing **MarketSnapshot** (the benefits and their weighting),\n the **requirements** (`requirements` family — the functional/non-functional\n requirements the features must satisfy), and the **VisionSnapshot**\n (`vision-brief` — the differentiation anchor). You map capability against the\n real market intent, the real requirements, and the real differentiation — not\n from scratch.\n\n\nYou **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**\nthe refined `market-snapshot` (edge wired) and the `feature-drafts` family (the\nnew drafts).\n\n## The mapping loop (benefit by benefit)\n\nFor each benefit in the snapshot:\n\n1. **Identify the delivering feature(s).** Ask what capability the product must\n have for this benefit's claim to be true. Prefer *one clear feature per\n benefit*; a benefit may legitimately need more than one, and one feature may\n deliver several benefits.\n2. **Reuse before you create.** If a delivering feature already appears on\n another benefit's `deliveredByFeatureRefs`, or already has a draft from an\n earlier run, **reuse that same feature ref** — never mint a second ref for the\n same capability. Reusing refs is what keeps the map coherent and lets the\n downstream scope/roadmap playbook slot each feature exactly once.\n3. **Wire the edge.** Add the feature ref(s) to the benefit's\n `deliveredByFeatureRefs[]`. Every benefit must end with a non-empty edge —\n the gate fails a benefit with an empty `deliveredByFeatureRefs` as\n `EMPTY_BENEFIT_DELIVERED_BY` (ERROR).\n4. **Draft the new feature (spec-first).** If the feature is new (no code\n registry entry, no prior draft), author its `FeatureSpecificationDraft` into\n the `feature-drafts` family. A draft is the **prose subset** of a feature\n spec: a business-language `purpose`, its `businessRole` / optional\n `lifecycleRole`, `useWhen` / `avoidWhen`, optional `businessConstraints`, and\n the `availabilityRole` (how the feature gates / packages). **Author ONLY these\n prose fields.** Do NOT author a `ref` — the factory injects it later from the\n runtime feature identifier, which is why a draft is authored ref-less. Do NOT\n wire `codeHandling` (it links a spec back to a runtime enum member +\n collection entry that does not exist yet at this phase) — the code-handling\n provenance is added when the feature is actually built, not now.\n Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.\n5. **Trace to requirements + vision.** A feature only earns its place if it\n delivers a benefit that traces to the vision's differentiation AND satisfies\n real requirements. When a benefit's delivering feature has no requirement\n behind it, that is a signal to either add the requirement upstream or drop the\n claim — not to invent a feature the product does not need.\n\n## The scoring seam — FIT + Kano, kept PLUGGABLE and VERSIONED\n\nAssess the mapped capability set with a **FIT-scoring + Kano** step, and let that\nassessment inform how the capabilities get prioritized.\n\n**FIT is a fit signal, NOT a priority ranking — do not conflate them.**\n`computeFeatureFitScoreForICP` answers one narrow question: *how well does this\nfeature serve this ICP* on a deterministic 0–100 scale (edge `degree` × the ICP's\nown edge weight). It deliberately does NOT answer \"which feature do we build\nfirst\" — that is prioritization, a separate, deferred concern. Combine the FIT\nscore with the per-ICP Kano category (`THRESHOLD` = table-stakes, `PERFORMANCE` =\nmore-is-better, `DELIGHTER` = upside) to read *table-stakes vs. upside per\nsegment* — a fit judgement, not a build-order. Bending the FIT score into a\nbuild-order ranking yields wrong answers (this is the locked FIT-vs-priority\nvocabulary the `market-scoring-interpretation` skill enforces).\n\n**This step is a pluggable, versioned interface — bind to it, never embed it.**\nThe scoring / prioritization methodology is expected to change substantially in a\nlater phase, so this playbook references the scoring *interface* (via the\n`market-scoring-interpretation` skill) and consumes its output; it does **not**\nre-implement the scoring math and does **not** hard-couple to any specific scoring\nfunction (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). You do\nnot run the scorer and must not estimate its output: the per-ICP FIT scores are\ncomputed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each\nbenefit's authored Kano category. Read them there and use them to sanity-check the\ncapability set — a `0` carrying a stated reason is structural (an anti-target, or no\nbenefit covering that ICP), not a measurement of poor fit. If\nyou find yourself hand-writing a scoring formula, tuning weights to hit a target\nresult, or building an actual build-order prioritization model, **stop** — that is\nthe depth phase's job, and hard-coding it here would break the pluggability\ncontract (OQ-6).\n\nAt scaffold depth this is a *fit sanity check on the capability set*, not a\ndefended prioritization. The headline gap it surfaces: a table-stakes capability\n(a `THRESHOLD` benefit for a `CORE`/`EXPANSION` ICP) whose delivering feature has\nno draft.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite edges or drafts that are already\n correct. Only add/correct where a benefit lacks a delivering feature, a new\n benefit appeared, or a draft is genuinely wrong.\n- **Never orphan a ref.** A benefit points at feature refs; those refs must have\n a draft (for new features) or a real registry entry (once code exists).\n The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.\n- **One capability, one ref.** When two benefits are delivered by the same\n capability, they share the feature ref — do not fork it.\n\n## Quality gate\n\nValidate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.\n\nA draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.\n\nValidation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **A real prioritization model.** The FIT/Kano step here is a *fit* sanity\n check, not a defended, weighted, capacity-fitted *prioritization* (RICE/WSJF\n and the like are later-phase — and FIT is not priority, see the scoring seam).\n The scoring seam stays pluggable — do NOT build or tune a scoring or\n build-order model in this playbook.\n- **Deep feature-spec drafts.** A draft here is a first-cut capability contract\n (purpose / roles / use-when). Rich operation inventories, interaction\n semantics, and UX are the bottom-up build phase's job, not the capability map.\n- **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and\n jobs but NOT market pains/gains, so the \"this requirement delivers\n `gain-X`\" trace that would let capability mapping run benefit → requirement →\n feature *deterministically* is lossy (expressible only in prose). Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase\n question — do NOT reshape the requirements contract here.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nTwo artifacts for this journey:\n\n1. The SAME **MarketSnapshot** at `specifications/src/market/index.ts`,\n with every benefit's `deliveredByFeatureRefs` edge wired to its delivering\n feature(s), passing the `market-snapshot-valid` gate.\n2. The **feature-drafts** at `specifications/src/feature-drafts/index.ts` —\n one spec-first `FeatureSpecificationDraft` per new delivering feature.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's capability map.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `journey-status` — read the current journey state and\n scope, and confirm a `market-snapshot` already exists to map from.\n- `market-add-feature-benefit` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `spec-feature-update` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `market-scoring-interpretation` — the FIT/Kano scoring\n interface: interpret the deterministic scorer's ranking to sanity-check the\n capability set (pluggable seam — consume it, do not re-implement it).\n- `market-snapshot-validation` — the full validation issue\n catalogue the quality gate enforces.\n",
58
55
  "skillRefs": [
59
56
  "journey-status",
60
57
  "market-add-feature-benefit",
61
58
  "market-scoring-interpretation",
62
59
  "market-snapshot-validation",
63
60
  "spec-feature-update"
64
- ]
61
+ ],
62
+ "skillBodyRefs": [],
63
+ "contextSources": [
64
+ "market_fit_scores"
65
+ ],
66
+ "draftableDocumentDefinitionRefs": [],
67
+ "suspendsForClarification": false,
68
+ "briefAdequacyGate": false,
69
+ "briefAdequacyExcludedSources": []
65
70
  },
66
71
  "executor": "companion_agent",
67
- "qualityGates": [
68
- {
69
- "ref": "capability-map-output-set-valid",
70
- "kind": "deterministic_validator",
71
- "validatorRef": "saas-specifications:validateCapabilityMapOutputSet",
72
- "required": true
73
- }
74
- ],
75
72
  "approval": "approve_result",
76
73
  "budget": {
77
74
  "maxRuns": 3
@@ -0,0 +1,41 @@
1
+ # Compliance Analysis — the evidence-grounded posture composite
2
+
3
+ ### Target Application Framing
4
+
5
+ This knowledge is for configuring behavior in the target application.
6
+ Wildo is the framework surface being used, not the product being built.
7
+
8
+ Read and apply these patterns from the application-developer point of view:
9
+
10
+ - how the application should configure the relevant app-level file
11
+ - how the application should use framework-provided factories, enums, and helpers
12
+ - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
+
14
+
15
+ You are the **conductor's scheduler**, not an author. This composite exists so the
16
+ application's compliance posture rests on regime texts and regulator pages someone
17
+ actually read — not on what a model remembers about the law, which is confident,
18
+ fluent, and stale in exactly the cases that carry liability.
19
+
20
+ ## The shape
21
+
22
+ Three children, self-ordered by their own preconditions:
23
+
24
+ 1. **compliance-research** — a read-only web lane gathering regime evidence for the
25
+ jurisdictions, data classes and sector the vision (and the creator's answers)
26
+ put in scope. Returns a condensed, source-attributed brief.
27
+ 2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to
28
+ state a posture from, and when it is not, names precisely what is missing so the
29
+ next research round is aimed rather than repeated.
30
+ 3. **compliance-posture** — the artifact-producing child: records each applicable
31
+ regime as a `compliance`-kind constraint on the vision, deriving from the
32
+ creator's elicitation answers AND the gathered evidence, only once the adequacy
33
+ gate has returned ADEQUATE.
34
+
35
+ ## What a round's research objective should name
36
+
37
+ Compose each research objective for THIS round: on the first pass, the candidate
38
+ regimes the vision's jurisdictions/data/sector suggest (verify applicability
39
+ triggers against authoritative sources — regulator pages, official texts, not
40
+ blogs); on later passes, exactly the gaps the adequacy verdict named. Never re-ask
41
+ what a prior round established — its evidence is in the step results.
@@ -0,0 +1,101 @@
1
+ {
2
+ "ref": "top_down.compliance-analysis",
3
+ "version": "0.1.3",
4
+ "phase": "top_down",
5
+ "intent": "Establish the compliance posture by gathering regime EVIDENCE from authoritative sources, judging whether it is enough, and recording the applicable regimes as vision constraints only once it is. An umbrella: it authors nothing itself — its deliverable is what its children land, and the order between them is decided by their own preconditions rather than declared here.",
6
+ "preconditions": [
7
+ {
8
+ "kind": "artifact_valid",
9
+ "selector": {
10
+ "family": "vision-brief"
11
+ }
12
+ }
13
+ ],
14
+ "inputs": [
15
+ {
16
+ "family": "vision-brief"
17
+ }
18
+ ],
19
+ "outputs": [],
20
+ "stepOutputs": [],
21
+ "method": {
22
+ "guidance": "# Compliance Analysis — the evidence-grounded posture composite\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\nYou are the **conductor's scheduler**, not an author. This composite exists so the\napplication's compliance posture rests on regime texts and regulator pages someone\nactually read — not on what a model remembers about the law, which is confident,\nfluent, and stale in exactly the cases that carry liability.\n\n## The shape\n\nThree children, self-ordered by their own preconditions:\n\n1. **compliance-research** — a read-only web lane gathering regime evidence for the\n jurisdictions, data classes and sector the vision (and the creator's answers)\n put in scope. Returns a condensed, source-attributed brief.\n2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to\n state a posture from, and when it is not, names precisely what is missing so the\n next research round is aimed rather than repeated.\n3. **compliance-posture** — the artifact-producing child: records each applicable\n regime as a `compliance`-kind constraint on the vision, deriving from the\n creator's elicitation answers AND the gathered evidence, only once the adequacy\n gate has returned ADEQUATE.\n\n## What a round's research objective should name\n\nCompose each research objective for THIS round: on the first pass, the candidate\nregimes the vision's jurisdictions/data/sector suggest (verify applicability\ntriggers against authoritative sources — regulator pages, official texts, not\nblogs); on later passes, exactly the gaps the adequacy verdict named. Never re-ask\nwhat a prior round established — its evidence is in the step results.\n",
23
+ "skillRefs": [
24
+ "journey-status"
25
+ ],
26
+ "skillBodyRefs": [],
27
+ "elicitation": {
28
+ "questions": [
29
+ {
30
+ "ref": "handles-regulated-data",
31
+ "question": "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?",
32
+ "kind": "confirm"
33
+ },
34
+ {
35
+ "ref": "data-classes",
36
+ "question": "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.",
37
+ "kind": "free_text"
38
+ },
39
+ {
40
+ "ref": "vendor-establishment",
41
+ "question": "Where is the VENDOR established — the legal entity (or intended entity) operating the product, its country/region, and where is the product hosted or planned to be hosted? Territorial-scope tests (GDPR Art. 3, UK GDPR, CCPA \"doing business\") turn on the vendor's establishment and conduct, not only on where users live. Answer \"not yet decided\" for whatever is genuinely open.",
42
+ "kind": "free_text"
43
+ },
44
+ {
45
+ "ref": "jurisdictions",
46
+ "question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
47
+ "kind": "free_text"
48
+ },
49
+ {
50
+ "ref": "sector",
51
+ "question": "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".",
52
+ "kind": "free_text"
53
+ },
54
+ {
55
+ "ref": "gdpr-applies",
56
+ "question": "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)",
57
+ "kind": "confirm"
58
+ },
59
+ {
60
+ "ref": "hipaa-applies",
61
+ "question": "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)",
62
+ "kind": "confirm"
63
+ },
64
+ {
65
+ "ref": "external-assurance-applies",
66
+ "question": "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.",
67
+ "kind": "confirm"
68
+ },
69
+ {
70
+ "ref": "data-residency",
71
+ "question": "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".",
72
+ "kind": "free_text"
73
+ },
74
+ {
75
+ "ref": "additional-regimes",
76
+ "question": "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".",
77
+ "kind": "free_text"
78
+ }
79
+ ]
80
+ },
81
+ "contextSources": [],
82
+ "draftableDocumentDefinitionRefs": [],
83
+ "choreography": {
84
+ "admits": [
85
+ "top_down.compliance-posture",
86
+ "top_down.compliance-research",
87
+ "top_down.compliance-evidence-adequacy"
88
+ ],
89
+ "maximumIterations": 14,
90
+ "maximumLanesPerIteration": 3,
91
+ "maximumDepth": 1,
92
+ "maximumDurationMs": 4800000
93
+ },
94
+ "suspendsForClarification": false,
95
+ "briefAdequacyGate": false,
96
+ "briefAdequacyExcludedSources": []
97
+ },
98
+ "approval": "approve_result",
99
+ "budget": {},
100
+ "onFailure": "keep_and_flag"
101
+ }
@@ -0,0 +1 @@
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-program-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/compliance-program-grounded-in-the-product","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-program-grounded-in-the-product","requirementVersion":1}],"instruction":"The subject under judgment is the landed `compliance-program` file; `document-publication` and `document-release-policy` are context, not subject. For EACH obligation in its register, find the objective in the computed context — its intent, and its applicability computed for THIS application from the capabilities it enables — and read the obligation against the application's compliance-relevant declarations. Decide four things. (1) Is the objective's intent actually TRUE of this product as declared? An obligation whose intent the declarations do not show — an export nothing declares, a record the application does not keep, a data subject it does not hold — is unsupported. (2) Do not re-check applicability: the computation is exact, and a programme that contradicts it (a NOT_APPLICABLE objective bound, or APPLICABLE where it says UNDETERMINED) is refused before you see it. Use it instead to read what each UNDETERMINED obligation must be open about — the capabilities it names as absent. (3) Is every UNDETERMINED obligation scoped honestly — does its rationale say what is open and why, rather than restate the objective? A matter the creator named as undetermined in this run is a legitimate UNDETERMINED. (4) Do the rationales and limitations claim no more than configuration? Operating effectiveness, conformity with a named regime, or a scope wider than the services the declarations list is unsupported. Name every finding by its `obligationRef` (or quote the limitation) and quote the words. Separate severities by CONSEQUENCE: wording a reader would not act on differently is a CONCERN; a claim an obligation register or a governed document would quote as true that nothing establishes, or that the computed applicability contradicts, is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with repairable drift a reader would not act on differently: a rationale vaguer than the declarations allow, an UNDETERMINED obligation that restates its objective instead of naming what is open, or a limitation that is true but leaves out an unbound area. Name each one.","GAP":"At least one obligation binds an objective whose intent the declarations do not show, or a rationale or limitation claims operating effectiveness, regime conformity or a scope wider than declared. Name each obligationRef and quote the unsupported words.","INDETERMINATE":"The computed applicability or the application's declarations are absent from the evidence, so whether an objective is true of this product cannot be judged. Say which is missing.","PASS":"Every bound objective's intent is shown by the declarations, every UNDETERMINED obligation says what is open, and nothing claims operating effectiveness, regime conformity or a scope wider than declared."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-program","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.compliance-conception"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}