@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
@@ -0,0 +1 @@
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-compliance-program","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/compliance-program-grounded-in-the-product"],"requirementRef":"application-creation:authority-requirement/compliance-program-result","requirementVersion":1,"riskClassRef":"application-creation:risk/compliance-claim-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/compliance-program","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-program-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-program","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-program-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-program-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-program","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-program-grounded-in-the-product","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/compliance-program-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/compliance-programme-change","triggerRefs":["application-creation:trigger/compliance-program-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-program-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-program-grounded-in-the-product"],"hardFloorRef":"application-creation:hard-floor/compliance-program-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/compliance-program-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-program","definitionVersion":1,"evaluationProtocol":{"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"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/compliance-program","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-program-declarations-and-applicability","criterionRef":"application-creation:criterion/compliance-program-grounded-in-the-product","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":3,"requirementRef":"application-creation:evidence-requirement/compliance-program-grounded-in-the-product","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/compliance-program-declarations-and-computed-applicability"}],"schemaVersion":1}
@@ -0,0 +1,209 @@
1
+ # Compliance Conception — Derivation Method (v1)
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
+ > **This is the first step in the journey that makes a POSITIVE compliance claim.** Everything before
16
+ > it describes the product. This one says what the product commits to, and a governed document will
17
+ > later quote it. Treat every sentence you write as something an auditor may read back to the
18
+ > operator.
19
+
20
+ ## What this playbook does
21
+
22
+ The compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind
23
+ constraints on the vision. You turn that into the application's **assurance programme**: which Wildo
24
+ control objectives this product binds, which external requirement each one answers, who is
25
+ accountable, and what is explicitly undetermined.
26
+
27
+ You do **not** re-elicit the vision, design the domain, or draft any document. You produce one
28
+ artifact — the `compliance-program` family — and nothing else.
29
+
30
+ ## The one rule that governs everything below
31
+
32
+ **A vision sentence is not a control mapping.** The posture step recorded "must be GDPR-compliant for
33
+ EU customer personal data". That is product intent. It is *not* a decision that this application binds
34
+ `WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the
35
+ posture step's own method forbids: the transition "must not reinterpret a vision sentence as a control
36
+ mapping or positive compliance claim."
37
+
38
+ So every element of the programme comes from one of exactly three places:
39
+
40
+ | element | comes from |
41
+ |---|---|
42
+ | which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |
43
+ | which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |
44
+ | what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |
45
+ | which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |
46
+ | WHEN this draft was produced | the HOST's observed instant — stamped, never answered |
47
+ | WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |
48
+ | whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |
49
+ | whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |
50
+ | what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |
51
+
52
+ If something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or
53
+ state it as a limitation.
54
+
55
+ ## What you will be refused for
56
+
57
+ The runtime normalizes your answer and **rejects** it — spending one of three runs — if you:
58
+
59
+ - bind an objective the authority basis states no expectation for. The basis covers a small set; you
60
+ were shown exactly which. There is no partial credit for a plausible objective.
61
+ - cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`
62
+ prefix, spelled exactly.
63
+ - bind the same objective twice.
64
+ - bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability
65
+ it requires is absent, so nothing could ever evidence it.
66
+ - state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would
67
+ attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it
68
+ `UNDETERMINED` and say what is open.
69
+
70
+ These are not style checks. Each one is a claim the framework cannot stand behind, and the rejection
71
+ message names what you got wrong — read it and fix that, rather than restructuring the answer.
72
+
73
+ ## Deciding an obligation
74
+
75
+ For each objective you were shown, ask three questions **in order**, and stop at the first "no".
76
+
77
+ 1. **Does this application actually do what the intent describes?** You have its resource declarations
78
+ — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective
79
+ whose intent describes something the declarations do not show is not bound. Read the computed
80
+ applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only
81
+ as `UNDETERMINED`.
82
+ 2. **Which external requirement does it answer, and does that source reach this application?** If the
83
+ product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.
84
+ 3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can
85
+ defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is
86
+ the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a
87
+ disposition you cannot point at evidence for; "the objective sounded right" is the failure this
88
+ whole step exists to prevent.
89
+
90
+ An objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,
91
+ readable answer** — a programme binding one objective honestly is worth more than one binding four
92
+ hopefully.
93
+
94
+ ### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess
95
+
96
+ `UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture
97
+ step asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident
98
+ `APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.
99
+
100
+ `NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not
101
+ apply, and evidence is not something a derivation can produce.
102
+
103
+ ## Limitations are required, and they are the honest part
104
+
105
+ You must state at least one. The programme you produce binds a handful of objectives out of everything
106
+ a regime demands, and a reader who is not told that will read it as a complete posture. Say plainly
107
+ what it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and
108
+ that the programme is not a conformity assertion for any named regime.
109
+
110
+ This is not a disclaimer bolted on. It is what makes the rest of the document quotable.
111
+
112
+ ## What reads your programme back
113
+
114
+ An advisory judge reads the landed programme against the same declarations and the same computed
115
+ applicability you were given. For each obligation it asks whether the objective's intent is true of this
116
+ product, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses
117
+ nothing — its verdict travels with the result — but it is why "the objective sounded right" does not
118
+ survive to the commit.
119
+
120
+ It replaced a question that asked the creator, per objective, whether the application met it. That answer
121
+ is either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a
122
+ form's.
123
+
124
+ ## What you never do
125
+
126
+ - **Never author a rights record, an edition, or an authority name.** Those come from the registry
127
+ because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody
128
+ reviewed.
129
+ - **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host
130
+ stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's
131
+ COMMIT — a landed programme is a working edit until then — so write the disposition you can
132
+ justify from the evidence and let acceptance happen where acceptance happens.
133
+ - **Never author a next-review date, and never write a review-schedule limitation.** You are not asked
134
+ for either. The host applies the application's declared review cadence; where none is declared the
135
+ programme is still produced and carries a stamped limitation saying no schedule is committed. A
136
+ limitation of your own on the same point would say it twice, in words nothing checks.
137
+ - **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are
138
+ SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application
139
+ declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is
140
+ worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds
141
+ a responsibility, record an explicit gap.
142
+
143
+ **A programme role is TWO fields, and the key goes in only one of them.** `applicationRoleRef` is the
144
+ application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is
145
+ the programme's OWN lowercase, hyphenated name for the responsibility (`application-owner`,
146
+ `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and
147
+ `reviewerRoleSlug` refer to. Two programme roles may map to the same key; a slug never carries one.
148
+ - **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role
149
+ answers for one tenant; the programme is about the product. The two scopes are rendered separately
150
+ and labelled for exactly this reason.
151
+ - **Never state operating effectiveness.** That a control is configured is not that it has worked. The
152
+ programme has no way to say the latter, and a document downstream is refused for claiming it.
153
+ - **Never widen the scope you were given, and do not ask for it.** What the programme covers is
154
+ DECLARED: the product, its type and its services are in
155
+ the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from
156
+ build-time tooling that is deliberately outside it. State the boundary from that, naming the
157
+ services individually — an application, its environments and its services, never the operator's
158
+ whole organisation. A service not listed there is not part of this application.
159
+
160
+ ## The two routing decisions you emit beside the programme
161
+
162
+ Naming which documents are required and stopping there leaves the next step with nothing to route by.
163
+ So this playbook also answers where those documents are published, and what must happen before one
164
+ faces a real reader.
165
+
166
+ ### `document-publication` — which variants exist at all
167
+
168
+ One entry per exact **locale x jurisdiction** combination the application publishes in. The two are an
169
+ INSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants
170
+ carrying different clauses, and neither implies a third assembled from one of each. Nothing
171
+ downstream may recombine the axes.
172
+
173
+ Take the jurisdictions from what the application has DECLARED — its operating regions, its posture —
174
+ never from where you imagine it might expand. A variant nobody publishes in is a routing claim no
175
+ document can honour, and every later release must name a variant declared here.
176
+
177
+ ### `document-release-policy` — which approval lane each requirement takes
178
+
179
+ One selection per documentation requirement the authority section lists under **Documentation
180
+ requirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.
181
+ Those are DERIVED from what the application declares — the programme declares exactly them, and you do
182
+ not write them — so a selection naming any other requirement is refused:
183
+
184
+ | lane | means |
185
+ |---|---|
186
+ | `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |
187
+ | `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |
188
+ | `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |
189
+
190
+ **Choose the lane the application can honestly satisfy today, and prefer the strictest only where it
191
+ is true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a
192
+ failure state: a drafted document and an unapproved release are both legitimate artifacts an
193
+ application holds for most of its life.
194
+
195
+ **None of these lanes blocks drafting or composing a release.** They decide what must be true before
196
+ a document faces a REAL READER, which is a later question than the one this journey is answering. A
197
+ lane that stopped the build would be a compliance workflow standing in front of the
198
+ application-creation mechanism.
199
+
200
+ ## Where this leaves the journey
201
+
202
+ The programme you land is the accepted answer for which controls this product commits to. It is what
203
+ an obligation register reads, what a governed document cites when it says the operator has a
204
+ programme, and what a later mapping pass binds to external framework identifiers.
205
+
206
+ It is accepted the way everything is accepted here: by a commit, which this run does not make. Who
207
+ makes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a
208
+ PERSON commits them. A commit the development companion makes under the YOLO posture is authored as
209
+ the companion: it accepts the working edit and reviews nothing.
@@ -0,0 +1,68 @@
1
+ {
2
+ "ref": "top_down.compliance-conception",
3
+ "version": "0.6.0",
4
+ "phase": "top_down",
5
+ "intent": "Compliance-conception pass: turn the applicable regimes the posture step recorded as prose constraints into the application's accepted `compliance-program` — the structured, reviewable record of which Wildo control objectives this product binds, which external requirement each answers, who is accountable, and what is explicitly undetermined. It does NOT re-elicit the vision and it does not draft any document. It is the first step in the lane that produces a POSITIVE compliance claim, so every claim it makes is derived — from an engine authority, the application's declarations, or the one thing no declaration records (what the creator says is genuinely undetermined) — drafted as a proposal a human accepts by committing it, and read back by an advisory judge. Nothing is inferred from a vision sentence.",
6
+ "preconditions": [
7
+ {
8
+ "kind": "artifact_exists",
9
+ "selector": {
10
+ "family": "vision-brief"
11
+ }
12
+ }
13
+ ],
14
+ "inputs": [
15
+ {
16
+ "family": "vision-brief"
17
+ }
18
+ ],
19
+ "outputs": [
20
+ {
21
+ "family": "document-publication",
22
+ "schemaRef": "saas-specifications:ApplicationDocumentPublicationSpecification",
23
+ "description": "Which locale x jurisdiction combinations the application publishes its public governed documents in. Decided HERE because it is the same decision surface as the programme: naming which documents are required without saying where they are published leaves the next step with nothing to route by, and every downstream release must name a variant this family declared. Locale and jurisdictions are ONE inseparable pair per variant — `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants, and nothing may recombine the axes."
24
+ },
25
+ {
26
+ "family": "document-release-policy",
27
+ "schemaRef": "saas-specifications:ApplicationDocumentReleasePolicySpecification",
28
+ "description": "Which approval lane each documentation requirement must take before a release may be SERVED: DRAFT_ONLY, OPERATOR_ATTESTED (an accountable operator releases an exact draft with explicit limitations) or QUALIFIED_REVIEW. Keyed by `requirementRef`/`requirementVersion` to the documentation requirements the application OWES — derived from what it declares, declared by the programme, and listed in the authority section — so a selection naming any other requirement is refused. This lane never BLOCKS drafting or composing — it decides what must be true before a document faces a real reader."
29
+ },
30
+ {
31
+ "family": "compliance-program",
32
+ "schemaRef": "saas-specifications:AssuranceProgramSpecification",
33
+ "description": "The application's accepted assurance programme: source references and their applicability, one obligation per bound Wildo objective with its coverage decision and implementation decision, responsibility assignments, and the limitations it does not claim beyond. Answered against the STRICT generation contract (`AssuranceProgramGenerationSchema`) and normalized into a v3 `AssuranceProgramSpecification` — the runtime stamps every ref, version and ordering, and refuses an objective the authority basis has no expectation for or a source the registry does not carry."
34
+ }
35
+ ],
36
+ "stepOutputs": [],
37
+ "method": {
38
+ "guidance": "# Compliance Conception — Derivation Method (v1)\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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which external requirement does it answer, and does that source reach this application?** If the\n product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is TWO fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated name for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. Two programme roles may map to the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
39
+ "skillRefs": [
40
+ "journey-status"
41
+ ],
42
+ "skillBodyRefs": [],
43
+ "elicitation": {
44
+ "questions": [
45
+ {
46
+ "ref": "undetermined-and-gaps",
47
+ "question": "What is genuinely undetermined — something you cannot answer today without more work? List them. These become explicit UNDETERMINED applicability or stated limitations rather than silent omissions.",
48
+ "kind": "free_text"
49
+ }
50
+ ]
51
+ },
52
+ "contextSources": [
53
+ "assurance_program_authority",
54
+ "compliance_primary_facts",
55
+ "application_role_graph"
56
+ ],
57
+ "draftableDocumentDefinitionRefs": [],
58
+ "suspendsForClarification": false,
59
+ "briefAdequacyGate": false,
60
+ "briefAdequacyExcludedSources": []
61
+ },
62
+ "executor": "companion_agent",
63
+ "approval": "approve_result",
64
+ "budget": {
65
+ "maxRuns": 3
66
+ },
67
+ "onFailure": "keep_and_flag"
68
+ }
@@ -0,0 +1,61 @@
1
+ # Compliance Evidence Adequacy — is this enough to state a posture from?
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 **gate**, not the author. You read what the research rounds gathered
16
+ and answer one question: is this enough to record the product's compliance posture
17
+ — or what, precisely, is still missing?
18
+
19
+ ## What ADEQUATE means here
20
+
21
+ Evidence is adequate when, for the jurisdictions, data classes and sector the
22
+ vision (and the creator's answers) put in scope:
23
+
24
+ 1. **Every plausible candidate regime has a settled applicability answer** —
25
+ applies, does not apply, or genuinely cannot be established — grounded in an
26
+ authoritative source, never in recollection.
27
+ 2. **No scope dimension is unexamined.** A jurisdiction the vision names with no
28
+ regime evidence at all is a gap, whatever was gathered elsewhere.
29
+ 3. **The claims carry sources.** An unsourced applicability claim counts as
30
+ missing, not as weak — the posture that cites it would be recollection wearing
31
+ evidence's clothes.
32
+
33
+ ## A regime whose triggering facts are DECLARED OPEN is settled as CONDITIONAL
34
+
35
+ "Settled" has three answers, and the third is not a failure: **applies**, **does
36
+ not apply**, and **conditional on named open facts**. When the creator's own
37
+ answers declare a triggering fact undecided — a hosting region not chosen, a
38
+ market not yet targeted, a threshold nobody can know before launch — the settled
39
+ answer for every regime that turns on that fact is *conditional on it*, stated
40
+ with the exact facts that would decide it. That answer is ADEQUATE as it stands.
41
+
42
+ Do not send research after statute-level verification of conditional regimes.
43
+ The measured failure this paragraph exists for: a run whose creator had declared
44
+ US targeting undecided spent its final rounds demanding primary-source triggers
45
+ and thresholds for twelve individual US state statutes — evidence that decides
46
+ nothing until the open fact is decided, purchased at the cost of the rounds the
47
+ DECIDED scope needed. Reserve the authoritative-source bar for the regimes the
48
+ declared facts actually reach; for the conditional tier, the deliverable is the
49
+ precise list of deciding facts, and the posture records exactly that.
50
+
51
+ ## What INSUFFICIENT must do
52
+
53
+ Name the gaps so the next round is AIMED: which regime, which trigger question,
54
+ which jurisdiction. "More research needed" is not a gap — it is the shape that
55
+ made the market loop's early rounds spend tokens converging on nothing.
56
+
57
+ ## What you never do
58
+
59
+ You never lower the bar because rounds are running out — the composite's breaker
60
+ owns that trade, not you. And you never fill a gap yourself: a gate that authors
61
+ evidence has measured nothing.
@@ -0,0 +1,42 @@
1
+ {
2
+ "ref": "top_down.compliance-evidence-adequacy",
3
+ "version": "0.1.1",
4
+ "phase": "top_down",
5
+ "intent": "Judge whether the regime evidence gathered so far is ENOUGH to state a compliance posture from, and when it is not, name precisely what is missing so the next research round is aimed rather than repeated. Returns a verdict a sibling's precondition READS; it authors nothing and lands nothing.",
6
+ "preconditions": [
7
+ {
8
+ "kind": "step_available",
9
+ "ref": "compliance-evidence"
10
+ }
11
+ ],
12
+ "inputs": [
13
+ {
14
+ "family": "vision-brief"
15
+ }
16
+ ],
17
+ "outputs": [],
18
+ "stepOutputs": [
19
+ {
20
+ "ref": "compliance-adequacy",
21
+ "schemaRef": "saas-models:MetaWorkflow_EvidenceAdequacy",
22
+ "condensation": "A verdict, the gaps that produced it, and a rationale grounded in what was actually gathered.",
23
+ "description": "The adequacy gate the posture step is conditioned on."
24
+ }
25
+ ],
26
+ "method": {
27
+ "guidance": "# Compliance Evidence Adequacy — is this enough to state a posture from?\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 **gate**, not the author. You read what the research rounds gathered\nand answer one question: is this enough to record the product's compliance posture\n— or what, precisely, is still missing?\n\n## What ADEQUATE means here\n\nEvidence is adequate when, for the jurisdictions, data classes and sector the\nvision (and the creator's answers) put in scope:\n\n1. **Every plausible candidate regime has a settled applicability answer** —\n applies, does not apply, or genuinely cannot be established — grounded in an\n authoritative source, never in recollection.\n2. **No scope dimension is unexamined.** A jurisdiction the vision names with no\n regime evidence at all is a gap, whatever was gathered elsewhere.\n3. **The claims carry sources.** An unsourced applicability claim counts as\n missing, not as weak — the posture that cites it would be recollection wearing\n evidence's clothes.\n\n## A regime whose triggering facts are DECLARED OPEN is settled as CONDITIONAL\n\n\"Settled\" has three answers, and the third is not a failure: **applies**, **does\nnot apply**, and **conditional on named open facts**. When the creator's own\nanswers declare a triggering fact undecided — a hosting region not chosen, a\nmarket not yet targeted, a threshold nobody can know before launch — the settled\nanswer for every regime that turns on that fact is *conditional on it*, stated\nwith the exact facts that would decide it. That answer is ADEQUATE as it stands.\n\nDo not send research after statute-level verification of conditional regimes.\nThe measured failure this paragraph exists for: a run whose creator had declared\nUS targeting undecided spent its final rounds demanding primary-source triggers\nand thresholds for twelve individual US state statutes — evidence that decides\nnothing until the open fact is decided, purchased at the cost of the rounds the\nDECIDED scope needed. Reserve the authoritative-source bar for the regimes the\ndeclared facts actually reach; for the conditional tier, the deliverable is the\nprecise list of deciding facts, and the posture records exactly that.\n\n## What INSUFFICIENT must do\n\nName the gaps so the next round is AIMED: which regime, which trigger question,\nwhich jurisdiction. \"More research needed\" is not a gap — it is the shape that\nmade the market loop's early rounds spend tokens converging on nothing.\n\n## What you never do\n\nYou never lower the bar because rounds are running out — the composite's breaker\nowns that trade, not you. And you never fill a gap yourself: a gate that authors\nevidence has measured nothing.\n",
28
+ "skillRefs": [
29
+ "journey-status"
30
+ ],
31
+ "skillBodyRefs": [],
32
+ "contextSources": [],
33
+ "draftableDocumentDefinitionRefs": [],
34
+ "suspendsForClarification": false,
35
+ "briefAdequacyGate": false,
36
+ "briefAdequacyExcludedSources": []
37
+ },
38
+ "executor": "companion_agent",
39
+ "approval": "auto",
40
+ "budget": {},
41
+ "onFailure": "keep_and_flag"
42
+ }
@@ -0,0 +1 @@
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-posture-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["vision.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1}],"instruction":"Determine whether the posture is written as one constraint per regime with a stable kebab-case ref prefixed `constraint-`, unique across the set; whether a regime already present in the vision (under any slug the vision-elicitation step chose) was matched by the regime its statement names and updated IN PLACE under its existing ref; and whether re-running would converge to one entry per regime rather than accumulating near-duplicates.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Regimes are separate but a ref is minted for a regime that already existed under another slug, or two statements overlap in scope.","GAP":"An omnibus constraint merging several regimes, a duplicate entry for one regime, or a malformed ref.","INDETERMINATE":"The vision's prior constraints are not in evidence, so convergence cannot be compared.","PASS":"One entry per regime, stable unique refs, and every pre-existing regime refined under its own ref."}},{"criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1}],"instruction":"Determine whether each compliance constraint is derived rather than recalled: its statement names the regime, the trigger (jurisdiction, data class, sector or commitment) and what it governs, in the terms of the regime evidence and the creator's facts this run carried; a regime the evidence EXCLUDES is not written as a constraint and, where the creator's answers suggested it, the exclusion is made legible on a neighbouring constraint; a trigger the evidence could NOT establish becomes a constraint stating the open question, never a guessed answer; and a product with no triggers honestly carries no compliance constraints.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, but a statement is thinner than the evidence allows, or an exclusion is dropped silently where the creator had suggested the regime.","GAP":"A regime stated as settled that the evidence did not establish, a regime invented to look thorough, or a regime the evidence establishes that is absent.","INDETERMINATE":"The regime evidence or the creator's facts are not in evidence, so derivation cannot be checked.","PASS":"Every constraint is grounded in the evidence, exclusions are legible, and open triggers are stated as open."}},{"assessesAspects":["vision.constraint","vision.idea","vision.problem","vision.mission","vision.success-criterion"],"criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"instruction":"Determine whether the run touched exactly the `kind: compliance` entries of the vision's constraints and nothing else: the idea, problem, mission, success criteria and every non-compliance constraint are unchanged, and no constraint models controls, obligation graphs, residency matrices, retention schedules or audit configuration, which belong to the later compliance-conception step.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A non-compliance entity was reworded incidentally, or a constraint drifts toward listing controls.","GAP":"A vision entity outside the compliance constraints altered, or a constraint that models controls or obligations.","INDETERMINATE":"The vision as it was BEFORE this run is not in evidence.","PASS":"Only compliance constraints changed, and each stays a prose regime statement at scaffold depth."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-posture","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.compliance-posture"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -0,0 +1 @@
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-vision-brief","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence"],"requirementRef":"application-creation:authority-requirement/compliance-posture-result","requirementVersion":1,"riskClassRef":"application-creation:risk/vision-brief-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/compliance-posture","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/compliance-posture-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/compliance-posture","policyVersion":1},"decisionPointRef":"application-creation:decision-point/compliance-posture-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/compliance-posture-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/compliance-posture","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/vision-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-vision-brief-change","triggerRefs":["application-creation:trigger/vision-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-compliance-posture-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding"],"hardFloorRef":"application-creation:hard-floor/vision-brief-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/compliance-posture-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/compliance-posture","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-compliance-posture-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["vision.constraint"],"criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1}],"instruction":"Determine whether the posture is written as one constraint per regime with a stable kebab-case ref prefixed `constraint-`, unique across the set; whether a regime already present in the vision (under any slug the vision-elicitation step chose) was matched by the regime its statement names and updated IN PLACE under its existing ref; and whether re-running would converge to one entry per regime rather than accumulating near-duplicates.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Regimes are separate but a ref is minted for a regime that already existed under another slug, or two statements overlap in scope.","GAP":"An omnibus constraint merging several regimes, a duplicate entry for one regime, or a malformed ref.","INDETERMINATE":"The vision's prior constraints are not in evidence, so convergence cannot be compared.","PASS":"One entry per regime, stable unique refs, and every pre-existing regime refined under its own ref."}},{"criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1}],"instruction":"Determine whether each compliance constraint is derived rather than recalled: its statement names the regime, the trigger (jurisdiction, data class, sector or commitment) and what it governs, in the terms of the regime evidence and the creator's facts this run carried; a regime the evidence EXCLUDES is not written as a constraint and, where the creator's answers suggested it, the exclusion is made legible on a neighbouring constraint; a trigger the evidence could NOT establish becomes a constraint stating the open question, never a guessed answer; and a product with no triggers honestly carries no compliance constraints.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, but a statement is thinner than the evidence allows, or an exclusion is dropped silently where the creator had suggested the regime.","GAP":"A regime stated as settled that the evidence did not establish, a regime invented to look thorough, or a regime the evidence establishes that is absent.","INDETERMINATE":"The regime evidence or the creator's facts are not in evidence, so derivation cannot be checked.","PASS":"Every constraint is grounded in the evidence, exclusions are legible, and open triggers are stated as open."}},{"assessesAspects":["vision.constraint","vision.idea","vision.problem","vision.mission","vision.success-criterion"],"criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1}],"instruction":"Determine whether the run touched exactly the `kind: compliance` entries of the vision's constraints and nothing else: the idea, problem, mission, success criteria and every non-compliance constraint are unchanged, and no constraint models controls, obligation graphs, residency matrices, retention schedules or audit configuration, which belong to the later compliance-conception step.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A non-compliance entity was reworded incidentally, or a constraint drifts toward listing controls.","GAP":"A vision entity outside the compliance constraints altered, or a constraint that models controls or obligations.","INDETERMINATE":"The vision as it was BEFORE this run is not in evidence.","PASS":"Only compliance constraints changed, and each stays a prose regime statement at scaffold depth."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/compliance-posture","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.compliance-posture"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/compliance-posture","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-one-regime-one-constraint-and-convergence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-one-regime-one-constraint-and-convergence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-regime-derivation-grounding","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-regime-derivation-grounding","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-compliance-posture-inputs-and-candidate","criterionRef":"application-creation:criterion/compliance-posture-slice-discipline","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":1,"requirementRef":"application-creation:evidence-requirement/compliance-posture-slice-discipline","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-and-regime-evidence-candidate"}],"schemaVersion":1}
@@ -69,19 +69,21 @@ requirements and explicit gaps.
69
69
  The transition is not an automatic conversion and must not reinterpret a
