@wildo-ai/framework-knowledge 1.1.4 → 1.1.6

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 (1167) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +14 -0
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
  3. package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
  4. package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
  5. package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
  7. package/dist/claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md +110 -0
  8. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
  9. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
  10. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +46 -0
  11. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
  12. package/dist/claude-marketplace/plugins/wildo/references/specification-family-map.md +88 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
  14. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
  15. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
  17. package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
  18. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
  19. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
  20. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
  21. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
  22. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  23. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  24. package/dist/esm/framework-knowledge.definitions.js +547 -17
  25. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  26. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  27. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  28. package/dist/esm/framework-knowledge.loader.js +47 -1
  29. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  30. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  31. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  32. package/dist/esm/index.d.ts.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  34. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -4
  36. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +135 -0
  38. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  39. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +208 -0
  40. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  41. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +218 -9
  42. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  43. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +374 -11
  44. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  45. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +6 -4
  46. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  47. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +22 -20
  48. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  49. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  50. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  51. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -6
  52. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  53. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  54. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  55. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +62 -0
  56. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  57. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  58. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  59. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +188 -0
  60. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  61. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +74 -0
  62. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  63. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +80 -0
  64. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  65. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  66. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +18 -8
  68. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  69. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  70. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  71. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +81 -0
  72. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  73. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +31 -11
  74. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  75. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +132 -10
  76. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  77. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +68 -0
  78. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  79. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +84 -0
  80. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  81. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  82. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  83. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +69 -0
  84. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  85. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +2 -2
  86. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
  88. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  89. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +78 -0
  90. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  91. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +93 -0
  92. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  93. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +104 -0
  94. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  95. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +184 -0
  96. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  97. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  98. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  99. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  100. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  101. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
  102. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
  103. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
  104. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
  105. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
  106. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
  107. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
  108. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -0
  109. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  110. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  111. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  112. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  113. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +172 -2
  114. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  115. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +147 -2
  116. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  117. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
  118. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
  119. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
  120. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
  121. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  122. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  123. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  124. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  125. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +158 -5
  126. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  127. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +173 -5
  128. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  129. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +6 -5
  130. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  131. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +9 -8
  132. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  133. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  134. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  135. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +23 -4
  136. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  137. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +6 -4
  138. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  139. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +22 -13
  140. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  141. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +193 -28
  142. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  143. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +173 -34
  144. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  145. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +3 -2
  146. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +7 -3
  148. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  149. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +183 -6
  150. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  151. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +192 -6
  152. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  153. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +3 -2
  154. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  155. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +4 -3
  156. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  157. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +173 -0
  158. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  159. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +264 -0
  160. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  161. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  162. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  163. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  164. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  165. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +45 -0
  166. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
  167. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
  168. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -0
  169. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  170. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  171. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +3 -2
  172. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  173. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  174. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  175. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +7 -3
  176. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  177. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  178. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  179. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +3 -2
  180. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  181. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  182. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  183. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -4
  184. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  185. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +33 -5
  186. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  187. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +28 -4
  188. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  189. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -3
  190. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  191. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +5 -3
  192. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  193. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  194. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  195. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  196. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  197. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +6 -4
  198. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  199. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +19 -5
  200. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  201. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +156 -5
  202. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  203. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -5
  204. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  205. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +7 -6
  206. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  207. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +28 -19
  208. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  209. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  210. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  211. package/dist/knowledge/manifest.json +9 -8
  212. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  213. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +40 -0
  214. package/dist/knowledge/playbooks/bottom_up.build/method.md +81 -0
  215. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +89 -0
  216. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  217. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  218. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1234 -80
  219. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +53 -14
  220. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  221. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  222. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +743 -64
  223. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -21
  224. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +34 -49
  225. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -21
  226. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +93 -0
  227. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +61 -0
  228. package/dist/knowledge/playbooks/bottom_up.conception/method.md +98 -0
  229. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +98 -0
  230. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +109 -0
  231. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +77 -0
  232. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +9 -11
  233. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +16 -16
  234. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +181 -0
  235. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +73 -0
  236. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +222 -145
  237. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +60 -24
  238. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +152 -0
  239. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  240. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  241. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +67 -0
  242. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  243. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +62 -0
  244. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +117 -0
  245. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +86 -0
  246. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  247. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +92 -0
  248. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  249. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +65 -0
  250. package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
  251. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
  252. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
  253. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -0
  254. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  255. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  256. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +964 -15
  257. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  258. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  259. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  260. package/dist/knowledge/playbooks/refinement.document-facts/method.md +191 -21
  261. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -18
  262. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
  263. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
  264. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  265. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  266. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +349 -0
  267. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  268. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  269. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  270. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +24 -11
  271. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -18
  272. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +9 -18
  273. package/dist/knowledge/playbooks/top_down.capability-map/method.md +26 -52
  274. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -18
  275. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  276. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +99 -0
  277. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  278. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  279. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +211 -0
  280. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +66 -0
  281. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  282. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +40 -0
  283. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  284. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  285. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +37 -14
  286. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +19 -69
  287. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  288. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +41 -0
  289. package/dist/knowledge/playbooks/top_down.definition/method.md +106 -0
  290. package/dist/knowledge/playbooks/top_down.definition/playbook.json +120 -0
  291. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  292. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +46 -0
  293. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
  294. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
  295. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  296. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -45
  297. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  298. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +42 -0
  299. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  300. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +44 -0
  301. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  302. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  303. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +245 -0
  304. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +70 -0
  305. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  306. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  307. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  308. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -13
  309. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +28 -8
  310. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -19
  311. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  312. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  313. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  314. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +57 -0
  315. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +25 -10
  316. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -20
  317. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  318. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  319. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +24 -17
  320. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -18
  321. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +12 -4
  322. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +23 -20
  323. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  324. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  325. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  326. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  327. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  328. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  329. package/dist/knowledge/references/application-maturity.config.md +319 -0
  330. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  331. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  332. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +212 -0
  333. package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
  334. package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
  335. package/dist/knowledge/references/brand.asset.config.md +8 -16
  336. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  337. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  338. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  339. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  340. package/dist/knowledge/references/build-plan.task-graph.config.md +649 -10
  341. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  342. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  343. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  344. package/dist/knowledge/references/capability-composition.config.md +174 -0
  345. package/dist/knowledge/references/cli.market.generate-command.md +18 -2
  346. package/dist/knowledge/references/cli.market.utils.md +1 -0
  347. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  348. package/dist/knowledge/references/engine.client-bundle.allow-list.md +28 -22
  349. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  350. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  351. package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
  352. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  353. package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
  354. package/dist/knowledge/references/example.backend.addon-wiring.module.md +13 -12
  355. package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
  356. package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
  357. package/dist/knowledge/references/example.config.app-shell.full.md +53 -7
  358. package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
  359. package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
  360. package/dist/knowledge/references/example.config.backend.required-floors.md +11 -0
  361. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  362. package/dist/knowledge/references/example.config.navigation.full.md +45 -2
  363. package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
  364. package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
  365. package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -0
  366. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  367. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  368. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  369. package/dist/knowledge/references/example.flows-actors.autonomous-agent.md +23 -0
  370. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
  371. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +30 -6
  372. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +7 -11
  373. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  374. package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
  375. package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
  376. package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
  377. package/dist/knowledge/references/example.infra.environment-config.local.md +104 -43
  378. package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
  379. package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
  380. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  381. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  382. package/dist/knowledge/references/example.module.companion-exports.full.md +46 -16
  383. package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
  384. package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
  385. package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
  386. package/dist/knowledge/references/example.provider.backend-module-shape.md +34 -13
  387. package/dist/knowledge/references/example.provider.frontend-app.module.md +112 -0
  388. package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
  389. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +34 -13
  390. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +25 -3
  391. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  392. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +16 -0
  393. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +5 -0
  394. package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
  395. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
  396. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +112 -10
  397. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +90 -0
  398. package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
  399. package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
  400. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  401. package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
  402. package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
  403. package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
  404. package/dist/knowledge/references/example.website.page.manifest.md +30 -0
  405. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  406. package/dist/knowledge/references/experience-plan.config.md +318 -0
  407. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +152 -9
  408. package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
  409. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  410. package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
  411. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
  412. package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
  413. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
  414. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
  415. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
  416. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +290 -0
  417. package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
  418. package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
  419. package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
  420. package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
  421. package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
  422. package/dist/knowledge/references/integration-plan.config.md +217 -0
  423. package/dist/knowledge/references/market.alternative.config.md +2 -2
  424. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  425. package/dist/knowledge/references/market.buying-journey.config.md +1 -1
  426. package/dist/knowledge/references/market.category.config.md +1 -1
  427. package/dist/knowledge/references/market.channel.config.md +4 -4
  428. package/dist/knowledge/references/market.feature-benefit.config.md +2 -2
  429. package/dist/knowledge/references/market.gain.config.md +2 -2
  430. package/dist/knowledge/references/market.icp.config.md +3 -3
  431. package/dist/knowledge/references/market.job.config.md +2 -2
  432. package/dist/knowledge/references/market.message-template.config.md +3 -3
  433. package/dist/knowledge/references/market.objection.config.md +2 -2
  434. package/dist/knowledge/references/market.pain.config.md +2 -2
  435. package/dist/knowledge/references/market.persona.config.md +3 -3
  436. package/dist/knowledge/references/market.positioning.config.md +1 -1
  437. package/dist/knowledge/references/market.proof.config.md +2 -2
  438. package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
  439. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  440. package/dist/knowledge/references/market.tone-of-voice.config.md +2 -2
  441. package/dist/knowledge/references/market.trigger.config.md +2 -2
  442. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  443. package/dist/knowledge/references/placement-plan.config.md +375 -0
  444. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  445. package/dist/knowledge/references/platform.config.backing-services.md +15 -36
  446. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  447. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  448. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  449. package/dist/knowledge/references/platform.config.saas.md +261 -9
  450. package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
  451. package/dist/knowledge/references/presets.3d.layout-contract.md +213 -0
  452. package/dist/knowledge/references/presets.3d.register-layout.md +95 -0
  453. package/dist/knowledge/references/presets.models.labelling.sections.md +19 -0
  454. package/dist/knowledge/references/presets.models.shell-region.md +47 -0
  455. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  456. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  457. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
  458. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  459. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  460. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  461. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  462. package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
  463. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  464. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
  465. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  466. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +87 -0
  467. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  468. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  469. package/dist/knowledge/references/saas.backend.compliance.governed-documents-pdf-template.md +370 -0
  470. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +194 -0
  471. package/dist/knowledge/references/saas.backend.domain-module.md +118 -16
  472. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  473. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
  474. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
  475. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +206 -0
  476. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  477. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +19 -4
  478. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  479. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  480. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +73 -0
  481. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +224 -0
  482. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  483. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  484. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  485. package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
  486. package/dist/knowledge/references/saas.backend.system-access-service.md +148 -41
  487. package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
  488. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  489. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  490. package/dist/knowledge/references/saas.config.providers.augmentations.md +61 -0
  491. package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
  492. package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -0
  493. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  494. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  495. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +56 -2
  496. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  497. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  498. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  499. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +43 -13
  500. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  501. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +250 -0
  502. package/dist/knowledge/references/saas.frontend.billing-context.md +131 -0
  503. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  504. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  505. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
  506. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  507. package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
  508. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  509. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  510. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  511. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  512. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  513. package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
  514. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  515. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  516. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
  517. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +47 -0
  518. package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
  519. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  520. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +80 -0
  521. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  522. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
  523. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
  524. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  525. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +136 -1
  526. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +422 -11
  527. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
  528. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +259 -0
  529. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  530. package/dist/knowledge/references/saas.market.generation-agent.md +26 -10
  531. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
  532. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
  533. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
  534. package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
  535. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
  536. package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
  537. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  538. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
  539. package/dist/knowledge/references/saas.models.audit.trail-config.md +161 -0
  540. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  541. package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
  542. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +90 -0
  543. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +130 -0
  544. package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
  545. package/dist/knowledge/references/saas.models.config.organization-types.md +266 -0
  546. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  547. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +98 -0
  548. package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
  549. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  550. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  551. package/dist/knowledge/references/saas.models.engine-capabilities.md +97 -7
  552. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +65 -0
  553. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
  554. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
  555. package/dist/knowledge/references/saas.models.external-data-pipeline.md +710 -10
  556. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  557. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  558. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  559. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +98 -0
  560. package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
  561. package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
  562. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
  563. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
  564. package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
  565. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  566. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  567. package/dist/knowledge/references/saas.models.http-api-binding.md +884 -135
  568. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
  569. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
  570. package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
  571. package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
  572. package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
  573. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  574. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  575. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +28 -0
  576. package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
  577. package/dist/knowledge/references/saas.models.navigation.layout.md +13 -9
  578. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +133 -0
  579. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +103 -0
  580. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +152 -0
  581. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +84 -0
  582. package/dist/knowledge/references/saas.models.notifications.targets.md +146 -0
  583. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +283 -0
  584. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  585. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  586. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +59 -0
  587. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  588. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
  589. package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
  590. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
  591. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
  592. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  593. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
  594. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
  595. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  596. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
  597. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
  598. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
  599. package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
  600. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
  601. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  602. package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
  603. package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
  604. package/dist/knowledge/references/saas.models.provider-capabilities.md +42 -5
  605. package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
  606. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
  607. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +133 -0
  608. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  609. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  610. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +196 -0
  611. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
  612. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  613. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  614. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  615. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +244 -32
  616. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  617. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  618. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  619. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  620. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  621. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  622. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  623. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  624. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  625. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  626. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
  627. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  628. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  629. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  630. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  631. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +16 -0
  632. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +22 -0
  633. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -0
  634. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  635. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  636. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  637. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  638. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  639. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  640. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  641. package/dist/knowledge/references/saas.models.system-of-record-actions.md +226 -0
  642. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
  643. package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
  644. package/dist/knowledge/references/saas.models.systems-of-record.md +870 -0
  645. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
  646. package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
  647. package/dist/knowledge/references/saas.public-runtime.contract.md +268 -3
  648. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  649. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  650. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  651. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  652. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  653. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  654. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  655. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +108 -7
  656. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +880 -66
  657. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
  658. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
  659. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
  660. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
  661. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
  662. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +217 -18
  663. package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
  664. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  665. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +376 -0
  666. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  667. package/dist/knowledge/references/saas.specifications.processor-register.md +410 -0
  668. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
  669. package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
  670. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +120 -45
  671. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +35 -1
  672. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
  673. package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
  674. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
  675. package/dist/knowledge/references/saas.website.astro.bridge.md +92 -7
  676. package/dist/knowledge/references/saas.website.astro.head-renderer.md +33 -13
  677. package/dist/knowledge/references/saas.website.astro.label-loader.md +10 -4
  678. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +29 -16
  679. package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
  680. package/dist/knowledge/references/saas.website.blog.bridge.md +34 -1
  681. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
  682. package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
  683. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  684. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  685. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  686. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -4
  687. package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
  688. package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
  689. package/dist/knowledge/references/saas.website.page-layout.component.md +70 -1
  690. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  691. package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
  692. package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
  693. package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
  694. package/dist/knowledge/references/saas.website.runtime.context.md +66 -11
  695. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  696. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  697. package/dist/knowledge/references/saas.website.sections.definition-schema.md +14 -7
  698. package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
  699. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
  700. package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
  701. package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
  702. package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
  703. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  704. package/dist/knowledge/references/website-plan.config.md +238 -0
  705. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  706. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  707. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  708. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +53 -5
  709. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +75 -1
  710. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +36 -2
  711. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  712. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  713. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  714. package/dist/knowledge/references/zod.decorators.file-schema.md +95 -18
  715. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +87 -0
  716. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +148 -6
  717. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  718. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  719. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  720. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  721. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +50 -12
  722. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +35 -12
  723. package/dist/knowledge/references/zod.factories.address.md +118 -0
  724. package/dist/knowledge/references/zod.factories.code.md +4 -2
  725. package/dist/knowledge/references/zod.factories.duration.md +6 -4
  726. package/dist/knowledge/references/zod.factories.money.md +5 -3
  727. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  728. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  729. package/dist/knowledge/registries/framework-topics.json +2602 -214
  730. package/dist/knowledge/registries/playbooks.json +468 -92
  731. package/dist/knowledge/registries/source-tags.json +6171 -1996
  732. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  733. package/dist/knowledge/rules/live-context-door.md +137 -0
  734. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  735. package/dist/knowledge/skills/INDEX.md +67 -29
  736. package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
  737. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
  738. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
  739. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
  740. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
  741. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
  742. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
  743. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
  744. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
  745. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +111 -37
  746. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  747. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  748. package/dist/knowledge/skills/application-database-migrations/SKILL.md +11 -3
  749. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  750. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  751. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +95 -3
  752. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +59 -0
  753. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +32 -19
  754. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +119 -17
  755. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  756. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +96 -20
  757. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  758. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  759. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  760. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +214 -0
  761. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +39 -1
  762. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  763. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  764. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +162 -8
  765. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  766. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +518 -132
  767. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  768. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  769. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  770. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +162 -26
  771. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +734 -23
  772. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +436 -0
  773. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +221 -0
  774. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
  775. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
  776. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
  777. package/dist/knowledge/skills/config-app-shell/SKILL.md +95 -11
  778. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +87 -21
  779. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +276 -0
  780. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  781. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  782. package/dist/knowledge/skills/config-app-shell/references/framework-shell-region-markers-api.md +66 -0
  783. package/dist/knowledge/skills/config-design-system/SKILL.md +44 -3
  784. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  785. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  786. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  787. package/dist/knowledge/skills/config-navigation/SKILL.md +200 -19
  788. package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
  789. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  790. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +13 -9
  791. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +78 -0
  792. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +245 -0
  793. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +174 -0
  794. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +253 -0
  795. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  796. package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
  797. package/dist/knowledge/skills/config-saas/SKILL.md +88 -9
  798. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +206 -0
  799. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +189 -0
  800. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  801. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +157 -0
  802. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +292 -0
  803. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  804. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +139 -12
  805. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +1024 -0
  806. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  807. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  808. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  809. package/dist/knowledge/skills/config-saas-backend/SKILL.md +66 -3
  810. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  811. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  812. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  813. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  814. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +397 -0
  815. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  816. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +143 -0
  817. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  818. package/dist/knowledge/skills/configure-billing/SKILL.md +91 -46
  819. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +62 -17
  820. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +55 -0
  821. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +39 -17
  822. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  823. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +192 -0
  824. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  825. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +259 -0
  826. package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
  827. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +91 -0
  828. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +289 -0
  829. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +192 -0
  830. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  831. package/dist/knowledge/skills/email-add-template/SKILL.md +100 -91
  832. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  833. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +123 -0
  834. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
  835. package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
  836. package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
  837. package/dist/knowledge/skills/engine-component-registration/SKILL.md +20 -12
  838. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +60 -31
  839. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  840. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  841. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  842. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  843. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +60 -27
  844. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  845. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  846. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +180 -0
  847. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
  848. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
  849. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
  850. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
  851. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +41 -12
  852. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +31 -7
  853. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
  854. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
  855. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +248 -9
  856. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +127 -22
  857. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +236 -0
  858. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +8 -11
  859. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  860. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  861. package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
  862. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +259 -0
  863. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  864. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3988 -0
  865. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +212 -0
  866. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  867. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  868. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  869. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  870. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +14 -1
  871. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +19 -0
  872. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
  873. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +19 -0
  874. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +11 -2
  875. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +19 -0
  876. package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
  877. package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
  878. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
  879. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
  880. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
  881. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
  882. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
  883. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
  884. package/dist/knowledge/skills/infra-environment-config/SKILL.md +387 -81
  885. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  886. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +198 -36
  887. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  888. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  889. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +176 -0
  890. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
  891. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +223 -0
  892. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +103 -0
  893. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +256 -0
  894. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
  895. package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +29 -0
  896. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
  897. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +184 -46
  898. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  899. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  900. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +2 -1
  901. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +289 -37
  902. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +3 -2
  903. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +2 -2
  904. package/dist/knowledge/skills/market-alternatives/SKILL.md +4 -3
  905. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
  906. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
  907. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  908. package/dist/knowledge/skills/market-category/SKILL.md +2 -1
  909. package/dist/knowledge/skills/market-channels/SKILL.md +5 -4
  910. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +233 -18
  911. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +232 -18
  912. package/dist/knowledge/skills/market-generation-cli/SKILL.md +77 -15
  913. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +50 -12
  914. package/dist/knowledge/skills/market-icp/SKILL.md +4 -3
  915. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +7 -6
  916. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +4 -3
  917. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +18 -3
  918. package/dist/knowledge/skills/market-persona/SKILL.md +4 -3
  919. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
  920. package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
  921. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +5 -4
  922. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
  923. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +16 -0
  924. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  925. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +3 -2
  926. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +4 -3
  927. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +199 -0
  928. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  929. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  930. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  931. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  932. package/dist/knowledge/skills/minion-authoring/SKILL.md +144 -0
  933. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  934. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  935. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +143 -0
  936. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
  937. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
  938. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
  939. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
  940. package/dist/knowledge/skills/module-companion-exports/SKILL.md +55 -19
  941. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +217 -18
  942. package/dist/knowledge/skills/module-registration/SKILL.md +50 -32
  943. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +143 -16
  944. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +227 -0
  945. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  946. package/dist/knowledge/skills/module-relationships/SKILL.md +65 -2
  947. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  948. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
  949. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
  950. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
  951. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
  952. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
  953. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
  954. package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
  955. package/dist/knowledge/skills/provider-backend-package/SKILL.md +518 -0
  956. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  957. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +227 -0
  958. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
  959. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
  960. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -0
  961. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  962. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-allow-list-api.md +111 -0
  963. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  964. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
  965. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +165 -29
  966. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  967. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +399 -0
  968. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +270 -9
  969. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
  970. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
  971. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
  972. package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
  973. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
  974. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +247 -0
  975. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  976. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +141 -0
  977. package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
  978. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +86 -0
  979. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +73 -0
  980. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
  981. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +300 -0
  982. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +70 -11
  983. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  984. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  985. package/dist/knowledge/skills/resource-add-field/SKILL.md +13 -5
  986. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
  987. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +472 -23
  988. package/dist/knowledge/skills/resource-add-module/SKILL.md +117 -265
  989. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +134 -0
  990. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  991. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  992. package/dist/knowledge/skills/resource-add-resource/SKILL.md +29 -3
  993. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +244 -32
  994. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +26 -0
  995. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +101 -0
  996. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +145 -0
  997. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +101 -0
  998. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  999. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  1000. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  1001. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +953 -0
  1002. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  1003. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +125 -0
  1004. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  1005. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +595 -45
  1006. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  1007. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +259 -45
  1008. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +486 -0
  1009. package/dist/knowledge/skills/resource-custom-view/SKILL.md +6 -0
  1010. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +422 -11
  1011. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  1012. package/dist/knowledge/skills/resource-external-data/SKILL.md +1242 -31
  1013. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
  1014. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
  1015. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
  1016. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +739 -17
  1017. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +987 -140
  1018. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +175 -10
  1019. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
  1020. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
  1021. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
  1022. package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
  1023. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
  1024. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
  1025. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
  1026. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
  1027. package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
  1028. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
  1029. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +70 -26
  1030. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  1031. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  1032. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  1033. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +44 -48
  1034. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +108 -14
  1035. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  1036. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  1037. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +186 -0
  1038. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
  1039. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
  1040. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
  1041. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
  1042. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
  1043. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
  1044. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +34 -4
  1045. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
  1046. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  1047. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  1048. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +3 -1
  1049. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +77 -5
  1050. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +210 -0
  1051. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  1052. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  1053. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +50 -12
  1054. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +497 -28
  1055. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  1056. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +78 -14
  1057. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  1058. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  1059. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  1060. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  1061. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +300 -23
  1062. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +75 -1
  1063. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +36 -2
  1064. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +447 -12
  1065. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +148 -6
  1066. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  1067. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
  1068. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +216 -6
  1069. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +266 -0
  1070. package/dist/knowledge/skills/seeding-authoring/SKILL.md +10 -1
  1071. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  1072. package/dist/knowledge/skills/seeding-operations/SKILL.md +34 -29
  1073. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  1074. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  1075. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  1076. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +455 -0
  1077. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
  1078. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
  1079. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
  1080. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
  1081. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
  1082. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +206 -0
  1083. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +266 -0
  1084. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  1085. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
  1086. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
  1087. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +52 -19
  1088. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +217 -18
  1089. package/dist/knowledge/skills/spec-component-update/SKILL.md +31 -11
  1090. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
  1091. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  1092. package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
  1093. package/dist/knowledge/skills/spec-feature-update/SKILL.md +48 -9
  1094. package/dist/knowledge/skills/spec-resource-update/SKILL.md +16 -0
  1095. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  1096. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +188 -46
  1097. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
  1098. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
  1099. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  1100. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +14 -2
  1101. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  1102. package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
  1103. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  1104. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +44 -1
  1105. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
  1106. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +6 -1
  1107. package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
  1108. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  1109. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +4 -0
  1110. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  1111. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  1112. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +72 -13
  1113. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
  1114. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +34 -1
  1115. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +44 -28
  1116. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +48 -23
  1117. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +882 -211
  1118. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
  1119. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +117 -13
  1120. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
  1121. package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
  1122. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +71 -1
  1123. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +22 -2
  1124. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +21 -6
  1125. package/dist/knowledge/skills/website-page-authoring/SKILL.md +206 -35
  1126. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
  1127. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  1128. package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
  1129. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
  1130. package/dist/knowledge/skills/website-section-contact/SKILL.md +159 -180
  1131. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +38 -31
  1132. package/dist/knowledge/skills/website-section-cta/SKILL.md +51 -42
  1133. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +38 -31
  1134. package/dist/knowledge/skills/website-section-faq/SKILL.md +118 -83
  1135. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +38 -31
  1136. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +46 -38
  1137. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +38 -31
  1138. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +52 -42
  1139. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +38 -31
  1140. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +50 -40
  1141. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +38 -31
  1142. package/dist/knowledge/skills/website-section-hero/SKILL.md +101 -69
  1143. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +38 -31
  1144. package/dist/knowledge/skills/website-section-pricing/SKILL.md +236 -220
  1145. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +38 -31
  1146. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
  1147. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +64 -54
  1148. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +38 -31
  1149. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
  1150. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
  1151. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +44 -26
  1152. package/dist/knowledge/skills/worker-authoring/SKILL.md +165 -0
  1153. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  1154. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  1155. package/dist/knowledge/topic-index.json +12659 -4142
  1156. package/dist/tsconfig.build.tsbuildinfo +1 -1
  1157. package/dist/tsconfig.tsbuildinfo +1 -1
  1158. package/package.json +4 -4
  1159. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  1160. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  1161. package/dist/knowledge/skills/journey-approve/SKILL.md +0 -43
  1162. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -42
  1163. package/dist/knowledge/skills/journey-next/SKILL.md +0 -42
  1164. package/dist/knowledge/skills/journey-report/SKILL.md +0 -43
  1165. package/dist/knowledge/skills/journey-run/SKILL.md +0 -55
  1166. package/dist/knowledge/skills/journey-status/SKILL.md +0 -50
  1167. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -1,10 +1,10 @@
