@wildo-ai/framework-knowledge 1.1.3 → 1.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (841) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +349 -17
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  6. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.loader.js +47 -1
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
  13. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  14. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
  15. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  25. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  26. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
  27. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  28. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  29. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  30. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
  31. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  32. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
  33. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  34. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
  35. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  36. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  41. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  44. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
  45. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
  47. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
  49. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  50. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
  51. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  52. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  53. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  54. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
  55. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  56. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  57. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
  60. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  61. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  63. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
  64. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  65. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  68. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  69. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  70. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  71. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  72. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  74. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
  76. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
  78. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  80. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  81. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  82. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
  84. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
  86. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  87. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
  88. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  89. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
  90. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  92. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
  94. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  95. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
  96. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  99. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
  100. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  101. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  103. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
  104. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  105. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
  112. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  113. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
  114. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
  116. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  117. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
  118. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  120. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  121. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  122. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  123. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  124. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  125. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
  126. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  127. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  128. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  129. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
  130. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  131. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  132. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  133. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
  134. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  135. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  136. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  137. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
  138. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  139. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
  140. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  141. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
  142. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  143. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
  144. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
  146. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  147. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  148. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  149. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  150. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  151. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
  152. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  153. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
  154. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
  156. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  157. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
  158. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  159. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
  160. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  161. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
  162. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  163. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  164. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  165. package/dist/knowledge/manifest.json +9 -8
  166. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  167. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  168. package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
  169. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
  170. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  171. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  172. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
  173. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
  174. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  175. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  176. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
  177. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
  178. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
  179. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
  180. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
  181. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
  182. package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
  183. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
  184. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
  185. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
  186. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
  187. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
  188. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
  189. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
  190. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
  191. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
  192. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
  193. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  194. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  195. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
  196. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  197. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
  198. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
  199. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
  200. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  201. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
  202. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  203. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
  204. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  205. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  206. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
  207. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  208. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  209. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  210. package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
  211. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
  212. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  213. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  214. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
  215. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  216. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  217. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  218. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
  219. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
  220. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
  221. package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
  222. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
  223. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  224. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
  225. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  226. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  227. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
  228. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
  229. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  230. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
  231. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  232. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  233. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
  234. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
  235. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  236. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
  237. package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
  238. package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
  239. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  240. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
  241. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  242. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
  243. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  244. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
  245. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  246. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
  247. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  248. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  249. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
  250. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
  251. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  252. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  253. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  254. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
  255. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
  256. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
  257. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  258. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  259. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  260. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
  261. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
  262. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
  263. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  264. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  265. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
  266. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
  267. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  268. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
  269. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  270. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  271. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  272. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  273. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  274. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  275. package/dist/knowledge/references/application-maturity.config.md +319 -0
  276. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  277. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  278. package/dist/knowledge/references/brand.asset.config.md +8 -16
  279. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  280. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  281. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  282. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  283. package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
  284. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  285. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  286. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  287. package/dist/knowledge/references/capability-composition.config.md +155 -0
  288. package/dist/knowledge/references/cli.market.utils.md +1 -0
  289. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  290. package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
  291. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  292. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  293. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  294. package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
  295. package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
  296. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
  297. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  298. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  299. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  300. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  301. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
  302. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
  303. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  304. package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
  305. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  306. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  307. package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
  308. package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
  309. package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
  310. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
  311. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
  312. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  313. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
  314. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
  315. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
  316. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
  317. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  318. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  319. package/dist/knowledge/references/experience-plan.config.md +311 -0
  320. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
  321. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  322. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
  323. package/dist/knowledge/references/integration-plan.config.md +185 -0
  324. package/dist/knowledge/references/market.alternative.config.md +1 -1
  325. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  326. package/dist/knowledge/references/market.channel.config.md +3 -3
  327. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  328. package/dist/knowledge/references/market.gain.config.md +1 -1
  329. package/dist/knowledge/references/market.icp.config.md +2 -2
  330. package/dist/knowledge/references/market.job.config.md +1 -1
  331. package/dist/knowledge/references/market.message-template.config.md +2 -2
  332. package/dist/knowledge/references/market.objection.config.md +1 -1
  333. package/dist/knowledge/references/market.pain.config.md +1 -1
  334. package/dist/knowledge/references/market.persona.config.md +2 -2
  335. package/dist/knowledge/references/market.proof.config.md +1 -1
  336. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  337. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  338. package/dist/knowledge/references/market.trigger.config.md +1 -1
  339. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  340. package/dist/knowledge/references/placement-plan.config.md +369 -0
  341. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  342. package/dist/knowledge/references/platform.config.backing-services.md +0 -21
  343. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  344. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  345. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  346. package/dist/knowledge/references/platform.config.saas.md +261 -9
  347. package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
  348. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  349. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  350. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  351. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  352. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  353. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  354. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  355. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  356. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
  357. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  358. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  359. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
  360. package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
  361. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  362. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
  363. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  364. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
  365. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  366. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  367. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
  368. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  369. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  370. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  371. package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
  372. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  373. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  374. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  375. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  376. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  377. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  378. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  379. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
  380. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  381. package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
  382. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  383. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  384. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  385. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  386. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  387. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  388. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  389. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  390. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  391. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  392. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  393. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  394. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
  395. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  396. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  397. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
  398. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
  399. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
  400. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  401. package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
  402. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  403. package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
  404. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  405. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
  406. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
  407. package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
  408. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  409. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
  410. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  411. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  412. package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
  413. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
  414. package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
  415. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  416. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  417. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  418. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  419. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  420. package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
  421. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  422. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  423. package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
  424. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  425. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  426. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
  427. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
  428. package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
  429. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
  430. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  431. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  432. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
  433. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  434. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  435. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  436. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  437. package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
  438. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
  439. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  440. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  441. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
  442. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  443. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  444. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  445. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
  446. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  447. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  448. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  449. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  450. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  451. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  452. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  453. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  454. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  455. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  456. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  457. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  458. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  459. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  460. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
  461. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
  462. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  463. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  464. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  465. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  466. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  467. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  468. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  469. package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
  470. package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
  471. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  472. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  473. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  474. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  475. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  476. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  477. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  478. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
  479. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
  480. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
  481. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  482. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
  483. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  484. package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
  485. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
  486. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  487. package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
  488. package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
  489. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  490. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
  491. package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
  492. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  493. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  494. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  495. package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
  496. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  497. package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
  498. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  499. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  500. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  501. package/dist/knowledge/references/website-plan.config.md +205 -0
  502. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  503. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  504. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  505. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
  506. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
  507. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
  508. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  509. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  510. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  511. package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
  512. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
  513. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
  514. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  515. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  516. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  517. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  518. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
  519. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
  520. package/dist/knowledge/references/zod.factories.address.md +118 -0
  521. package/dist/knowledge/references/zod.factories.code.md +2 -0
  522. package/dist/knowledge/references/zod.factories.duration.md +2 -0
  523. package/dist/knowledge/references/zod.factories.money.md +2 -0
  524. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  525. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  526. package/dist/knowledge/registries/framework-topics.json +1215 -11
  527. package/dist/knowledge/registries/playbooks.json +454 -50
  528. package/dist/knowledge/registries/source-tags.json +3153 -1043
  529. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  530. package/dist/knowledge/rules/live-context-door.md +108 -0
  531. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  532. package/dist/knowledge/skills/INDEX.md +46 -11
  533. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
  534. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  535. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  536. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
  537. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  538. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  539. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
  540. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
  541. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
  542. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
  543. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  544. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
  545. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  546. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  547. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  548. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
  549. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
  550. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  551. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  552. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
  553. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  554. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
  555. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  556. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  557. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  558. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
  559. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
  560. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
  561. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
  562. package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
  563. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
  564. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  565. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  566. package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
  567. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  568. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  569. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  570. package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
  571. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  572. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
  573. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  574. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  575. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
  576. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
  577. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  578. package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
  579. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
  580. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
  581. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  582. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
  583. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
  584. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  585. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
  586. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
  587. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  588. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  589. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  590. package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
  591. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  592. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  593. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  594. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  595. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
  596. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  597. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
  598. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  599. package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
  600. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
  601. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
  602. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
  603. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  604. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
  605. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  606. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
  607. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
  608. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
  609. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
  610. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  611. package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
  612. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  613. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
  614. package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
  615. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
  616. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  617. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  618. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  619. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  620. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
  621. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  622. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  623. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
  624. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
  625. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
  626. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
  627. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
  628. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
  629. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  630. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  631. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
  632. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  633. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
  634. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
  635. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  636. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  637. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  638. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  639. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
  640. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
  641. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
  642. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
  643. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
  644. package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
  645. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  646. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
  647. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  648. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  649. package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
  650. package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
  651. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
  652. package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
  653. package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
  654. package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
  655. package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
  656. package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
  657. package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
  658. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
  659. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  660. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  661. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
  662. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
  663. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  664. package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
  665. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  666. package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
  667. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
  668. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
  669. package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
  670. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
  671. package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
  672. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
  673. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
  674. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
  675. package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
  676. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
  677. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
  678. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  679. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
  680. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
  681. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
  682. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  683. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  684. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  685. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  686. package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
  687. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  688. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  689. package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
  690. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
  691. package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
  692. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
  693. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
  694. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  695. package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
  696. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  697. package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
  698. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  699. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  700. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  701. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
  702. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  703. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
  704. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
  705. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  706. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
  707. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
  708. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
  709. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
  710. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
  711. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  712. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  713. package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
  714. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
  715. package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
  716. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
  717. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  718. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  719. package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
  720. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
  721. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
  722. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
  723. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
  724. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
  725. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  726. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  727. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  728. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
  729. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  730. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
  731. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  732. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
  733. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  734. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
  735. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
  736. package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
  737. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
  738. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  739. package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
  740. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
  741. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
  742. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
  743. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
  744. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  745. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  746. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  747. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
  748. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
  749. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  750. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  751. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
  752. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  753. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  754. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
  755. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
  756. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  757. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  758. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
  759. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
  760. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  761. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
  762. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  763. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  764. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  765. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  766. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
  767. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
  768. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
  769. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
  770. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
  771. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  772. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
  773. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
  774. package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
  775. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  776. package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
  777. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  778. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  779. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  780. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
  781. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
  782. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  783. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
  784. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
  785. package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
  786. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  787. package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
  788. package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
  789. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  790. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
  791. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
  792. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
  793. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  794. package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
  795. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  796. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
  797. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
  798. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  799. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
  800. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  801. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  802. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
  803. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
  804. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
  805. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
  806. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
  807. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
  808. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
  809. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
  810. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
  811. package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
  812. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  813. package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
  814. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
  815. package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
  816. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
  817. package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
  818. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
  819. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
  820. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
  821. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
  822. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
  823. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
  824. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
  825. package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
  826. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
  827. package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
  828. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
  829. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
  830. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
  831. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
  832. package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
  833. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  834. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  835. package/dist/knowledge/topic-index.json +5335 -1010
  836. package/dist/tsconfig.build.tsbuildinfo +1 -1
  837. package/dist/tsconfig.tsbuildinfo +1 -1
  838. package/package.json +4 -4
  839. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  840. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  841. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -31,14 +31,25 @@ first draft from reading as either uniformly confident or uniformly empty.
