@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
@@ -1,17 +1,875 @@
1
1
  # Compliance document candidate method
2
2
 
3
- Use the `compliance-document-authoring` skill and the exact host-supplied
4
- blueprint and fact projection. Produce only the structured
5
- `ApplicationAssuranceDocumentCandidateContentDraftV1` proposal requested by the
6
- host.
7
-
8
- Preserve section and clause order, exact semantic refs, fact bindings,
9
- source-policy refs, claim-guard refs, variant selections, review checklists and
10
- limitations. Do not fill an unresolved fact, infer a legal decision, copy
11
- restricted text, or describe the candidate as approved, compliant, legally
12
- valid, released or published.
13
-
14
- Locale and jurisdiction are candidate review inputs, not proof of legal
15
- applicability. Leave every unresolved or unsupported item visible. The trusted
16
- runtime—not this method—validates the proposal, derives candidate status and
17
- seals exact content and provenance digests.
3
+ You are drafting ONE governed document for this application, from what the application has already
4
+ declared. Follow the `compliance-document-authoring` skill for the rules — its full text is in your
5
+ brief, under "The skills this method tells you to FOLLOW", because this step has no tools and cannot
6
+ open a file. This method says which document, what shape, and what the two closed vocabularies are.
7
+
8
+ ## Choose the document, from the two this lane may draft
9
+
10
+ `documentRef` must be one of six and the contract refuses anything else, but only two of the six are
11
+ YOURS. The four internal `governance.*` documents belong to `refinement.governance-document-candidate`,
12
+ which ships their blueprints; drafting one here would mean writing a document whose obligations you were
13
+ never given.
14
+
15
+ | `documentRef` | what it is | drafted by |
16
+ |---|---|---|
17
+ | `document:public.privacy-notice` | what personal data the application holds and what happens to it | **this lane** |
18
+ | `document:public.service-terms` | the commercial and service relationship | **this lane** |
19
+ | `document:governance.scope-system-description` | what the system IS, for an assurance reader | `refinement.governance-document-candidate` |
20
+ | `document:governance.roles-responsibilities` | who is accountable for what | `refinement.governance-document-candidate` |
21
+ | `document:governance.program-handbook` | how the governance program runs | `refinement.governance-document-candidate` |
22
+ | `document:governance.document-record-control` | how governed documents are themselves controlled | `refinement.governance-document-candidate` |
23
+
24
+ **Draft a document this application does not already hold.** The run tells you which those are: the
25
+ brief opens with what the application has already drafted, listing each document it may produce here
26
+ as ALREADY DRAFTED or not yet drafted. Drafts are keyed by `documentRef`, so drafting one that is
27
+ already there REPLACES it — right when that draft is wrong, and a wasted run when it is not.
28
+
29
+ Where several remain, the **privacy notice** comes first: it is the one every application holding
30
+ personal data needs. Where none remains, the honest reason to draft again is that a held draft is
31
+ wrong — say which one and why in your own reasoning, rather than redrafting the first on the list.
32
+
33
+ This paragraph used to read "draft the privacy notice unless the run tells you otherwise", at a time
34
+ when no run told it anything. Measured against a real application on 2026-09-16: with its privacy
35
+ notice already drafted, two consecutive runs meant to produce the service terms drafted the notice
36
+ again and replaced it, and the application finished each run holding exactly what it started with.
37
+ The second sentence was stale as well — it said the privacy notice was "the only one whose facts the
38
+ current derivation supplies", which stopped being true once the fact-declaring playbook began
39
+ declaring the account, billing and AI facts the service terms rest on.
40
+
41
+ Naming a document outside this set is not a smaller decision than it looks. Each of the six has a
42
+ concern composition the framework measures a draft against, so a seventh name is a document nobody can
43
+ state the gaps in — and stating the gaps is the whole point.
44
+
45
+ ## One section per concern, and SAY which concern
46
+
47
+ Every section carries `concernRef`, from the closed compliance-concern vocabulary. **The composition
48
+ for each document is inlined at the end of this method** — one entry per concern, saying what it
49
+ asserts, what in the application it derives from, what state it usually reaches, and what closes it
50
+ when it cannot. Draft one section per concern, in the order given, and produce **every** one:
51
+ a concern nothing can answer becomes a section with a marked clause, never a missing heading.
52
+
53
+ Those entries are the difference between a draft that states its gaps and one that guesses at them.
54
+ Where a concern's entry names an issue number as the remedy, say so in `incompleteness.closedBy` —
55
+ `#89`, `#91` — because a numbered issue is a remedy a reader can open, and "application configuration
56
+ owner" is not.
57
+
58
+ Use `concernRef: null` only for a section that genuinely answers no concern: a preamble, a contact
59
+ block. It is not a way past a concern you found hard. A concern you cannot establish gets a SECTION,
60
+ with a clause marked incomplete — which is the mechanism this whole document exists around.
61
+
62
+ The value must be the concern's exact name. A near miss (`retention` for `retention-and-deletion`) is
63
+ worse than a null: it reports the concern as unaddressed while the document addresses it.
64
+
65
+
66
+ ## And SAY which required parts the section supplies
67
+
68
+ Every section also carries `satisfiesSectionRefs`: the refs, from the document definition rendered in
69
+ your brief, that this section actually addresses. This is a different question from `concernRef` and
70
+ both are answered — the concern says what compliance TOPIC the section is about, the satisfied refs
71
+ say what part of THIS document it supplies.
72
+
73
+ You are asked for the join because you are the only reader that holds both. The concern set is one
74
+ flat vocabulary spanning every document type; the required parts are defined per document, and the
75
+ same concern does not sit under the same heading in a privacy notice and a governance handbook. A
76
+ mapping written once in the framework would have to pick one answer and be wrong somewhere.
77
+
78
+ - A section may claim several refs, and several sections may claim one between them.
79
+ - A section that answers no required part — a preamble, a contact block — answers `null`. Not an
80
+ empty list: `null` and `[]` would be two spellings of one state, and the contract refuses the second.
81
+ - **Claim honestly.** A required ref nobody claims is reported as a part the document may not address,
82
+ which is a true and useful finding. Claiming one you did not address hides that, and nothing
83
+ downstream reads your prose to catch it.
84
+
85
+ Do NOT adopt the definition's refs as your own `sectionRef` values. Your section set is the concern
86
+ rule above; these are a claim you attach to it, not names you take.
87
+
88
+ **Clauses carry the same claim**, as `satisfiesClauseRefs`, and answer `null` the same way. Your brief
89
+ lists the blueprint's clauses under each section, each marked REQUIRED or CONDITIONAL; name the ones
90
+ your clause supplies.
91
+
92
+ Both keys were ASKED FOR HERE and absent from the strict contract you answer until 2026-09-02, so a
93
+ draft that followed this section could not parse and every landed document claimed nothing. If you
94
+ are reading a document produced before then, its empty coverage is that defect and not a finding
95
+ about the document.
96
+
97
+ - Several of your clauses may supply one blueprint clause between them, and one clause may supply
98
+ several.
99
+ - A clause supplying none — a transition, a heading gloss — claims none.
100
+ - **Only the clauses marked REQUIRED are owed.** A CONDITIONAL clause is supplied when its condition
101
+ holds and correctly omitted otherwise, so leaving one unclaimed is not a gap.
102
+
103
+ This is the anchor a clause did not previously have. A fact is named by the catalog and a section
104
+ carries its concern, so both survive a redraft; a clause was named freely and joined to nothing, which
105
+ is why a reviewer who approved one could not find it in the next revision.
106
+ ## What a clause may say
107
+
108
+ The rule is ASSERT versus MARK, and the skill states it in full. In short: a clause may say "this is
109
+ not yet established"; it may not say something untrue.
110
+
111
+ - `DERIVED` — established by a fact this application has declared. Cite it in `factRefs`. A `DERIVED`
112
+ clause citing a fact the facts file does not declare is REFUSED before the write.
113
+
114
+ **This is decided against the facts file as it stands NOW, not against any earlier draft.** You are
115
+ producing the whole document from what the application currently declares, so a concern the facts
116
+ answer today is `DERIVED` today — even if a previous version of this document marked it incomplete
117
+ and is still in the tree. Re-running this playbook is how a document that went stale is repaired,
118
+ and it only repairs anything if the re-draft is willing to close a mark.
119
+
120
+ **A fact the application declared NOT APPLICABLE is a fact, and a clause may rest on it.** *"No
121
+ external analytics provider is configured"* is `DERIVED`, not incomplete: the application settled the
122
+ question and recorded the answer. Marking such a concern incomplete says the application does not
123
+ know something it does know, which is as wrong as overstating. What is refused is citing a fact the
124
+ facts file does not declare AT ALL.
125
+ - `NEEDS_FRAMEWORK` / `NEEDS_DECISION` / `NEEDS_CONFIGURATION` — mark it, and say in `incompleteness`
126
+ what is missing and who closes it. Four distinct suppliers, four distinct remedies; do not merge them.
127
+
128
+ **When what is missing is a FACT, name it in `incompleteness.awaitingFactRefs`.** The skill argues
129
+ this in full; the short version is that a marked clause asserts an ABSENCE in the application's own
130
+ configuration, and that assertion goes false the moment someone declares the thing — silently, since
131
+ nothing about the document changes. The awaited ref is what lets generation, landing and the
132
+ standing coherence report all say the clause has gone stale. A clause that awaits nothing rots
133
+ unobserved, and one already has.
134
+
135
+ **`NEEDS_DECISION` and `NEEDS_FRAMEWORK` are the pair most easily confused, and the difference is
136
+ the REMEDY.** `NEEDS_DECISION` means a surface exists and nobody filled it in — the reader goes and
137
+ answers. `NEEDS_FRAMEWORK` means there is NOWHERE to record the answer; telling a reader to decide
138
+ is telling them to write into a void.
139
+
140
+ Measured on 2026-08-30, a produced notice marked operator identity `NEEDS_DECISION` when no surface
141
+ for it existed at all, beside retention periods marked identically and genuinely just unfilled. Two
142
+ remedies, rendered the same, and a reader could act on neither.
143
+
144
+ **So every incomplete clause must NAME THE SURFACE its answer goes to**, or say plainly that none
145
+ exists. A gap with a named surface is a task; a gap without one is a request for work nobody has
146
+ scoped. The fragment you are working from names the surface where there is one — carry it into
147
+ `incompleteness` rather than leaving the reader to find it.
148
+
149
+ **`closedBy` must name WHO can reach that surface, and an ENGINE resource is not the application
150
+ author's to edit.** `retentionPolicy`, `systemAccessPolicy.exportSubject` and `.dataCategories()`
151
+ on an engine resource live in engine source. Writing "application authors must declare
152
+ `retentionPolicy` for each affected engine resource" hands the reader a task they cannot perform —
153
+ and a produced notice said exactly that, for 83 resources, in the same confident register as the
154
+ remedies that ARE actionable. An unreachable remedy is worse than an unnamed one: it looks like
155
+ work, gets scheduled, and fails when someone tries it.
156
+
157
+ Where the closer is the FRAMEWORK, say so plainly — "the framework must declare these on its own
158
+ resources" — and keep it separate from what this application owes.
159
+
160
+ Never fill an unresolved fact, infer a legal decision, or describe the draft as approved, compliant,
161
+ legally valid, released or published. Locale and jurisdiction are review inputs; leaving them
162
+ unresolved is a legitimate answer and never a reason not to draft.
163
+
164
+ **And the mirror of that, which matters just as much: a missing approval never stops you.** Approval
165
+ happens at the END and is a human commit; a downstream release can be composed and MARKED
166
+ `UNAPPROVED`. So the absence of one is a STATE to record, never a reason to produce nothing and never
167
+ an outcome to report as blocked. The two failures are symmetric — claiming an approval that did not
168
+ happen, and refusing to act because it has not happened yet — and a compliance workflow standing in
169
+ front of the application-creation mechanism is the second one.
170
+
171
+ ## The refs you write, and their exact shape
172
+
173
+ Every `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by
174
+ hyphens. `clause:retention-duration-not-declared` is one; `clause:Retention Duration` is not, and a
175
+ whole draft is rejected for a single malformed one. Ref ARRAYS are arrays of those strings — never
176
+ objects, never `{ ref: … }`.
177
+
178
+ Per clause, all three ref arrays are required. Two of them may be empty, but **not both of the
179
+ first two at once** — a clause that names no fact and no policy is sourced by nothing and is
180
+ rejected:
181
+
182
+ - `factRefs` — the facts this clause rests on, exactly as the facts file declares them. It may be
183
+ EMPTY for a clause that establishes nothing (a marked clause often does).
184
+ - `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and nothing else.
185
+ Every entry must be in the `policy:` namespace (`policy:retention`, `policy:recipients`,
186
+ `policy:security-controls`); any other namespace is rejected outright. **Do NOT put a fact
187
+ authority here.** A clause resting on declared facts already cites its authorities through
188
+ `factRefs`, which resolves them — repeating them here duplicates the citation beside it and
189
+ resolves to nothing. So this array is EMPTY for a fact-backed clause, and carries a policy area
190
+ for a clause that is sourced from a policy rather than from a fact.
191
+ - `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. These are the
192
+ boundaries you are already holding — `claim-guard:no-legal-applicability-claim`,
193
+ `claim-guard:no-invented-retention-period`, `claim-guard:known-fact-only`. Name the ones that apply
194
+ to this clause; do not repeat the same guard on every clause out of habit. You do not name the
195
+ CATALOG's guard for the material: it is added for you from the blueprint clauses this clause
196
+ `satisfiesClauseRefs`, so a clause that says what it satisfies is checked against it automatically.
197
+
198
+ `evidenceRefs` is **`null` on every clause of a public document**, and that is not a gap to work around.
199
+ It cites a judged run from this application's own assurance repository — self-attested internal
200
+ evidence — and a public notice may carry none, whatever the run says: a reader of one cannot weigh an
201
+ operator's judgement of its own product, and any citation here is refused before the draft becomes a
202
+ file. That evidence belongs to the internal governance documents, which
203
+ `refinement.governance-document-candidate` draws. Where you would have leaned on a measurement, say
204
+ what is CONFIGURED or DECLARED, or MARK the statement.
205
+
206
+ `reviewChecklistRefs` needs at least one (`review-checklist:<slug>`) — what a human must confirm before
207
+ this draft is worth anything. `limitationRefs` may be empty, but rarely should be: it is where you say
208
+ what the document does NOT cover, in your own words as the drafter, rather than leaving the reader to
209
+ discover it.
210
+
211
+ ## You do not compose the release — and a release nobody approved is marked UNAPPROVED
212
+
213
+ You draft the candidate. You do NOT author its release, and that is a boundary rather than an
214
+ omission: almost everything a release carries is DERIVED from the accepted document definition — the
215
+ document's class, who it addresses, which channels may carry it, which interactions it permits — and
216
+ a model restating those would create five ways to disagree with the catalog, invisibly. The rest
217
+ (which declared variant, when it takes effect) is a composition over families you are not holding.
218
+
219
+ A human declares a release DECISION in the application's
220
+ `specifications/src/document-releases/compositions.ts`, and `wildo config document-releases` composes
221
+ each decision not yet recorded — your candidate plus the declared variant and release policy — and
222
+ records the finished release, text included. Nothing records a release because you landed a draft: an
223
+ application with no decision holds no release yet, which is a valid state and not yours to fix from
224
+ this playbook. Until a public document (privacy notice, service terms) has a release, its public page
225
+ shows your latest draft, marked as a draft — so what you mark as not established is what a reader sees.
226
+ What matters for your work is what composition produces when it runs: a release carrying
227
+ `approvalState`, and one nobody has approved is `UNAPPROVED` and exists anyway.
228
+
229
+ **Which is why a missing approval never changes what you do here.** Draft the document completely,
230
+ mark every statement you cannot establish, and let the release be composed and marked. Waiting for an
231
+ approval before drafting — or describing a draft as approved to get past the gate — are the two
232
+ symmetric failures, and the first is a compliance workflow standing in front of the mechanism that
233
+ builds the application.
234
+
235
+ ## Where the draft goes
236
+
237
+ It lands as a FILE in the application's specifications package, as an ordinary working edit. It is
238
+ accepted by a commit and by nothing else; who makes that commit is the host's autonomy posture, and
239
+ only a PERSON's commit is an approval. Landing is not approval, release or publication — and neither is
240
+ a commit the development companion authors under the YOLO posture.
241
+
242
+
243
+ ---
244
+
245
+ # The compositions
246
+
247
+ Each of the following is one document's full concern list. Use the one matching your `documentRef`
248
+ and ignore the rest.
249
+
250
+ ## `document:public.privacy-notice` — thirteen concerns
251
+
252
+ ### Concern: operator identity
253
+
254
+ **Asserts** — who legally operates the service: entity name, registered address, contact route for
255
+ data-protection questions, and a representative where one is required.
256
+
257
+ **Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
258
+ registered address, the privacy contact route, and an Art. 27 representative where one is required.
259
+
260
+ The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
261
+ What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
262
+ said "no engine change would close it", which was right about derivation and wrong about the home.
263
+ The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
264
+ who answered by editing the document lost the answer at the next regeneration — the answer has to live
265
+ in the application or it does not survive.
266
+
267
+ **Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
268
+
269
+ ⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
270
+ exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
271
+ and nobody has. They have different remedies — build something, versus fill something in — and a
272
+ reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
273
+
274
+ **What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
275
+ filled in later without redrafting anything around it, which is the reason it is not a blocker.
276
+
277
+ **Never infer it.** Not from the application name, not from a domain, not from another application,
278
+ not from model memory. A published legal document naming the wrong entity is worse than one that says
279
+ the entity is not yet recorded — the first misdirects a person exercising a right, the second tells
280
+ them the document is incomplete.
281
+
282
+ **Every document needs this fragment**, which makes it the clearest demonstration of why producing
283
+ with gaps beats blocking: the whole document set would be unproducible until one form is filled in.
284
+
285
+
286
+ ### Concern: legal basis and controller/processor role
287
+
288
+ **Asserts** — the lawful basis for each processing purpose, and whether the operator acts as
289
+ controller or processor for it.
290
+
291
+ **Derives from** — `operatorComplianceIdentity.lawfulBases` and `.roleAllocations` in
292
+ `wildo.saas.config.ts`.
293
+
294
+ The DETERMINATIONS are never derivable — both are legal conclusions about the operator's own
295
+ arrangements, and the framework can show WHAT is processed and BY WHICH MECHANISM without establishing
296
+ under which basis or in which role. What it now provides is where to record the conclusion, so that a
297
+ regeneration reproduces it instead of destroying it.
298
+
299
+ **The role is a LIST, not a field, and the produced notice said so before the surface existed:**
300
+ *"This notice therefore does not assign a single legal role to all data processed in a workspace."* A
301
+ B2B SaaS is typically a processor for the records its customers put in and a controller for its
302
+ account holders' own data, simultaneously. `roleAllocations` carries one role per population, and a
303
+ document that collapses them into one is wrong about both.
304
+
305
+ **The `lawful-bases` fact is COMPUTED from `lawfulBases`** — every purpose, its basis and, for
306
+ legitimate interests, the assessment. You never declare it: a restatement would be a second copy of the
307
+ operator's decision that nothing compares with the first. Absent bases leave the fact absent.
308
+
309
+ **`LEGITIMATE_INTERESTS` cannot be declared without its assessment** — the schema refuses it. It is
310
+ the only Art. 6(1) basis whose lawfulness depends on a balancing test, so the bare claim asserts a
311
+ conclusion nobody reached.
312
+
313
+ **Completeness** — `DERIVED` when declared; `NEEDS_DECISION` when not. Never `NEEDS_FRAMEWORK`: there
314
+ is a surface, so the remedy is to fill it in, not to build something. Name the surface when reporting
315
+ the gap.
316
+
317
+ **What closes it** — the operator determining, per purpose, the basis and the role, ideally with
318
+ counsel, and declaring them in `operatorComplianceIdentity`. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for
319
+ the data a customer stores about its own people, controller for the data the operator holds about
320
+ account holders — but describing the common shape is not the same as determining this operator's, and
321
+ the produced document must not present the first as the second.
322
+
323
+ **This is the fragment most likely to be filled in by a confident guess**, because the shape is
324
+ familiar and the sentence is easy to write. Resist it. A basis stated in a published notice is a
325
+ position the operator has taken; a basis that was never determined is a position nobody can defend.
326
+
327
+
328
+ ### Concern: personal data held
329
+
330
+ **Asserts** — which of the application's own records are about identifiable people, and which hold no
331
+ personal data of their own.
332
+
333
+ **Derives from** — each resource's `retentionPolicy.mode` (`ErasureRetentionMode`, in
334
+ `@wildo-ai/saas-models`), read for every resource the application declares:
335
+
336
+ | declaration | what the document may state |
337
+ |---|---|
338
+ | `RETAIN_AND_IMPERSONALIZE` | this record holds personal data; the fields marked `.impersonalizeWith()` are what is scrubbed on erasure |
339
+ | `RETAIN_ONLY` | this record holds **no personal data of its own** — a positive, factory-enforced statement, because declaring a scrub treatment under this mode fails at config build |
340
+ | absent | the application has not said |
341
+
342
+ Read `dataSubjectPolicy.kind` for the SESSION question only. `NO_PRINCIPAL` is equally true of an
343
+ invoice and of a CRM contact, so it never tells you whether a record is about a person — the
344
+ retention mode does.
345
+
346
+ **Completeness** — `DERIVED` for every resource that declares a retention policy.
347
+
348
+ **An erasure-coverage gap does NOT license a claim about whether personal data is held.** The two are
349
+ different axes and the facts report them separately: `retentionPolicy` answers *what happens to this
350
+ row on erasure*, while a field's `.dataCategories()` answers *what kind of data is in it*. A resource
351
+ can declare the second and not the first, and 48 of the engine's 85 do.
352
+
353
+ So writing "N resources have no declared erasure treatment, so this notice cannot establish whether
354
+ they hold personal data" is an over-reach, and it contradicts the data-categories section of the same
355
+ document — which enumerates categories drawn from those very resources. It was produced twice on
356
+ 2026-08-30 before this paragraph existed.
357
+
358
+ State the gap as what it is: those resources have not declared an erasure TREATMENT, so a notice
359
+ cannot say what an erasure does to them. Where the facts also report a category coverage for the same
360
+ origin, say what IS established alongside it.
361
+ `NEEDS_CONFIGURATION` for every resource that does not.
362
+
363
+ **What closes it** — the application's own authors declaring `retentionPolicy` on the resource. Name
364
+ the resources individually: the remedy is per-resource, and a count is not actionable.
365
+
366
+
367
+ ### Concern: data categories
368
+
369
+ **Asserts** — which CATEGORIES of personal data are held: identity, contact details, credentials,
370
+ financial, usage, location, user content, professional, and any GDPR Art. 9 special-category or
371
+ Art. 10 criminal-offence data.
372
+
373
+ **Derives from** — each field's `.dataCategories()` declaration, reported per resource and unioned
374
+ across the application in the compliance-primary-facts section. One category is DERIVED rather than
375
+ declared: `credentials`, from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, which are
376
+ markers the author already wrote.
377
+
378
+ **Nothing is derived from a field NAME.** `email`, `phone` and `dateOfBirth` are suggestive while
379
+ `notes` is not, so a category list assembled by pattern-matching identifiers is a guess presented as
380
+ an inventory — and its failure mode is silent, because whatever the guess misses is simply not
381
+ disclosed. The declaration exists so that never happens.
382
+
383
+ **Completeness** — `DERIVED` when the application declares categories; `NEEDS_CONFIGURATION` when it
384
+ declares none, or when the facts section lists OUTSTANDING fields.
385
+
386
+ **The two gaps are different and must not be written the same way.**
387
+
388
+ - A resource that declares no category at all may genuinely hold no personal data. Nothing
389
+ distinguishes "considered and not applicable" from "never asked", so state that the question is
390
+ unanswered — never that the application holds no personal data.
391
+ - A field the facts section lists as OUTSTANDING is a provable omission. The application already
392
+ declared that field personal by another door — an erasure scrub treatment, a portability
393
+ provenance, or a credential marker — so the missing category is an omission, not a judgement.
394
+ Name the field and its basis. Do not guess what it contains.
395
+
396
+ **Say WHICH special category, not that there is one.** A `special-category:*` value is Art. 9 data
397
+ and carries a lawful-basis condition of its own beyond Art. 6; `criminal-offence` is Art. 10, a
398
+ separate article with a different condition. "We process special category data" is not a disclosure —
399
+ the enum names the kind precisely so a notice can.
400
+
401
+ **Do NOT point at `Compliance_DataClassification`.** It exists, it is a four-level SENSITIVITY ladder
402
+ (public / internal / confidential / restricted) applied only to flows-actors configuration, and it
403
+ answers "how protected must this be" rather than "what kind of personal data is this". Using it here
404
+ would produce a notice describing protection levels where a reader expects data types. It is named
405
+ explicitly because it is a near-miss a reader will otherwise find and assume answers this concern.
406
+
407
+
408
+ ### Concern: consent and preferences
409
+
410
+ **Asserts** — what the application asks consent for, at what granularity, and what a person's choice
411
+ actually controls.
412
+
413
+ **Derives from**
414
+
415
+ - `ConsentPurpose` (`@wildo-ai/saas-models`): `ANALYTICS` · `MARKETING` — a SET of purposes, each
416
+ granted or not on its own. There is no ordering: agreeing to marketing says nothing about analytics.
417
+ - per-person `privacy.consentedPurposes` — the purposes each person granted, empty until they grant
418
+ one — and `privacy.consentDecidedAt`, stamped by the server when they decide. An empty set WITH an
419
+ instant is "declined everything"; no instant is "never asked". A notice must not state the second
420
+ as the first.
421
+ - `analytics.requiresConsent` (default `true`) — whether the application's analytics rest on
422
+ `ANALYTICS`. It governs analytics alone, never use of the service.
423
+ - the visitor tier: a marketing website keeps a visitor's decision in their browser and starts a
424
+ consent-based provider (product analytics) only once its purpose is granted.
425
+
426
+ - `operatorComplianceIdentity.serviceConsentRequirement` (`wildo.saas.config.ts`) — what a person
427
+ must agree to in order to use the service AT ALL, and what that gate covers.
428
+
429
+ **An empty `requiredPurposes` is a POSITIVE answer and the usual one.** The operator declaring that nothing is gated on
430
+ consent has answered the question; a document must state it as settled rather than treating it as an
431
+ absence. ABSENT is the different case — nobody was asked — and the brief distinguishes the two.
432
+
433
+ **A consent GATE is not a lawful BASIS.** For most B2B SaaS the basis for core processing is CONTRACT:
434
+ a person uses the product because their employer signed for it. A notice that reads a gate as a basis
435
+ states that their data is processed on consent they could withdraw, which is wrong about the single
436
+ most consequential thing in the document. The basis is declared per purpose in `lawfulBases`.
437
+
438
+ **Completeness** — `DERIVED` for the analytics gate, each person's granted purposes, and the
439
+ service-wide requirement once declared — which the application ENFORCES: until the required purposes are
440
+ granted, the backend refuses every operation the person initiates — API and MCP operations, queued work,
441
+ WebSocket reads and subscriptions, agent tools, retrieval, charts and analytics, A2A task reads, and A2A or
442
+ WebSocket conversations, including resuming one after an approval — except their own profile and preferences,
443
+ where they record the consent, and cancelling an A2A task they already started (signing in and out stay open;
444
+ updates the server pushes on its own are not held back), and the web
445
+ application withholds its pages; `NEEDS_DECISION` naming `serviceConsentRequirement` when it is not.
446
+
447
+ This was `NEEDS_FRAMEWORK` until 2026-08-30, correctly: there was nowhere to record the answer. Issue
448
+ #139 built the surface, so the remedy changed from "someone must build this" to "fill this in" — a
449
+ different party and a different task, which is why the two states are never interchangeable.
450
+
451
+ **Say the thing readers get wrong.** Consent is one lawful basis among several, and it is not the one
452
+ most B2B processing rests on. **Never write that all processing rests on consent, and never write
453
+ that accepting terms supplies a lawful basis** — accepting a contract is a different basis with
454
+ different consequences, and conflating them is the single most common defect in a generated privacy
455
+ notice. Which basis applies is a `NEEDS_DECISION`; see the legal-basis fragment.
456
+
457
+
458
+ ### Concern: retention and deletion
459
+
460
+ **Asserts** — what happens to a record when its subject is erased, and how long records are kept.
461
+
462
+ Two questions, and the framework answers only the first.
463
+
464
+ **Derives from (the HOW — answerable)** — each resource's `retentionPolicy.mode`:
465
+ `RETAIN_AND_IMPERSONALIZE` keeps the row, freezes it, hides it from normal reads and scrubs the fields
466
+ marked `.impersonalizeWith()`; `RETAIN_ONLY` keeps and freezes a row that holds no personal data of
467
+ its own. Reading the per-field treatments tells the document exactly WHICH values are destroyed and
468
+ which survive, which is a genuinely strong statement most notices cannot make.
469
+
470
+ **Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config
471
+ over four data classes: `RESOURCE_DATA` (its records), `FILES` (uploaded bytes), `AUDIT_LOGS` (the
472
+ tamper-evident trail, kept longest and for a different reason — it is the evidence an operator may
473
+ lawfully retain under GDPR Art. 17(3)) and `OPERATIONAL_LOGS`. Each declared class carries a period in
474
+ days AND the operator's stated reason for it.
475
+
476
+ The classes are the STORES on purpose: the same declaration answers what a notice must state and what
477
+ a backup-and-restore inventory must protect (issue #8).
478
+
479
+ **The `retention-rules` fact is COMPUTED from both** — the declared periods with their reasons, the
480
+ classes with no period, each resource's declared erasure treatment, and the resources declaring none.
481
+ You never declare it. It is absent when no schedule is declared, because a treatment alone would read as
482
+ the whole answer.
483
+
484
+ **Completeness** — `DERIVED` for the treatment, and for each retention class the application HAS
485
+ declared. `NEEDS_DECISION` for each class it has not: the mechanism exists, so what is missing is an
486
+ operator's decision rather than an engine change. Do not let the derivable half hide the missing one —
487
+ a statement about erasure mechanics reads to a reader as an answer about retention, so both go in the
488
+ same breath.
489
+
490
+ **What closes it** — the operator deciding a period, and saying why. Not a framework change: issue #89
491
+ delivered the declaration surface, so an undeclared class is now an unanswered question rather than an
492
+ unaskable one.
493
+
494
+ **An UNDECLARED class is not "kept indefinitely" and not "deleted immediately".** It is a decision
495
+ nobody has taken, and the document must say exactly that.
496
+
497
+ **Never write a placeholder period.** "Typically 12 months" in a published notice is a commitment
498
+ nobody made and nothing enforces.
499
+
500
+
501
+ ### Concern: recipients and processors
502
+
503
+ **Asserts** — who else receives personal data, in what role, and where they process it.
504
+
505
+ **Derives from (partial)** — the engine capabilities the application has a provider configured for
506
+ (`EngineCapability` in `saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`).
507
+ Runtime bindings establish the configured function — email delivery, storage, payments, LLM inference
508
+ or observability. Deployment choices determine whether a third party operates that function; a
509
+ configured capability alone does not establish a third-party recipient.
510
+
511
+ **Derives from (the identities)** — the application's PROCESSOR REGISTER, which your brief renders
512
+ under *"Who else processes personal data"*. Per entry: the processor's **legal entity**, the
513
+ **regions** it processes in, and its own **subprocessors** with their regions.
514
+
515
+ **The register holds two kinds of entry and the brief labels them differently — say which.** A
516
+ CONFIGURED PROVIDER entry joins to the application's composition, so it can be checked against it: a
517
+ claim about a provider the application does not configure is detectable, and a configured provider
518
+ with no entry is reported as UNDECLARED. An AUTHORED entry — a hosting company, a CDN, a support desk
519
+ — joins to nothing, because no configuration mentions it. The framework can neither confirm it nor
520
+ notice its absence.
521
+
522
+ Both kinds of declared relationship can belong in the notice when their role is established. What
523
+ 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
524
+ as though the framework verified it overstates what anyone checked.
525
+
526
+ **A SELF-HOSTED provider is not a recipient either, and this is the second way to get the section
527
+ wrong.** The brief's *"Who RUNS each bound provider"* block splits runtime-bound providers three ways:
528
+ THIRD-PARTY RECIPIENTS (vendor-hosted, so data reaches a third party — enumerate these with their
529
+ region), OPERATOR-RUN (self-hosted, so no third party receives anything — state them as processing
530
+ under the operator's own control, never as recipients), and UNANSWERED.
531
+
532
+ An UNANSWERED provider is bound to a runtime with no declared deployment model. **Do not assume
533
+ vendor-hosted.** It looks like the cautious reading and it is not: it publishes that a person's data
534
+ goes to a third party when nobody said so. Report it as not established, and name the surface —
535
+ `providerComplianceChoices` in `wildo.saas.config.ts`.
536
+
537
+ **A provider PROFILE is not a recipient.** The brief separates providers BOUND TO A RUNTIME — backend,
538
+ companion, workers, minions, a frontend service, which can process the application's data — from
539
+ provider profiles with no runtime binding. A profile says how to reach a provider; build-time tooling
540
+ lives there, and a coding agent operating on the workspace receives no customer records. Never name a
541
+ profile-only provider as a recipient. Naming one reads as caution and is a false statement about
542
+ somebody's data, exactly like omitting a real one.
543
+
544
+ The section joins the register to runtime-bound RECIPIENT CANDIDATES after excluding explicit
545
+ self-hosted providers, so it tells you three different things
546
+ and they are not interchangeable:
547
+
548
+ - a candidate WITH an entry — its declared identity and regions are available. Establish its
549
+ deployment role before presenting it as a recipient.
550
+ - a candidate listed **UNDECLARED** — a runtime binding has no matching processor entry. Name its
551
+ configured function and unresolved declarations; an unanswered deployment choice remains unknown,
552
+ not automatically vendor-hosted. `NEEDS_DECISION`, resolved by the operator.
553
+ - a provider entry listed **STALE** — it no longer matches the current recipient-candidate set.
554
+ Reconcile the declaration and deployment choice; this check alone does not establish its actual
555
+ historical processing or that all external data has been removed.
556
+
557
+ **Completeness** — `DERIVED` per provider that is declared, `NEEDS_DECISION` per provider that is not.
558
+ Not `NEEDS_FRAMEWORK` any more: issue #88 delivered the declaration surface, so an undeclared processor
559
+ is an unanswered question rather than an unaskable one.
560
+
561
+ **Never infer a region from a vendor's brand.** "It is a US company" is not a processing location, and
562
+ a transfer statement built on it is a claim about somebody's data made from a guess.
563
+
564
+ **Distinguish the register declaration from its reconciliation.**
565
+
566
+ | Observed state | What it establishes | What the document may say |
567
+ | --- | --- | --- |
568
+ | Register absent | No processor declaration was supplied | The operator has not established the register; do not infer recipients or their absence |
569
+ | 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 |
570
+ | 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 |
571
+
572
+ Reconcile only runtime-bound candidates. Exclude explicitly SELF_HOSTED providers and profile-only
573
+ providers; keep unanswered deployment choices visible as unanswered. `registerEstablishesNoProcessorRecipients`
574
+ answers the declaration question; `undeclaredProcessorRefs` answers candidate coverage. A true answer to
575
+ the first does not erase gaps returned by the second.
576
+
577
+ Name third-party recipients only when their role is established. An empty register does not justify
578
+ an unconditional statement that third parties provide email, storage or payments. Equally, do not
579
+ omit unresolved candidate questions and thereby imply that absence was verified. Authored recipients
580
+ remain operator declarations whose completeness cannot be inferred from runtime bindings.
581
+
582
+
583
+ ### Concern: international transfers
584
+
585
+ **Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer
586
+ mechanism.
587
+
588
+ **Derives from** — the processor register's regions, at BOTH levels: each declared processor and
589
+ each processor's own subprocessors. Your brief renders them under *"Personal data reaches processors
590
+ in: …"*.
591
+
592
+ Both levels, because the chain is what makes a transfer statement hard. An operator in France using a
593
+ French vendor that runs on a US cloud HAS a transfer, and reading only the vendor's region misses it.
594
+
595
+ **The question has three inputs, and the framework derives only one of them.** Where declared
596
+ processors process is declared. Which jurisdiction is the ORIGIN is `operatingJurisdictions`. Which
597
+ MECHANISM makes a given transfer lawful is a legal determination with a shelf life — adequacy decisions
598
+ move by court ruling — so the framework never computes it: the operator RECORDS it, per register entry,
599
+ as a `transferDetermination`:
600
+
601
+ - `NO_TRANSFER`, with the reason none of the entry's regions lies outside the origin jurisdictions —
602
+ regions are free text, so this comparison is the operator's and never the framework's;
603
+ - `TRANSFER`, with one safeguard per origin jurisdiction: the GDPR Chapter V mechanism
604
+ (`ADEQUACY_DECISION`, `STANDARD_CONTRACTUAL_CLAUSES`, `BINDING_CORPORATE_RULES`,
605
+ `APPROVED_CODE_OF_CONDUCT`, `APPROVED_CERTIFICATION`, or a `DEROGATION` naming its Art. 49 ground) and
606
+ the instrument a reader could look up.
607
+
608
+ The determination sits on the ENTRY because the processor's own contract binds its onward transfers to
609
+ its subprocessors; reaching the processor is the transfer the operator answers for.
610
+
611
+ **The `international-transfers` fact is COMPUTED from those determinations** — you never declare it.
612
+ It carries each determined entry, the origin jurisdictions, `undeterminedRecipients` — a register entry
613
+ with no determination, or a configured provider the register does not establish — and `safeguardGaps`:
614
+ a declared origin a TRANSFER names no safeguard for.
615
+
616
+ **Completeness** — do not round any state up.
617
+
618
+ | the register | what you may state | completeness |
619
+ |---|---|---|
620
+ | ABSENT | nothing — where data lands is unknown, and the fact is absent | `NEEDS_CONFIGURATION` |
621
+ | a recipient in `undeterminedRecipients` | that its transfer position is not determined; never fold it into "no transfer" | `NEEDS_DECISION` for that recipient |
622
+ | declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |
623
+ | 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 |
624
+
625
+ **The residual is not optional wording.** "No processor receives personal data" establishes nothing
626
+ about the operator's OWN processing — its infrastructure, its staff, its own establishment. A document
627
+ that says "we do not transfer data internationally" on the strength of an empty register has answered
628
+ a larger question than it was asked.
629
+
630
+ **What closes an undetermined entry** — the operator researching the vendor's data processing
631
+ agreement and recording what it relies on, per origin jurisdiction. A vendor's DPA usually names it:
632
+ standard contractual clauses for EU data, the UK Addendum to them for UK data, and sometimes a
633
+ certification under an adequacy framework beside them. Record what the contract says, not what is
634
+ typical.
635
+
636
+ **"We do not transfer data internationally" is a claim, not a default.** It may be true, and it is
637
+ citable when an application has declared it as a fact — but it must never be produced because nothing
638
+ said otherwise. Absence of a region declaration means the region is unknown, which is the opposite of
639
+ knowing it stays put.
640
+
641
+
642
+ ### Concern: automated decisions and AI
643
+
644
+ **Asserts** — where the application uses AI, on what data, and whether any of it decides something
645
+ about a person.
646
+
647
+ **Derives from (partial)** — the AI capabilities the application has a provider configured for:
648
+ `AI_LLM`, `AI_EMBEDDINGS`, `AI_DOCUMENT_EXTRACTION`, `AI_CODING_AGENT`. That establishes that AI is in
649
+ use and for what function.
650
+
651
+ **Not derivable** — whether any of it produces a **decision with a legal or similarly significant
652
+ effect** on a person, and whether a human reviews it. Nothing in the framework declares consequence or
653
+ human-review posture, and neither can be inferred from a capability being enabled.
654
+
655
+ **Derives from (the consequence)** — the AI POSTURE section of your brief, per ENABLED AI capability:
656
+ what it is used for, whether it `NO_DECISION` / `ASSISTS_HUMAN_DECISION` / `DECIDES_AUTONOMOUSLY`, and —
657
+ where it decides anything — how a person obtains human intervention.
658
+
659
+ An application enabling NO AI capability gets a plain statement to that effect: it performs no AI
660
+ processing of personal data. That is a positive, checkable answer, not a gap.
661
+
662
+ **Completeness** — `DERIVED` per capability with a declared posture; `NEEDS_DECISION` per capability
663
+ listed OUTSTANDING. Not `NEEDS_FRAMEWORK` any more: issue #92 delivered the declaration, so an
664
+ undeclared posture is an unanswered question rather than an unaskable one.
665
+
666
+ **An OUTSTANDING capability is not a harmless one.** This is the one concern where silence is more
667
+ dangerous than elsewhere: a notice describing AI use and saying nothing about consequence does not read
668
+ as "unknown", it reads as "nothing significant happens here" — which is the exemption, claimed for
669
+ free. State the gap explicitly.
670
+
671
+ **Why the distinction carries weight.** Automated decision-making with significant effects attracts
672
+ specific obligations — information about the logic, and a right to human intervention. A generated
673
+ notice must not silently claim the exemption by describing AI use without addressing consequence. The
674
+ honest statement says AI is used for these functions, and that whether any of it decides something
675
+ about a person is not yet established.
676
+
677
+
678
+ ### Concern: analytics and tracking
679
+
680
+ **Asserts** — what is observed about how people use the service, and what a person's consent controls.
681
+
682
+ **Derives from (partial)** — the observability and analytics capabilities the application has
683
+ configured (`FRONTEND_PRODUCT_ANALYTICS`, `LLM_OBSERVABILITY`, `OBSERVABILITY_TELEMETRY`), together
684
+ with the consent posture: `analytics.requiresConsent` and each person's `privacy.consentedPurposes` make
685
+ `ConsentPurpose.ANALYTICS` a real, enforced boundary rather than a stated intention — in the application,
686
+ and on the marketing website, where a product-analytics provider does not start until a visitor grants it.
687
+
688
+ **Derives from (the inventory)** — the CLIENT STORAGE section of your brief: each cookie and storage
689
+ key, its mechanism, purpose, necessity and lifetime, split by who sets it.
690
+
691
+ The FRAMEWORK's own entries are listed first and belong in every application's table — the cookies
692
+ `__wildo_refresh` and `__wildo_anon_session`, strictly necessary, with lifetimes taken from the
693
+ application's session configuration, and the website's `__wildo_website_consent` storage key, strictly
694
+ necessary because it is what makes a visitor's refusal hold. **No application authored these and every application sets them**, so a table
695
+ built only from what the application declared would omit the session cookie, which is the entry a
696
+ visitor is most certain to have.
697
+
698
+ Then, per frontend surface: its declared entries, an explicit "sets nothing of its own", or
699
+ UNINVENTORIED.
700
+
701
+ **UNINVENTORIED is not "sets nothing".** The first says nobody catalogued that surface; the second is a
702
+ positive statement. Writing the second from the first tells a visitor they are tracked by less than they
703
+ are, which is the under-reporting direction a notice must never fail in.
704
+
705
+ **Completeness** — `DERIVED` for the capability and consent posture, and for each surface that IS
706
+ inventoried; `NEEDS_DECISION` per uninventoried surface. Not `NEEDS_FRAMEWORK` any more: issue #91
707
+ delivered the declaration surface, so an uninventoried surface is an unanswered question rather than an
708
+ unaskable one.
709
+
710
+ Say both halves: which analytics are in use and what consent gates them (strong, derived, enforced), and
711
+ what the table still lacks — naming the surfaces, not the concern.
712
+
713
+
714
+ ### Concern: subject rights
715
+
716
+ **Asserts** — which request mechanisms the application configures, what they select and what their
717
+ results establish. A configured mechanism does not establish that a particular request was fulfilled.
718
+
719
+ **Derives from**
720
+
721
+ - `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20` — two selections over the declared
722
+ subject relationships. Access includes eligible owned rows and non-owned rows referring to the
723
+ subject. Portability applies narrower relationship and field-provenance selection. Neither is an
724
+ unrestricted recursive export of everything reachable from an account.
725
+ - Each participating resource's `systemAccessPolicy.exportSubject` — an explicit disclosure choice,
726
+ checked before collection. Missing and forbidden are different decisions:
727
+
728
+ | Declaration | Runtime result | Meaning for the request |
729
+ | --- | --- | --- |
730
+ | Absent on a participating resource | Refuses collection | A required disclosure decision is unanswered; no silently incomplete bundle is returned |
731
+ | `ALLOWED` | Passes this disclosure gate | Relationship selection, system-read admission, field security and purpose-specific checks still apply |
732
+ | `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 |
733
+ | `FORBIDDEN` on the subject's own resource | Refuses the bundle | The subject cannot be omitted from its own export |
734
+
735
+ - `portabilityPolicy.defaultProvenance` and per-field `.portabilityProvenance(...)` — the field
736
+ declaration overrides the resource default. `SUBJECT_PROVIDED` and `OBSERVED` values are eligible
737
+ for portability; `DERIVED` values are excluded and reported. Unresolved provenance refuses
738
+ portability collection rather than silently dropping fields. Explicitly forbidden resources do
739
+ not need portability provenance for this export because their rows are not collected. Access uses
740
+ its separate field selection; backend-only and write-only fields remain withheld.
741
+ - Erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, invoked by the application's verified request
742
+ workflow. A contact or lead without a login can still be a data subject. Retention, relationship
743
+ treatments and account linkage are separate declarations; inspect the receipt before claiming
744
+ completion, including dependent execution, session resolution and incomplete external effects.
745
+
746
+ **The rights a notice states are COMPUTED, in the `rights-and-complaint-route` fact.** Which rights
747
+ apply, and where a person may complain, are the law of the regime each `operatingJurisdictions` entry
748
+ falls under, conditioned on the declared lawful bases: portability only for purposes resting on consent
749
+ or contract, objection only for public task or legitimate interests, withdrawal of consent only where
750
+ consent is the basis. The channel is `privacyContact`; the verification step is the operator's
751
+ `subjectRequestIdentityVerification`; who answers comes from `roleAllocations` — the operator for data it
752
+ controls, the customer (with the operator forwarding and assisting) for data it processes on a
753
+ customer's behalf. A jurisdiction no known regime reaches is named in `jurisdictionsWithoutKnownRegime`:
754
+ state that its rights are not established here, never borrow another regime's words for it.
755
+
756
+ **Completeness** — derive the configured posture from actual resource declarations and the selected
757
+ relationships. Describe an unresolved declaration as a configuration refusal, an explicit exclusion
758
+ as an exclusion, and an observed request outcome from its report. Declarations alone are not runtime
759
+ proof that a right has been fulfilled.
760
+
761
+ **What resolves a missing declaration** — the owning resource explicitly declares ALLOWED or FORBIDDEN
762
+ according to its intended disclosure policy. Portability additionally needs a valid resource default
763
+ or field-level provenance for the fields it would collect. Do not ask a notice author to replace a
764
+ missing product declaration with a free-text promise.
765
+
766
+ **Never state** that an undeclared participating resource is merely omitted while the remainder is
767
+ exported. The runtime refuses collection. Preserve deliberate exclusions and explain their recorded
768
+ reasons; the application's request workflow owns verification, protected delivery and any necessary
769
+ follow-up.
770
+
771
+
772
+ ### Concern: data exit
773
+
774
+ **Asserts** — what a customer gets back when they leave, in what form, and what happens to what
775
+ remains.
776
+
777
+ **Derives from** — `SubjectExportPurpose.PORTABILITY_ART_20` and the resources declaring
778
+ `exportSubject`; the account-closure path; and each resource's `retentionPolicy.mode`, which decides
779
+ whether a record is removed or **retained and impersonalized** on erasure.
780
+
781
+ **Completeness** — `DERIVED` for the mechanism.
782
+
783
+ **Retained-and-impersonalized is the part a reader must not be surprised by**, and the part a
784
+ generated document most often gets wrong by omission. A retained row is kept, frozen, hidden from
785
+ normal reads and reachable only through an audited privileged path — it is not deleted. Say so. A
786
+ notice that implies everything is erased, when financial and audit records are lawfully retained with
787
+ their personal fields scrubbed, is inaccurate in the direction that damages trust when discovered.
788
+
789
+ **How LONG anything is retained is not derivable** — see the retention-and-deletion fragment.
790
+
791
+
792
+ ### Concern: tenancy model
793
+
794
+ **Asserts** — that customer data is separated per organization, and where the boundary between the
795
+ operator's responsibilities and the customer's lies.
796
+
797
+ **Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every
798
+ tenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be
799
+ declared and carry a usable access grant. The application audit viewer is a separate policy surface:
800
+ it defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with
801
+ `auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under
802
+ which a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
803
+ role-based access neither implies anonymized records nor supplies an approval that never occurred.
804
+
805
+ **Completeness** — `DERIVED`.
806
+
807
+ **This fragment is where shared responsibility is described, and it must never be flattened.** In a
808
+ B2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a
809
+ CONTROLLER for the data it holds about the customer's users as account holders. Those are different
810
+ roles with different duties over the same database. Say which is which; do not pick one and apply it
811
+ to everything.
812
+
813
+ **The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
814
+ `wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
815
+ stores about its own people, CONTROLLER for the account data of the people who administer them. It is
816
+ a LIST for exactly the reason this fragment gives: those are different roles over the same database,
817
+ and a single field would force one of them to be wrong.
818
+
819
+ Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
820
+ surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
821
+ so the remedy is to fill it in rather than to build something. See the legal-basis fragment.
822
+
823
+
824
+ ## `document:public.service-terms` — six concerns
825
+
826
+ ### Concern: service scope
827
+
828
+ **Asserts** — what the service actually is: the modules it runs, the resources it manages, and the
829
+ surfaces it exposes.
830
+
831
+ **Derives from** — the application's declared modules and their resources, and the surfaces it builds
832
+ (application, API, public website, technical documentation).
833
+
834
+ **Completeness** — `DERIVED`.
835
+
836
+ **Derive it; do not describe the product from its marketing.** Scope in a governed document is the
837
+ boundary of what the statements around it apply to, so an aspirational description silently widens
838
+ every other clause. The declared modules are the honest boundary, and a capability the application
839
+ does not run does not belong here even if it is on the roadmap.
840
+
841
+
842
+ ### Concern: commercial terms
843
+
844
+ **Asserts** — what is sold, how it is charged, and what happens on renewal, change and cancellation.
845
+
846
+ **Derives from** — the application's billing declarations
847
+ (`saas-models` → `billing/billing-enums.shared.schemas.ts`): `ProductType`, `BillingTiming`,
848
+ `ProrationBehavior`, `TaxCalculationMode`, plus the declared products and any usage metering.
849
+
850
+ **Completeness** — `DERIVED` where billing is configured; `NEEDS_CONFIGURATION` where the application
851
+ declares no products, in which case say that the commercial terms are not yet established rather than
852
+ describing a plan nobody has authored.
853
+
854
+ **Keep consumer and business audiences apart.** Consumer pre-contract obligations (withdrawal
855
+ periods, pre-contractual information) apply only when a declared audience includes consumers. A terms
856
+ document that blends both into one ambiguous set is worse than one that states which audience it is
857
+ for — so read the declared audience before writing a single clause about cancellation rights.
858
+
859
+
860
+ ### Concern: governing law and liability
861
+
862
+ **Asserts** — which law governs the agreement, where disputes are heard, and how liability is limited.
863
+
864
+ **Derives from** — nothing. These are negotiated commercial and legal positions.
865
+
866
+ **Completeness** — `NEEDS_DECISION`.
867
+
868
+ **What closes it** — the operator deciding, with counsel. Note that liability limits interact with
869
+ the declared audience: consumer-facing terms cannot limit liability as freely as business-to-business
870
+ ones, so this fragment cannot be settled before the commercial-terms fragment establishes who the
871
+ terms are for.
872
+
873
+ **Never produce a liability clause from a template.** A limitation of liability that was copied
874
+ rather than decided is either unenforceable or committing the operator to something nobody agreed —
875
+ and unlike most gaps in a produced document, this one is not discovered until it matters.