@wildo-ai/framework-knowledge 1.1.3 → 1.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (841) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +349 -17
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  6. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.loader.js +47 -1
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +125 -0
  13. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -0
  14. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +177 -0
  15. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -0
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +213 -7
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +326 -8
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +5 -3
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +21 -14
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +57 -0
  25. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -0
  26. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +63 -0
  27. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -0
  28. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +132 -0
  29. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -0
  30. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +179 -0
  31. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -0
  32. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +67 -0
  33. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -0
  34. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +76 -0
  35. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -0
  36. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +5 -4
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +10 -5
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +67 -0
  41. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -0
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +82 -0
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -0
  44. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +25 -9
  45. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +124 -7
  47. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +67 -0
  49. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -0
  50. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +83 -0
  51. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -0
  52. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +69 -0
  53. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -0
  54. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +71 -0
  55. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -0
  56. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  57. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +71 -0
  60. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -0
  61. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +88 -0
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -0
  63. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +97 -0
  64. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -0
  65. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +156 -0
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -0
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +115 -0
  68. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -0
  69. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +152 -0
  70. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -0
  71. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +188 -8
  72. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +167 -9
  74. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +171 -1
  76. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +146 -1
  78. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts +248 -0
  80. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -0
  81. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js +248 -0
  82. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +157 -4
  84. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +172 -4
  86. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  87. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +5 -4
  88. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  89. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +8 -7
  90. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +3 -2
  92. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +22 -3
  94. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  95. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +5 -3
  96. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +21 -12
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  99. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +192 -27
  100. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  101. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +172 -33
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  103. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +2 -1
  104. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  105. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +6 -2
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +182 -5
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +191 -5
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +2 -1
  112. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  113. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +3 -2
  114. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +154 -0
  116. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -0
  117. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +214 -0
  118. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -0
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +44 -0
  120. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -0
  121. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +51 -0
  122. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -0
  123. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -1
  124. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  125. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +2 -1
  126. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  127. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +2 -1
  128. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  129. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +6 -2
  130. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  131. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +2 -1
  132. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  133. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +2 -1
  134. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  135. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -2
  136. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  137. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +7 -3
  138. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  139. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +32 -4
  140. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  141. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +27 -3
  142. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  143. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -2
  144. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +4 -2
  146. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  147. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +199 -0
  148. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -0
  149. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +227 -0
  150. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -0
  151. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +5 -3
  152. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  153. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +18 -4
  154. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +155 -4
  156. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  157. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +187 -4
  158. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  159. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +6 -5
  160. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  161. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +18 -17
  162. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  163. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  164. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -0
  165. package/dist/knowledge/manifest.json +9 -8
  166. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +75 -0
  167. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +43 -0
  168. package/dist/knowledge/playbooks/bottom_up.build/method.md +79 -0
  169. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +65 -0
  170. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -0
  171. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -0
  172. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +1122 -76
  173. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +49 -13
  174. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-protocol.json +1 -1
  175. package/dist/knowledge/playbooks/bottom_up.build-dispatch/evaluation-treatment.json +1 -1
  176. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +671 -47
  177. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +10 -16
  178. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +31 -35
  179. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -16
  180. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +95 -0
  181. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +62 -0
  182. package/dist/knowledge/playbooks/bottom_up.conception/method.md +80 -0
  183. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +90 -0
  184. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +107 -0
  185. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +70 -0
  186. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +8 -8
  187. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +14 -13
  188. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +165 -0
  189. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +74 -0
  190. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +219 -140
  191. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -22
  192. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +138 -0
  193. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +70 -0
  194. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +87 -0
  195. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +69 -0
  196. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +236 -0
  197. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +63 -0
  198. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +116 -0
  199. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +79 -0
  200. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +71 -0
  201. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +70 -0
  202. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +83 -0
  203. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +68 -0
  204. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -0
  205. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -0
  206. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +873 -15
  207. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +19 -12
  208. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-protocol.json +1 -0
  209. package/dist/knowledge/playbooks/refinement.document-facts/evaluation-treatment.json +1 -0
  210. package/dist/knowledge/playbooks/refinement.document-facts/method.md +186 -21
  211. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +12 -16
  212. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-protocol.json +1 -0
  213. package/dist/knowledge/playbooks/refinement.governance-document-candidate/evaluation-treatment.json +1 -0
  214. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +343 -0
  215. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +54 -0
  216. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -0
  217. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -0
  218. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +28 -11
  219. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -17
  220. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +8 -15
  221. package/dist/knowledge/playbooks/top_down.capability-map/method.md +25 -49
  222. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +14 -17
  223. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +41 -0
  224. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +101 -0
  225. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-protocol.json +1 -0
  226. package/dist/knowledge/playbooks/top_down.compliance-conception/evaluation-treatment.json +1 -0
  227. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +209 -0
  228. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +68 -0
  229. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +61 -0
  230. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +42 -0
  231. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -0
  232. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -0
  233. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +39 -12
  234. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +18 -66
  235. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +78 -0
  236. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +43 -0
  237. package/dist/knowledge/playbooks/top_down.definition/method.md +103 -0
  238. package/dist/knowledge/playbooks/top_down.definition/playbook.json +75 -0
  239. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +56 -0
  240. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +48 -0
  241. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +51 -165
  242. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +25 -44
  243. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +56 -0
  244. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +43 -0
  245. package/dist/knowledge/playbooks/top_down.market-research/method.md +68 -0
  246. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +45 -0
  247. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-protocol.json +1 -1
  248. package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/evaluation-treatment.json +1 -1
  249. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +247 -0
  250. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +71 -0
  251. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  252. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  253. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +36 -69
  254. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +12 -9
  255. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +11 -7
  256. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +12 -16
  257. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-protocol.json +1 -0
  258. package/dist/knowledge/playbooks/top_down.risk-register/evaluation-treatment.json +1 -0
  259. package/dist/knowledge/playbooks/top_down.risk-register/method.md +46 -0
  260. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +59 -0
  261. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +12 -5
  262. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +15 -17
  263. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-protocol.json +1 -0
  264. package/dist/knowledge/playbooks/top_down.value-proposition/evaluation-treatment.json +1 -0
  265. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +23 -14
  266. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +12 -17
  267. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  268. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +13 -17
  269. package/dist/knowledge/references/acp.execution-profile.md +266 -0
  270. package/dist/knowledge/references/acp.host-configuration-inheritance.md +29 -0
  271. package/dist/knowledge/references/acp.permission-ceiling.md +105 -0
  272. package/dist/knowledge/references/acp.permission-escalation.md +37 -0
  273. package/dist/knowledge/references/application-documentation-chapters.config.md +152 -0
  274. package/dist/knowledge/references/application-documentation-plan.config.md +136 -0
  275. package/dist/knowledge/references/application-maturity.config.md +319 -0
  276. package/dist/knowledge/references/assertions.authored-metadata.config.md +1 -1
  277. package/dist/knowledge/references/assertions.specification.config.md +1 -1
  278. package/dist/knowledge/references/brand.asset.config.md +8 -16
  279. package/dist/knowledge/references/brand.authored-metadata.config.md +2 -2
  280. package/dist/knowledge/references/brand.logo-direction.config.md +9 -7
  281. package/dist/knowledge/references/brand.snapshot.config.md +16 -2
  282. package/dist/knowledge/references/brand.snapshot.validation.md +0 -7
  283. package/dist/knowledge/references/build-plan.task-graph.config.md +581 -7
  284. package/dist/knowledge/references/business-model.authored-metadata.config.md +2 -2
  285. package/dist/knowledge/references/business-model.pricing-plan.config.md +1 -1
  286. package/dist/knowledge/references/business-model.snapshot.validation.md +15 -0
  287. package/dist/knowledge/references/capability-composition.config.md +155 -0
  288. package/dist/knowledge/references/cli.market.utils.md +1 -0
  289. package/dist/knowledge/references/companion.technical-doc.service.md +453 -98
  290. package/dist/knowledge/references/engine.client-bundle.allow-list.md +21 -0
  291. package/dist/knowledge/references/engine.client-bundle.external-connectors-public.discipline.md +20 -1
  292. package/dist/knowledge/references/engine.saas-technical-doc.config.md +8 -4
  293. package/dist/knowledge/references/engine.saas-website.config.md +22 -10
  294. package/dist/knowledge/references/example.backend.addon-wiring.module.md +8 -12
  295. package/dist/knowledge/references/example.config.app-shell.full.md +42 -7
  296. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -0
  297. package/dist/knowledge/references/example.config.design-system.full.md +3 -0
  298. package/dist/knowledge/references/example.engine.product-definitions.feature-and-profiles.md +19 -7
  299. package/dist/knowledge/references/example.features.connected-feature.declaration.md +66 -0
  300. package/dist/knowledge/references/example.features.connected-feature.surface.md +42 -0
  301. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +4 -3
  302. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +6 -10
  303. package/dist/knowledge/references/example.guidance.bound-survey-flow.md +82 -0
  304. package/dist/knowledge/references/example.infra.environment-config.local.md +88 -11
  305. package/dist/knowledge/references/example.milestones.module-definitions.md +73 -0
  306. package/dist/knowledge/references/example.minion.contained-tick.md +79 -0
  307. package/dist/knowledge/references/example.module.companion-exports.full.md +38 -3
  308. package/dist/knowledge/references/example.provider.backend-module-shape.md +31 -13
  309. package/dist/knowledge/references/example.provider.frontend-app.module.md +103 -0
  310. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +20 -0
  311. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +7 -3
  312. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +30 -0
  313. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +11 -0
  314. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +3 -0
  315. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +94 -10
  316. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +79 -0
  317. package/dist/knowledge/references/example.spec.frontend-component.prop-vocabulary.md +18 -0
  318. package/dist/knowledge/references/example.worker.node-route.md +94 -0
  319. package/dist/knowledge/references/experience-plan.config.md +311 -0
  320. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +132 -9
  321. package/dist/knowledge/references/external-connectors.backend.provider-package-convention.md +36 -0
  322. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +269 -0
  323. package/dist/knowledge/references/integration-plan.config.md +185 -0
  324. package/dist/knowledge/references/market.alternative.config.md +1 -1
  325. package/dist/knowledge/references/market.authored-metadata.config.md +12 -9
  326. package/dist/knowledge/references/market.channel.config.md +3 -3
  327. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  328. package/dist/knowledge/references/market.gain.config.md +1 -1
  329. package/dist/knowledge/references/market.icp.config.md +2 -2
  330. package/dist/knowledge/references/market.job.config.md +1 -1
  331. package/dist/knowledge/references/market.message-template.config.md +2 -2
  332. package/dist/knowledge/references/market.objection.config.md +1 -1
  333. package/dist/knowledge/references/market.pain.config.md +1 -1
  334. package/dist/knowledge/references/market.persona.config.md +2 -2
  335. package/dist/knowledge/references/market.proof.config.md +1 -1
  336. package/dist/knowledge/references/market.snapshot.validation.md +15 -0
  337. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  338. package/dist/knowledge/references/market.trigger.config.md +1 -1
  339. package/dist/knowledge/references/minions.tick-contract.md +83 -0
  340. package/dist/knowledge/references/placement-plan.config.md +369 -0
  341. package/dist/knowledge/references/platform.config.application-database.md +5 -2
  342. package/dist/knowledge/references/platform.config.backing-services.md +0 -21
  343. package/dist/knowledge/references/platform.config.environment.deployment.md +206 -14
  344. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +170 -0
  345. package/dist/knowledge/references/platform.config.infrastructure-host.md +87 -0
  346. package/dist/knowledge/references/platform.config.saas.md +261 -9
  347. package/dist/knowledge/references/presets.models.labelling.sections.md +14 -0
  348. package/dist/knowledge/references/presets.models.surface-policy.md +19 -10
  349. package/dist/knowledge/references/requirements.authored-metadata.config.md +2 -2
  350. package/dist/knowledge/references/requirements.snapshot.validation.md +15 -0
  351. package/dist/knowledge/references/roadmap.authored-metadata.config.md +2 -2
  352. package/dist/knowledge/references/roadmap.snapshot.validation.md +15 -7
  353. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +71 -0
  354. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +1 -2
  355. package/dist/knowledge/references/saas.backend.auth.federated-identity-provider-private-networks.md +62 -0
  356. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +86 -0
  357. package/dist/knowledge/references/saas.backend.billing.catalog-sync-result.md +37 -0
  358. package/dist/knowledge/references/saas.backend.billing.resolution-failure-reasons.md +24 -5
  359. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +187 -0
  360. package/dist/knowledge/references/saas.backend.domain-module.md +25 -1
  361. package/dist/knowledge/references/saas.backend.error-builder.user-guidance.md +82 -0
  362. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +6 -0
  363. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +22 -4
  364. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +17 -4
  365. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +84 -0
  366. package/dist/knowledge/references/saas.backend.health-readiness-contributor.md +73 -0
  367. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +200 -0
  368. package/dist/knowledge/references/saas.backend.providers.operation-executor.md +51 -0
  369. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +71 -0
  370. package/dist/knowledge/references/saas.backend.queue.worker-topology.md +39 -0
  371. package/dist/knowledge/references/saas.backend.system-access-service.md +51 -42
  372. package/dist/knowledge/references/saas.composition.scenario-apply.md +51 -0
  373. package/dist/knowledge/references/saas.config.content-security-policy.md +97 -0
  374. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +91 -21
  375. package/dist/knowledge/references/saas.data-seeding.definition-input.md +4 -0
  376. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +38 -0
  377. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +27 -27
  378. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +65 -16
  379. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +41 -11
  380. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +44 -8
  381. package/dist/knowledge/references/saas.frontend.billing-context.md +108 -0
  382. package/dist/knowledge/references/saas.frontend.brand-identity.md +38 -0
  383. package/dist/knowledge/references/saas.frontend.celebration-overlay-contract.md +41 -0
  384. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +64 -0
  385. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +34 -0
  386. package/dist/knowledge/references/saas.frontend.errors.user-facing-error-message.md +47 -0
  387. package/dist/knowledge/references/saas.frontend.execution-view.action-status-contract.per-action-retry-loop.md +7 -1
  388. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +3 -3
  389. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +7 -4
  390. package/dist/knowledge/references/saas.frontend.form-fields.file-provider-constraints.md +30 -48
  391. package/dist/knowledge/references/saas.frontend.full-custom-view.definition.md +24 -0
  392. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +45 -0
  393. package/dist/knowledge/references/saas.frontend.onboarding-view.md +84 -0
  394. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +65 -0
  395. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +65 -0
  396. package/dist/knowledge/references/saas.frontend.resource-header-title.md +28 -4
  397. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +127 -1
  398. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +327 -11
  399. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +198 -0
  400. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +220 -0
  401. package/dist/knowledge/references/saas.market.generation-agent.md +26 -9
  402. package/dist/knowledge/references/saas.models.analytics.value-moments.md +132 -0
  403. package/dist/knowledge/references/saas.models.audit.trail-config.md +155 -0
  404. package/dist/knowledge/references/saas.models.auth.methods.md +513 -0
  405. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +82 -0
  406. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +77 -0
  407. package/dist/knowledge/references/saas.models.config.organization-types.md +192 -0
  408. package/dist/knowledge/references/saas.models.config.registration.md +188 -0
  409. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +81 -0
  410. package/dist/knowledge/references/saas.models.data-mode-read-list.md +173 -3
  411. package/dist/knowledge/references/saas.models.email.template-type.md +40 -0
  412. package/dist/knowledge/references/saas.models.engine-capabilities.md +85 -7
  413. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +61 -0
  414. package/dist/knowledge/references/saas.models.external-data-pipeline.md +43 -4
  415. package/dist/knowledge/references/saas.models.features.definition-builders.md +162 -0
  416. package/dist/knowledge/references/saas.models.file-upload-grant.md +222 -0
  417. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +54 -5
  418. package/dist/knowledge/references/saas.models.governed-document-acceptance-mode.md +116 -0
  419. package/dist/knowledge/references/saas.models.guidance-flow.md +160 -0
  420. package/dist/knowledge/references/saas.models.http-api-binding.md +76 -110
  421. package/dist/knowledge/references/saas.models.milestone-celebration.md +69 -0
  422. package/dist/knowledge/references/saas.models.milestone-definition.md +209 -0
  423. package/dist/knowledge/references/saas.models.navigation.layout.md +2 -2
  424. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +124 -0
  425. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +99 -0
  426. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +150 -0
  427. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +70 -0
  428. package/dist/knowledge/references/saas.models.notifications.targets.md +138 -0
  429. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +256 -0
  430. package/dist/knowledge/references/saas.models.onboarding-elements.md +375 -0
  431. package/dist/knowledge/references/saas.models.onboarding-trigger.md +52 -0
  432. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +50 -0
  433. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +129 -0
  434. package/dist/knowledge/references/saas.models.privacy.client-instance-id-scope.md +49 -0
  435. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +106 -0
  436. package/dist/knowledge/references/saas.models.progression-tracker-variant.md +76 -0
  437. package/dist/knowledge/references/saas.models.provider-capabilities.md +8 -5
  438. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +72 -0
  439. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +50 -0
  440. package/dist/knowledge/references/saas.models.providers.capability-surface.md +58 -0
  441. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +111 -0
  442. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +156 -0
  443. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +11 -1
  444. package/dist/knowledge/references/saas.models.relationship-handling-settings.md +23 -1
  445. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -4
  446. package/dist/knowledge/references/saas.models.resource-config.forwarded-label.md +5 -4
  447. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +69 -0
  448. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +15 -2
  449. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +66 -0
  450. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +24 -1
  451. package/dist/knowledge/references/saas.models.resource-config.operation-cron-job.md +59 -0
  452. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +55 -0
  453. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +5 -4
  454. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +158 -0
  455. package/dist/knowledge/references/saas.models.resource-config.operation-step-up.md +77 -0
  456. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +42 -0
  457. package/dist/knowledge/references/saas.models.resource-config.operation-variant-for-key.md +6 -1
  458. package/dist/knowledge/references/saas.models.resource-config.queue-policy.md +49 -0
  459. package/dist/knowledge/references/saas.models.resource-config.required-features.md +84 -0
  460. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +10 -0
  461. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +14 -0
  462. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +111 -4
  463. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +39 -0
  464. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +48 -0
  465. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +38 -0
  466. package/dist/knowledge/references/saas.models.resource-primary-scope.md +11 -2
  467. package/dist/knowledge/references/saas.models.scope-membership.md +3 -4
  468. package/dist/knowledge/references/saas.models.shared-saas-module.md +25 -0
  469. package/dist/knowledge/references/saas.models.systems-of-record.md +635 -0
  470. package/dist/knowledge/references/saas.public-runtime.contract.md +198 -1
  471. package/dist/knowledge/references/saas.rag.retrieval-result.md +19 -8
  472. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +29 -0
  473. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +15 -36
  474. package/dist/knowledge/references/saas.specifications.application-document-publication.contract.md +9 -5
  475. package/dist/knowledge/references/saas.specifications.application-document-publication.generation.md +63 -0
  476. package/dist/knowledge/references/saas.specifications.application-document-release-set.contract.md +74 -0
  477. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +123 -0
  478. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +88 -7
  479. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +774 -53
  480. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +211 -14
  481. package/dist/knowledge/references/saas.specifications.composite-view-specification.md +10 -0
  482. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +364 -0
  483. package/dist/knowledge/references/saas.specifications.playbook-approval-and-failure-policies.md +96 -0
  484. package/dist/knowledge/references/saas.specifications.processor-register.md +333 -0
  485. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +8 -0
  486. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +22 -0
  487. package/dist/knowledge/references/saas.website.astro.bridge.md +64 -2
  488. package/dist/knowledge/references/saas.website.astro.head-renderer.md +32 -12
  489. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  490. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +14 -1
  491. package/dist/knowledge/references/saas.website.blog.bridge.md +21 -1
  492. package/dist/knowledge/references/saas.website.consent.banner.md +218 -0
  493. package/dist/knowledge/references/saas.website.consent.context.md +162 -0
  494. package/dist/knowledge/references/saas.website.consent.gate.md +38 -0
  495. package/dist/knowledge/references/saas.website.page-layout.component.md +67 -1
  496. package/dist/knowledge/references/saas.website.page.context.md +4 -3
  497. package/dist/knowledge/references/saas.website.runtime.context.md +43 -7
  498. package/dist/knowledge/references/saas.website.section.context.md +3 -2
  499. package/dist/knowledge/references/saas.website.sections.category-enum.md +19 -20
  500. package/dist/knowledge/references/vision.authored-metadata.config.md +2 -2
  501. package/dist/knowledge/references/website-plan.config.md +205 -0
  502. package/dist/knowledge/references/workers.node.worker-init-contract.md +57 -0
  503. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +43 -2
  504. package/dist/knowledge/references/zod.decorators.data-categories.md +197 -0
  505. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +51 -4
  506. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +54 -1
  507. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +35 -0
  508. package/dist/knowledge/references/zod.decorators.field-spec-params.md +32 -5
  509. package/dist/knowledge/references/zod.decorators.file-nature-constraints.md +86 -0
  510. package/dist/knowledge/references/zod.decorators.file-readiness-metadata.md +67 -0
  511. package/dist/knowledge/references/zod.decorators.file-schema.md +90 -14
  512. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +84 -0
  513. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +140 -4
  514. package/dist/knowledge/references/zod.decorators.primitive-ui.md +3 -0
  515. package/dist/knowledge/references/zod.decorators.rag-source.md +6 -2
  516. package/dist/knowledge/references/zod.decorators.schema-metadata.md +24 -0
  517. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +35 -0
  518. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +46 -12
  519. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +31 -12
  520. package/dist/knowledge/references/zod.factories.address.md +118 -0
  521. package/dist/knowledge/references/zod.factories.code.md +2 -0
  522. package/dist/knowledge/references/zod.factories.duration.md +2 -0
  523. package/dist/knowledge/references/zod.factories.money.md +2 -0
  524. package/dist/knowledge/references/zod.factories.phone.md +14 -1
  525. package/dist/knowledge/registries/assurance-authority-bases.json +3 -2
  526. package/dist/knowledge/registries/framework-topics.json +1215 -11
  527. package/dist/knowledge/registries/playbooks.json +454 -50
  528. package/dist/knowledge/registries/source-tags.json +3153 -1043
  529. package/dist/knowledge/rules/database-migration-obligation.md +110 -0
  530. package/dist/knowledge/rules/live-context-door.md +108 -0
  531. package/dist/knowledge/rules/resource-schema-awareness.md +75 -0
  532. package/dist/knowledge/skills/INDEX.md +46 -11
  533. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +80 -37
  534. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +167 -0
  535. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +6 -3
  536. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -3
  537. package/dist/knowledge/skills/application-database-migrations/references/framework-application-database-api.md +5 -2
  538. package/dist/knowledge/skills/application-database-migrations/references/migration-refusals.md +32 -0
  539. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +94 -3
  540. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +50 -0
  541. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +26 -19
  542. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +25 -1
  543. package/dist/knowledge/skills/backend-addon-wiring/references/framework-readiness-contributor-api.md +135 -0
  544. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +75 -12
  545. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +137 -0
  546. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-user-guidance-api.md +112 -0
  547. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +72 -1
  548. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +207 -0
  549. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +31 -1
  550. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-asset-api.md +8 -16
  551. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +25 -9
  552. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +135 -5
  553. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +80 -17
  554. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +369 -111
  555. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +32 -10
  556. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +103 -58
  557. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-publication-contract.md +19 -13
  558. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +142 -26
  559. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +722 -23
  560. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +348 -0
  561. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +123 -0
  562. package/dist/knowledge/skills/config-app-shell/SKILL.md +74 -11
  563. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +85 -19
  564. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +70 -0
  565. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +124 -0
  566. package/dist/knowledge/skills/config-design-system/SKILL.md +43 -3
  567. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +19 -10
  568. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +47 -0
  569. package/dist/knowledge/skills/config-design-system/references/surface-policy-authoring.md +19 -10
  570. package/dist/knowledge/skills/config-navigation/SKILL.md +85 -2
  571. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +98 -0
  572. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +2 -2
  573. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +54 -0
  574. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +232 -0
  575. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +172 -0
  576. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +146 -0
  577. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +141 -0
  578. package/dist/knowledge/skills/config-saas/SKILL.md +86 -9
  579. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +199 -0
  580. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +179 -0
  581. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +493 -0
  582. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +153 -0
  583. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +242 -0
  584. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +161 -0
  585. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +93 -12
  586. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +785 -0
  587. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +172 -0
  588. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +261 -9
  589. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +9 -0
  590. package/dist/knowledge/skills/config-saas-backend/SKILL.md +58 -3
  591. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +151 -0
  592. package/dist/knowledge/skills/config-saas-backend/references/framework-auth-methods-api.md +579 -0
  593. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +8 -2
  594. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +96 -0
  595. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +316 -0
  596. package/dist/knowledge/skills/config-saas-backend/references/framework-registration-config-api.md +221 -0
  597. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +121 -0
  598. package/dist/knowledge/skills/config-saas-backend/references/managed-startup-configuration.md +46 -0
  599. package/dist/knowledge/skills/configure-billing/SKILL.md +27 -22
  600. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +27 -15
  601. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +41 -0
  602. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +36 -17
  603. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +30 -28
  604. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +169 -0
  605. package/dist/knowledge/skills/configure-billing/references/framework-billing-resolution-failure-api.md +44 -11
  606. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +187 -0
  607. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +76 -0
  608. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +280 -0
  609. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +168 -0
  610. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +504 -0
  611. package/dist/knowledge/skills/email-add-template/SKILL.md +41 -69
  612. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +15 -7
  613. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +120 -0
  614. package/dist/knowledge/skills/engine-component-registration/SKILL.md +19 -12
  615. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +54 -31
  616. package/dist/knowledge/skills/engine-product-definitions/references/connected-feature-workflow.md +130 -0
  617. package/dist/knowledge/skills/engine-product-definitions/references/framework-engine-product-definitions-api.md +25 -0
  618. package/dist/knowledge/skills/engine-product-definitions/references/framework-feature-builders-api.md +215 -0
  619. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +78 -0
  620. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +33 -24
  621. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +121 -0
  622. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +4 -3
  623. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -8
  624. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +5 -4
  625. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +46 -9
  626. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +34 -7
  627. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +151 -0
  628. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +6 -10
  629. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +54 -5
  630. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +75 -21
  631. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +258 -0
  632. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +480 -0
  633. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +3983 -0
  634. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +211 -0
  635. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +165 -0
  636. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-elements-api.md +381 -0
  637. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-trigger-api.md +57 -0
  638. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-onboarding-view-api.md +89 -0
  639. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +13 -1
  640. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +14 -0
  641. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +14 -0
  642. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +3 -1
  643. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +14 -0
  644. package/dist/knowledge/skills/infra-environment-config/SKILL.md +237 -37
  645. package/dist/knowledge/skills/infra-environment-config/references/framework-application-database-api.md +5 -2
  646. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +174 -21
  647. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +206 -14
  648. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +95 -0
  649. package/dist/knowledge/skills/journey-approve/SKILL.md +28 -8
  650. package/dist/knowledge/skills/journey-approve/references/specification-family-map.md +88 -0
  651. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +37 -2
  652. package/dist/knowledge/skills/journey-next/SKILL.md +41 -1
  653. package/dist/knowledge/skills/journey-report/SKILL.md +16 -3
  654. package/dist/knowledge/skills/journey-run/SKILL.md +92 -7
  655. package/dist/knowledge/skills/journey-run/references/expert-personas-and-deliberations.md +46 -0
  656. package/dist/knowledge/skills/journey-run/references/framework-playbook-approval-policy.md +108 -0
  657. package/dist/knowledge/skills/journey-status/SKILL.md +14 -4
  658. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +153 -46
  659. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +119 -0
  660. package/dist/knowledge/skills/local-environment-bootstrap/references/initialization-recovery-recipe.md +7 -4
  661. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +253 -33
  662. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +1 -1
  663. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  664. package/dist/knowledge/skills/market-alternatives/SKILL.md +1 -1
  665. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-snapshot-api.md +12 -9
  666. package/dist/knowledge/skills/market-channels/SKILL.md +3 -3
  667. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +226 -14
  668. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +226 -14
  669. package/dist/knowledge/skills/market-generation-cli/SKILL.md +56 -9
  670. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +32 -9
  671. package/dist/knowledge/skills/market-icp/SKILL.md +2 -2
  672. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +3 -3
  673. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -2
  674. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +17 -2
  675. package/dist/knowledge/skills/market-persona/SKILL.md +2 -2
  676. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +2 -2
  677. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -0
  678. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +15 -0
  679. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +1 -1
  680. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +1 -1
  681. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +198 -0
  682. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-celebration-overlay-contract.md +51 -0
  683. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-celebration-api.md +79 -0
  684. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-milestone-definition-api.md +220 -0
  685. package/dist/knowledge/skills/milestones-and-celebrations/references/framework-progression-tracker-api.md +86 -0
  686. package/dist/knowledge/skills/minion-authoring/SKILL.md +140 -0
  687. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +84 -0
  688. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +91 -0
  689. package/dist/knowledge/skills/module-companion-exports/SKILL.md +38 -3
  690. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +211 -14
  691. package/dist/knowledge/skills/module-registration/SKILL.md +50 -33
  692. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +50 -1
  693. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +142 -0
  694. package/dist/knowledge/skills/module-registration/references/registry-files.md +14 -5
  695. package/dist/knowledge/skills/module-relationships/SKILL.md +62 -0
  696. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +26 -5
  697. package/dist/knowledge/skills/provider-backend-package/SKILL.md +279 -0
  698. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +80 -0
  699. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +55 -0
  700. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-convention-api.md +48 -0
  701. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +33 -6
  702. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-file-provider-constraints-api.md +99 -47
  703. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +241 -9
  704. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +196 -0
  705. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +50 -0
  706. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +80 -0
  707. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +71 -0
  708. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +58 -0
  709. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +275 -0
  710. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +64 -11
  711. package/dist/knowledge/skills/rate-limit-authoring/references/fixed-window-and-environment-multiplier.md +27 -0
  712. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +19 -6
  713. package/dist/knowledge/skills/resource-add-field/SKILL.md +12 -5
  714. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +373 -23
  715. package/dist/knowledge/skills/resource-add-module/SKILL.md +116 -265
  716. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +133 -0
  717. package/dist/knowledge/skills/resource-add-module/references/framework-new-module-wiring-api.md +25 -0
  718. package/dist/knowledge/skills/resource-add-module/references/module-scaffold-layout.md +12 -12
  719. package/dist/knowledge/skills/resource-add-resource/SKILL.md +26 -3
  720. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +122 -4
  721. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +25 -0
  722. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +93 -0
  723. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +136 -0
  724. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +85 -0
  725. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +133 -0
  726. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +141 -0
  727. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-step-up-api.md +126 -0
  728. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +859 -0
  729. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +122 -0
  730. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +124 -0
  731. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +97 -2
  732. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +457 -15
  733. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +197 -0
  734. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +162 -46
  735. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +452 -0
  736. package/dist/knowledge/skills/resource-custom-view/SKILL.md +5 -0
  737. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +327 -11
  738. package/dist/knowledge/skills/resource-custom-view/references/framework-user-facing-error-message-api.md +50 -0
  739. package/dist/knowledge/skills/resource-external-data/SKILL.md +228 -15
  740. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +54 -7
  741. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +87 -113
  742. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +13 -8
  743. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +69 -26
  744. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +246 -0
  745. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +7 -6
  746. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +5 -3
  747. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +43 -48
  748. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +96 -14
  749. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +47 -15
  750. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +6 -2
  751. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +32 -2
  752. package/dist/knowledge/skills/resource-schema-authoring/examples/basic-resource-schema.example.md +2 -1
  753. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +17 -0
  754. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +75 -4
  755. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +182 -0
  756. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +245 -0
  757. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +35 -0
  758. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +46 -12
  759. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +480 -15
  760. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +67 -0
  761. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +74 -14
  762. package/dist/knowledge/skills/resource-schema-authoring/references/polymorphic-per-scope-resources.md +28 -5
  763. package/dist/knowledge/skills/resource-schema-authoring/references/schema-variants-and-discriminators.md +25 -0
  764. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -1
  765. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +34 -0
  766. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +236 -18
  767. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +54 -1
  768. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +35 -0
  769. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +327 -11
  770. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +140 -4
  771. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +3 -0
  772. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +155 -5
  773. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +165 -0
  774. package/dist/knowledge/skills/seeding-authoring/SKILL.md +9 -1
  775. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +4 -0
  776. package/dist/knowledge/skills/seeding-operations/SKILL.md +33 -29
  777. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +13 -5
  778. package/dist/knowledge/skills/seeding-operations/references/data-seeding-cron-scheduler.md +67 -74
  779. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +97 -24
  780. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +205 -0
  781. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +205 -0
  782. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +229 -0
  783. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +38 -3
  784. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +211 -14
  785. package/dist/knowledge/skills/spec-component-update/SKILL.md +30 -11
  786. package/dist/knowledge/skills/spec-composite-view-update/references/framework-composite-view-specification-api.md +10 -0
  787. package/dist/knowledge/skills/spec-feature-update/SKILL.md +47 -9
  788. package/dist/knowledge/skills/spec-resource-update/SKILL.md +3 -0
  789. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +32 -5
  790. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +30 -0
  791. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +1 -0
  792. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +13 -2
  793. package/dist/knowledge/skills/views-add-custom-view/references/framework-view-scope-and-full-custom-api.md +24 -0
  794. package/dist/knowledge/skills/views-app-level/SKILL.md +1 -0
  795. package/dist/knowledge/skills/views-app-level/references/framework-view-scope-and-full-custom-api.md +24 -0
  796. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +1 -0
  797. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +1 -0
  798. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +64 -0
  799. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +3 -0
  800. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +3 -3
  801. package/dist/knowledge/skills/views-execution-authoring/references/framework-user-facing-error-message-api.md +50 -0
  802. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +43 -7
  803. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +21 -1
  804. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +21 -0
  805. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +41 -1
  806. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +735 -211
  807. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +54 -7
  808. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +67 -1
  809. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -0
  810. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +19 -5
  811. package/dist/knowledge/skills/website-page-authoring/SKILL.md +94 -7
  812. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +126 -0
  813. package/dist/knowledge/skills/website-section-contact/SKILL.md +96 -146
  814. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -20
  815. package/dist/knowledge/skills/website-section-cta/SKILL.md +19 -20
  816. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -20
  817. package/dist/knowledge/skills/website-section-faq/SKILL.md +19 -20
  818. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -20
  819. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +19 -20
  820. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -20
  821. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +19 -20
  822. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -20
  823. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +19 -20
  824. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -20
  825. package/dist/knowledge/skills/website-section-hero/SKILL.md +37 -26
  826. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -20
  827. package/dist/knowledge/skills/website-section-pricing/SKILL.md +19 -20
  828. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -20
  829. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +19 -20
  830. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -20
  831. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +14 -1
  832. package/dist/knowledge/skills/worker-authoring/SKILL.md +164 -0
  833. package/dist/knowledge/skills/worker-authoring/examples/worker-route.example.md +98 -0
  834. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +65 -0
  835. package/dist/knowledge/topic-index.json +5335 -1010
  836. package/dist/tsconfig.build.tsbuildinfo +1 -1
  837. package/dist/tsconfig.tsbuildinfo +1 -1
  838. package/package.json +4 -4
  839. package/dist/knowledge/references/example.provider.contribution.backend-billing.md +0 -12
  840. package/dist/knowledge/skills/configure-billing/references/example-provider-contribution-and-backend-config.md +0 -48
  841. /package/dist/knowledge/playbooks/{top_down.market-analysis → top_down.market-snapshot-produce}/structured-artifact-action.json +0 -0