31
31
  **Asserts** — who legally operates the service: entity name, registered address, contact route for
32
32
  data-protection questions, and a representative where one is required.
33
33
 
34
- **Derives from** — nothing, and nothing could. A legal entity is a fact about the world, not a
35
- property of a codebase, so this is not a framework gap and no engine change would close it.
34
+ **Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
35
+ registered address, the privacy contact route, and an Art. 27 representative where one is required.
36
36
 
37
- **Completeness** — `NEEDS_DECISION`, always, until the operator supplies it.
37
+ The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
38
+ What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
39
+ said "no engine change would close it", which was right about derivation and wrong about the home.
40
+ The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
41
+ who answered by editing the document lost the answer at the next regeneration — the answer has to live
42
+ in the application or it does not survive.
38
43
 
39
- **What closes it** — the operator recording the entity, address and contact route. That is the second
40
- step, and it is cheap: the reason it is not a blocker is precisely that it can be filled in later
41
- without redrafting anything around it.
44
+ **Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
45
+
46
+ ⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
47
+ exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
48
+ and nobody has. They have different remedies — build something, versus fill something in — and a
49
+ reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
50
+
51
+ **What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
52
+ filled in later without redrafting anything around it, which is the reason it is not a blocker.
42
53
 
43
54
  **Never infer it.** Not from the application name, not from a domain, not from another application,