1
1
  # Composing `public.privacy-notice`
2
2
 
3
- The thirteen concerns this document is made of, in the order a reader meets them. Draft one section
3
+ The fourteen concerns this document is made of, in the order a reader meets them. Draft one section
4
4
  per concern, in this order, and produce **every** one — including the concerns nothing can answer,
5
5
  which become marked clauses naming what is missing and who supplies it.
6
6
 
7
- Eight of the thirteen are answered by the ENGINE for every generated application. Five are not, and
7
+ Nine of the fourteen are answered by the ENGINE for every generated application. Five are not, and
8
8
  four of those five are the same two remedies. Knowing that split before you start is what stops a
9
9
  first draft from reading as either uniformly confident or uniformly empty.
10
10
 
@@ -14,15 +14,16 @@ first draft from reading as either uniformly confident or uniformly empty.
14
14
  | 2 | legal basis and role | `NEEDS_DECISION` |
15
15
  | 3 | personal data held | `DERIVED` |
16
16
  | 4 | data categories | `NEEDS_FRAMEWORK` |
17
- | 5 | consent and preferences | `DERIVED` |
18
- | 6 | retention and deletion | `DERIVED` (treatment) + `NEEDS_FRAMEWORK` (duration) |
19
- | 7 | recipients and processors | `NEEDS_FRAMEWORK` |
20
- | 8 | international transfers | `NEEDS_FRAMEWORK`, dependent on 7 |
21
- | 9 | automated decisions and AI | `DERIVED` (functions) + `NEEDS_FRAMEWORK` (consequence) |
22
- | 10 | analytics and tracking | `DERIVED` (consent) + `NEEDS_FRAMEWORK` (cookie inventory) |
23
- | 11 | subject rights | `DERIVED` |
24
- | 12 | data exit | `DERIVED` |
25
- | 13 | tenancy model and shared responsibility | `DERIVED` |
17
+ | 5 | sources of data not collected from the person | `DERIVED` |
18
+ | 6 | consent and preferences | `DERIVED` |
19
+ | 7 | retention and deletion | `DERIVED` (treatment) + `NEEDS_FRAMEWORK` (duration) |
20
+ | 8 | recipients and processors | `NEEDS_FRAMEWORK` |
21
+ | 9 | international transfers | `NEEDS_FRAMEWORK`, dependent on 8 |
22
+ | 10 | automated decisions and AI | `DERIVED` (functions) + `NEEDS_FRAMEWORK` (consequence) |
23
+ | 11 | analytics and tracking | `DERIVED` (consent) + `NEEDS_FRAMEWORK` (cookie inventory) |
24
+ | 12 | subject rights | `DERIVED` |
25
+ | 13 | data exit | `DERIVED` |
26
+ | 14 | tenancy model and shared responsibility | `DERIVED` |
26
27
 