70
70
  vision sentence as a control mapping or positive compliance claim. Preserve
71
71
  the vision constraint as product intent, record any missing detail as
72
- `UNDETERMINED` or an explicit gap, and accept the structured family through the
73
- normal semantic-delta authority. Runtime organizations, assignees, evidence,
72
+ `UNDETERMINED` or an explicit gap, and land the structured family as files in the
73
+ specifications package. Landing is not accepting: the run leaves working edits,
74
+ and acceptance is a later commit. Who makes it is the host's autonomy posture, and only a
75
+ person's commit reviews what it accepts. Runtime organizations, assignees, evidence,
74
76
  control occurrences and assessments remain outside both artifacts.
75
77
 
76
78
  ## The derivation posture
77
79
 
78
- - **Derive, then confirm — do not just transcribe.** The typed questions on
79
- this playbook (`method.elicitation`) gather the raw triggers: jurisdictions,
80
- data classes, sector, and direct yes/no reads on the common regimes. Your
81
- value is reasoning from those triggers to the regime set, then reflecting
82
- each derived regime back to the creator for confirmation. If EU users +
83
- personal data are present, GDPR applies whether or not the creator named it;
84
- surface that, don't wait to be told.
80
+ - **Derive from the product and gathered evidence.** Read the existing vision,
81
+ product facts and cumulative regime evidence supplied by the parent choreography.
82
+ The current `compliance-adequacy` verdict establishes readiness. This playbook
83
+ declares no interview: do not fabricate answers or submit arbitrary
84
+ `elicitationAnswers`. Preserve source-backed applicability reasoning and explicit
85
+ uncertainty. Creator-owned facts that remain unresolved need a supported input or
86
+ clarification path; do not ask the creator to reconstruct externally researchable obligations.
85
87
  - **Regime derivation rubric (v1).** Use these as the starting triggers, and