44
55
  not from model memory. A published legal document naming the wrong entity is worse than one that says
@@ -54,14 +65,34 @@ with gaps beats blocking: the whole document set would be unproducible until one
54
65
  **Asserts** — the lawful basis for each processing purpose, and whether the operator acts as
55
66
  controller or processor for it.
56
67
 
57
- **Derives from** — nothing. Both are legal determinations about the operator's own arrangements. The
58
- framework can show WHAT is processed and BY WHICH MECHANISM; it cannot establish under which basis, or
59
- in which role.
68
+ **Derives from** — `operatorComplianceIdentity.lawfulBases` and `.roleAllocations` in
69
+ `wildo.saas.config.ts`.
70
+
71
+ The DETERMINATIONS are never derivable — both are legal conclusions about the operator's own
72
+ arrangements, and the framework can show WHAT is processed and BY WHICH MECHANISM without establishing
73
+ under which basis or in which role. What it now provides is where to record the conclusion, so that a
74
+ regeneration reproduces it instead of destroying it.
75
+
76
+ **The role is a LIST, not a field, and the produced notice said so before the surface existed:**
77
+ *"This notice therefore does not assign a single legal role to all data processed in a workspace."* A
78
+ B2B SaaS is typically a processor for the records its customers put in and a controller for its
79
+ account holders' own data, simultaneously. `roleAllocations` carries one role per population, and a
80
+ document that collapses them into one is wrong about both.
60
81
 
61
- **Completeness** — `NEEDS_DECISION`.
82
+ **The `lawful-bases` fact is COMPUTED from `lawfulBases`** — every purpose, its basis and, for
83
+ legitimate interests, the assessment. You never declare it: a restatement would be a second copy of the
84
+ operator's decision that nothing compares with the first. Absent bases leave the fact absent.
85
+
86
+ **`LEGITIMATE_INTERESTS` cannot be declared without its assessment** — the schema refuses it. It is
87
+ the only Art. 6(1) basis whose lawfulness depends on a balancing test, so the bare claim asserts a
88
+ conclusion nobody reached.
89
+
90
+ **Completeness** — `DERIVED` when declared; `NEEDS_DECISION` when not. Never `NEEDS_FRAMEWORK`: there
91
+ is a surface, so the remedy is to fill it in, not to build something. Name the surface when reporting
92
+ the gap.
62
93
 
63
94
  **What closes it** — the operator determining, per purpose, the basis and the role, ideally with
64
- counsel. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for
95
+ counsel, and declaring them in `operatorComplianceIdentity`. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for
65
96
  the data a customer stores about its own people, controller for the data the operator holds about
66
97
  account holders — but describing the common shape is not the same as determining this operator's, and
67
98
  the produced document must not present the first as the second.
@@ -90,6 +121,20 @@ invoice and of a CRM contact, so it never tells you whether a record is about a
90
121
  retention mode does.
91
122
 
92
123
  **Completeness** — `DERIVED` for every resource that declares a retention policy.
124
+
125
+ **An erasure-coverage gap does NOT license a claim about whether personal data is held.** The two are
126
+ different axes and the facts report them separately: `retentionPolicy` answers *what happens to this
127
+ row on erasure*, while a field's `.dataCategories()` answers *what kind of data is in it*. A resource
128
+ can declare the second and not the first, and 48 of the engine's 85 do.
129
+
130
+ So writing "N resources have no declared erasure treatment, so this notice cannot establish whether
131
+ they hold personal data" is an over-reach, and it contradicts the data-categories section of the same
132
+ document — which enumerates categories drawn from those very resources. It was produced twice on
133
+ 2026-08-30 before this paragraph existed.
134
+
135
+ State the gap as what it is: those resources have not declared an erasure TREATMENT, so a notice
136
+ cannot say what an erasure does to them. Where the facts also report a category coverage for the same
137
+ origin, say what IS established alongside it.
93
138
  `NEEDS_CONFIGURATION` for every resource that does not.
94
139
 
95
140
  **What closes it** — the application's own authors declaring `retentionPolicy` on the resource. Name
@@ -98,28 +143,43 @@ the resources individually: the remedy is per-resource, and a count is not actio
98
143
 
99
144
  ### Concern: data categories
100
145
 
101
- **Asserts** — which CATEGORIES of personal data are held: contact details, identifiers, financial
102
- data, usage data, and any special-category data.
146
+ **Asserts** — which CATEGORIES of personal data are held: identity, contact details, credentials,
147
+ financial, usage, location, user content, professional, and any GDPR Art. 9 special-category or
148
+ Art. 10 criminal-offence data.
149
+
150
+ **Derives from** — each field's `.dataCategories()` declaration, reported per resource and unioned
151
+ across the application in the compliance-primary-facts section. One category is DERIVED rather than
152
+ declared: `credentials`, from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, which are
153
+ markers the author already wrote.
103
154
 
104
- **Derives from** — nothing usable today, and the near-miss matters. `Compliance_DataClassification`
105
- exists and is a four-level SENSITIVITY ladder (public / internal / confidential / restricted) applied
106
- only to flows-actors configuration. It answers "how protected must this be", not "what kind of
107
- personal data is this", and using it as a category vocabulary would produce a notice describing
108
- protection levels where a reader expects data types.
155
+ **Nothing is derived from a field NAME.** `email`, `phone` and `dateOfBirth` are suggestive while
156
+ `notes` is not, so a category list assembled by pattern-matching identifiers is a guess presented as
157
+ an inventory — and its failure mode is silent, because whatever the guess misses is simply not
158
+ disclosed. The declaration exists so that never happens.
109
159
 
110
- Say that explicitly when recording this gap, or the next reader will point at that enum and assume
111
- the concern is already answered.
160
+ **Completeness** — `DERIVED` when the application declares categories; `NEEDS_CONFIGURATION` when it
161
+ declares none, or when the facts section lists OUTSTANDING fields.
112
162
 
113
- **Completeness** — `NEEDS_FRAMEWORK`.
163
+ **The two gaps are different and must not be written the same way.**
114
164
 