27
28
  ---
28
29
 
@@ -31,14 +32,25 @@ first draft from reading as either uniformly confident or uniformly empty.
31
32
  **Asserts** — who legally operates the service: entity name, registered address, contact route for
32
33
  data-protection questions, and a representative where one is required.
33
34
 
34
- **Derives from** — nothing, and nothing could. A legal entity is a fact about the world, not a
35
- property of a codebase, so this is not a framework gap and no engine change would close it.
35
+ **Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
36
+ registered address, the privacy contact route, and an Art. 27 representative where one is required.
36
37
 
37
- **Completeness** — `NEEDS_DECISION`, always, until the operator supplies it.
38
+ The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
39
+ What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
40
+ said "no engine change would close it", which was right about derivation and wrong about the home.
41
+ The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
42
+ who answered by editing the document lost the answer at the next regeneration — the answer has to live
43
+ in the application or it does not survive.
38
44
 
39
- **What closes it** — the operator recording the entity, address and contact route. That is the second
40
- step, and it is cheap: the reason it is not a blocker is precisely that it can be filled in later
41
- without redrafting anything around it.
45
+ **Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
46
+
47
+ ⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
48
+ exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
49
+ and nobody has. They have different remedies — build something, versus fill something in — and a
50
+ reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
51
+
52
+ **What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
53
+ filled in later without redrafting anything around it, which is the reason it is not a blocker.
42
54
 