86
88
  follow up where an answer is thin:
87
89
  - **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing
@@ -151,6 +153,11 @@ unique refs the first time. Note that a vision with no compliance constraints
151
153
  is perfectly valid — an honestly unregulated product should pass the gate with
152
154
  none.
153
155
 
156
+ Beyond the deterministic gate, the advisory judge reads the refined vision against
157
+ three criteria — regime derivation grounded in the evidence, one regime per constraint
158
+ converging on re-run, and slice discipline — and its verdicts reach the creator's
159
+ review as notes. A verdict never refuses a landing.
160
+
154
161
  ## Approval
155
162
 
156
163
  The refined `VisionSnapshot` is presented to the creator for approval before it
@@ -167,11 +174,31 @@ Before you start, read the current journey state and scope, and read the
167
174
  existing vision so you refine its compliance constraints rather than writing a
168
175
  fresh, disconnected set.
169
176
 
170
- // TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
171
- // TODO CLI COMMAND: wildo context vision-brief (read the existing vision + its current constraints)
177
+ (The existing vision and its current constraints are already in your brief as the `vision-brief`
178
+ input section.)
179
+
180
+ ## The evidence, and how to use it
181
+
182
+ Your run carries what sibling steps gathered — source-attributed regime evidence and the adequacy
183
+ verdict that admitted this step. Derive each constraint from the creator's answers AND that
184
+ evidence, never from recollection:
185
+
186
+ - A regime the evidence establishes as APPLICABLE becomes a `compliance` constraint whose statement
187
+ names the regime, the trigger (jurisdiction / data class / sector / commitment), and what it
188
+ governs — in the evidence's terms.
189
+ - A regime the evidence EXCLUDES is not written as a constraint, and is not silently dropped either:
190
+ where the creator's answers suggested it, the statement of a neighbouring constraint may note the
191
+ exclusion so the decision is legible.
192
+ - A trigger the evidence could NOT establish becomes a constraint stating the OPEN QUESTION, never a
193
+ guessed answer — an unestablished regime stated as settled is the defect this composite exists to
194
+ end.
172
195
 
173
196
  ## References
174
197
 
175
- - `.claude/skills/journey-status/SKILL.md` — read current journey state and
198
+ These are skill FOLDERS installed in the application, named so each piece of work has an
199
+ authoring contract a later coding agent can open. This step has no tools and does not open them;
200
+ what reaches you is this method, your declared inputs, and the brief's own sections.
201
+
202
+ - `journey-status` — read current journey state and
176
203
  scope before deriving, and to see the `vision-brief` (and its existing
177
204
  compliance constraints) you refine.