115
- **What closes it** — an engine change adding a data-category vocabulary declarable per resource and
116
- per field — issue #90. Per FIELD is what makes it worth having: a resource-level category
117
- cannot express that one row holds a name, an email and a payment token, which is exactly what a
118
- notice must enumerate.
165
+ - A resource that declares no category at all may genuinely hold no personal data. Nothing
166
+ distinguishes "considered and not applicable" from "never asked", so state that the question is
167
+ unanswered — never that the application holds no personal data.
168
+ - A field the facts section lists as OUTSTANDING is a provable omission. The application already
169
+ declared that field personal by another door — an erasure scrub treatment, a portability
170
+ provenance, or a credential marker — so the missing category is an omission, not a judgement.
171
+ Name the field and its basis. Do not guess what it contains.
119
172
 
120
- **Do not derive categories from field names.** `email`, `phone`, `dateOfBirth` are suggestive and
121
- `notes` is not, and a category list assembled by pattern-matching identifiers is a guess presented as
122
- an inventory — the failure mode being that whatever the guess misses simply is not disclosed.
173
+ **Say WHICH special category, not that there is one.** A `special-category:*` value is Art. 9 data
174
+ and carries a lawful-basis condition of its own beyond Art. 6; `criminal-offence` is Art. 10, a
175
+ separate article with a different condition. "We process special category data" is not a disclosure —
176
+ the enum names the kind precisely so a notice can.
177
+
178
+ **Do NOT point at `Compliance_DataClassification`.** It exists, it is a four-level SENSITIVITY ladder
179
+ (public / internal / confidential / restricted) applied only to flows-actors configuration, and it
180
+ answers "how protected must this be" rather than "what kind of personal data is this". Using it here
181
+ would produce a notice describing protection levels where a reader expects data types. It is named
182
+ explicitly because it is a near-miss a reader will otherwise find and assume answers this concern.
123
183
 
124
184
 
125
185
  ### Concern: consent and preferences
@@ -129,13 +189,41 @@ actually controls.
129
189
 
130
190
  **Derives from**
131
191
 
132
- - `DataProcessingConsent` (`saas-models` → `compliance/privacy/privacy.shared.schemas.ts`):
133
- `NONE` · `BASIC` · `ANALYTICS` · `MARKETING` · `FULL` — a ladder, so a level implies the ones below it.
134
- - the application's `requiredConsent` (`app-configuration-shared.shared.schemas.ts`, default
135
- `ANALYTICS`) — the minimum a person must give to use the service.
136
- - per-user `dataProcessingConsent` — the level each person actually chose.
137
-
138
- **Completeness** — `DERIVED`.
192
+ - `ConsentPurpose` (`@wildo-ai/saas-models`): `ANALYTICS` · `MARKETING` — a SET of purposes, each
193
+ granted or not on its own. There is no ordering: agreeing to marketing says nothing about analytics.
194
+ - per-person `privacy.consentedPurposes` — the purposes each person granted, empty until they grant
195
+ one — and `privacy.consentDecidedAt`, stamped by the server when they decide. An empty set WITH an
196
+ instant is "declined everything"; no instant is "never asked". A notice must not state the second
197
+ as the first.
198
+ - `analytics.requiresConsent` (default `true`) — whether the application's analytics rest on
199
+ `ANALYTICS`. It governs analytics alone, never use of the service.
200
+ - the visitor tier: a marketing website keeps a visitor's decision in their browser and starts a
201
+ consent-based provider (product analytics) only once its purpose is granted.
202
+
203
+ - `operatorComplianceIdentity.serviceConsentRequirement` (`wildo.saas.config.ts`) — what a person
204
+ must agree to in order to use the service AT ALL, and what that gate covers.
205
+
206
+ **An empty `requiredPurposes` is a POSITIVE answer and the usual one.** The operator declaring that nothing is gated on
207
+ consent has answered the question; a document must state it as settled rather than treating it as an
208
+ absence. ABSENT is the different case — nobody was asked — and the brief distinguishes the two.
209
+
210
+ **A consent GATE is not a lawful BASIS.** For most B2B SaaS the basis for core processing is CONTRACT:
211
+ a person uses the product because their employer signed for it. A notice that reads a gate as a basis
212
+ states that their data is processed on consent they could withdraw, which is wrong about the single
213
+ most consequential thing in the document. The basis is declared per purpose in `lawfulBases`.
214
+
215
+ **Completeness** — `DERIVED` for the analytics gate, each person's granted purposes, and the
216
+ service-wide requirement once declared — which the application ENFORCES: until the required purposes are
217
+ granted, the backend refuses every operation the person initiates — API and MCP operations, queued work,
218
+ WebSocket reads and subscriptions, agent tools, retrieval, charts and analytics, A2A task reads, and A2A or
219
+ WebSocket conversations, including resuming one after an approval — except their own profile and preferences,
220
+ where they record the consent, and cancelling an A2A task they already started (signing in and out stay open;
221
+ updates the server pushes on its own are not held back), and the web
222
+ application withholds its pages; `NEEDS_DECISION` naming `serviceConsentRequirement` when it is not.
223
+
224
+ This was `NEEDS_FRAMEWORK` until 2026-08-30, correctly: there was nowhere to record the answer. Issue
225
+ #139 built the surface, so the remedy changed from "someone must build this" to "fill this in" — a
226
+ different party and a different task, which is why the two states are never interchangeable.
139
227
 
140
228
  **Say the thing readers get wrong.** Consent is one lawful basis among several, and it is not the one
141
229
  most B2B processing rests on. **Never write that all processing rests on consent, and never write
@@ -156,17 +244,32 @@ marked `.impersonalizeWith()`; `RETAIN_ONLY` keeps and freezes a row that holds
156
244
  its own. Reading the per-field treatments tells the document exactly WHICH values are destroyed and
157
245
  which survive, which is a genuinely strong statement most notices cannot make.
158
246
 