43
55
  **Never infer it.** Not from the application name, not from a domain, not from another application,
44
56
  not from model memory. A published legal document naming the wrong entity is worse than one that says
@@ -54,14 +66,39 @@ with gaps beats blocking: the whole document set would be unproducible until one
54
66
  **Asserts** — the lawful basis for each processing purpose, and whether the operator acts as
55
67
  controller or processor for it.
56
68
 
57
- **Derives from** — nothing. Both are legal determinations about the operator's own arrangements. The
58
- framework can show WHAT is processed and BY WHICH MECHANISM; it cannot establish under which basis, or
59
- in which role.
69
+ **Derives from** — `operatorComplianceIdentity.lawfulBases` and `.roleAllocations` in
70
+ `wildo.saas.config.ts`.
71
+
72
+ The DETERMINATIONS are never derivable — both are legal conclusions about the operator's own
73
+ arrangements, and the framework can show WHAT is processed and BY WHICH MECHANISM without establishing
74
+ under which basis or in which role. What it now provides is where to record the conclusion, so that a
75
+ regeneration reproduces it instead of destroying it.
76
+
77
+ **The role is a LIST, not a field, and the produced notice said so before the surface existed:**
78
+ *"This notice therefore does not assign a single legal role to all data processed in a workspace."* A
79
+ B2B SaaS is typically a processor for the records its customers put in and a controller for its
80
+ account holders' own data, simultaneously. `roleAllocations` carries one role per population, and a
81
+ document that collapses them into one is wrong about both.
82
+
83
+ **The `lawful-bases` fact is COMPUTED from `lawfulBases`** — every purpose, its basis and, for
84
+ legitimate interests, the assessment. You never declare it: a restatement would be a second copy of the
85
+ operator's decision that nothing compares with the first. Absent bases leave the fact absent.
60
86
 
61
- **Completeness** — `NEEDS_DECISION`.
87
+ **Give each purpose a stable `purposeRef`** (`account-security`) when a recipient serves it. A vendor
88
+ names the purposes it serves in `providerComplianceChoices.<ref>.purposeRefs`, and the recipients fact
89
+ joins the two. The prose `purpose` can then be reworded without breaking the link; a ref naming no
90
+ declared purpose is reported, never refused.
91
+
92
+ **`LEGITIMATE_INTERESTS` cannot be declared without its assessment** — the schema refuses it. It is
93
+ the only Art. 6(1) basis whose lawfulness depends on a balancing test, so the bare claim asserts a
94
+ conclusion nobody reached.
95
+
96
+ **Completeness** — `DERIVED` when declared; `NEEDS_DECISION` when not. Never `NEEDS_FRAMEWORK`: there
97
+ is a surface, so the remedy is to fill it in, not to build something. Name the surface when reporting
98
+ the gap.
62
99
 
63
100
  **What closes it** — the operator determining, per purpose, the basis and the role, ideally with
64
- counsel. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for
101
+ counsel, and declaring them in `operatorComplianceIdentity`. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for
65
102
  the data a customer stores about its own people, controller for the data the operator holds about
66
103
  account holders — but describing the common shape is not the same as determining this operator's, and
67
104
  the produced document must not present the first as the second.
@@ -90,6 +127,20 @@ invoice and of a CRM contact, so it never tells you whether a record is about a
90
127
  retention mode does.
91
128
 
92
129
  **Completeness** — `DERIVED` for every resource that declares a retention policy.
130
+
131
+ **An erasure-coverage gap does NOT license a claim about whether personal data is held.** The two are
132
+ different axes and the facts report them separately: `retentionPolicy` answers *what happens to this
133
+ row on erasure*, while a field's `.dataCategories()` answers *what kind of data is in it*. A resource
134
+ can declare the second and not the first, and 48 of the engine's 85 do.
135
+
136
+ So writing "N resources have no declared erasure treatment, so this notice cannot establish whether
137
+ they hold personal data" is an over-reach, and it contradicts the data-categories section of the same
138
+ document — which enumerates categories drawn from those very resources. It was produced twice on
139
+ 2026-08-30 before this paragraph existed.
140
+
141
+ State the gap as what it is: those resources have not declared an erasure TREATMENT, so a notice
142
+ cannot say what an erasure does to them. Where the facts also report a category coverage for the same
143
+ origin, say what IS established alongside it.
93
144
  `NEEDS_CONFIGURATION` for every resource that does not.
94
145
 
95
146
  **What closes it** — the application's own authors declaring `retentionPolicy` on the resource. Name
@@ -98,28 +149,104 @@ the resources individually: the remedy is per-resource, and a count is not actio
98
149
 
99
150
  ### Concern: data categories
100
151
 