@@ -1,9 +1,8 @@
1
1
  {
2
2
  "ref": "refinement.compliance-document-candidate",
3
- "version": "0.1.0",
3
+ "version": "0.7.0",
4
4
  "phase": "refinement",
5
5
  "intent": "Propose structured privacy-notice or service-terms candidate content from the application's accepted document facts. The companion agent may draft prose but cannot invent a fact, decide a legal question, approve, release or publish the document: every clause it writes is checked against the `document-facts` family, and a clause asserting a fact the application never declared is refused before it becomes a file.",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
7
  {
9
8
  "kind": "artifact_expected",
@@ -21,25 +20,33 @@
21
20
  {
22
21
  "family": "compliance-document-candidate",
23
22
  "schemaRef": "saas-specifications:ComplianceDocumentCandidate",
24
- "placement": "specifications/src/compliance-document-candidates/",
25
23
  "description": "An untrusted structured content proposal that lands as a FILE for a human to read and commit. Its clauses are validated against the application's accepted document facts before the write; landing is never an approval, a release or a publication. Nothing is sealed — the draft is accepted by being committed."
26
24
  }
27
25
  ],
26
+ "stepOutputs": [],
28
27
  "method": {
29
- "guidance": "# Compliance document candidate method\n\nUse the `compliance-document-authoring` skill and the exact host-supplied\nblueprint and fact projection. Produce only the structured\n`ApplicationAssuranceDocumentCandidateContentDraftV1` proposal requested by the\nhost.\n\nPreserve section and clause order, exact semantic refs, fact bindings,\nsource-policy refs, claim-guard refs, variant selections, review checklists and\nlimitations. Do not fill an unresolved fact, infer a legal decision, copy\nrestricted text, or describe the candidate as approved, compliant, legally\nvalid, released or published.\n\nLocale and jurisdiction are candidate review inputs, not proof of legal\napplicability. Leave every unresolved or unsupported item visible. The trusted\nruntime—not this method—validates the proposal, derives candidate status and\nseals exact content and provenance digests.\n",
28
+ "guidance": "# Compliance document candidate method\n\nYou are drafting ONE governed document for this application, from what the application has already\ndeclared. Follow the `compliance-document-authoring` skill for the rules — its full text is in your\nbrief, under \"The skills this method tells you to FOLLOW\", because this step has no tools and cannot\nopen a file. This method says which document, what shape, and what the two closed vocabularies are.\n\n## Choose the document, from the two this lane may draft\n\n`documentRef` must be one of six and the contract refuses anything else, but only two of the six are\nYOURS. The four internal `governance.*` documents belong to `refinement.governance-document-candidate`,\nwhich ships their blueprints; drafting one here would mean writing a document whose obligations you were\nnever given.\n\n| `documentRef` | what it is | drafted by |\n|---|---|---|\n| `document:public.privacy-notice` | what personal data the application holds and what happens to it | **this lane** |\n| `document:public.service-terms` | the commercial and service relationship | **this lane** |\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | `refinement.governance-document-candidate` |\n| `document:governance.roles-responsibilities` | who is accountable for what | `refinement.governance-document-candidate` |\n| `document:governance.program-handbook` | how the governance program runs | `refinement.governance-document-candidate` |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | `refinement.governance-document-candidate` |\n\n**Draft a document this application does not already hold.** The run tells you which those are: the\nbrief opens with what the application has already drafted, listing each document it may produce here\nas ALREADY DRAFTED or not yet drafted. Drafts are keyed by `documentRef`, so drafting one that is\nalready there REPLACES it — right when that draft is wrong, and a wasted run when it is not.\n\nWhere several remain, the **privacy notice** comes first: it is the one every application holding\npersonal data needs. Where none remains, the honest reason to draft again is that a held draft is\nwrong — say which one and why in your own reasoning, rather than redrafting the first on the list.\n\nThis paragraph used to read \"draft the privacy notice unless the run tells you otherwise\", at a time\nwhen no run told it anything. Measured against a real application on 2026-09-16: with its privacy\nnotice already drafted, two consecutive runs meant to produce the service terms drafted the notice\nagain and replaced it, and the application finished each run holding exactly what it started with.\nThe second sentence was stale as well — it said the privacy notice was \"the only one whose facts the\ncurrent derivation supplies\", which stopped being true once the fact-declaring playbook began\ndeclaring the account, billing and AI facts the service terms rest on.\n\nNaming a document outside this set is not a smaller decision than it looks. Each of the six has a\nconcern composition the framework measures a draft against, so a seventh name is a document nobody can\nstate the gaps in — and stating the gaps is the whole point.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef`, from the closed compliance-concern vocabulary. **The composition\nfor each document is inlined at the end of this method** — one entry per concern, saying what it\nasserts, what in the application it derives from, what state it usually reaches, and what closes it\nwhen it cannot. Draft one section per concern, in the order given, and produce **every** one:\na concern nothing can answer becomes a section with a marked clause, never a missing heading.\n\nThose entries are the difference between a draft that states its gaps and one that guesses at them.\nWhere a concern's entry names an issue number as the remedy, say so in `incompleteness.closedBy` —\n`#89`, `#91` — because a numbered issue is a remedy a reader can open, and \"application configuration\nowner\" is not.\n\nUse `concernRef: null` only for a section that genuinely answers no concern: a preamble, a contact\nblock. It is not a way past a concern you found hard. A concern you cannot establish gets a SECTION,\nwith a clause marked incomplete — which is the mechanism this whole document exists around.\n\nThe value must be the concern's exact name. A near miss (`retention` for `retention-and-deletion`) is\nworse than a null: it reports the concern as unaddressed while the document addresses it.\n\n\n## And SAY which required parts the section supplies\n\nEvery section also carries `satisfiesSectionRefs`: the refs, from the document definition rendered in\nyour brief, that this section actually addresses. This is a different question from `concernRef` and\nboth are answered — the concern says what compliance TOPIC the section is about, the satisfied refs\nsay what part of THIS document it supplies.\n\nYou are asked for the join because you are the only reader that holds both. The concern set is one\nflat vocabulary spanning every document type; the required parts are defined per document, and the\nsame concern does not sit under the same heading in a privacy notice and a governance handbook. A\nmapping written once in the framework would have to pick one answer and be wrong somewhere.\n\n- A section may claim several refs, and several sections may claim one between them.\n- A section that answers no required part — a preamble, a contact block — answers `null`. Not an\n empty list: `null` and `[]` would be two spellings of one state, and the contract refuses the second.\n- **Claim honestly.** A required ref nobody claims is reported as a part the document may not address,\n which is a true and useful finding. Claiming one you did not address hides that, and nothing\n downstream reads your prose to catch it.\n\nDo NOT adopt the definition's refs as your own `sectionRef` values. Your section set is the concern\nrule above; these are a claim you attach to it, not names you take.\n\n**Clauses carry the same claim**, as `satisfiesClauseRefs`, and answer `null` the same way. Your brief\nlists the blueprint's clauses under each section, each marked REQUIRED or CONDITIONAL; name the ones\nyour clause supplies.\n\nBoth keys were ASKED FOR HERE and absent from the strict contract you answer until 2026-09-02, so a\ndraft that followed this section could not parse and every landed document claimed nothing. If you\nare reading a document produced before then, its empty coverage is that defect and not a finding\nabout the document.\n\n- Several of your clauses may supply one blueprint clause between them, and one clause may supply\n several.\n- A clause supplying none — a transition, a heading gloss — claims none.\n- **Only the clauses marked REQUIRED are owed.** A CONDITIONAL clause is supplied when its condition\n holds and correctly omitted otherwise, so leaving one unclaimed is not a gap.\n\nThis is the anchor a clause did not previously have. A fact is named by the catalog and a section\ncarries its concern, so both survive a redraft; a clause was named freely and joined to nothing, which\nis why a reviewer who approved one could not find it in the next revision.\n## What a clause may say\n\nThe rule is ASSERT versus MARK, and the skill states it in full. In short: a clause may say \"this is\nnot yet established\"; it may not say something untrue.\n\n- `DERIVED` — established by a fact this application has declared. Cite it in `factRefs`. A `DERIVED`\n clause citing a fact the facts file does not declare is REFUSED before the write.\n\n **This is decided against the facts file as it stands NOW, not against any earlier draft.** You are\n producing the whole document from what the application currently declares, so a concern the facts\n answer today is `DERIVED` today — even if a previous version of this document marked it incomplete\n and is still in the tree. Re-running this playbook is how a document that went stale is repaired,\n and it only repairs anything if the re-draft is willing to close a mark.\n\n **A fact the application declared NOT APPLICABLE is a fact, and a clause may rest on it.** *\"No\n external analytics provider is configured\"* is `DERIVED`, not incomplete: the application settled the\n question and recorded the answer. Marking such a concern incomplete says the application does not\n know something it does know, which is as wrong as overstating. What is refused is citing a fact the\n facts file does not declare AT ALL.\n- `NEEDS_FRAMEWORK` / `NEEDS_DECISION` / `NEEDS_CONFIGURATION` — mark it, and say in `incompleteness`\n what is missing and who closes it. Four distinct suppliers, four distinct remedies; do not merge them.\n\n **When what is missing is a FACT, name it in `incompleteness.awaitingFactRefs`.** The skill argues\n this in full; the short version is that a marked clause asserts an ABSENCE in the application's own\n configuration, and that assertion goes false the moment someone declares the thing — silently, since\n nothing about the document changes. The awaited ref is what lets generation, landing and the\n standing coherence report all say the clause has gone stale. A clause that awaits nothing rots\n unobserved, and one already has.\n\n **`NEEDS_DECISION` and `NEEDS_FRAMEWORK` are the pair most easily confused, and the difference is\n the REMEDY.** `NEEDS_DECISION` means a surface exists and nobody filled it in — the reader goes and\n answers. `NEEDS_FRAMEWORK` means there is NOWHERE to record the answer; telling a reader to decide\n is telling them to write into a void.\n\n Measured on 2026-08-30, a produced notice marked operator identity `NEEDS_DECISION` when no surface\n for it existed at all, beside retention periods marked identically and genuinely just unfilled. Two\n remedies, rendered the same, and a reader could act on neither.\n\n **So every incomplete clause must NAME THE SURFACE its answer goes to**, or say plainly that none\n exists. A gap with a named surface is a task; a gap without one is a request for work nobody has\n scoped. The fragment you are working from names the surface where there is one — carry it into\n `incompleteness` rather than leaving the reader to find it.\n\n **`closedBy` must name WHO can reach that surface, and an ENGINE resource is not the application\n author's to edit.** `retentionPolicy`, `systemAccessPolicy.exportSubject` and `.dataCategories()`\n on an engine resource live in engine source. Writing \"application authors must declare\n `retentionPolicy` for each affected engine resource\" hands the reader a task they cannot perform —\n and a produced notice said exactly that, for 83 resources, in the same confident register as the\n remedies that ARE actionable. An unreachable remedy is worse than an unnamed one: it looks like\n work, gets scheduled, and fails when someone tries it.\n\n Where the closer is the FRAMEWORK, say so plainly — \"the framework must declare these on its own\n resources\" — and keep it separate from what this application owes.\n\nNever fill an unresolved fact, infer a legal decision, or describe the draft as approved, compliant,\nlegally valid, released or published. Locale and jurisdiction are review inputs; leaving them\nunresolved is a legitimate answer and never a reason not to draft.\n\n**And the mirror of that, which matters just as much: a missing approval never stops you.** Approval\nhappens at the END and is a human commit; a downstream release can be composed and MARKED\n`UNAPPROVED`. So the absence of one is a STATE to record, never a reason to produce nothing and never\nan outcome to report as blocked. The two failures are symmetric — claiming an approval that did not\nhappen, and refusing to act because it has not happened yet — and a compliance workflow standing in\nfront of the application-creation mechanism is the second one.\n\n## The refs you write, and their exact shape\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. `clause:retention-duration-not-declared` is one; `clause:Retention Duration` is not, and a\nwhole draft is rejected for a single malformed one. Ref ARRAYS are arrays of those strings — never\nobjects, never `{ ref: … }`.\n\nPer clause, all three ref arrays are required. Two of them may be empty, but **not both of the\nfirst two at once** — a clause that names no fact and no policy is sourced by nothing and is\nrejected:\n\n- `factRefs` — the facts this clause rests on, exactly as the facts file declares them. It may be\n EMPTY for a clause that establishes nothing (a marked clause often does).\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and nothing else.\n Every entry must be in the `policy:` namespace (`policy:retention`, `policy:recipients`,\n `policy:security-controls`); any other namespace is rejected outright. **Do NOT put a fact\n authority here.** A clause resting on declared facts already cites its authorities through\n `factRefs`, which resolves them — repeating them here duplicates the citation beside it and\n resolves to nothing. So this array is EMPTY for a fact-backed clause, and carries a policy area\n for a clause that is sourced from a policy rather than from a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. These are the\n boundaries you are already holding — `claim-guard:no-legal-applicability-claim`,\n `claim-guard:no-invented-retention-period`, `claim-guard:known-fact-only`. Name the ones that apply\n to this clause; do not repeat the same guard on every clause out of habit. You do not name the\n CATALOG's guard for the material: it is added for you from the blueprint clauses this clause\n `satisfiesClauseRefs`, so a clause that says what it satisfies is checked against it automatically.\n\n`evidenceRefs` is **`null` on every clause of a public document**, and that is not a gap to work around.\nIt cites a judged run from this application's own assurance repository — self-attested internal\nevidence — and a public notice may carry none, whatever the run says: a reader of one cannot weigh an\noperator's judgement of its own product, and any citation here is refused before the draft becomes a\nfile. That evidence belongs to the internal governance documents, which\n`refinement.governance-document-candidate` draws. Where you would have leaned on a measurement, say\nwhat is CONFIGURED or DECLARED, or MARK the statement.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`) — what a human must confirm before\nthis draft is worth anything. `limitationRefs` may be empty, but rarely should be: it is where you say\nwhat the document does NOT cover, in your own words as the drafter, rather than leaving the reader to\ndiscover it.\n\n## You do not compose the release — and a release nobody approved is marked UNAPPROVED\n\nYou draft the candidate. You do NOT author its release, and that is a boundary rather than an\nomission: almost everything a release carries is DERIVED from the accepted document definition — the\ndocument's class, who it addresses, which channels may carry it, which interactions it permits — and\na model restating those would create five ways to disagree with the catalog, invisibly. The rest\n(which declared variant, when it takes effect) is a composition over families you are not holding.\n\nA human declares a release DECISION in the application's\n`specifications/src/document-releases/compositions.ts`, and `wildo config document-releases` composes\neach decision not yet recorded — your candidate plus the declared variant and release policy — and\nrecords the finished release, text included. Nothing records a release because you landed a draft: an\napplication with no decision holds no release yet, which is a valid state and not yours to fix from\nthis playbook. Until a public document (privacy notice, service terms) has a release, its public page\nshows your latest draft, marked as a draft — so what you mark as not established is what a reader sees.\nWhat matters for your work is what composition produces when it runs: a release carrying\n`approvalState`, and one nobody has approved is `UNAPPROVED` and exists anyway.\n\n**Which is why a missing approval never changes what you do here.** Draft the document completely,\nmark every statement you cannot establish, and let the release be composed and marked. Waiting for an\napproval before drafting — or describing a draft as approved to get past the gate — are the two\nsymmetric failures, and the first is a compliance workflow standing in front of the mechanism that\nbuilds the application.\n\n## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit. It is\naccepted by a commit and by nothing else; who makes that commit is the host's autonomy posture, and\nonly a PERSON's commit is an approval. Landing is not approval, release or publication — and neither is\na commit the development companion authors under the YOLO posture.\n\n\n---\n\n# The compositions\n\nEach of the following is one document's full concern list. Use the one matching your `documentRef`\nand ignore the rest.\n\n## `document:public.privacy-notice` — thirteen concerns\n\n### Concern: operator identity\n\n**Asserts** — who legally operates the service: entity name, registered address, contact route for\ndata-protection questions, and a representative where one is required.\n\n**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its\nregistered address, the privacy contact route, and an Art. 27 representative where one is required.\n\nThe VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.\nWhat the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment\nsaid \"no engine change would close it\", which was right about derivation and wrong about the home.\nThe consequence was concrete. A landing REPLACES the produced document on every run, so an operator\nwho answered by editing the document lost the answer at the next regeneration — the answer has to live\nin the application or it does not survive.\n\n**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.\n\n⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface\nexists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is\nand nobody has. They have different remedies — build something, versus fill something in — and a\nreader who cannot tell them apart cannot act on either. Say which surface the answer goes to.\n\n**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be\nfilled in later without redrafting anything around it, which is the reason it is not a blocker.\n\n**Never infer it.** Not from the application name, not from a domain, not from another application,\nnot from model memory. A published legal document naming the wrong entity is worse than one that says\nthe entity is not yet recorded — the first misdirects a person exercising a right, the second tells\nthem the document is incomplete.\n\n**Every document needs this fragment**, which makes it the clearest demonstration of why producing\nwith gaps beats blocking: the whole document set would be unproducible until one form is filled in.\n\n\n### Concern: legal basis and controller/processor role\n\n**Asserts** — the lawful basis for each processing purpose, and whether the operator acts as\ncontroller or processor for it.\n\n**Derives from** — `operatorComplianceIdentity.lawfulBases` and `.roleAllocations` in\n`wildo.saas.config.ts`.\n\nThe DETERMINATIONS are never derivable — both are legal conclusions about the operator's own\narrangements, and the framework can show WHAT is processed and BY WHICH MECHANISM without establishing\nunder which basis or in which role. What it now provides is where to record the conclusion, so that a\nregeneration reproduces it instead of destroying it.\n\n**The role is a LIST, not a field, and the produced notice said so before the surface existed:**\n*\"This notice therefore does not assign a single legal role to all data processed in a workspace.\"* A\nB2B SaaS is typically a processor for the records its customers put in and a controller for its\naccount holders' own data, simultaneously. `roleAllocations` carries one role per population, and a\ndocument that collapses them into one is wrong about both.\n\n**The `lawful-bases` fact is COMPUTED from `lawfulBases`** — every purpose, its basis and, for\nlegitimate interests, the assessment. You never declare it: a restatement would be a second copy of the\noperator's decision that nothing compares with the first. Absent bases leave the fact absent.\n\n**`LEGITIMATE_INTERESTS` cannot be declared without its assessment** — the schema refuses it. It is\nthe only Art. 6(1) basis whose lawfulness depends on a balancing test, so the bare claim asserts a\nconclusion nobody reached.\n\n**Completeness** — `DERIVED` when declared; `NEEDS_DECISION` when not. Never `NEEDS_FRAMEWORK`: there\nis a surface, so the remedy is to fill it in, not to build something. Name the surface when reporting\nthe gap.\n\n**What closes it** — the operator determining, per purpose, the basis and the role, ideally with\ncounsel, and declaring them in `operatorComplianceIdentity`. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for\nthe data a customer stores about its own people, controller for the data the operator holds about\naccount holders — but describing the common shape is not the same as determining this operator's, and\nthe produced document must not present the first as the second.\n\n**This is the fragment most likely to be filled in by a confident guess**, because the shape is\nfamiliar and the sentence is easy to write. Resist it. A basis stated in a published notice is a\nposition the operator has taken; a basis that was never determined is a position nobody can defend.\n\n\n### Concern: personal data held\n\n**Asserts** — which of the application's own records are about identifiable people, and which hold no\npersonal data of their own.\n\n**Derives from** — each resource's `retentionPolicy.mode` (`ErasureRetentionMode`, in\n`@wildo-ai/saas-models`), read for every resource the application declares:\n\n| declaration | what the document may state |\n|---|---|\n| `RETAIN_AND_IMPERSONALIZE` | this record holds personal data; the fields marked `.impersonalizeWith()` are what is scrubbed on erasure |\n| `RETAIN_ONLY` | this record holds **no personal data of its own** — a positive, factory-enforced statement, because declaring a scrub treatment under this mode fails at config build |\n| absent | the application has not said |\n\nRead `dataSubjectPolicy.kind` for the SESSION question only. `NO_PRINCIPAL` is equally true of an\ninvoice and of a CRM contact, so it never tells you whether a record is about a person — the\nretention mode does.\n\n**Completeness** — `DERIVED` for every resource that declares a retention policy.\n\n**An erasure-coverage gap does NOT license a claim about whether personal data is held.** The two are\ndifferent axes and the facts report them separately: `retentionPolicy` answers *what happens to this\nrow on erasure*, while a field's `.dataCategories()` answers *what kind of data is in it*. A resource\ncan declare the second and not the first, and 48 of the engine's 85 do.\n\nSo writing \"N resources have no declared erasure treatment, so this notice cannot establish whether\nthey hold personal data\" is an over-reach, and it contradicts the data-categories section of the same\ndocument — which enumerates categories drawn from those very resources. It was produced twice on\n2026-08-30 before this paragraph existed.\n\nState the gap as what it is: those resources have not declared an erasure TREATMENT, so a notice\ncannot say what an erasure does to them. Where the facts also report a category coverage for the same\norigin, say what IS established alongside it.\n`NEEDS_CONFIGURATION` for every resource that does not.\n\n**What closes it** — the application's own authors declaring `retentionPolicy` on the resource. Name\nthe resources individually: the remedy is per-resource, and a count is not actionable.\n\n\n### Concern: data categories\n\n**Asserts** — which CATEGORIES of personal data are held: identity, contact details, credentials,\nfinancial, usage, location, user content, professional, and any GDPR Art. 9 special-category or\nArt. 10 criminal-offence data.\n\n**Derives from** — each field's `.dataCategories()` declaration, reported per resource and unioned\nacross the application in the compliance-primary-facts section. One category is DERIVED rather than\ndeclared: `credentials`, from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, which are\nmarkers the author already wrote.\n\n**Nothing is derived from a field NAME.** `email`, `phone` and `dateOfBirth` are suggestive while\n`notes` is not, so a category list assembled by pattern-matching identifiers is a guess presented as\nan inventory — and its failure mode is silent, because whatever the guess misses is simply not\ndisclosed. The declaration exists so that never happens.\n\n**Completeness** — `DERIVED` when the application declares categories; `NEEDS_CONFIGURATION` when it\ndeclares none, or when the facts section lists OUTSTANDING fields.\n\n**The two gaps are different and must not be written the same way.**\n\n- A resource that declares no category at all may genuinely hold no personal data. Nothing\n distinguishes \"considered and not applicable\" from \"never asked\", so state that the question is\n unanswered — never that the application holds no personal data.\n- A field the facts section lists as OUTSTANDING is a provable omission. The application already\n declared that field personal by another door — an erasure scrub treatment, a portability\n provenance, or a credential marker — so the missing category is an omission, not a judgement.\n Name the field and its basis. Do not guess what it contains.\n\n**Say WHICH special category, not that there is one.** A `special-category:*` value is Art. 9 data\nand carries a lawful-basis condition of its own beyond Art. 6; `criminal-offence` is Art. 10, a\nseparate article with a different condition. \"We process special category data\" is not a disclosure —\nthe enum names the kind precisely so a notice can.\n\n**Do NOT point at `Compliance_DataClassification`.** It exists, it is a four-level SENSITIVITY ladder\n(public / internal / confidential / restricted) applied only to flows-actors configuration, and it\nanswers \"how protected must this be\" rather than \"what kind of personal data is this\". Using it here\nwould produce a notice describing protection levels where a reader expects data types. It is named\nexplicitly because it is a near-miss a reader will otherwise find and assume answers this concern.\n\n\n### Concern: consent and preferences\n\n**Asserts** — what the application asks consent for, at what granularity, and what a person's choice\nactually controls.\n\n**Derives from**\n\n- `ConsentPurpose` (`@wildo-ai/saas-models`): `ANALYTICS` · `MARKETING` — a SET of purposes, each\n granted or not on its own. There is no ordering: agreeing to marketing says nothing about analytics.\n- per-person `privacy.consentedPurposes` — the purposes each person granted, empty until they grant\n one — and `privacy.consentDecidedAt`, stamped by the server when they decide. An empty set WITH an\n instant is \"declined everything\"; no instant is \"never asked\". A notice must not state the second\n as the first.\n- `analytics.requiresConsent` (default `true`) — whether the application's analytics rest on\n `ANALYTICS`. It governs analytics alone, never use of the service.\n- the visitor tier: a marketing website keeps a visitor's decision in their browser and starts a\n consent-based provider (product analytics) only once its purpose is granted.\n\n- `operatorComplianceIdentity.serviceConsentRequirement` (`wildo.saas.config.ts`) — what a person\n must agree to in order to use the service AT ALL, and what that gate covers.\n\n**An empty `requiredPurposes` is a POSITIVE answer and the usual one.** The operator declaring that nothing is gated on\nconsent has answered the question; a document must state it as settled rather than treating it as an\nabsence. ABSENT is the different case — nobody was asked — and the brief distinguishes the two.\n\n**A consent GATE is not a lawful BASIS.** For most B2B SaaS the basis for core processing is CONTRACT:\na person uses the product because their employer signed for it. A notice that reads a gate as a basis\nstates that their data is processed on consent they could withdraw, which is wrong about the single\nmost consequential thing in the document. The basis is declared per purpose in `lawfulBases`.\n\n**Completeness** — `DERIVED` for the analytics gate, each person's granted purposes, and the\nservice-wide requirement once declared — which the application ENFORCES: until the required purposes are\ngranted, the backend refuses every operation the person initiates — API and MCP operations, queued work,\nWebSocket reads and subscriptions, agent tools, retrieval, charts and analytics, A2A task reads, and A2A or\nWebSocket conversations, including resuming one after an approval — except their own profile and preferences,\nwhere they record the consent, and cancelling an A2A task they already started (signing in and out stay open;\nupdates the server pushes on its own are not held back), and the web\napplication withholds its pages; `NEEDS_DECISION` naming `serviceConsentRequirement` when it is not.\n\nThis was `NEEDS_FRAMEWORK` until 2026-08-30, correctly: there was nowhere to record the answer. Issue\n#139 built the surface, so the remedy changed from \"someone must build this\" to \"fill this in\" — a\ndifferent party and a different task, which is why the two states are never interchangeable.\n\n**Say the thing readers get wrong.** Consent is one lawful basis among several, and it is not the one\nmost B2B processing rests on. **Never write that all processing rests on consent, and never write\nthat accepting terms supplies a lawful basis** — accepting a contract is a different basis with\ndifferent consequences, and conflating them is the single most common defect in a generated privacy\nnotice. Which basis applies is a `NEEDS_DECISION`; see the legal-basis fragment.\n\n\n### Concern: retention and deletion\n\n**Asserts** — what happens to a record when its subject is erased, and how long records are kept.\n\nTwo questions, and the framework answers only the first.\n\n**Derives from (the HOW — answerable)** — each resource's `retentionPolicy.mode`:\n`RETAIN_AND_IMPERSONALIZE` keeps the row, freezes it, hides it from normal reads and scrubs the fields\nmarked `.impersonalizeWith()`; `RETAIN_ONLY` keeps and freezes a row that holds no personal data of\nits own. Reading the per-field treatments tells the document exactly WHICH values are destroyed and\nwhich survive, which is a genuinely strong statement most notices cannot make.\n\n**Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config\nover four data classes: `RESOURCE_DATA` (its records), `FILES` (uploaded bytes), `AUDIT_LOGS` (the\ntamper-evident trail, kept longest and for a different reason — it is the evidence an operator may\nlawfully retain under GDPR Art. 17(3)) and `OPERATIONAL_LOGS`. Each declared class carries a period in\ndays AND the operator's stated reason for it.\n\nThe classes are the STORES on purpose: the same declaration answers what a notice must state and what\na backup-and-restore inventory must protect (issue #8).\n\n**The `retention-rules` fact is COMPUTED from both** — the declared periods with their reasons, the\nclasses with no period, each resource's declared erasure treatment, and the resources declaring none.\nYou never declare it. It is absent when no schedule is declared, because a treatment alone would read as\nthe whole answer.\n\n**Completeness** — `DERIVED` for the treatment, and for each retention class the application HAS\ndeclared. `NEEDS_DECISION` for each class it has not: the mechanism exists, so what is missing is an\noperator's decision rather than an engine change. Do not let the derivable half hide the missing one —\na statement about erasure mechanics reads to a reader as an answer about retention, so both go in the\nsame breath.\n\n**What closes it** — the operator deciding a period, and saying why. Not a framework change: issue #89\ndelivered the declaration surface, so an undeclared class is now an unanswered question rather than an\nunaskable one.\n\n**An UNDECLARED class is not \"kept indefinitely\" and not \"deleted immediately\".** It is a decision\nnobody has taken, and the document must say exactly that.\n\n**Never write a placeholder period.** \"Typically 12 months\" in a published notice is a commitment\nnobody made and nothing enforces.\n\n\n### Concern: recipients and processors\n\n**Asserts** — who else receives personal data, in what role, and where they process it.\n\n**Derives from (partial)** — the engine capabilities the application has a provider configured for\n(`EngineCapability` in `saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`).\nRuntime bindings establish the configured function — email delivery, storage, payments, LLM inference\nor observability. Deployment choices determine whether a third party operates that function; a\nconfigured capability alone does not establish a third-party recipient.\n\n**Derives from (the identities)** — the application's PROCESSOR REGISTER, which your brief renders\nunder *\"Who else processes personal data\"*. Per entry: the processor's **legal entity**, the\n**regions** it processes in, and its own **subprocessors** with their regions.\n\n**The register holds two kinds of entry and the brief labels them differently — say which.** A\nCONFIGURED PROVIDER entry joins to the application's composition, so it can be checked against it: a\nclaim about a provider the application does not configure is detectable, and a configured provider\nwith no entry is reported as UNDECLARED. An AUTHORED entry — a hosting company, a CDN, a support desk\n— joins to nothing, because no configuration mentions it. The framework can neither confirm it nor\nnotice its absence.\n\nBoth kinds of declared relationship can belong in the notice when their role is established. What\nmust 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\nas though the framework verified it overstates what anyone checked.\n\n**A SELF-HOSTED provider is not a recipient either, and this is the second way to get the section\nwrong.** The brief's *\"Who RUNS each bound provider\"* block splits runtime-bound providers three ways:\nTHIRD-PARTY RECIPIENTS (vendor-hosted, so data reaches a third party — enumerate these with their\nregion), OPERATOR-RUN (self-hosted, so no third party receives anything — state them as processing\nunder the operator's own control, never as recipients), and UNANSWERED.\n\nAn UNANSWERED provider is bound to a runtime with no declared deployment model. **Do not assume\nvendor-hosted.** It looks like the cautious reading and it is not: it publishes that a person's data\ngoes to a third party when nobody said so. Report it as not established, and name the surface —\n`providerComplianceChoices` in `wildo.saas.config.ts`.\n\n**A provider PROFILE is not a recipient.** The brief separates providers BOUND TO A RUNTIME — backend,\ncompanion, workers, minions, a frontend service, which can process the application's data — from\nprovider profiles with no runtime binding. A profile says how to reach a provider; build-time tooling\nlives there, and a coding agent operating on the workspace receives no customer records. Never name a\nprofile-only provider as a recipient. Naming one reads as caution and is a false statement about\nsomebody's data, exactly like omitting a real one.\n\nThe section joins the register to runtime-bound RECIPIENT CANDIDATES after excluding explicit\nself-hosted providers, so it tells you three different things\nand they are not interchangeable:\n\n- a candidate WITH an entry — its declared identity and regions are available. Establish its\n deployment role before presenting it as a recipient.\n- a candidate listed **UNDECLARED** — a runtime binding has no matching processor entry. Name its\n configured function and unresolved declarations; an unanswered deployment choice remains unknown,\n not automatically vendor-hosted. `NEEDS_DECISION`, resolved by the operator.\n- a provider entry listed **STALE** — it no longer matches the current recipient-candidate set.\n Reconcile the declaration and deployment choice; this check alone does not establish its actual\n historical processing or that all external data has been removed.\n\n**Completeness** — `DERIVED` per provider that is declared, `NEEDS_DECISION` per provider that is not.\nNot `NEEDS_FRAMEWORK` any more: issue #88 delivered the declaration surface, so an undeclared processor\nis an unanswered question rather than an unaskable one.\n\n**Never infer a region from a vendor's brand.** \"It is a US company\" is not a processing location, and\na transfer statement built on it is a claim about somebody's data made from a guess.\n\n**Distinguish the register declaration from its reconciliation.**\n\n| Observed state | What it establishes | What the document may say |\n| --- | --- | --- |\n| Register absent | No processor declaration was supplied | The operator has not established the register; do not infer recipients or their absence |\n| 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 |\n| 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 |\n\nReconcile only runtime-bound candidates. Exclude explicitly SELF_HOSTED providers and profile-only\nproviders; keep unanswered deployment choices visible as unanswered. `registerEstablishesNoProcessorRecipients`\nanswers the declaration question; `undeclaredProcessorRefs` answers candidate coverage. A true answer to\nthe first does not erase gaps returned by the second.\n\nName third-party recipients only when their role is established. An empty register does not justify\nan unconditional statement that third parties provide email, storage or payments. Equally, do not\nomit unresolved candidate questions and thereby imply that absence was verified. Authored recipients\nremain operator declarations whose completeness cannot be inferred from runtime bindings.\n\n\n### Concern: international transfers\n\n**Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer\nmechanism.\n\n**Derives from** — the processor register's regions, at BOTH levels: each declared processor and\neach processor's own subprocessors. Your brief renders them under *\"Personal data reaches processors\nin: …\"*.\n\nBoth levels, because the chain is what makes a transfer statement hard. An operator in France using a\nFrench vendor that runs on a US cloud HAS a transfer, and reading only the vendor's region misses it.\n\n**The question has three inputs, and the framework derives only one of them.** Where declared\nprocessors process is declared. Which jurisdiction is the ORIGIN is `operatingJurisdictions`. Which\nMECHANISM makes a given transfer lawful is a legal determination with a shelf life — adequacy decisions\nmove by court ruling — so the framework never computes it: the operator RECORDS it, per register entry,\nas a `transferDetermination`:\n\n- `NO_TRANSFER`, with the reason none of the entry's regions lies outside the origin jurisdictions —\n regions are free text, so this comparison is the operator's and never the framework's;\n- `TRANSFER`, with one safeguard per origin jurisdiction: the GDPR Chapter V mechanism\n (`ADEQUACY_DECISION`, `STANDARD_CONTRACTUAL_CLAUSES`, `BINDING_CORPORATE_RULES`,\n `APPROVED_CODE_OF_CONDUCT`, `APPROVED_CERTIFICATION`, or a `DEROGATION` naming its Art. 49 ground) and\n the instrument a reader could look up.\n\nThe determination sits on the ENTRY because the processor's own contract binds its onward transfers to\nits subprocessors; reaching the processor is the transfer the operator answers for.\n\n**The `international-transfers` fact is COMPUTED from those determinations** — you never declare it.\nIt carries each determined entry, the origin jurisdictions, `undeterminedRecipients` — a register entry\nwith no determination, or a configured provider the register does not establish — and `safeguardGaps`:\na declared origin a TRANSFER names no safeguard for.\n\n**Completeness** — do not round any state up.\n\n| the register | what you may state | completeness |\n|---|---|---|\n| ABSENT | nothing — where data lands is unknown, and the fact is absent | `NEEDS_CONFIGURATION` |\n| a recipient in `undeterminedRecipients` | that its transfer position is not determined; never fold it into \"no transfer\" | `NEEDS_DECISION` for that recipient |\n| declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |\n| 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 |\n\n**The residual is not optional wording.** \"No processor receives personal data\" establishes nothing\nabout the operator's OWN processing — its infrastructure, its staff, its own establishment. A document\nthat says \"we do not transfer data internationally\" on the strength of an empty register has answered\na larger question than it was asked.\n\n**What closes an undetermined entry** — the operator researching the vendor's data processing\nagreement and recording what it relies on, per origin jurisdiction. A vendor's DPA usually names it:\nstandard contractual clauses for EU data, the UK Addendum to them for UK data, and sometimes a\ncertification under an adequacy framework beside them. Record what the contract says, not what is\ntypical.\n\n**\"We do not transfer data internationally\" is a claim, not a default.** It may be true, and it is\ncitable when an application has declared it as a fact — but it must never be produced because nothing\nsaid otherwise. Absence of a region declaration means the region is unknown, which is the opposite of\nknowing it stays put.\n\n\n### Concern: automated decisions and AI\n\n**Asserts** — where the application uses AI, on what data, and whether any of it decides something\nabout a person.\n\n**Derives from (partial)** — the AI capabilities the application has a provider configured for:\n`AI_LLM`, `AI_EMBEDDINGS`, `AI_DOCUMENT_EXTRACTION`, `AI_CODING_AGENT`. That establishes that AI is in\nuse and for what function.\n\n**Not derivable** — whether any of it produces a **decision with a legal or similarly significant\neffect** on a person, and whether a human reviews it. Nothing in the framework declares consequence or\nhuman-review posture, and neither can be inferred from a capability being enabled.\n\n**Derives from (the consequence)** — the AI POSTURE section of your brief, per ENABLED AI capability:\nwhat it is used for, whether it `NO_DECISION` / `ASSISTS_HUMAN_DECISION` / `DECIDES_AUTONOMOUSLY`, and —\nwhere it decides anything — how a person obtains human intervention.\n\nAn application enabling NO AI capability gets a plain statement to that effect: it performs no AI\nprocessing of personal data. That is a positive, checkable answer, not a gap.\n\n**Completeness** — `DERIVED` per capability with a declared posture; `NEEDS_DECISION` per capability\nlisted OUTSTANDING. Not `NEEDS_FRAMEWORK` any more: issue #92 delivered the declaration, so an\nundeclared posture is an unanswered question rather than an unaskable one.\n\n**An OUTSTANDING capability is not a harmless one.** This is the one concern where silence is more\ndangerous than elsewhere: a notice describing AI use and saying nothing about consequence does not read\nas \"unknown\", it reads as \"nothing significant happens here\" — which is the exemption, claimed for\nfree. State the gap explicitly.\n\n**Why the distinction carries weight.** Automated decision-making with significant effects attracts\nspecific obligations — information about the logic, and a right to human intervention. A generated\nnotice must not silently claim the exemption by describing AI use without addressing consequence. The\nhonest statement says AI is used for these functions, and that whether any of it decides something\nabout a person is not yet established.\n\n\n### Concern: analytics and tracking\n\n**Asserts** — what is observed about how people use the service, and what a person's consent controls.\n\n**Derives from (partial)** — the observability and analytics capabilities the application has\nconfigured (`FRONTEND_PRODUCT_ANALYTICS`, `LLM_OBSERVABILITY`, `OBSERVABILITY_TELEMETRY`), together\nwith the consent posture: `analytics.requiresConsent` and each person's `privacy.consentedPurposes` make\n`ConsentPurpose.ANALYTICS` a real, enforced boundary rather than a stated intention — in the application,\nand on the marketing website, where a product-analytics provider does not start until a visitor grants it.\n\n**Derives from (the inventory)** — the CLIENT STORAGE section of your brief: each cookie and storage\nkey, its mechanism, purpose, necessity and lifetime, split by who sets it.\n\nThe FRAMEWORK's own entries are listed first and belong in every application's table — the cookies\n`__wildo_refresh` and `__wildo_anon_session`, strictly necessary, with lifetimes taken from the\napplication's session configuration, and the website's `__wildo_website_consent` storage key, strictly\nnecessary because it is what makes a visitor's refusal hold. **No application authored these and every application sets them**, so a table\nbuilt only from what the application declared would omit the session cookie, which is the entry a\nvisitor is most certain to have.\n\nThen, per frontend surface: its declared entries, an explicit \"sets nothing of its own\", or\nUNINVENTORIED.\n\n**UNINVENTORIED is not \"sets nothing\".** The first says nobody catalogued that surface; the second is a\npositive statement. Writing the second from the first tells a visitor they are tracked by less than they\nare, which is the under-reporting direction a notice must never fail in.\n\n**Completeness** — `DERIVED` for the capability and consent posture, and for each surface that IS\ninventoried; `NEEDS_DECISION` per uninventoried surface. Not `NEEDS_FRAMEWORK` any more: issue #91\ndelivered the declaration surface, so an uninventoried surface is an unanswered question rather than an\nunaskable one.\n\nSay both halves: which analytics are in use and what consent gates them (strong, derived, enforced), and\nwhat the table still lacks — naming the surfaces, not the concern.\n\n\n### Concern: subject rights\n\n**Asserts** — which request mechanisms the application configures, what they select and what their\nresults establish. A configured mechanism does not establish that a particular request was fulfilled.\n\n**Derives from**\n\n- `SubjectExportPurpose.ACCESS_ART_15` and `PORTABILITY_ART_20` — two selections over the declared\n subject relationships. Access includes eligible owned rows and non-owned rows referring to the\n subject. Portability applies narrower relationship and field-provenance selection. Neither is an\n unrestricted recursive export of everything reachable from an account.\n- Each participating resource's `systemAccessPolicy.exportSubject` — an explicit disclosure choice,\n checked before collection. Missing and forbidden are different decisions:\n\n| Declaration | Runtime result | Meaning for the request |\n| --- | --- | --- |\n| Absent on a participating resource | Refuses collection | A required disclosure decision is unanswered; no silently incomplete bundle is returned |\n| `ALLOWED` | Passes this disclosure gate | Relationship selection, system-read admission, field security and purpose-specific checks still apply |\n| `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 |\n| `FORBIDDEN` on the subject's own resource | Refuses the bundle | The subject cannot be omitted from its own export |\n\n- `portabilityPolicy.defaultProvenance` and per-field `.portabilityProvenance(...)` — the field\n declaration overrides the resource default. `SUBJECT_PROVIDED` and `OBSERVED` values are eligible\n for portability; `DERIVED` values are excluded and reported. Unresolved provenance refuses\n portability collection rather than silently dropping fields. Explicitly forbidden resources do\n not need portability provenance for this export because their rows are not collected. Access uses\n its separate field selection; backend-only and write-only fields remain withheld.\n- Erasure: `eraseSubjectAsSystem(resourceType, rowIds)`, invoked by the application's verified request\n workflow. A contact or lead without a login can still be a data subject. Retention, relationship\n treatments and account linkage are separate declarations; inspect the receipt before claiming\n completion, including dependent execution, session resolution and incomplete external effects.\n\n**The rights a notice states are COMPUTED, in the `rights-and-complaint-route` fact.** Which rights\napply, and where a person may complain, are the law of the regime each `operatingJurisdictions` entry\nfalls under, conditioned on the declared lawful bases: portability only for purposes resting on consent\nor contract, objection only for public task or legitimate interests, withdrawal of consent only where\nconsent is the basis. The channel is `privacyContact`; the verification step is the operator's\n`subjectRequestIdentityVerification`; who answers comes from `roleAllocations` — the operator for data it\ncontrols, the customer (with the operator forwarding and assisting) for data it processes on a\ncustomer's behalf. A jurisdiction no known regime reaches is named in `jurisdictionsWithoutKnownRegime`:\nstate that its rights are not established here, never borrow another regime's words for it.\n\n**Completeness** — derive the configured posture from actual resource declarations and the selected\nrelationships. Describe an unresolved declaration as a configuration refusal, an explicit exclusion\nas an exclusion, and an observed request outcome from its report. Declarations alone are not runtime\nproof that a right has been fulfilled.\n\n**What resolves a missing declaration** — the owning resource explicitly declares ALLOWED or FORBIDDEN\naccording to its intended disclosure policy. Portability additionally needs a valid resource default\nor field-level provenance for the fields it would collect. Do not ask a notice author to replace a\nmissing product declaration with a free-text promise.\n\n**Never state** that an undeclared participating resource is merely omitted while the remainder is\nexported. The runtime refuses collection. Preserve deliberate exclusions and explain their recorded\nreasons; the application's request workflow owns verification, protected delivery and any necessary\nfollow-up.\n\n\n### Concern: data exit\n\n**Asserts** — what a customer gets back when they leave, in what form, and what happens to what\nremains.\n\n**Derives from** — `SubjectExportPurpose.PORTABILITY_ART_20` and the resources declaring\n`exportSubject`; the account-closure path; and each resource's `retentionPolicy.mode`, which decides\nwhether a record is removed or **retained and impersonalized** on erasure.\n\n**Completeness** — `DERIVED` for the mechanism.\n\n**Retained-and-impersonalized is the part a reader must not be surprised by**, and the part a\ngenerated document most often gets wrong by omission. A retained row is kept, frozen, hidden from\nnormal reads and reachable only through an audited privileged path — it is not deleted. Say so. A\nnotice that implies everything is erased, when financial and audit records are lawfully retained with\ntheir personal fields scrubbed, is inaccurate in the direction that damages trust when discovered.\n\n**How LONG anything is retained is not derivable** — see the retention-and-deletion fragment.\n\n\n### Concern: tenancy model\n\n**Asserts** — that customer data is separated per organization, and where the boundary between the\noperator's responsibilities and the customer's lies.\n\n**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every\ntenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be\ndeclared and carry a usable access grant. The application audit viewer is a separate policy surface:\nit defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with\n`auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under\nwhich a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;\nrole-based access neither implies anonymized records nor supplies an approval that never occurred.\n\n**Completeness** — `DERIVED`.\n\n**This fragment is where shared responsibility is described, and it must never be flattened.** In a\nB2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a\nCONTROLLER for the data it holds about the customer's users as account holders. Those are different\nroles with different duties over the same database. Say which is which; do not pick one and apply it\nto everything.\n\n**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in\n`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer\nstores about its own people, CONTROLLER for the account data of the people who administer them. It is\na LIST for exactly the reason this fragment gives: those are different roles over the same database,\nand a single field would force one of them to be wrong.\n\nWhere the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the\nsurface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,\nso the remedy is to fill it in rather than to build something. See the legal-basis fragment.\n\n\n## `document:public.service-terms` — six concerns\n\n### Concern: service scope\n\n**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the\nsurfaces it exposes.\n\n**Derives from** — the application's declared modules and their resources, and the surfaces it builds\n(application, API, public website, technical documentation).\n\n**Completeness** — `DERIVED`.\n\n**Derive it; do not describe the product from its marketing.** Scope in a governed document is the\nboundary of what the statements around it apply to, so an aspirational description silently widens\nevery other clause. The declared modules are the honest boundary, and a capability the application\ndoes not run does not belong here even if it is on the roadmap.\n\n\n### Concern: commercial terms\n\n**Asserts** — what is sold, how it is charged, and what happens on renewal, change and cancellation.\n\n**Derives from** — the application's billing declarations\n(`saas-models` → `billing/billing-enums.shared.schemas.ts`): `ProductType`, `BillingTiming`,\n`ProrationBehavior`, `TaxCalculationMode`, plus the declared products and any usage metering.\n\n**Completeness** — `DERIVED` where billing is configured; `NEEDS_CONFIGURATION` where the application\ndeclares no products, in which case say that the commercial terms are not yet established rather than\ndescribing a plan nobody has authored.\n\n**Keep consumer and business audiences apart.** Consumer pre-contract obligations (withdrawal\nperiods, pre-contractual information) apply only when a declared audience includes consumers. A terms\ndocument that blends both into one ambiguous set is worse than one that states which audience it is\nfor — so read the declared audience before writing a single clause about cancellation rights.\n\n\n### Concern: governing law and liability\n\n**Asserts** — which law governs the agreement, where disputes are heard, and how liability is limited.\n\n**Derives from** — nothing. These are negotiated commercial and legal positions.\n\n**Completeness** — `NEEDS_DECISION`.\n\n**What closes it** — the operator deciding, with counsel. Note that liability limits interact with\nthe declared audience: consumer-facing terms cannot limit liability as freely as business-to-business\nones, so this fragment cannot be settled before the commercial-terms fragment establishes who the\nterms are for.\n\n**Never produce a liability clause from a template.** A limitation of liability that was copied\nrather than decided is either unenforceable or committing the operator to something nobody agreed —\nand unlike most gaps in a produced document, this one is not discovered until it matters.\n",
30
29
  "skillRefs": [
31
30
  "compliance-document-authoring"
31
+ ],
32
+ "skillBodyRefs": [
33
+ "compliance-document-authoring"
34
+ ],
35
+ "contextSources": [
36
+ "document_blueprint",
37
+ "authored_document_facts"
38
+ ],
39
+ "draftableDocumentDefinitionRefs": [
40
+ "document-definition:public.privacy-notice",
41
+ "document-definition:public.service-terms"
42
+ ],
43
+ "suspendsForClarification": false,
44
+ "briefAdequacyGate": true,
45
+ "briefAdequacyExcludedSources": [
46
+ "compliance_primary_facts"
32
47
  ]
33
48
  },
34
49
  "executor": "companion_agent",
35
- "qualityGates": [
36
- {
37
- "ref": "compliance-document-candidate-content-valid",
38
- "kind": "deterministic_validator",
39
- "validatorRef": "saas-specifications:validateComplianceDocumentCandidate",
40
- "required": true
41
- }
42
- ],
43
50
  "approval": "approve_result",
44
51
  "budget": {
45
52
  "maxRuns": 3
@@ -0,0 +1 @@
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-document-facts-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/document-facts-grounded-in-declarations","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/document-facts-grounded-in-declarations","requirementVersion":1}],"instruction":"The subject under judgment is the landed `document-facts` file. For EACH declaration in it, read the value (or the not-applicable reason) against the accepted application truth the run derived from and the computed context: the application's compliance-relevant declarations and the facts the runtime computed. Decide whether the statement claims more than those establish. A fact may paraphrase, summarise and name a gap; it may not assert a recipient, processor, transfer, retention period, lawful basis, AI use, data category or capability that nothing in the evidence supplies, and it may not state as settled what the declarations record as undeclared. The computed facts are not under judgment and are absent from the file on purpose — never ask for them to be declared, but DO report a landed fact that contradicts one. Name every unsupported claim by its fact ref and quote the words. Separate severities by CONSEQUENCE: wording a reader would not act on differently is a CONCERN; a claim a governed document would publish as true that nothing establishes, or that the evidence contradicts, is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with repairable wording drift a reader would not act on differently: an embellished emphasis, a vaguer summary than the evidence allows, or a claim that is supported but not traceable from its wording. Name each one.","GAP":"At least one declaration asserts something a governed document would publish as true that nothing in the evidence establishes, contradicts a declaration or a computed fact, or presents an undeclared matter as settled. Name each fact ref and quote the unsupported words.","INDETERMINATE":"The declarations or accepted inputs needed to decide are absent from the evidence, so groundedness cannot be judged. Say which evidence is missing.","PASS":"Every declaration states only what the accepted inputs, the declarations or the computed facts establish, and every gap the evidence records is stated as a gap."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/document-facts","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.document-facts"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -0,0 +1 @@
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-document-facts","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/document-facts-grounded-in-declarations"],"requirementRef":"application-creation:authority-requirement/document-facts-result","requirementVersion":1,"riskClassRef":"application-creation:risk/governed-document-fact-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/document-facts","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/document-facts-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/document-facts","policyVersion":1},"decisionPointRef":"application-creation:decision-point/document-facts-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/document-facts-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/document-facts","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/document-facts-grounded-in-declarations","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/document-facts-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/governed-document-fact-change","triggerRefs":["application-creation:trigger/document-facts-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-document-facts-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/document-facts-grounded-in-declarations"],"hardFloorRef":"application-creation:hard-floor/document-facts-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/document-facts-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/document-facts","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-document-facts-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/document-facts-grounded-in-declarations","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/document-facts-grounded-in-declarations","requirementVersion":1}],"instruction":"The subject under judgment is the landed `document-facts` file. For EACH declaration in it, read the value (or the not-applicable reason) against the accepted application truth the run derived from and the computed context: the application's compliance-relevant declarations and the facts the runtime computed. Decide whether the statement claims more than those establish. A fact may paraphrase, summarise and name a gap; it may not assert a recipient, processor, transfer, retention period, lawful basis, AI use, data category or capability that nothing in the evidence supplies, and it may not state as settled what the declarations record as undeclared. The computed facts are not under judgment and are absent from the file on purpose — never ask for them to be declared, but DO report a landed fact that contradicts one. Name every unsupported claim by its fact ref and quote the words. Separate severities by CONSEQUENCE: wording a reader would not act on differently is a CONCERN; a claim a governed document would publish as true that nothing establishes, or that the evidence contradicts, is a GAP.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with repairable wording drift a reader would not act on differently: an embellished emphasis, a vaguer summary than the evidence allows, or a claim that is supported but not traceable from its wording. Name each one.","GAP":"At least one declaration asserts something a governed document would publish as true that nothing in the evidence establishes, contradicts a declaration or a computed fact, or presents an undeclared matter as settled. Name each fact ref and quote the unsupported words.","INDETERMINATE":"The declarations or accepted inputs needed to decide are absent from the evidence, so groundedness cannot be judged. Say which evidence is missing.","PASS":"Every declaration states only what the accepted inputs, the declarations or the computed facts establish, and every gap the evidence records is stated as a gap."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/document-facts","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:refinement.document-facts"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/document-facts","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-document-facts-and-declarations","criterionRef":"application-creation:criterion/document-facts-grounded-in-declarations","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":2,"minCount":2,"requirementRef":"application-creation:evidence-requirement/document-facts-grounded-in-declarations","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/document-facts-and-application-declarations"}],"schemaVersion":1}
@@ -33,12 +33,17 @@ strongest support is not prose about the application, it is **the application's
33
33
 
34
34
  Read in this order:
35
35
 
36
- 1. **The resource configurations** — the `compliance-primary-facts` introspection behavior reads them
37
- for you, per resource: `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind`
38
- (whether those rows are a person), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20
39
- export can answer for them) and `seeRetained` (the audited path to retained data). These are
40
- DECLARATIONS, already written down and enforced at runtime. They are the best evidence a governed
41
- document can rest on, and they need no interpretation — only phrasing.
36
+ 1. **The resource declarations**, which are already in this brief, under *"The application's
37
+ compliance-relevant resource declarations (read from its CODE)"*. Per resource:
38
+ `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session
39
+ an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer
40
+ for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already
41
+ written down and enforced at runtime. They are the best evidence a governed document can rest on,
42
+ and they need no interpretation — only phrasing.
43
+
44
+ **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that
45
+ does not correspond to a declaration in that section is not derived, it is recalled, and this
46
+ playbook's whole reason for existing is the difference.
42
47
  2. **The compliance constraints on the vision**, which tell you which facts a reader will need.
43
48
  3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.
44
49
 
@@ -46,10 +51,82 @@ The split between 1 and 3 is the point. A specification says what the applicatio
46
51
  resource configuration says what it will actually do to a row tomorrow morning. Where they disagree,
47
52
  the configuration is the fact.
48
53
 
49
- Note the behavior reports engine-declared and application-declared coverage **separately**, and you
50
- should keep them apart in your facts too. The engine already answers most of the personal-data core —
51
- identity, credentials, sessions, membership — for every application. What it cannot answer is the
52
- application's own domain data, which is usually what a reader most wants to know about.
54
+ That section reports engine-declared and application-declared coverage **separately**, and you should
55
+ keep them apart in your facts too: the two have different owners, so they have different remedies. An
56
+ application's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.
57
+
58
+ Do not assume the engine half is the settled half. Read the counts. On the first real application to
59
+ be measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user
60
+ account and its self-view — and nothing on credentials, profiles, audit logs, files or membership.
61
+ Whatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with
62
+ declarations it has not made is exactly as false as one crediting the application.
63
+
64
+ ## COVER THE WHOLE SET — this is the half a first attempt gets wrong
65
+
66
+ The facts you declare here are the only thing a later document can state as established. A concern you
67
+ say nothing about does not become a cautious sentence in the notice; it becomes a clause reading *"this
68
+ has not yet been established"*, in a document about somebody's personal data, when the application had
69
+ already established it.
70
+
71
+ Measured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and
72
+ the notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,
73
+ which every one of that application's resources declares, and analytics, which it does not enable. Both
74
+ were answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:
75
+ a notice that understates what an application does is as wrong as one that overstates it.
76
+
77
+ Work through this list and declare a fact for each one you can answer:
78
+
79
+ | what a document will need | where the answer is |
80
+ |---|---|
81
+ | what personal data is held, and in which records | the resource declarations + the domain plan |
82
+ | what erasure does to each record | `retentionPolicy.mode` per resource |
83
+ | how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |
84
+ | whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |
85
+ | whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |
86
+ | who else can see the data inside the application | the domain model — roles, membership, sharing |
87
+ | which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |
88
+ | whether the application makes automated decisions or uses AI | the AI POSTURE section — per enabled capability, a declared consequence or OUTSTANDING |
89
+ | what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |
90
+ | what consent the application asks for | the declared capabilities + the domain plan |
91
+ | how organizations are separated from each other | the domain model and the tenancy declarations |
92
+
93
+ ## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief
94
+
95
+ The sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE
96
+ and nothing else — it never sees the resource declarations, the retention schedule, the processor
97
+ register, the AI posture or the client-storage inventory. **A gap you notice and do not write down is a
98
+ gap that disappears**, and the document then states the half that was answered as though it were the
99
+ whole.
100
+
101
+ So when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,
102
+ declare a fact recording it, naming what is missing:
103
+
104
+ - *"No retention period is declared for any of the four data classes; all four require an operator
105
+ decision."*
106
+ - *"The `app` frontend surface's own client storage has not been catalogued."*
107
+
108
+ This is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated
109
+ browser storage is configured — true — and said nothing about the frontend surface nobody had
110
+ inventoried. A reader of the notice would take the first as the whole answer.
111
+
112
+ A gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`
113
+ for it — that says the question does not arise, and it does.
114
+
115
+ **An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can
116
+ declare a period for each of the four data classes and has not for some of them. State which classes
117
+ are declared, with their periods and the reasons given, and state plainly which are still undecided —
118
+ the remedy is an operator deciding, not the framework growing a mechanism. Never write a period the
119
+ application has not declared, and never soften an absent one into "as long as necessary": that is a
120
+ commitment nobody made and nothing enforces.
121
+
122
+ **An absent capability is a fact, not a silence.** If no analytics provider is configured, that is
123
+ `KNOWN`: *"no external analytics provider is configured"*. If no AI capability is declared, say so. These
124
+ are the answers that let a notice state something true instead of confessing ignorance about a decision
125
+ the application already made — and the composition section in your brief lists them exactly.
126
+
127
+ **Declare mechanism facts per RESOURCE where the resources differ.** "All eight application resources
128
+ declare a subject-export mode" is a usable fact; "the application supports exports" is not, because a
129
+ reader cannot tell which records it covers.
53
130
 
54
131
  You are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,
55
132
  a liability position and a retention *duration the product has not chosen* are all decisions, and none
@@ -62,6 +139,23 @@ it is marked as not yet established, names what it needs and who can supply it,
62
139
  produced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact
63
140
  costs them a published false statement about somebody's data, which is not.
64
141
 
142
+ ## The shape of a declaration — get this right or the whole file is rejected
143
+
144
+ Each declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),
145
+ and **every one of them must be UNIQUE across the file**:
146
+
147
+ - `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the
148
+ single most common way a good fact set fails: a drafter answering several facts about retention
149
+ gives them all `slug: "retention"`. Make each one describe its own fact.
150
+ - `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two
151
+ declarations may not share a `factSlug` either. If you want to say two things about retention, they
152
+ are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.
153
+ - `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY
154
+ repeat; it is a classification, not an identity.
155
+
156
+ A rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:
157
+ re-read your list for two entries sharing a name.
158
+
65
159
  ## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence
66
160
 
67
161
  Three states, and confusing them is the most common way this pass goes wrong.
@@ -109,21 +203,82 @@ human makes it.
109
203
  - A retention period the product has not chosen, or one you inferred from a default.
110
204
  - A named human, a reviewer, a qualification or an independence statement. Every fact you produce
111
205
  carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it
112
- is the only one a derivation can honestly claim.
206
+ is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE
207
+ accepts. A declaration carrying any other authority is refused before it reaches a file.
113
208
  - A decision instant. You have no clock, and the honest instant for a human decision is the commit that
114
209
  records it.
115
210
  - A security claim beyond what the application's configuration actually shows.
116
211
  - A fact about a provider, region or capability the application has not configured.
117
212
 
213
+ ## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch
214
+
215
+ Your output replaces `document-facts` entirely on every run. That is why the facts only a human may
216
+ establish — a creator decision, a qualified review — live in a SEPARATE family,
217
+ `document-facts-authored`, which you neither read nor write. Before the two were split they shared one
218
+ file, and a producer run silently deleted the human half.
219
+
220
+ So an absent fact is never something for you to fill in "because nobody else will". The brief already
221
+ names which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent
222
+ is the correct outcome rather than a gap you are working around.
223
+
224
+ ## Some facts are COMPUTED, and you do not declare them
225
+
226
+ A few facts are not written by anyone. The runtime computes them from the application's own typed
227
+ declarations every time the facts are read:
228
+
229
+ - `controller-and-contact` is computed from `operatorComplianceIdentity`;
230
+ - `recipients-and-processors` is computed from the processor register and the providers' deployment
231
+ choices;
232
+ - `lawful-bases` is computed from `operatorComplianceIdentity.lawfulBases`;
233
+ - `retention-rules` is computed from the `dataRetention` schedule and each resource's erasure treatment;
234
+ - `international-transfers` is computed from each register entry's `transferDetermination`;
235
+ - `rights-and-complaint-route` is computed from the operating jurisdictions, the lawful bases, the
236
+ privacy contact, the identity-verification procedure and the role allocations.
237
+
238
+ The brief lists them under a separate "do not declare" heading. Declaring one is refused at
239
+ generation, and a copy in the file is refused by the family's validator.
240
+
241
+ The reason is drift. Your answer would be a paraphrase of a declaration that already exists, and it
242
+ would go stale the day that declaration changes. If the declaration a computed fact reads is missing,
243
+ the fact stays absent, and the documents mark it as owed. Leave that gap alone. Do not state a
244
+ controller, a recipient, a basis, a period, a transfer or a right in prose to fill it: say what is missing in a fact you do own, or leave it to
245
+ the document's gap marking.
246
+
247
+ ## A judge reads your facts against what you were given
248
+
249
+ After the file lands, an advisory judge reads every declaration beside the same evidence you had: the
250
+ input families, the application's compliance-relevant declarations and the computed facts. It reports
251
+ two kinds of finding. A **gap** is a claim a governed document would publish as true that nothing
252
+ establishes: a recipient, a transfer, a retention period, a lawful basis or an AI use that no
253
+ declaration names, or an undeclared matter stated as settled. A **concern** is wording drift a reader
254
+ would not act on differently.
255
+
256
+ The judge refuses nothing, and a finding does not undo your file. It is written so that an unsupported
257
+ claim is named before a document cites it. Write each fact so that its source is obvious from the
258
+ words.
259
+
118
260
  ## Refs are stamped for you
119
261
 
120
- Supply slugs — `retention-rules`, `data-categories-and-sources`, `recipients-and-processors`. The
121
- runtime turns each into its namespaced ref, attaches the governance scope and authority, assigns
122
- versions and sorts the declarations. Do not author a ref, a version or an ordering; a contract that
123
- asked you to would be asking you to fail on form rather than on substance.
262
+ Supply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and
263
+ authority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;
264
+ a contract that asked you to would be asking you to fail on form rather than on substance.
265
+
266
+ (This paragraph listed `retention-rules`, `data-categories-and-sources` and
267
+ `recipients-and-processors` as examples. All three are required fact names, and naming three of eight
268
+ as "examples" invited a drafter to treat them as a style to imitate rather than a set to use. The
269
+ authoritative list now arrives in the brief.)
124
270
 
125
- Use a stable, descriptive `factSlug` — it is the name a document clause will cite, so it should read as
126
- the question it answers.
271
+ **For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were
272
+ given lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.
273
+
274
+ This is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a
275
+ fact answering the right question under a different name is a fact the document cannot cite — it reads
276
+ as missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of
277
+ the eight a privacy notice requires, because the names were semantically adjacent and lexically
278
+ disjoint (`retention-period-schedule-status` for `retention-rules`).
279
+
280
+ For anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as
281
+ the question it answers. An application legitimately declares facts no document requires.
127
282
 
128
283
  ## Verification
129
284
 
@@ -145,10 +300,20 @@ somebody still owes.
145
300
 
146
301
  ## Runtime context
147
302
 
148
- // TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
149
- // TODO CLI COMMAND: wildo context vision-brief (read the vision and its compliance constraints)
150
- // TODO CLI COMMAND: wildo context resources (read the resources and fields whose data these facts describe)
303
+ Everything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as
304
+ input sections under "# Accepted application truth", and the application's live resource
305
+ DECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as
306
+ the declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to
307
+ run in this mode.
151
308
 
152
309
  ## References
153
310
 
154
- - `.claude/skills/journey-status/SKILL.md` — read current journey state and the artifacts you derive from.
311
+ These are skill FOLDERS installed in the application, named so each piece of work has an
312
+ authoring contract a later coding agent can open. This step has no tools and does not open them;
313
+ what reaches you is this method, your declared inputs, and the brief's own sections.
314
+
315
+ - `journey-status` — read current journey state and the artifacts you derive from.
316
+
317
+ ## External sign-in assurance
318
+
319
+ Derive `document-fact:external-sign-in-assurance` from the brief's declared authentication policy, including organization restrictions. Do not infer an active enterprise connection from an enabled method. Describe enterprise OAuth2/OIDC responsibility delegation separately from observed MFA. For social login, name the configured warning/strict treatment and provider evidence limitations. An unreadable configuration remains unresolved, never “no external login”. Feed this fact into the service-terms account-duties clause; liability conclusions still require qualified review.
@@ -3,12 +3,7 @@
3
3
  "version": "0.1.0",
4
4
  "phase": "refinement",
5
5
  "intent": "Derive the application's governed-document FACTS from truth it has already accepted — its vision (including the compliance regimes the posture pass recorded), its domain and its requirements — and land them as the `document-facts` family. A fact is a plain statement about how this application actually behaves: what data it holds, how long it keeps it, who it discloses to, what rights it honours. This produces the raw material a privacy notice or service terms is drafted FROM; it never drafts the document, never decides a legal question, and never states a fact the application's own code and accepted specifications do not support. Mechanism facts — retention treatment, data-subject kind, subject export — are read from the resource configurations, which declare what the application will actually do to a row; specifications supply purpose, not mechanism.",
6
- "functionalTopics": [],
7
6
  "preconditions": [
8
- {
9
- "kind": "phase_is",
10
- "phase": "refinement"
11
- },
12
7
  {
13
8
  "kind": "artifact_valid",
14
9
  "selector": {
@@ -37,25 +32,26 @@
37
32
  {
38
33
  "family": "document-facts",
39
34
  "schemaRef": "saas-specifications:ApplicationDocumentFactSpecification",
40
- "placement": "specifications/src/document-facts/",
41
35
  "description": "The application's declared governed-document facts, one declaration per fact, each either KNOWN with its value or NOT_APPLICABLE with a reason. Authority is APPLICATION_SPECIFICATION throughout: these are facts the application's own accepted specifications establish. A fact needing a named human decision is deliberately ABSENT rather than dressed in an authority nobody holds."
42
36
  }
43
37
  ],
38
+ "stepOutputs": [],
44
39
  "method": {
45
- "guidance": "# Governed-document facts — derivation method\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource configurations** — the `compliance-primary-facts` introspection behavior reads them\n for you, per resource: `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind`\n (whether those rows are a person), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20\n export can answer for them) and `seeRetained` (the audited path to retained data). These are\n DECLARATIONS, already written down and enforced at runtime. They are the best evidence a governed\n document can rest on, and they need no interpretation — only phrasing.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nNote the behavior reports engine-declared and application-declared coverage **separately**, and you\nshould keep them apart in your facts too. The engine already answers most of the personal-data core —\nidentity, credentials, sessions, membership — for every application. What it cannot answer is the\napplication's own domain data, which is usually what a reader most wants to know about.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## Refs are stamped for you\n\nSupply slugs — `retention-rules`, `data-categories-and-sources`, `recipients-and-processors`. The\nruntime turns each into its namespaced ref, attaches the governance scope and authority, assigns\nversions and sorts the declarations. Do not author a ref, a version or an ordering; a contract that\nasked you to would be asking you to fail on form rather than on substance.\n\nUse a stable, descriptive `factSlug` — it is the name a document clause will cite, so it should read as\nthe question it answers.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the vision and its compliance constraints)\n// TODO CLI COMMAND: wildo context resources (read the resources and fields whose data these facts describe)\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and the artifacts you derive from.\n",
40
+ "guidance": "# Governed-document facts — derivation method\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource declarations**, which are already in this brief, under *\"The application's\n compliance-relevant resource declarations (read from its CODE)\"*. Per resource:\n `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session\n an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer\n for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already\n written down and enforced at runtime. They are the best evidence a governed document can rest on,\n and they need no interpretation — only phrasing.\n\n **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that\n does not correspond to a declaration in that section is not derived, it is recalled, and this\n playbook's whole reason for existing is the difference.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nThat section reports engine-declared and application-declared coverage **separately**, and you should\nkeep them apart in your facts too: the two have different owners, so they have different remedies. An\napplication's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.\n\nDo not assume the engine half is the settled half. Read the counts. On the first real application to\nbe measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user\naccount and its self-view — and nothing on credentials, profiles, audit logs, files or membership.\nWhatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with\ndeclarations it has not made is exactly as false as one crediting the application.\n\n## COVER THE WHOLE SET — this is the half a first attempt gets wrong\n\nThe facts you declare here are the only thing a later document can state as established. A concern you\nsay nothing about does not become a cautious sentence in the notice; it becomes a clause reading *\"this\nhas not yet been established\"*, in a document about somebody's personal data, when the application had\nalready established it.\n\nMeasured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and\nthe notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,\nwhich every one of that application's resources declares, and analytics, which it does not enable. Both\nwere answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:\na notice that understates what an application does is as wrong as one that overstates it.\n\nWork through this list and declare a fact for each one you can answer:\n\n| what a document will need | where the answer is |\n|---|---|\n| what personal data is held, and in which records | the resource declarations + the domain plan |\n| what erasure does to each record | `retentionPolicy.mode` per resource |\n| how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |\n| whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |\n| whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |\n| who else can see the data inside the application | the domain model — roles, membership, sharing |\n| which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |\n| whether the application makes automated decisions or uses AI | the AI POSTURE section — per enabled capability, a declared consequence or OUTSTANDING |\n| what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |\n| what consent the application asks for | the declared capabilities + the domain plan |\n| how organizations are separated from each other | the domain model and the tenancy declarations |\n\n## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief\n\nThe sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE\nand nothing else — it never sees the resource declarations, the retention schedule, the processor\nregister, the AI posture or the client-storage inventory. **A gap you notice and do not write down is a\ngap that disappears**, and the document then states the half that was answered as though it were the\nwhole.\n\nSo when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,\ndeclare a fact recording it, naming what is missing:\n\n- *\"No retention period is declared for any of the four data classes; all four require an operator\n decision.\"*\n- *\"The `app` frontend surface's own client storage has not been catalogued.\"*\n\nThis is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated\nbrowser storage is configured — true — and said nothing about the frontend surface nobody had\ninventoried. A reader of the notice would take the first as the whole answer.\n\nA gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`\nfor it — that says the question does not arise, and it does.\n\n**An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can\ndeclare a period for each of the four data classes and has not for some of them. State which classes\nare declared, with their periods and the reasons given, and state plainly which are still undecided —\nthe remedy is an operator deciding, not the framework growing a mechanism. Never write a period the\napplication has not declared, and never soften an absent one into \"as long as necessary\": that is a\ncommitment nobody made and nothing enforces.\n\n**An absent capability is a fact, not a silence.** If no analytics provider is configured, that is\n`KNOWN`: *\"no external analytics provider is configured\"*. If no AI capability is declared, say so. These\nare the answers that let a notice state something true instead of confessing ignorance about a decision\nthe application already made — and the composition section in your brief lists them exactly.\n\n**Declare mechanism facts per RESOURCE where the resources differ.** \"All eight application resources\ndeclare a subject-export mode\" is a usable fact; \"the application supports exports\" is not, because a\nreader cannot tell which records it covers.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## The shape of a declaration — get this right or the whole file is rejected\n\nEach declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),\nand **every one of them must be UNIQUE across the file**:\n\n- `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the\n single most common way a good fact set fails: a drafter answering several facts about retention\n gives them all `slug: \"retention\"`. Make each one describe its own fact.\n- `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two\n declarations may not share a `factSlug` either. If you want to say two things about retention, they\n are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.\n- `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY\n repeat; it is a classification, not an identity.\n\nA rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:\nre-read your list for two entries sharing a name.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE\n accepts. A declaration carrying any other authority is refused before it reaches a file.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch\n\nYour output replaces `document-facts` entirely on every run. That is why the facts only a human may\nestablish — a creator decision, a qualified review — live in a SEPARATE family,\n`document-facts-authored`, which you neither read nor write. Before the two were split they shared one\nfile, and a producer run silently deleted the human half.\n\nSo an absent fact is never something for you to fill in \"because nobody else will\". The brief already\nnames which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent\nis the correct outcome rather than a gap you are working around.\n\n## Some facts are COMPUTED, and you do not declare them\n\nA few facts are not written by anyone. The runtime computes them from the application's own typed\ndeclarations every time the facts are read:\n\n- `controller-and-contact` is computed from `operatorComplianceIdentity`;\n- `recipients-and-processors` is computed from the processor register and the providers' deployment\n choices;\n- `lawful-bases` is computed from `operatorComplianceIdentity.lawfulBases`;\n- `retention-rules` is computed from the `dataRetention` schedule and each resource's erasure treatment;\n- `international-transfers` is computed from each register entry's `transferDetermination`;\n- `rights-and-complaint-route` is computed from the operating jurisdictions, the lawful bases, the\n privacy contact, the identity-verification procedure and the role allocations.\n\nThe brief lists them under a separate \"do not declare\" heading. Declaring one is refused at\ngeneration, and a copy in the file is refused by the family's validator.\n\nThe reason is drift. Your answer would be a paraphrase of a declaration that already exists, and it\nwould go stale the day that declaration changes. If the declaration a computed fact reads is missing,\nthe fact stays absent, and the documents mark it as owed. Leave that gap alone. Do not state a\ncontroller, a recipient, a basis, a period, a transfer or a right in prose to fill it: say what is missing in a fact you do own, or leave it to\nthe document's gap marking.\n\n## A judge reads your facts against what you were given\n\nAfter the file lands, an advisory judge reads every declaration beside the same evidence you had: the\ninput families, the application's compliance-relevant declarations and the computed facts. It reports\ntwo kinds of finding. A **gap** is a claim a governed document would publish as true that nothing\nestablishes: a recipient, a transfer, a retention period, a lawful basis or an AI use that no\ndeclaration names, or an undeclared matter stated as settled. A **concern** is wording drift a reader\nwould not act on differently.\n\nThe judge refuses nothing, and a finding does not undo your file. It is written so that an unsupported\nclaim is named before a document cites it. Write each fact so that its source is obvious from the\nwords.\n\n## Refs are stamped for you\n\nSupply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and\nauthority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;\na contract that asked you to would be asking you to fail on form rather than on substance.\n\n(This paragraph listed `retention-rules`, `data-categories-and-sources` and\n`recipients-and-processors` as examples. All three are required fact names, and naming three of eight\nas \"examples\" invited a drafter to treat them as a style to imitate rather than a set to use. The\nauthoritative list now arrives in the brief.)\n\n**For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were\ngiven lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.\n\nThis is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a\nfact answering the right question under a different name is a fact the document cannot cite — it reads\nas missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of\nthe eight a privacy notice requires, because the names were semantically adjacent and lexically\ndisjoint (`retention-period-schedule-status` for `retention-rules`).\n\nFor anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as\nthe question it answers. An application legitimately declares facts no document requires.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\nEverything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as\ninput sections under \"# Accepted application truth\", and the application's live resource\nDECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as\nthe declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to\nrun in this mode.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `journey-status` — read current journey state and the artifacts you derive from.\n\n## External sign-in assurance\n\nDerive `document-fact:external-sign-in-assurance` from the brief's declared authentication policy, including organization restrictions. Do not infer an active enterprise connection from an enabled method. Describe enterprise OAuth2/OIDC responsibility delegation separately from observed MFA. For social login, name the configured warning/strict treatment and provider evidence limitations. An unreadable configuration remains unresolved, never “no external login”. Feed this fact into the service-terms account-duties clause; liability conclusions still require qualified review.\n",
46
41
  "skillRefs": [
47
42
  "journey-status"
48
- ]
43
+ ],
44
+ "skillBodyRefs": [],
45
+ "contextSources": [
46
+ "compliance_primary_facts",
47
+ "document_fact_obligations"
48
+ ],
49
+ "draftableDocumentDefinitionRefs": [],
50
+ "suspendsForClarification": false,
51
+ "briefAdequacyGate": false,
52
+ "briefAdequacyExcludedSources": []
49
53
  },
50
54
  "executor": "companion_agent",
51
- "qualityGates": [
52
- {
53
- "ref": "document-fact-specification-valid",
54
- "kind": "deterministic_validator",
55
- "validatorRef": "saas-specifications:validateApplicationDocumentFactSpecification",
56
- "required": true
57
- }
58
- ],
59
55
  "approval": "approve_result",
60
56
  "budget": {
61
57
  "maxRuns": 3