159
- **Not derivable (the HOW LONG)** — nothing in the framework declares a retention DURATION. A resource
160
- says what erasure does to it; no declaration says "kept for seven years", and none can be inferred
161
- from anything present.
247
+ **Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config
248
+ over four data classes: `RESOURCE_DATA` (its records), `FILES` (uploaded bytes), `AUDIT_LOGS` (the
249
+ tamper-evident trail, kept longest and for a different reason — it is the evidence an operator may
250
+ lawfully retain under GDPR Art. 17(3)) and `OPERATIONAL_LOGS`. Each declared class carries a period in
251
+ days AND the operator's stated reason for it.
252
+
253
+ The classes are the STORES on purpose: the same declaration answers what a notice must state and what
254
+ a backup-and-restore inventory must protect (issue #8).
255
+
256
+ **The `retention-rules` fact is COMPUTED from both** — the declared periods with their reasons, the
257
+ classes with no period, each resource's declared erasure treatment, and the resources declaring none.
258
+ You never declare it. It is absent when no schedule is declared, because a treatment alone would read as
259
+ the whole answer.
260
+
261
+ **Completeness** — `DERIVED` for the treatment, and for each retention class the application HAS
262
+ declared. `NEEDS_DECISION` for each class it has not: the mechanism exists, so what is missing is an
263
+ operator's decision rather than an engine change. Do not let the derivable half hide the missing one —
264
+ a statement about erasure mechanics reads to a reader as an answer about retention, so both go in the
265
+ same breath.
162
266
 
163
- **Completeness** — `DERIVED` for the treatment, `NEEDS_FRAMEWORK` for the duration, in the same
164
- fragment. Do not let the derivable half hide the missing one: a statement about erasure mechanics
165
- reads to a reader as an answer about retention, so the gap must be stated in the same breath.
267
+ **What closes it** — the operator deciding a period, and saying why. Not a framework change: issue #89
268
+ delivered the declaration surface, so an undeclared class is now an unanswered question rather than an
269
+ unaskable one.
166
270
 
167
- **What closes it** — an engine change adding a declared retention period per resource or data
168
- category — issue #89. Until then the produced document says the duration is not yet
169
- established and names what would settle it.
271
+ **An UNDECLARED class is not "kept indefinitely" and not "deleted immediately".** It is a decision
272
+ nobody has taken, and the document must say exactly that.
170
273
 
171
274
  **Never write a placeholder period.** "Typically 12 months" in a published notice is a commitment
172
275
  nobody made and nothing enforces.
@@ -178,41 +281,134 @@ nobody made and nothing enforces.
178
281
 
179
282
  **Derives from (partial)** — the engine capabilities the application has a provider configured for
180
283
  (`EngineCapability` in `saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`).
181
- That establishes THAT a third party is involved and WHAT FUNCTION it performs — email delivery,
182
- storage, payments, LLM inference, observability.
284
+ Runtime bindings establish the configured function — email delivery, storage, payments, LLM inference
285
+ or observability. Deployment choices determine whether a third party operates that function; a
286
+ configured capability alone does not establish a third-party recipient.
287
+
288
+ **Derives from (the identities)** — the application's PROCESSOR REGISTER, which your brief renders
289
+ under *"Who else processes personal data"*. Per entry: the processor's **legal entity**, the
290
+ **regions** it processes in, and its own **subprocessors** with their regions.
291
+
292
+ **The register holds two kinds of entry and the brief labels them differently — say which.** A
293
+ CONFIGURED PROVIDER entry joins to the application's composition, so it can be checked against it: a
294
+ claim about a provider the application does not configure is detectable, and a configured provider
295
+ with no entry is reported as UNDECLARED. An AUTHORED entry — a hosting company, a CDN, a support desk
296
+ — joins to nothing, because no configuration mentions it. The framework can neither confirm it nor
297
+ notice its absence.
298
+
299
+ Both kinds of declared relationship can belong in the notice when their role is established. What
300
+ must not happen is presenting the second with the authority of the first: an authored entry is the operator's word, and a document that reads
301
+ as though the framework verified it overstates what anyone checked.
302
+
303
+ **A SELF-HOSTED provider is not a recipient either, and this is the second way to get the section
304
+ wrong.** The brief's *"Who RUNS each bound provider"* block splits runtime-bound providers three ways:
305
+ THIRD-PARTY RECIPIENTS (vendor-hosted, so data reaches a third party — enumerate these with their
306
+ region), OPERATOR-RUN (self-hosted, so no third party receives anything — state them as processing
307
+ under the operator's own control, never as recipients), and UNANSWERED.
308
+
309
+ An UNANSWERED provider is bound to a runtime with no declared deployment model. **Do not assume
310
+ vendor-hosted.** It looks like the cautious reading and it is not: it publishes that a person's data
311
+ goes to a third party when nobody said so. Report it as not established, and name the surface —
312
+ `providerComplianceChoices` in `wildo.saas.config.ts`.
313
+
314
+ **A provider PROFILE is not a recipient.** The brief separates providers BOUND TO A RUNTIME — backend,
315
+ companion, workers, minions, a frontend service, which can process the application's data — from
316
+ provider profiles with no runtime binding. A profile says how to reach a provider; build-time tooling
317
+ lives there, and a coding agent operating on the workspace receives no customer records. Never name a
318
+ profile-only provider as a recipient. Naming one reads as caution and is a false statement about
319
+ somebody's data, exactly like omitting a real one.
320
+
321
+ The section joins the register to runtime-bound RECIPIENT CANDIDATES after excluding explicit
322
+ self-hosted providers, so it tells you three different things
323
+ and they are not interchangeable:
324
+
325
+ - a candidate WITH an entry — its declared identity and regions are available. Establish its
326
+ deployment role before presenting it as a recipient.
327
+ - a candidate listed **UNDECLARED** — a runtime binding has no matching processor entry. Name its
328
+ configured function and unresolved declarations; an unanswered deployment choice remains unknown,
329
+ not automatically vendor-hosted. `NEEDS_DECISION`, resolved by the operator.
330
+ - a provider entry listed **STALE** — it no longer matches the current recipient-candidate set.
331
+ Reconcile the declaration and deployment choice; this check alone does not establish its actual
332
+ historical processing or that all external data has been removed.
333
+
334
+ **Completeness** — `DERIVED` per provider that is declared, `NEEDS_DECISION` per provider that is not.
335
+ Not `NEEDS_FRAMEWORK` any more: issue #88 delivered the declaration surface, so an undeclared processor
336
+ is an unanswered question rather than an unaskable one.
337
+
338
+ **Never infer a region from a vendor's brand.** "It is a US company" is not a processing location, and
339
+ a transfer statement built on it is a claim about somebody's data made from a guess.
340
+
341
+ **Distinguish the register declaration from its reconciliation.**
342
+
343
+ | Observed state | What it establishes | What the document may say |
344
+ | --- | --- | --- |
345
+ | Register absent | No processor declaration was supplied | The operator has not established the register; do not infer recipients or their absence |
346
+ | Register present with `processors: []` | The operator declares no processors | Report that declaration, then check it against runtime-bound recipient candidates; it is not independent proof that nobody receives data |
347
+ | Recipient candidates have no matching entries, including with an empty register | The composition and declarations leave named questions unresolved | Identify the configured functions and outstanding deployment, identity or location decisions without inventing third parties |
348
+
349
+ Reconcile only runtime-bound candidates. Exclude explicitly SELF_HOSTED providers and profile-only
350
+ providers; keep unanswered deployment choices visible as unanswered. `registerEstablishesNoProcessorRecipients`
351
+ answers the declaration question; `undeclaredProcessorRefs` answers candidate coverage. A true answer to
352
+ the first does not erase gaps returned by the second.
353
+
354
+ Name third-party recipients only when their role is established. An empty register does not justify
355
+ an unconditional statement that third parties provide email, storage or payments. Equally, do not
356
+ omit unresolved candidate questions and thereby imply that absence was verified. Authored recipients
357
+ remain operator declarations whose completeness cannot be inferred from runtime bindings.
183
358
 
184
- **Not derivable** — the three things a reader actually needs: the processor's **legal identity**, the
185
- **region** it processes in, and its own **subprocessors**. A provider declares none of them.
186
359
 
187
- **Completeness** — `NEEDS_FRAMEWORK`, and this is the largest single gap in the produced document. It
188
- blocks this concern and the international-transfers one for every application, not just this one.
360
+ ### Concern: international transfers
189
361
 
190
- **What closes it** — an engine change giving a provider declaration a processor identity, a
191
- processing region and a subprocessor list — issue #88.
362
+ **Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer
363
+ mechanism.
192
364
 
193
- **The honest interim statement names the FUNCTIONS and admits the identities are outstanding.**
194
- "Third parties process data for email delivery, file storage and payments; their identities and
195
- processing locations are not yet established in this document" is true, useful and specific. What is
196
- forbidden is the other two moves: inventing a plausible vendor list, and omitting the section — the
197
- first is false and the second lets a reader assume there are no recipients at all.
365
+ **Derives from** — the processor register's regions, at BOTH levels: each declared processor and
366
+ each processor's own subprocessors. Your brief renders them under *"Personal data reaches processors
367
+ in: …"*.
198
368
 
369
+ Both levels, because the chain is what makes a transfer statement hard. An operator in France using a
370
+ French vendor that runs on a US cloud HAS a transfer, and reading only the vendor's region misses it.
199
371
 
200
- ### Concern: international transfers
372
+ **The question has three inputs, and the framework derives only one of them.** Where declared
373
+ processors process is declared. Which jurisdiction is the ORIGIN is `operatingJurisdictions`. Which
374
+ MECHANISM makes a given transfer lawful is a legal determination with a shelf life — adequacy decisions
375
+ move by court ruling — so the framework never computes it: the operator RECORDS it, per register entry,
376
+ as a `transferDetermination`:
201
377
 
202
- **Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer
203
- mechanism.
378
+ - `NO_TRANSFER`, with the reason none of the entry's regions lies outside the origin jurisdictions —
379
+ regions are free text, so this comparison is the operator's and never the framework's;
380
+ - `TRANSFER`, with one safeguard per origin jurisdiction: the GDPR Chapter V mechanism
381
+ (`ADEQUACY_DECISION`, `STANDARD_CONTRACTUAL_CLAUSES`, `BINDING_CORPORATE_RULES`,
382
+ `APPROVED_CODE_OF_CONDUCT`, `APPROVED_CERTIFICATION`, or a `DEROGATION` naming its Art. 49 ground) and
383
+ the instrument a reader could look up.
204
384
 
205
- **Derives from** — nothing, and it cannot until the recipients-and-processors concern is answered:
206
- a transfer statement is a statement about WHERE a recipient processes, so a provider declaration that
207
- carries no region cannot support one.
385
+ The determination sits on the ENTRY because the processor's own contract binds its onward transfers to
386
+ its subprocessors; reaching the processor is the transfer the operator answers for.
208
387
 
209
- **Completeness** — `NEEDS_FRAMEWORK`, dependent on that concern rather than independent of it. Say so
210
- in the produced document; two gaps with one remedy read very differently from two unrelated holes.
388
+ **The `international-transfers` fact is COMPUTED from those determinations** — you never declare it.
389
+ It carries each determined entry, the origin jurisdictions, `undeterminedRecipients` — a register entry
390
+ with no determination, or a configured provider the register does not establish — and `safeguardGaps`:
391
+ a declared origin a TRANSFER names no safeguard for.
211
392
 
212
- **What closes it** — the same engine change as the recipients concern — a processing region on a
213
- provider declaration, issue #88. The
214
- transfer MECHANISM (adequacy, standard contractual clauses, derogation) is then a `NEEDS_DECISION`
215
- layered on top, because a mechanism is chosen and documented rather than derived.
393
+ **Completeness** — do not round any state up.
394
+
395
+ | the register | what you may state | completeness |
396
+ |---|---|---|
397
+ | ABSENT | nothing — where data lands is unknown, and the fact is absent | `NEEDS_CONFIGURATION` |
398
+ | a recipient in `undeterminedRecipients` | that its transfer position is not determined; never fold it into "no transfer" | `NEEDS_DECISION` for that recipient |
399
+ | declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |
400
+ | a determined entry | its transfer with the safeguard per jurisdiction, or NO_TRANSFER as such | `DERIVED`; a `safeguardGaps` entry is stated as a transfer with no safeguard recorded for that jurisdiction |
401
+
402
+ **The residual is not optional wording.** "No processor receives personal data" establishes nothing
403
+ about the operator's OWN processing — its infrastructure, its staff, its own establishment. A document
404
+ that says "we do not transfer data internationally" on the strength of an empty register has answered
405
+ a larger question than it was asked.
406
+
407
+ **What closes an undetermined entry** — the operator researching the vendor's data processing
408
+ agreement and recording what it relies on, per origin jurisdiction. A vendor's DPA usually names it:
409
+ standard contractual clauses for EU data, the UK Addendum to them for UK data, and sometimes a
410
+ certification under an adequacy framework beside them. Record what the contract says, not what is
411
+ typical.
216
412
 
217
413
  **"We do not transfer data internationally" is a claim, not a default.** It may be true, and it is
218
414
  citable when an application has declared it as a fact — but it must never be produced because nothing
@@ -233,10 +429,21 @@ use and for what function.
233
429
  effect** on a person, and whether a human reviews it. Nothing in the framework declares consequence or
234
430
  human-review posture, and neither can be inferred from a capability being enabled.
235
431
 
236
- **Completeness** — `NEEDS_FRAMEWORK` for the consequence posture.
432
+ **Derives from (the consequence)** — the AI POSTURE section of your brief, per ENABLED AI capability:
433
+ what it is used for, whether it `NO_DECISION` / `ASSISTS_HUMAN_DECISION` / `DECIDES_AUTONOMOUSLY`, and —
434
+ where it decides anything — how a person obtains human intervention.
237
435
 
238
- **What closes it** — an engine change letting an AI use declare its consequence and its human-review
239
- arrangement — issue #92.
436
+ An application enabling NO AI capability gets a plain statement to that effect: it performs no AI
437
+ processing of personal data. That is a positive, checkable answer, not a gap.
438
+
439
+ **Completeness** — `DERIVED` per capability with a declared posture; `NEEDS_DECISION` per capability
440
+ listed OUTSTANDING. Not `NEEDS_FRAMEWORK` any more: issue #92 delivered the declaration, so an
441
+ undeclared posture is an unanswered question rather than an unaskable one.
442
+
443
+ **An OUTSTANDING capability is not a harmless one.** This is the one concern where silence is more
444
+ dangerous than elsewhere: a notice describing AI use and saying nothing about consequence does not read
445
+ as "unknown", it reads as "nothing significant happens here" — which is the exemption, claimed for
446
+ free. State the gap explicitly.
240
447
 
241
448
  **Why the distinction carries weight.** Automated decision-making with significant effects attracts
242
449
  specific obligations — information about the logic, and a right to human intervention. A generated
@@ -251,52 +458,92 @@ about a person is not yet established.
251
458
 
252
459
  **Derives from (partial)** — the observability and analytics capabilities the application has
253
460
  configured (`FRONTEND_PRODUCT_ANALYTICS`, `LLM_OBSERVABILITY`, `OBSERVABILITY_TELEMETRY`), together
254
- with the consent ladder: `requiredConsent` and per-user `dataProcessingConsent` make
255
- `DataProcessingConsent.ANALYTICS` a real, enforced boundary rather than a stated intention.
461
+ with the consent posture: `analytics.requiresConsent` and each person's `privacy.consentedPurposes` make
462
+ `ConsentPurpose.ANALYTICS` a real, enforced boundary rather than a stated intention — in the application,
463
+ and on the marketing website, where a product-analytics provider does not start until a visitor grants it.
256
464
 
257
- **Not derivable** — the **cookie and client-storage inventory**. Nothing declares which cookies, local
258
- storage keys or client-side SDKs the frontend sets, what each is for, or how long it persists — the
259
- exact table a cookie notice consists of.
465
+ **Derives from (the inventory)** — the CLIENT STORAGE section of your brief: each cookie and storage
466
+ key, its mechanism, purpose, necessity and lifetime, split by who sets it.
260
467
 
261
- **Completeness** — `DERIVED` for the capability and consent posture, `NEEDS_FRAMEWORK` for the
262
- inventory.
468
+ The FRAMEWORK's own entries are listed first and belong in every application's table — the cookies
469
+ `__wildo_refresh` and `__wildo_anon_session`, strictly necessary, with lifetimes taken from the
470
+ application's session configuration, and the website's `__wildo_website_consent` storage key, strictly
471
+ necessary because it is what makes a visitor's refusal hold. **No application authored these and every application sets them**, so a table
472
+ built only from what the application declared would omit the session cookie, which is the entry a
473
+ visitor is most certain to have.
263
474
 
264
- **What closes it** — an engine change declaring client-storage entries per capability and per
265
- frontend surface — issue #91.
475
+ Then, per frontend surface: its declared entries, an explicit "sets nothing of its own", or
476
+ UNINVENTORIED.
266
477
 
267
- Say both halves: which analytics are in use and what consent gates them (strong, derived, enforced),
268
- and that the itemised cookie table is not yet established (honest, and precisely what a cookie notice
269
- still needs before it can be published).
478
+ **UNINVENTORIED is not "sets nothing".** The first says nobody catalogued that surface; the second is a
479
+ positive statement. Writing the second from the first tells a visitor they are tracked by less than they
480
+ are, which is the under-reporting direction a notice must never fail in.
270
481
 
482
+ **Completeness** — `DERIVED` for the capability and consent posture, and for each surface that IS
483
+ inventoried; `NEEDS_DECISION` per uninventoried surface. Not `NEEDS_FRAMEWORK` any more: issue #91
484
+ delivered the declaration surface, so an uninventoried surface is an unanswered question rather than an
485
+ unaskable one.
271
486
 
272
- ### Concern: subject rights
273
-
274
- **Asserts** — which rights the application can actually honour, and through which mechanism. Not what
275
- the law grants; what this application will do when asked.
487
+ Say both halves: which analytics are in use and what consent gates them (strong, derived, enforced), and
488
+ what the table still lacks — naming the surfaces, not the concern.
276
489
 
277
- **Derives from**
278
490
 
279
- - `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20`
280
- (`saas-models` → `compliance/privacy/subject-export.shared.schemas.ts`) — the two distinct export
281
- bundles. Access is the broader one: every row concerning the subject, including rows they do not
282
- own, such as an audit entry about them or a membership an administrator created.
283
- - each resource's `systemAccessPolicy.exportSubject` — whether an export can answer for that resource
284
- at all. **Absent means the resource is excluded from every export**, so an application that has not
285
- declared it cannot honour Art. 15 over that data.
286
- - `portabilityPolicy` and per-field `.portabilityProvenance()` — Art. 20 covers what the subject
287
- supplied, not what the controller derived about them, and an Art. 20 export refuses on any field
288
- that has declared neither.
289
- - erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, which takes a resource type and row ids and
290
- needs no session. **An account is not required to be a data subject** — a contact, a lead or a
291
- subscriber is erased by exactly this path.
491
+ ### Concern: subject rights
292
492
 
293
- **Completeness** — `DERIVED` where the resources hold `exportSubject` declarations.
493
+ **Asserts** — which request mechanisms the application configures, what they select and what their
494
+ results establish. A configured mechanism does not establish that a particular request was fulfilled.
294
495
 
295
- **What closes it** — per-resource `exportSubject` and, for portability, a `portabilityPolicy` default
296
- plus provenance on the fields that differ from it.
496
+ **Derives from**
297
497
 
298
- **Never state** that a right is honoured for a resource whose `exportSubject` is absent. The export
299
- will not include it, and the notice would be describing a capability the application does not have.
498
+ - `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20` — two selections over the declared
499
+ subject relationships. Access includes eligible owned rows and non-owned rows referring to the
500
+ subject. Portability applies narrower relationship and field-provenance selection. Neither is an
501
+ unrestricted recursive export of everything reachable from an account.
502
+ - Each participating resource's `systemAccessPolicy.exportSubject` — an explicit disclosure choice,
503
+ checked before collection. Missing and forbidden are different decisions:
504
+
505
+ | Declaration | Runtime result | Meaning for the request |
506
+ | --- | --- | --- |
507
+ | Absent on a participating resource | Refuses collection | A required disclosure decision is unanswered; no silently incomplete bundle is returned |
508
+ | `ALLOWED` | Passes this disclosure gate | Relationship selection, system-read admission, field security and purpose-specific checks still apply |
509
+ | `FORBIDDEN` on a dependent resource | Excludes that resource and records the reason | A deliberate exclusion; do not change it to ALLOWED merely to remove a reported omission |
510
+ | `FORBIDDEN` on the subject's own resource | Refuses the bundle | The subject cannot be omitted from its own export |
511
+
512
+ - `portabilityPolicy.defaultProvenance` and per-field `.portabilityProvenance(...)` — the field
513
+ declaration overrides the resource default. `SUBJECT_PROVIDED` and `OBSERVED` values are eligible
514
+ for portability; `DERIVED` values are excluded and reported. Unresolved provenance refuses
515
+ portability collection rather than silently dropping fields. Explicitly forbidden resources do
516
+ not need portability provenance for this export because their rows are not collected. Access uses
517
+ its separate field selection; backend-only and write-only fields remain withheld.
518
+ - Erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, invoked by the application's verified request
519
+ workflow. A contact or lead without a login can still be a data subject. Retention, relationship
520
+ treatments and account linkage are separate declarations; inspect the receipt before claiming
521
+ completion, including dependent execution, session resolution and incomplete external effects.
522
+
523
+ **The rights a notice states are COMPUTED, in the `rights-and-complaint-route` fact.** Which rights
524
+ apply, and where a person may complain, are the law of the regime each `operatingJurisdictions` entry
525
+ falls under, conditioned on the declared lawful bases: portability only for purposes resting on consent
526
+ or contract, objection only for public task or legitimate interests, withdrawal of consent only where
527
+ consent is the basis. The channel is `privacyContact`; the verification step is the operator's
528
+ `subjectRequestIdentityVerification`; who answers comes from `roleAllocations` — the operator for data it
529
+ controls, the customer (with the operator forwarding and assisting) for data it processes on a
530
+ customer's behalf. A jurisdiction no known regime reaches is named in `jurisdictionsWithoutKnownRegime`:
531
+ state that its rights are not established here, never borrow another regime's words for it.
532
+
533
+ **Completeness** — derive the configured posture from actual resource declarations and the selected
534
+ relationships. Describe an unresolved declaration as a configuration refusal, an explicit exclusion
535
+ as an exclusion, and an observed request outcome from its report. Declarations alone are not runtime
536
+ proof that a right has been fulfilled.
537
+
538
+ **What resolves a missing declaration** — the owning resource explicitly declares ALLOWED or FORBIDDEN
539
+ according to its intended disclosure policy. Portability additionally needs a valid resource default
540
+ or field-level provenance for the fields it would collect. Do not ask a notice author to replace a
541
+ missing product declaration with a free-text promise.
542
+
543
+ **Never state** that an undeclared participating resource is merely omitted while the remainder is
544
+ exported. The runtime refuses collection. Preserve deliberate exclusions and explain their recorded
545
+ reasons; the application's request workflow owns verification, protected delivery and any necessary
546
+ follow-up.
300
547
 
301
548
 
302
549
  ### Concern: data exit
@@ -325,8 +572,12 @@ their personal fields scrubbed, is inaccurate in the direction that damages trus
325
572
  operator's responsibilities and the customer's lies.
326
573
 
327
574
  **Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every
328
- tenant-scoped resource, and the cross-tenant admission rules (a crossing must be declared on the
329
- operation and carries a usable access grant).
575
+ tenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be
576
+ declared and carry a usable access grant. The application audit viewer is a separate policy surface:
577
+ it defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with
578
+ `auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under
579
+ which a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
580
+ role-based access neither implies anonymized records nor supplies an approval that never occurred.
330
581
 
331
582
  **Completeness** — `DERIVED`.
332
583
 
@@ -336,5 +587,12 @@ CONTROLLER for the data it holds about the customer's users as account holders.
336
587
  roles with different duties over the same database. Say which is which; do not pick one and apply it
337
588
  to everything.
338
589
 
339
- Where a document needs to attribute a duty and the attribution is not established, that is a
340
- `NEEDS_DECISION` — never a guess. See the legal-basis fragment.
590
+ **The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
591
+ `wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
592
+ stores about its own people, CONTROLLER for the account data of the people who administer them. It is
593
+ a LIST for exactly the reason this fragment gives: those are different roles over the same database,
594
+ and a single field would force one of them to be wrong.
595
+
596
+ Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
597
+ surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
598
+ so the remedy is to fill it in rather than to build something. See the legal-basis fragment.