101
- **Asserts** — which CATEGORIES of personal data are held: contact details, identifiers, financial
102
- data, usage data, and any special-category data.
103
-
104
- **Derives from** — nothing usable today, and the near-miss matters. `Compliance_DataClassification`
105
- exists and is a four-level SENSITIVITY ladder (public / internal / confidential / restricted) applied
106
- only to flows-actors configuration. It answers "how protected must this be", not "what kind of
107
- personal data is this", and using it as a category vocabulary would produce a notice describing
108
- protection levels where a reader expects data types.
109
-
110
- Say that explicitly when recording this gap, or the next reader will point at that enum and assume
111
- the concern is already answered.
112
-
113
- **Completeness** — `NEEDS_FRAMEWORK`.
114
-
115
- **What closes it** — an engine change adding a data-category vocabulary declarable per resource and
116
- per field — issue #90. Per FIELD is what makes it worth having: a resource-level category
117
- cannot express that one row holds a name, an email and a payment token, which is exactly what a
118
- notice must enumerate.
119
-
120
- **Do not derive categories from field names.** `email`, `phone`, `dateOfBirth` are suggestive and
121
- `notes` is not, and a category list assembled by pattern-matching identifiers is a guess presented as
122
- an inventory — the failure mode being that whatever the guess misses simply is not disclosed.
152
+ **Asserts** — which CATEGORIES of personal data are held: identity, contact details, credentials,
153
+ financial, usage, location, user content, professional, and any GDPR Art. 9 special-category or
154
+ Art. 10 criminal-offence data.
155
+
156
+ **Derives from** — each field's `.dataCategories()` declaration, reported per resource and unioned
157
+ across the application in the compliance-primary-facts section. One category is DERIVED rather than
158
+ declared: `credentials`, from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, which are
159
+ markers the author already wrote.
160
+
161
+ **Nothing is derived from a field NAME.** `email`, `phone` and `dateOfBirth` are suggestive while
162
+ `notes` is not, so a category list assembled by pattern-matching identifiers is a guess presented as
163
+ an inventory — and its failure mode is silent, because whatever the guess misses is simply not
164
+ disclosed. The declaration exists so that never happens.
165
+
166
+ **Completeness** — `DERIVED` when the application declares categories; `NEEDS_CONFIGURATION` when it
167
+ declares none, or when the facts section lists OUTSTANDING fields.
168
+
169
+ **The two gaps are different and must not be written the same way.**
170
+
171
+ - A resource that declares no category at all may genuinely hold no personal data. Nothing
172
+ distinguishes "considered and not applicable" from "never asked", so state that the question is
173
+ unanswered — never that the application holds no personal data.
174
+ - A field the facts section lists as OUTSTANDING is a provable omission. The application already
175
+ declared that field personal by another door — an erasure scrub treatment, a portability
176
+ provenance, or a credential marker — so the missing category is an omission, not a judgement.
177
+ Name the field and its basis. Do not guess what it contains.
178
+
179
+ **Say WHICH special category, not that there is one.** A `special-category:*` value is Art. 9 data
180
+ and carries a lawful-basis condition of its own beyond Art. 6; `criminal-offence` is Art. 10, a
181
+ separate article with a different condition. "We process special category data" is not a disclosure —
182
+ the enum names the kind precisely so a notice can.
183
+
184
+ **Do NOT point at `Compliance_DataClassification`.** It exists, it is a four-level SENSITIVITY ladder
185
+ (public / internal / confidential / restricted) applied only to flows-actors configuration, and it
186
+ answers "how protected must this be" rather than "what kind of personal data is this". Using it here
187
+ would produce a notice describing protection levels where a reader expects data types. It is named
188
+ explicitly because it is a near-miss a reader will otherwise find and assume answers this concern.
189
+
190
+
191
+ ### Concern: sources of data not collected from the person
192
+
193
+ **Asserts** — for personal data the application reads or copies from the operator's own systems (an ERP,
194
+ a CRM), where it came from, whether that source is publicly accessible, which categories come from it,
195
+ and the purpose and legal basis for obtaining it.
196
+
197
+ **Derives from** — the computed fact `system-of-record-sources`: every resource the application binds to, or
198
+ pipes from, a declared system of record (`systemsOfRecord` in `wildo.saas.config.ts`). Per resource, the fact
199
+ gives:
200
+
201
+ - the instance and its vendor;
202
+ - the categories of the fields that come from it (their `.dataCategories()`), with any personal field that
203
+ names no category;
204
+ - the purposes the binding links (`purposeRefs` on the `httpApiBinding` or on the pipeline's `binding`),
205
+ resolved against `operatorComplianceIdentity.lawfulBases`;
206
+ - the instance's declared `personalDataOrigin`, when it declares one;
207
+ - for a pipeline (a local copy), whether its rows are kept until erased.
208
+
209
+ **Why it is its own concern** — data copied or read from the operator's ERP or CRM was not collected from the
210
+ person, so the notice owes where it came from and whether it came from a publicly accessible source (GDPR Art.
211
+ 14(2)(f)), beside the categories and the purpose and legal basis for obtaining it (Art. 14(1)(c), (d)).
212
+
213
+ **Name the source as what it is: the operator's own system.** A system of record is a deployment the operator
214
+ runs and reads with its own service identity. That is the proximate source, and the fact states it. Whether the
215
+ data ORIGINATED from a publicly accessible source is a different question: a contact in an ERP may have been
216
+ entered there from a public register or a website. The operator states it once per instance, as
217
+ `systemsOfRecord.<name>.personalDataOrigin` in `wildo.saas.config.ts`, and each source carries it:
218
+
219
+ - `no-publicly-accessible-sources` — say the data does not come from publicly accessible sources;
220
+ - `includes-publicly-accessible-sources` — say that some of it may, and name the kinds if the operator has;
221
+ - ABSENT — the instance has not stated it. Mark that half of the statement owed for the source. Never write
222
+ "not from publicly accessible sources" on the strength of the source being the operator's own system. The
223
+ remedy is the declaration above, not a sentence in the notice.
224
+
225
+ **Completeness** — `DERIVED`. Nobody answers this concern; the fact is computed from the declarations.
226
+
227
+ - An EMPTY `sources` list means no system of record is declared, or none sends personal data. It says nothing
228
+ about any OTHER indirect source — a colleague's invitation, a single sign-on or social login, a connected
229
+ account. Those come from `data-categories-and-sources`. So state only that no personal data is obtained from
230
+ the operator's systems of record; never conclude that everything is collected from the person.
231
+ - An ABSENT fact means systems of record are declared and their flows could not be read. Mark the clause owed;
232
+ never write "no other source".
233
+ - A source whose `purposes` is empty links no purpose. State the source and the categories, and mark the purpose
234
+ as owed. The remedy is `purposeRefs` on the binding, naming a declared lawful basis. A ref in
235
+ `purposeRefsNamingNoPurpose` is a broken link, owed the same way.
236
+ - A source with `keptUntilErased: true` is a local copy nobody decided how long to keep. Say it is kept until the
237
+ person or their organisation asks for erasure, never a period. The remedy is a retention-class binding on the
238
+ destination resource.
239
+
240
+ **What would close a gap** — every remedy is the application author's and every one is a declaration: a
241
+ `purposeRefs` entry on the binding, a `personalDataOrigin` on the instance (`NEEDS_CONFIGURATION` until
242
+ then), and a retention class on a copy's destination resource.
243
+ - A read-through source (`copiedLocally: false`) keeps nothing locally. The data is read from the system of record
244
+ when it is shown; say that, not that it is stored.
245
+
246
+ **Cite it beside `data-categories-and-sources`, never instead of it.** That fact covers every collection source
247
+ and is written when the application's document facts are produced; this one is computed from the system-of-record
248
+ declarations only. They are two facts because a computed fact REPLACES any stored fact under its own reference:
249
+ folded into one, the computed answer would discard everything the other states about every other source.
123
250
 
124
251
 
125
252
  ### Concern: consent and preferences
@@ -129,13 +256,41 @@ actually controls.
129
256
 
130
257
  **Derives from**
131
258
 
132
- - `DataProcessingConsent` (`saas-models` → `compliance/privacy/privacy.shared.schemas.ts`):
133
- `NONE` · `BASIC` · `ANALYTICS` · `MARKETING` · `FULL` — a ladder, so a level implies the ones below it.
134
- - the application's `requiredConsent` (`app-configuration-shared.shared.schemas.ts`, default
135
- `ANALYTICS`) — the minimum a person must give to use the service.
136
- - per-user `dataProcessingConsent` — the level each person actually chose.
137
-
138
- **Completeness** — `DERIVED`.
259
+ - `ConsentPurpose` (`@wildo-ai/saas-models`): `ANALYTICS` · `MARKETING` — a SET of purposes, each
260
+ granted or not on its own. There is no ordering: agreeing to marketing says nothing about analytics.
261
+ - per-person `privacy.consentedPurposes` — the purposes each person granted, empty until they grant
262
+ one — and `privacy.consentDecidedAt`, stamped by the server when they decide. An empty set WITH an
263
+ instant is "declined everything"; no instant is "never asked". A notice must not state the second
264
+ as the first.
265
+ - `analytics.requiresConsent` (default `true`) — whether the application's analytics rest on
266
+ `ANALYTICS`. It governs analytics alone, never use of the service.
267
+ - the visitor tier: a marketing website keeps a visitor's decision in their browser and starts a
268
+ consent-based provider (product analytics) only once its purpose is granted.
269
+
270
+ - `operatorComplianceIdentity.serviceConsentRequirement` (`wildo.saas.config.ts`) — what a person
271
+ must agree to in order to use the service AT ALL, and what that gate covers.
272
+
273
+ **An empty `requiredPurposes` is a POSITIVE answer and the usual one.** The operator declaring that nothing is gated on
274
+ consent has answered the question; a document must state it as settled rather than treating it as an
275
+ absence. ABSENT is the different case — nobody was asked — and the brief distinguishes the two.
276
+
277
+ **A consent GATE is not a lawful BASIS.** For most B2B SaaS the basis for core processing is CONTRACT:
278
+ a person uses the product because their employer signed for it. A notice that reads a gate as a basis
279
+ states that their data is processed on consent they could withdraw, which is wrong about the single
280
+ most consequential thing in the document. The basis is declared per purpose in `lawfulBases`.
281
+
282
+ **Completeness** — `DERIVED` for the analytics gate, each person's granted purposes, and the
283
+ service-wide requirement once declared — which the application ENFORCES: until the required purposes are
284
+ granted, the backend refuses every operation the person initiates — API and MCP operations, queued work,
285
+ WebSocket reads and subscriptions, agent tools, retrieval, charts and analytics, A2A task reads, and A2A or
286
+ WebSocket conversations, including resuming one after an approval — except their own profile and preferences,
287
+ where they record the consent, and cancelling an A2A task they already started (signing in and out stay open;
288
+ updates the server pushes on its own are not held back), and the web
289
+ application withholds its pages; `NEEDS_DECISION` naming `serviceConsentRequirement` when it is not.
290
+
291
+ This was `NEEDS_FRAMEWORK` until 2026-08-30, correctly: there was nowhere to record the answer. Issue
292
+ #139 built the surface, so the remedy changed from "someone must build this" to "fill this in" — a
293
+ different party and a different task, which is why the two states are never interchangeable.
139
294
 
140
295
  **Say the thing readers get wrong.** Consent is one lawful basis among several, and it is not the one
141
296
  most B2B processing rests on. **Never write that all processing rests on consent, and never write
@@ -148,7 +303,7 @@ notice. Which basis applies is a `NEEDS_DECISION`; see the legal-basis fragment.
148
303
 
149
304
  **Asserts** — what happens to a record when its subject is erased, and how long records are kept.
150
305
 
151
- Two questions, and the framework answers only the first.
306
+ Two questions, and the framework answers both — the second only for the resources bound to a class.
152
307
 
153
308
  **Derives from (the HOW — answerable)** — each resource's `retentionPolicy.mode`:
154
309
  `RETAIN_AND_IMPERSONALIZE` keeps the row, freezes it, hides it from normal reads and scrubs the fields
@@ -156,17 +311,68 @@ marked `.impersonalizeWith()`; `RETAIN_ONLY` keeps and freezes a row that holds
156
311
  its own. Reading the per-field treatments tells the document exactly WHICH values are destroyed and
157
312
  which survive, which is a genuinely strong statement most notices cannot make.
158
313
 
159
- **Not derivable (the HOW LONG)** — nothing in the framework declares a retention DURATION. A resource
160
- says what erasure does to it; no declaration says "kept for seven years", and none can be inferred
161
- from anything present.
162
-
163
- **Completeness** — `DERIVED` for the treatment, `NEEDS_FRAMEWORK` for the duration, in the same
164
- fragment. Do not let the derivable half hide the missing one: a statement about erasure mechanics
165
- reads to a reader as an answer about retention, so the gap must be stated in the same breath.
166
-
167
- **What closes it** — an engine change adding a declared retention period per resource or data
168
- category — issue #89. Until then the produced document says the duration is not yet
169
- established and names what would settle it.
314
+ **Records a statute keeps survive an erasure RESTRICTED, and the request still completes.** A resource
315
+ bound to `BUSINESS_RECORDS` declares `retentionPolicy.statutoryRetention`: the GDPR Art. 17(3)(b) ground
316
+ (`LEGAL_OBLIGATION`) and the statute in the operator's words. An erasure erases everything else, keeps
317
+ those rows retained and hidden from any other processing until their statutory period ends, and lists
318
+ each one with its ground and end date — which is what the notice must say: that some records are kept
319
+ because the law requires it, which law, and that they are deleted when the period ends. The
320
+ `retention-rules` fact names these resources and their statute under each erasure treatment. Never write
321
+ that an erasure is refused or delayed because of them.
322
+
323
+ **Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config
324
+ over five data classes: `RESOURCE_DATA` (its records), `FILES` (uploaded bytes), `AUDIT_LOGS` (the
325
+ tamper-evident trail, kept longest and for a different reason — it is the evidence an operator may
326
+ lawfully retain under GDPR Art. 17(3)), `OPERATIONAL_LOGS`, and `BUSINESS_RECORDS` (records a statute
327
+ requires to be kept for a minimum period). Each declared class carries a period in days AND the
328
+ operator's stated reason for it.
329
+
330
+ **Enforced where a resource is BOUND** — a resource declares `retentionBinding: { retentionClass,
331
+ startPoint }`, and the retention sweep deletes its rows once the period has passed since the start point
332
+ (the account closing, the record closing, its creation, the end of its calendar year). The period is
333
+ counted from when the record stops being needed, so a live record is never deleted for its age. The
334
+ `retention-rules` fact names, per class, the resources bound to it and the MECHANISMS that act on it:
335
+ `RETENTION_CLASS_SWEEP`, `FILES_CLEANUP` (file bytes after their row is gone), `AUDIT_ARCHIVAL`. An EMPTY
336
+ mechanism list means nothing is even wired to enforce the class — say exactly that. `AUDIT_ARCHIVAL` means the audit
337
+ trail is archived after the period and is NEVER deleted: do not write that audit records are deleted.
338
+ The fact also names the resources bound to no class — kept until erased, because nobody decided otherwise.
339
+
340
+ **Whether a period IS enforced is a different fact** — `retention-enforcement`, computed from the records the
341
+ retention sweep writes on every run (runtime evidence, not a declaration). Per declared class it reads
342
+ `ENFORCED` (every bound resource shows a recent completed or deferred run), `DECLARED` (a period nothing has
343
+ yet been shown to apply) or `FAILING` (the latest run of a bound resource failed). Say a period is enforced
344
+ ONLY where it reads `ENFORCED`, and as of its `observedAt` — and only for the resources bound to the class:
345
+ `mechanismsNotEvidencedByTheseRecords` names what the records cannot see (the audit trail's archival, the files
346
+ cleanup), so never write that the audit trail's or the files' retention is evidenced by this fact. A mechanism in `retention-rules` says the sweep
347
+ WILL act; only this fact says it did. When the fact is absent the records were not collected: say enforcement
348
+ is not yet evidenced, never that it is not happening.
349
+
350
+ The classes are the STORES on purpose: the same declaration answers what a notice must state and what
351
+ a backup-and-restore inventory must protect (issue #8).
352
+
353
+ **The `retention-rules` fact is COMPUTED from both** — the declared periods with their reasons and
354
+ mechanisms, the classes with no period, each resource's declared erasure treatment, the resources
355
+ declaring none, and the resources bound to no retention class.
356
+ You never declare it. It is absent when no schedule is declared, because a treatment alone would read as
357
+ the whole answer.
358
+
359
+ **Completeness** — `DERIVED` for the treatment, and for each retention class the application HAS
360
+ declared. `NEEDS_DECISION` for each class it has not: the mechanism exists, so what is missing is an
361
+ operator's decision rather than an engine change. Do not let the derivable half hide the missing one —
362
+ a statement about erasure mechanics reads to a reader as an answer about retention, so both go in the
363
+ same breath.
364
+
365
+ **What closes it** — the operator deciding a period, and saying why. Not a framework change: issue #89
366
+ delivered the declaration surface, so an undeclared class is now an unanswered question rather than an
367
+ unaskable one.
368
+
369
+ **An UNDECLARED class is not "kept indefinitely" and not "deleted immediately".** It is a decision
370
+ nobody has taken, and the document must say exactly that.
371
+
372
+ **A legal hold suspends every deletion of its scope** — the retention sweep, an erasure, the tenant purge,
373
+ file bytes — until the tier that placed it releases it (`legalHolds`). The notice may say that data is kept
374
+ beyond its period while a legal claim, an investigation or a legal obligation requires it, and that it is
375
+ deleted once that ends. Never write that a hold expires, and never name a matter.
170
376
 
171
377
  **Never write a placeholder period.** "Typically 12 months" in a published notice is a commitment
172
378
  nobody made and nothing enforces.
@@ -176,43 +382,155 @@ nobody made and nothing enforces.
176
382
 
177
383
  **Asserts** — who else receives personal data, in what role, and where they process it.
178
384
 
179
- **Derives from (partial)** — the engine capabilities the application has a provider configured for
180
- (`EngineCapability` in `saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`).
181
- That establishes THAT a third party is involved and WHAT FUNCTION it performs — email delivery,
182
- storage, payments, LLM inference, observability.
385
+ **Derives from (who receives)** — the RECIPIENT POPULATION, which your brief renders under *"Who
386
+ RECEIVES data, by whose account reaches them"*. It is computed by `computeRecipientPopulation`
387
+ (`@wildo-ai/saas-specifications/application-creation`) from the configuration and a scan of the
388
+ application's source, and the privacy notice's recipients fact and the assurance evidence read the SAME
389
+ population, so none of them can disagree with the others. Every provider declared under a runtime scope
390
+ (`backend`, `frontendServices.<service>`, `minions.<minion>`, `workers.<worker>`) and every
391
+ `systemsOfRecord` instance lands in exactly ONE of four classes:
392
+
393
+ | Class | What it means | What the document does with it |
394
+ | --- | --- | --- |
395
+ | **OPERATOR-RUN** | an explicit `SELF_HOSTED` compliance choice | processing under the operator's own control — never a recipient |
396
+ | **OPERATOR SUB-PROCESSOR** | some data path spends the APPLICATION's own account (an engine capability, a wired capability role, a typed client, a browser operation, a system of record) | the operator's recipient; it belongs in the processor register |
397
+ | **TENANT RECIPIENT** | reachable ONLY through a customer's or a person's own connected account | the customer's own vendor, reached at the customer's instruction. Never the operator's sub-processor; you may say a customer can connect its own account |
398
+ | **DECLARED, NO DATA PATH** | configured, and nothing in the application reaches it | receives nothing. Never name it as a recipient; the gap is the declaration itself |
399
+
400
+ An engine capability is ONE data path, not the definition of a recipient: a catalogue vendor called
401
+ through its typed client receives data with no capability at all, and a vendor declared "to exercise the
402
+ loading chain" with nothing calling it receives nothing. The tenant class matters most when the operator
403
+ is a PROCESSOR for the data: listing a customer's own vendor as its sub-processor states an engagement the
404
+ operator never made. The function and its limits are in the `compliance-document-authoring` skill's
405
+ `references/framework-recipient-population.md`.
406
+
407
+ **Derives from (the identities)** — the application's PROCESSOR REGISTER, which your brief renders
408
+ under *"Who else processes personal data"*. Per entry: the processor's **legal entity**, the
409
+ **regions** it processes in, and its own **subprocessors** with their regions.
410
+
411
+ **The register holds two kinds of entry and the brief labels them differently — say which.** A
412
+ CONFIGURED PROVIDER entry joins to the application's composition, so it can be checked against it: a
413
+ claim about a provider the application does not configure is detectable, and a configured provider
414
+ with no entry is reported as UNDECLARED. An AUTHORED entry — a hosting company, a CDN, a support desk
415
+ — joins to nothing, because no configuration mentions it. The framework can neither confirm it nor
416
+ notice its absence.
417
+
418
+ Both kinds of declared relationship can belong in the notice when their role is established. What
419
+ 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
420
+ as though the framework verified it overstates what anyone checked.
421
+
422
+ **A SELF-HOSTED provider is not a recipient either, and this is the second way to get the section
423
+ wrong.** The brief's *"Who RUNS each bound provider"* block splits the members the OPERATOR answers
424
+ for (operator sub-processors and operator-run) three ways:
425
+ THIRD-PARTY RECIPIENTS (vendor-hosted, so data reaches a third party — enumerate these with their
426
+ region), OPERATOR-RUN (self-hosted, so no third party receives anything — state them as processing
427
+ under the operator's own control, never as recipients), and UNANSWERED.
428
+
429
+ An UNANSWERED provider is bound to a runtime with no declared deployment model. **Do not assume
430
+ vendor-hosted.** It looks like the cautious reading and it is not: it publishes that a person's data
431
+ goes to a third party when nobody said so. Report it as not established, and name the surface —
432
+ `providerComplianceChoices` in `wildo.saas.config.ts`.
433
+
434
+ **A provider PROFILE is not a recipient.** The brief separates providers BOUND TO A RUNTIME — backend,
435
+ companion, workers, minions, a frontend service, which can process the application's data — from
436
+ provider profiles with no runtime binding. A profile says how to reach a provider; build-time tooling
437
+ lives there, and a coding agent operating on the workspace receives no customer records. Never name a
438
+ profile-only provider as a recipient. Naming one reads as caution and is a false statement about
439
+ somebody's data, exactly like omitting a real one.
440
+
441
+ The section joins the register to the OPERATOR SUB-PROCESSORS of the recipient population, so it tells
442
+ you these different things and they are not interchangeable:
443
+
444
+ - a candidate WITH an entry — its declared identity and regions are available. Establish its
445
+ deployment role before presenting it as a recipient.
446
+ - a candidate listed **UNDECLARED** — a runtime binding has no matching processor entry. Name its
447
+ configured function and unresolved declarations; an unanswered deployment choice remains unknown,
448
+ not automatically vendor-hosted. `NEEDS_DECISION`, resolved by the operator.
449
+ - a provider entry listed **STALE** — no data path reaches it from this operator any more.
450
+ Reconcile the declaration and deployment choice; this check alone does not establish its actual
451
+ historical processing or that all external data has been removed.
452
+ - a provider entry listed **REGISTERED TENANT RECIPIENT** — the register names, as the operator's
453
+ sub-processor, a vendor reached only through customers' own accounts. That entry is a false
454
+ statement about who engaged the vendor; do not publish it as one of the operator's processors.
455
+
456
+ **Completeness** — `DERIVED` per provider that is declared, `NEEDS_DECISION` per provider that is not.
457
+ Not `NEEDS_FRAMEWORK` any more: issue #88 delivered the declaration surface, so an undeclared processor
458
+ is an unanswered question rather than an unaskable one.
459
+
460
+ **Never infer a region from a vendor's brand.** "It is a US company" is not a processing location, and
461
+ a transfer statement built on it is a claim about somebody's data made from a guess.
462
+
463
+ **Distinguish the register declaration from its reconciliation.**
464
+
465
+ | Observed state | What it establishes | What the document may say |
466
+ | --- | --- | --- |
467
+ | Register absent | No processor declaration was supplied | The operator has not established the register; do not infer recipients or their absence |
468
+ | 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 |
469
+ | 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 |
470
+
471
+ Reconcile only operator sub-processors. Exclude operator-run, tenant-recipient, unreached and
472
+ profile-only providers; keep unanswered deployment choices visible as unanswered. `registerEstablishesNoProcessorRecipients`
473
+ answers the declaration question; `undeclaredProcessorRefs` answers candidate coverage. A true answer to
474
+ the first does not erase gaps returned by the second.
475
+
476
+ Name third-party recipients only when their role is established. An empty register does not justify
477
+ an unconditional statement that third parties provide email, storage or payments. Equally, do not
478
+ omit unresolved candidate questions and thereby imply that absence was verified. Authored recipients
479
+ remain operator declarations whose completeness cannot be inferred from runtime bindings.
183
480
 
184
- **Not derivable** — the three things a reader actually needs: the processor's **legal identity**, the
185
- **region** it processes in, and its own **subprocessors**. A provider declares none of them.
186
481
 
187
- **Completeness** — `NEEDS_FRAMEWORK`, and this is the largest single gap in the produced document. It
188
- blocks this concern and the international-transfers one for every application, not just this one.
482
+ ### Concern: international transfers
189
483
 
190
- **What closes it** — an engine change giving a provider declaration a processor identity, a
191
- processing region and a subprocessor list — issue #88.
484
+ **Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer
485
+ mechanism.
192
486
 
193
- **The honest interim statement names the FUNCTIONS and admits the identities are outstanding.**
194
- "Third parties process data for email delivery, file storage and payments; their identities and
195
- processing locations are not yet established in this document" is true, useful and specific. What is
196
- forbidden is the other two moves: inventing a plausible vendor list, and omitting the section — the
197
- first is false and the second lets a reader assume there are no recipients at all.
487
+ **Derives from** — the processor register's regions, at BOTH levels: each declared processor and
488
+ each processor's own subprocessors. Your brief renders them under *"Personal data reaches processors
489
+ in: …"*.
198
490
 
491
+ Both levels, because the chain is what makes a transfer statement hard. An operator in France using a
492
+ French vendor that runs on a US cloud HAS a transfer, and reading only the vendor's region misses it.
199
493
 
200
- ### Concern: international transfers
494
+ **The question has three inputs, and the framework derives only one of them.** Where declared
495
+ processors process is declared. Which jurisdiction is the ORIGIN is `operatingJurisdictions`. Which
496
+ MECHANISM makes a given transfer lawful is a legal determination with a shelf life — adequacy decisions
497
+ move by court ruling — so the framework never computes it: the operator RECORDS it, per register entry,
498
+ as a `transferDetermination`:
201
499
 
202
- **Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer
203
- mechanism.
500
+ - `NO_TRANSFER`, with the reason none of the entry's regions lies outside the origin jurisdictions —
501
+ regions are free text, so this comparison is the operator's and never the framework's;
502
+ - `TRANSFER`, with one safeguard per origin jurisdiction: the GDPR Chapter V mechanism
503
+ (`ADEQUACY_DECISION`, `STANDARD_CONTRACTUAL_CLAUSES`, `BINDING_CORPORATE_RULES`,
504
+ `APPROVED_CODE_OF_CONDUCT`, `APPROVED_CERTIFICATION`, or a `DEROGATION` naming its Art. 49 ground) and
505
+ the instrument a reader could look up.
204
506
 
205
- **Derives from** — nothing, and it cannot until the recipients-and-processors concern is answered:
206
- a transfer statement is a statement about WHERE a recipient processes, so a provider declaration that
207
- carries no region cannot support one.
507
+ The determination sits on the ENTRY because the processor's own contract binds its onward transfers to
508
+ its subprocessors; reaching the processor is the transfer the operator answers for.
208
509
 
209
- **Completeness** — `NEEDS_FRAMEWORK`, dependent on that concern rather than independent of it. Say so
210
- in the produced document; two gaps with one remedy read very differently from two unrelated holes.
510
+ **The `international-transfers` fact is COMPUTED from those determinations** — you never declare it.
511
+ It carries each determined entry, the origin jurisdictions, `undeterminedRecipients` — a register entry
512
+ with no determination, or a configured provider the register does not establish — and `safeguardGaps`:
513
+ a declared origin a TRANSFER names no safeguard for.
211
514
 
212
- **What closes it** — the same engine change as the recipients concern — a processing region on a
213
- provider declaration, issue #88. The
214
- transfer MECHANISM (adequacy, standard contractual clauses, derogation) is then a `NEEDS_DECISION`
215
- layered on top, because a mechanism is chosen and documented rather than derived.
515
+ **Completeness** — do not round any state up.
516
+
517
+ | the register | what you may state | completeness |
518
+ |---|---|---|
519
+ | ABSENT | nothing — where data lands is unknown, and the fact is absent | `NEEDS_CONFIGURATION` |
520
+ | a recipient in `undeterminedRecipients` | that its transfer position is not determined; never fold it into "no transfer" | `NEEDS_DECISION` for that recipient |
521
+ | declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |
522
+ | 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 |
523
+
524
+ **The residual is not optional wording.** "No processor receives personal data" establishes nothing
525
+ about the operator's OWN processing — its infrastructure, its staff, its own establishment. A document
526
+ that says "we do not transfer data internationally" on the strength of an empty register has answered
527
+ a larger question than it was asked.
528
+
529
+ **What closes an undetermined entry** — the operator researching the vendor's data processing
530
+ agreement and recording what it relies on, per origin jurisdiction. A vendor's DPA usually names it:
531
+ standard contractual clauses for EU data, the UK Addendum to them for UK data, and sometimes a
532
+ certification under an adequacy framework beside them. Record what the contract says, not what is
533
+ typical.
216
534
 
217
535
  **"We do not transfer data internationally" is a claim, not a default.** It may be true, and it is
218
536
  citable when an application has declared it as a fact — but it must never be produced because nothing
@@ -233,10 +551,21 @@ use and for what function.
233
551
  effect** on a person, and whether a human reviews it. Nothing in the framework declares consequence or
234
552
  human-review posture, and neither can be inferred from a capability being enabled.
235
553
 
236
- **Completeness** — `NEEDS_FRAMEWORK` for the consequence posture.
554
+ **Derives from (the consequence)** — the AI POSTURE section of your brief, per ENABLED AI capability:
555
+ what it is used for, whether it `NO_DECISION` / `ASSISTS_HUMAN_DECISION` / `DECIDES_AUTONOMOUSLY`, and —
556
+ where it decides anything — how a person obtains human intervention.
237
557
 
238
- **What closes it** — an engine change letting an AI use declare its consequence and its human-review
239
- arrangement — issue #92.
558
+ An application enabling NO AI capability gets a plain statement to that effect: it performs no AI
559
+ processing of personal data. That is a positive, checkable answer, not a gap.
560
+
561
+ **Completeness** — `DERIVED` per capability with a declared posture; `NEEDS_DECISION` per capability
562
+ listed OUTSTANDING. Not `NEEDS_FRAMEWORK` any more: issue #92 delivered the declaration, so an
563
+ undeclared posture is an unanswered question rather than an unaskable one.
564
+
565
+ **An OUTSTANDING capability is not a harmless one.** This is the one concern where silence is more
566
+ dangerous than elsewhere: a notice describing AI use and saying nothing about consequence does not read
567
+ as "unknown", it reads as "nothing significant happens here" — which is the exemption, claimed for
568
+ free. State the gap explicitly.
240
569
 
241
570
  **Why the distinction carries weight.** Automated decision-making with significant effects attracts
242
571
  specific obligations — information about the logic, and a right to human intervention. A generated
@@ -251,52 +580,98 @@ about a person is not yet established.
251
580
 
252
581
  **Derives from (partial)** — the observability and analytics capabilities the application has
253
582
  configured (`FRONTEND_PRODUCT_ANALYTICS`, `LLM_OBSERVABILITY`, `OBSERVABILITY_TELEMETRY`), together
254
- with the consent ladder: `requiredConsent` and per-user `dataProcessingConsent` make
255
- `DataProcessingConsent.ANALYTICS` a real, enforced boundary rather than a stated intention.
583
+ with the consent posture: `analytics.requiresConsent` and each person's `privacy.consentedPurposes` make
584
+ `ConsentPurpose.ANALYTICS` a real, enforced boundary rather than a stated intention — in the application,
585
+ where a product-analytics provider starts only on the signed-in person's grant and is stopped on
586
+ withdrawal or sign-out, and on the marketing website, where one does not start until a visitor grants it.
587
+ A consent-based provider must be stoppable in the page, so none is loaded as a `<script>` tag.
256
588
 
257
- **Not derivable** — the **cookie and client-storage inventory**. Nothing declares which cookies, local
258
- storage keys or client-side SDKs the frontend sets, what each is for, or how long it persists — the
259
- exact table a cookie notice consists of.
589
+ **Derives from (the inventory)** — the CLIENT STORAGE section of your brief: each cookie and storage
590
+ key, its mechanism, purpose, necessity and lifetime, split by who sets it.
260
591
 
261
- **Completeness** — `DERIVED` for the capability and consent posture, `NEEDS_FRAMEWORK` for the
262
- inventory.
592
+ The FRAMEWORK's own entries are listed first and belong in every application's table — the cookies
593
+ `__wildo_refresh` and `__wildo_anon_session`, strictly necessary, with lifetimes taken from the
594
+ application's session configuration, and the website's `__wildo_website_consent` storage key, strictly
595
+ necessary because it is what makes a visitor's refusal hold. **No application authored these and every application sets them**, so a table
596
+ built only from what the application declared would omit the session cookie, which is the entry a
597
+ visitor is most certain to have.
263
598
 
264
- **What closes it** — an engine change declaring client-storage entries per capability and per
265
- frontend surface — issue #91.
599
+ Then, per frontend surface: its declared entries, an explicit "sets nothing of its own", or
600
+ UNINVENTORIED.
266
601
 
267
- Say both halves: which analytics are in use and what consent gates them (strong, derived, enforced),
268
- and that the itemised cookie table is not yet established (honest, and precisely what a cookie notice
269
- still needs before it can be published).
602
+ **UNINVENTORIED is not "sets nothing".** The first says nobody catalogued that surface; the second is a
603
+ positive statement. Writing the second from the first tells a visitor they are tracked by less than they
604
+ are, which is the under-reporting direction a notice must never fail in.
270
605
 
606
+ **Completeness** — `DERIVED` for the capability and consent posture, and for each surface that IS
607
+ inventoried; `NEEDS_DECISION` per uninventoried surface. Not `NEEDS_FRAMEWORK` any more: issue #91
608
+ delivered the declaration surface, so an uninventoried surface is an unanswered question rather than an
609
+ unaskable one.
271
610
 
272
- ### Concern: subject rights
273
-
274
- **Asserts** — which rights the application can actually honour, and through which mechanism. Not what
275
- the law grants; what this application will do when asked.
611
+ Say both halves: which analytics are in use and what consent gates them (strong, derived, enforced), and
612
+ what the table still lacks — naming the surfaces, not the concern.
276
613
 
277
- **Derives from**
278
614
 
279
- - `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20`
280
- (`saas-models` → `compliance/privacy/subject-export.shared.schemas.ts`) — the two distinct export
281
- bundles. Access is the broader one: every row concerning the subject, including rows they do not
282
- own, such as an audit entry about them or a membership an administrator created.
283
- - each resource's `systemAccessPolicy.exportSubject` — whether an export can answer for that resource
284
- at all. **Absent means the resource is excluded from every export**, so an application that has not
285
- declared it cannot honour Art. 15 over that data.
286
- - `portabilityPolicy` and per-field `.portabilityProvenance()` — Art. 20 covers what the subject
287
- supplied, not what the controller derived about them, and an Art. 20 export refuses on any field
288
- that has declared neither.
289
- - erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, which takes a resource type and row ids and
290
- needs no session. **An account is not required to be a data subject** — a contact, a lead or a
291
- subscriber is erased by exactly this path.
615
+ ### Concern: subject rights
292
616
 
293
- **Completeness** — `DERIVED` where the resources hold `exportSubject` declarations.
617
+ **Asserts** — which request mechanisms the application configures, what they select and what their
618
+ results establish. A configured mechanism does not establish that a particular request was fulfilled.
294
619
 
295
- **What closes it** — per-resource `exportSubject` and, for portability, a `portabilityPolicy` default
296
- plus provenance on the fields that differ from it.
620
+ **Derives from**
297
621
 
298
- **Never state** that a right is honoured for a resource whose `exportSubject` is absent. The export
299
- will not include it, and the notice would be describing a capability the application does not have.
622
+ - `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20` — two selections over the declared
623
+ subject relationships. Access includes eligible owned rows and non-owned rows referring to the
624
+ subject. Portability applies narrower relationship and field-provenance selection. Neither is an
625
+ unrestricted recursive export of everything reachable from an account.
626
+ - Each participating resource's `systemAccessPolicy.exportSubject` — an explicit disclosure choice,
627
+ checked before collection. Missing and forbidden are different decisions:
628
+
629
+ | Declaration | Runtime result | Meaning for the request |
630
+ | --- | --- | --- |
631
+ | Absent on a participating resource | Refuses collection | A required disclosure decision is unanswered; no silently incomplete bundle is returned |
632
+ | `ALLOWED` | Passes this disclosure gate | Relationship selection, system-read admission, field security and purpose-specific checks still apply |
633
+ | `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 |
634
+ | `FORBIDDEN` on the subject's own resource | Refuses the bundle | The subject cannot be omitted from its own export |
635
+
636
+ - `portabilityPolicy.defaultProvenance` and per-field `.portabilityProvenance(...)` — the field
637
+ declaration overrides the resource default. `SUBJECT_PROVIDED` and `OBSERVED` values are eligible
638
+ for portability; `DERIVED` values are excluded and reported. Unresolved provenance refuses
639
+ portability collection rather than silently dropping fields. Explicitly forbidden resources do
640
+ not need portability provenance for this export because their rows are not collected. Access uses
641
+ its separate field selection; backend-only and write-only fields remain withheld.
642
+ - Erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, invoked by the application's verified request
643
+ workflow. A contact or lead without a login can still be a data subject. Retention, relationship
644
+ treatments and account linkage are separate declarations; inspect the receipt before claiming
645
+ completion, including dependent execution, session resolution and incomplete external effects.
646
+
647
+ **The rights a notice states are COMPUTED, in the `rights-and-complaint-route` fact.** Which rights
648
+ apply, and where a person may complain, are the law of the regime each `operatingJurisdictions` entry
649
+ falls under, conditioned on the declared lawful bases: portability only for purposes resting on consent
650
+ or contract, objection only for public task or legitimate interests, withdrawal of consent only where
651
+ consent is the basis. The channel is `privacyContact`; the verification step is the operator's
652
+ `subjectRequestIdentityVerification`; who answers comes from `roleAllocations` — the operator for data it
653
+ controls, the customer (with the operator forwarding and assisting) for data it processes on a
654
+ customer's behalf. Two regimes are known: the EU GDPR and the UK's. Their rights match article for article but their
655
+ complaint routes do not — since 19 June 2026 a UK notice names a complaint to the operator itself
656
+ (Data Protection Act 2018 s.164A, acknowledged within 30 days) and to the Information Commissioner
657
+ (s.165(2)), and never GDPR Art. 77. State each regime's route from the fact, not from memory. A
658
+ jurisdiction no known regime reaches is named in `jurisdictionsWithoutKnownRegime`: state that its
659
+ rights are not established here, never borrow another regime's words for it.
660
+
661
+ **Completeness** — derive the configured posture from actual resource declarations and the selected
662
+ relationships. Describe an unresolved declaration as a configuration refusal, an explicit exclusion
663
+ as an exclusion, and an observed request outcome from its report. Declarations alone are not runtime
664
+ proof that a right has been fulfilled.
665
+
666
+ **What resolves a missing declaration** — the owning resource explicitly declares ALLOWED or FORBIDDEN
667
+ according to its intended disclosure policy. Portability additionally needs a valid resource default
668
+ or field-level provenance for the fields it would collect. Do not ask a notice author to replace a
669
+ missing product declaration with a free-text promise.
670
+
671
+ **Never state** that an undeclared participating resource is merely omitted while the remainder is
672
+ exported. The runtime refuses collection. Preserve deliberate exclusions and explain their recorded
673
+ reasons; the application's request workflow owns verification, protected delivery and any necessary
674
+ follow-up.
300
675
 
301
676
 
302
677
  ### Concern: data exit
@@ -325,8 +700,12 @@ their personal fields scrubbed, is inaccurate in the direction that damages trus
325
700
  operator's responsibilities and the customer's lies.
326
701
 
327
702
  **Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every
328
- tenant-scoped resource, and the cross-tenant admission rules (a crossing must be declared on the
329
- operation and carries a usable access grant).
703
+ tenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be
704
+ declared and carry a usable access grant. The application audit viewer is a separate policy surface:
705
+ it defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with
706
+ `auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under
707
+ which a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
708
+ role-based access neither implies anonymized records nor supplies an approval that never occurred.
330
709
 
331
710
  **Completeness** — `DERIVED`.
332
711
 
@@ -336,5 +715,12 @@ CONTROLLER for the data it holds about the customer's users as account holders.
336
715
  roles with different duties over the same database. Say which is which; do not pick one and apply it
337
716
  to everything.
338
717
 
339
- Where a document needs to attribute a duty and the attribution is not established, that is a
340
- `NEEDS_DECISION` — never a guess. See the legal-basis fragment.
718
+ **The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
719
+ `wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
720
+ stores about its own people, CONTROLLER for the account data of the people who administer them. It is
721
+ a LIST for exactly the reason this fragment gives: those are different roles over the same database,
722
+ and a single field would force one of them to be wrong.
723
+
724
+ Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
725
+ surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
726
+ so the remedy is to fill it in rather than to build something. See the legal-basis fragment.