@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
@@ -0,0 +1,859 @@
1
+ # Framework Personal-Data Declaration API
2
+
3
+ Read this **once per resource**, before you consider it finished.
4
+
5
+ It answers one question: **do this resource's rows describe a person?** Every resource owes an
6
+ answer — including "no", which is a real answer and has a way to say it.
7
+
8
+ ## Why you are asked, when nothing forces you
9
+
10
+ The framework does NOT refuse to start a resource that says nothing. That was decided deliberately:
11
+ a hard constraint on every author, for every resource, forever is too strict, and the framework's
12
+ own directive is that the system works first and protection arrives as guidance rather than as a
13
+ refusal wired into the mechanism.
14
+
15
+ What happens instead is that the application logs a startup **warning** naming every resource of
16
+ yours that has said nothing, and the application's generated privacy notice can say nothing about
17
+ those resources. The measured consequence, in a real application: a notice that is accurate about
18
+ the platform — identity, credentials, sessions, membership all come free with the engine — and
19
+ silent about the contacts, deals and interaction history, which is the data the customers of that
20
+ application actually care about.
21
+
22
+ So this is the cheapest possible moment to answer. Later means editing a shipped schema.
23
+
24
+ ## Four ways to answer, and they are four different questions
25
+
26
+ Declaring ANY of them counts as having answered. Declare the ones that are true.
27
+
28
+ | declaration | where | the question it answers |
29
+ |---|---|---|
30
+ | `retentionPolicy` | `resources-config` | does an erasure KEEP this row, and are its fields scrubbed? |
31
+ | `dataSubjectPolicy` | `resources-config` | whose LOGIN SESSION does erasing this row end? |
32
+ | `systemAccessPolicy.exportSubject` | `resources-config` | do these rows belong in a subject's export bundle? |
33
+ | `.dataCategories(...)` | the schema, per field | what KIND of personal data does this field hold? |
34
+
35
+ ### The "no personal data" answer is `RETAIN_ONLY`
36
+
37
+ `retentionPolicy: { mode: ErasureRetentionMode.RETAIN_ONLY }` means *this resource holds no personal
38
+ data of its own*, and it is CHECKED: the resource factory refuses a `.impersonalizeWith()` treatment
39
+ beside it, because the treatment would never run. It is a positive statement a compliance document
40
+ can cite, not silence — which is exactly why saying it is worth a line.
41
+
42
+ A resource that genuinely holds nothing about people — a product catalog, a price list, a pipeline
43
+ stage — should say so this way.
44
+
45
+ ### The two config declarations that must travel together
46
+
47
+ `retentionPolicy` REQUIRES `dataSubjectPolicy`, and `dataSubjectPolicy` is rejected without a
48
+ `retentionPolicy`. A retention-governed resource is exactly one that can be handed to an erasure as a
49
+ subject, so it must say whether its rows ARE a person and, if so, which field names the user whose
50
+ session the erasure ends.
51
+
52
+ ⚠️ `dataSubjectPolicy.kind = NO_PRINCIPAL` is the SESSION axis and nothing else. It is equally true
53
+ of an invoice and of a CRM contact who has no account. It does NOT mean "not a person" — read
54
+ `retentionPolicy.mode` for that.
55
+
56
+ ### `.dataCategories()` is per FIELD, and is not derived from names
57
+
58
+ A resource-level category cannot express that one row holds a name, an email and a payment token,
59
+ which is exactly what a privacy notice enumerates. Nothing in the framework infers a category from a
60
+ field's NAME — `email`, `phone` and `dateOfBirth` are suggestive while `notes` is not, and an
61
+ inventory built that way is a guess whose misses are silently undisclosed.
62
+
63
+ The one category the framework derives is `CREDENTIALS`, from `.isPassword()` / `.isOtp()` /
64
+ `.isWriteOnlySecret()` — markers you wrote.
65
+
66
+ If you declare `.impersonalizeWith()` on a field, declare a category on it too. A field that is
67
+ personal by one declaration and uncategorized by another is reported BY NAME as an outstanding gap
68
+ in every compliance document the application produces.
69
+
70
+ ### Who OWES an `exportSubject`, and why a bare count of declarations misleads
71
+
72
+ The other three declarations are owed by every resource, and the framework only warns. `exportSubject`
73
+ is different: it is **enforced**, and on a defined population rather than on all of them. The
74
+ obligation covers exactly the resources whose rows would enter a subject-export bundle — those
75
+ reachable from the subject on the export graph, which includes edges an erasure calls `NOT_OWNED`
76
+ because the subject-access right covers all personal data concerning a person, not only what they own.
77
+ A resource off that graph owes nothing, and its silence is correct.
78
+
79
+ So if you ever audit this — counting how many of your resources declare `exportSubject` and reporting
80
+ the shortfall as a gap — **the denominator is the resources on the export graph, never the resource
81
+ count.** "11 of 13" is arithmetic; "13 of 13 that owe it" is the answer. Ask which resources are
82
+ reachable from the subject before you report anything missing.
83
+
84
+ ## Resource configuration surface
85
+
86
+ ## Import Origins
87
+
88
+ - `@wildo-ai/saas-models`
89
+
90
+ ## Source Excerpts
91
+
92
+ ### Origin Package: `@wildo-ai/saas-models`
93
+
94
+ ```typescript
95
+ *
96
+ * Valid operation keys from core + custom enums, and builder params for `createResourceConfiguration`.
97
+ */
98
+ // Helper type to extract valid operation keys, excluding undefined
99
+ export type ValidOperationKeys<
100
+ TCustomOperationEnum extends EnumLikeType | undefined,
101
+ TCoreOperationEnum extends Partial<CoreResourceOperation> | undefined
102
+ > = (TCustomOperationEnum extends EnumLikeType ? EnumValues<TCustomOperationEnum> : never) |
103
+ (TCoreOperationEnum extends Partial<CoreResourceOperation> ? TCoreOperationEnum : never);
104
+
105
+ /**
106
+ *
107
+ * Access mode for the ACL-bypassing system-context reads
108
+ * (`SystemAccessBackendService.readAsSystem` / `listAsSystem`, from
109
+ * `@wildo-ai/saas-backend-lib`).
110
+ *
111
+ * Those primitives run with a synthesised super-admin execution context and
112
+ * therefore SKIP the caller's scope and role checks entirely. A resource is
113
+ * readable that way ONLY if its resource configuration opts the verb in. Any
114
+ * verb left undeclared defaults to `FORBIDDEN`: a system read of a resource
115
+ * that has not opted in throws `ErrorType.CONFIGURATION` — the framework is
116
+ * fail-closed here by construction.
117
+ */
118
+ export enum ResourceSystemAccessMode {
119
+ /** The verb's system-context primitive is rejected for this resource (default). */
120
+ FORBIDDEN = 'FORBIDDEN',
121
+ /** The verb's system-context primitive is permitted for this resource. */
122
+ ALLOWED = 'ALLOWED',
123
+ }
124
+
125
+ /**
126
+ * Per-resource opt-in policy for the ACL-bypassing system-context primitives
127
+ * on `SystemAccessBackendService`: the reads (`readAsSystem` / `listAsSystem`)
128
+ * and the trusted writes (`createAsSystem` / `updateAsSystem` /
129
+ * `updateManyAsSystem`).
130
+ *
131
+ * A system-context call does not REMOVE the authorization decision — it
132
+ * RELOCATES it from the resource ACL onto the calling service, which MUST
133
+ * enforce an explicit alternative check (e.g. consumable-token or
134
+ * email-ownership matching). Declaring this policy is the data owner's
135
+ * statement that such a bypass is permissible at all, and for which verb. An
136
+ * absent policy — or a verb set to (or left defaulting to) `FORBIDDEN` — makes
137
+ * the primitive throw.
138
+ *
139
+ * The WRITE verbs additionally let a trusted in-process caller persist the
140
+ * fields the client-shaped request DTO strips — `.isBackendOnly()` material
141
+ * (e.g. a credential `passwordHash`) and the context-auto-populated FKs (e.g.
142
+ * `userId` on a system resource that has no HTTP surface to seed it) — by
143
+ * re-attaching exactly those fields after the strict parse. They are the
144
+ * sanctioned path for engine flows like registration that must write system
145
+ * resources directly; opting a verb in is the data owner's acknowledgement that
146
+ * a super-admin-context mutation of this resource is legitimate.
147
+ *
148
+ * Caveats a system-context call inherits (it runs as super-admin), to weigh
149
+ * before opting in:
150
+ * - a READ returns the FULL record — every field, including ones a normal
151
+ * caller's role / field-visibility would hide — so never forward the result
152
+ * verbatim to an under-privileged caller; project only what is safe.
153
+ * - a WRITE bypasses the caller's scope + role ACL, so the calling service
154
+ * owns the authorization decision (only trusted engine code can reach the
155
+ * primitive — it is never exposed to an HTTP payload).
156
+ * - feature flags do not gate it (it is an internal request).
157
+ * - the policy is RESOURCE-LEVEL: for a polymorphic resource it is shared by
158
+ * every scope variant (declare it once on the shared config).
159
+ *
160
+ * Intentionally DISTINCT from `isSystemResource`: marking a resource as
161
+ * framework infrastructure does NOT imply that an ACL bypass is acceptable
162
+ * for its data. Keep the two concepts separate.
163
+ */
164
+ /**
165
+ * Declares that THIS resource is the application's subject-erasure request lane, and how to read it.
166
+ *
167
+ * ## Why the application declares it rather than the framework knowing it
168
+ *
169
+ * The erasure lane is application-owned — four of the five marked sites for
170
+ * `WILDO.PRIVACY.SUBJECT_ERASURE` are in an application, not the engine — and its evidence demand
171
+ * (`evidence-requirement:subject-erasure-execution-record`) says so in terms: *"the row's schema and
172
+ * status vocabulary are the application's, so a collector queries it against that application's
173
+ * specification"*, and its verification step adds *"do NOT assert a specific channel vocabulary:
174
+ * that is one application's modelling choice"*.
175
+ *
176
+ * So a collector may not know that a request is raised through a field called `channel` carrying a
177
+ * value called `SUBJECT`. It has to be TOLD, by the application, in a form it can read. Before this
178
+ * existed, three clauses of that demand had a durable row holding every fact they wanted and no way
179
+ * to find it (#1209): not a missing control, a control nobody could point at.
180
+ *
181
+ * ## It binds FIELDS, never values the framework invents
182
+ *
183
+ * Every member below names something the application already authored. The one value the
184
+ * declaration carries — {@link ResourceSubjectErasureLane.raisedBy}`.subjectValue` — is the
185
+ * application's OWN enum member, quoted back so a reader can tell the two populations apart. The
186
+ * framework supplies no vocabulary here and must never grow one.
187
+ *
188
+ * ## What is deliberately NOT declared
189
+ *
190
+ * The SCHEDULE. C3 asks that requests be executed on the declared schedule, and that schedule is
191
+ * already on the executing operation's `CRON_JOB` variant (`cronExpression`) — declaring it again
192
+ * here would be a second copy that can only ever disagree with the one the scheduler reads.
193
+ * `executionOperationIdentifier` names the operation; the schedule is read from it.
194
+ */
195
+ export type ResourceSubjectErasureLane = {
196
+ /**
197
+ * How a row says WHO raised the request — the subject exercising their own right, or the
198
+ * controller acting on their behalf. C1's whole obligation is that the two are distinguishable.
199
+ */
200
+ raisedBy: {
201
+ /** The field carrying it. Must be a persisted field of this resource. */
202
+ fieldName: string,
203
+ /**
204
+ * The value of that field meaning the SUBJECT raised it themselves. Every other value is read as
205
+ * controller-raised — stated this way round because a lane may grow a second controller channel
206
+ * without the declaration going stale, whereas enumerating the controller values could not.
207
+ */
208
+ subjectValue: string,
209
+ },
210
+ /**
211
+ * The field carrying WHICH user raised a controller-raised request.
212
+ *
213
+ * Omitting it is a positive claim, not a gap: it says this lane admits no controller-raised
214
+ * request at all. A collector reads it that way and a row carrying a non-subject value then
215
+ * contradicts the declaration, which is a finding about the application rather than about the
216
+ * evidence.
217
+ */
218
+ requesterFieldName?: string,
219
+ /** The field carrying the justification a controller-raised request was made on, where the lane records one. */
220
+ justificationFieldName?: string,
221
+ /** The field carrying the instant the request was executed or failed. C3 judges execution against it. */
222
+ completedAtFieldName: string,
223
+ /** The field carrying what the execution did. Its vocabulary is the application's. */
224
+ outcomeFieldName: string,
225
+ /**
226
+ * The operation a SUBJECT uses to withdraw their own pending request (C2). Named rather than
227
+ * inferred: "the operation that cancels" is not derivable from an operation vocabulary, and
228
+ * guessing it would make the evidence depend on a naming convention no application agreed to.
229
+ */
230
+ withdrawalOperationIdentifier: string,
231
+ /**
232
+ * How a WITHDRAWN row is recognisable afterwards — the same shape as {@link raisedBy}, and for the
233
+ * same reason: the vocabulary is the application's.
234
+ *
235
+ * C2 asks for the withdrawal door AND for "any cancelled rows", and those are two different
236
+ * questions. The door is answered from {@link withdrawalOperationIdentifier} — is the operation
237
+ * reachable to a subject while the request is pending — and needs no data at all. The rows need a
238
+ * marker, and there is nothing to derive one from: withdrawal and execution both leave a request in
239
+ * a terminal state, so a reader that knows only `completedAtFieldName` cannot tell "the subject
240
+ * changed their mind" from "the sweep ran".
241
+ *
242
+ * OPTIONAL, because an application may not model withdrawal as a value at all — it may delete the
243
+ * row, or move it. Omitting it says the count is unavailable, and a collector reports that rather
244
+ * than guessing; it never turns into a zero, which would read as "nobody withdrew anything".
245
+ *
246
+ * Note an EMPTY withdrawal set is explicitly not a deficiency in the demand — people do not have
247
+ * to change their minds — so this exists to make the number REPORTABLE, never to make it a target.
248
+ */
249
+ withdrawnMarker?: {
250
+ /** The field carrying it. Must be a persisted field of this resource. */
251
+ fieldName: string,
252
+ /** The value of that field meaning the SUBJECT withdrew the request before it executed. */
253
+ withdrawnValue: string,
254
+ },
255
+ /** The scheduled operation that executes due requests. Its `cronExpression` IS the declared schedule. */
256
+ executionOperationIdentifier: string,
257
+ };
258
+
259
+ export type ResourceSystemAccessPolicy = {
260
+ /** Governs `readAsSystem`. Omitted ⇒ FORBIDDEN. */
261
+ read?: ResourceSystemAccessMode,
262
+ /** Governs `listAsSystem`. Omitted ⇒ FORBIDDEN. */
263
+ list?: ResourceSystemAccessMode,
264
+ /** Governs `createAsSystem`. Omitted ⇒ FORBIDDEN. */
265
+ create?: ResourceSystemAccessMode,
266
+ /** Governs `updateAsSystem`. Omitted ⇒ FORBIDDEN. */
267
+ update?: ResourceSystemAccessMode,
268
+ /** Governs `updateManyAsSystem`. Omitted ⇒ FORBIDDEN. */
269
+ updateMany?: ResourceSystemAccessMode,
270
+ // NOTE: there is deliberately NO `delete` verb here — there is no `deleteAsSystem` primitive. A row is
271
+ // removed either through its own DELETE operation ACL (e.g. an owner-facing `API_CALL` DELETE under the
272
+ // USER_SELF owner filter) or by the `onParentDelete` composition cascade (which deletes at the raw
273
+ // repository layer, variant-agnostic — see `deleteChildrenImmediate`). If you find yourself reaching
274
+ // for `systemAccessPolicy.delete`, model the removal as one of those two instead.
275
+ /**
276
+ * Governs the impersonalization see-through reads (`readRetainedAsSystem` /
277
+ * `listRetainedAsSystem`) — the privileged, audited path that reveals
278
+ * `retentionStatus = RETAINED` rows hidden-by-default. Omitted ⇒ FORBIDDEN.
279
+ * Auto-derived to `ALLOWED` by the factory when a resource opts into
280
+ * `retentionPolicy`; never authored by hand in the common case.
281
+ *
282
+ * **LIVE, and REACHABLE.** `readRetainedAsSystem` / `listRetainedAsSystem` exist and are enforced:
283
+ * the verb is asserted fail-closed, a privileged human role is required, and every reveal emits a
284
+ * human-attributed `RETAINED_DATA_ACCESS` audit event.
285
+ *
286
+ * "Reachable" is the half that was missing until #490, and the distinction is worth keeping. The
287
+ * primitives were correct and enforced from the day M5b landed — and had **no caller**, so the only
288
+ * route an operator actually had to a retained record was a database console: the unaudited path
289
+ * they were built to replace. `users | read_retained` is the operator surface that closes it, an
290
+ * authenticated `APP_ADMIN_SUPER_ADMIN` operation carrying a mandatory justification.
291
+ *
292
+ * A resource that derives this grant and exposes no such operation is reachable by nothing. That
293
+ * is a defensible state — not every retention resource needs an operator door — but it should be a
294
+ * decision rather than an oversight, and `retained-see-through-operator-surface.test.ts` is what
295
+ * makes it one.
296
+ *
297
+ * (This block previously said the primitives were "wired in a later phase" — false since M5b.)
298
+ */
299
+ seeRetained?: ResourceSystemAccessMode,
300
+
301
+ /**
302
+ * May this resource's rows be swept into a SUBJECT EXPORT bundle (GDPR Art. 15 / Art. 20)?
303
+ *
304
+ * Fail-closed by omission, like every other verb here. A subject export reads across the whole
305
+ * child-direction graph of its subject, so without an explicit opt-in a resource could be
306
+ * disclosed to a data subject because it merely sits on an edge — nobody having decided that its
307
+ * contents are appropriate to hand over.
308
+ *
309
+ * **The refusal is LOUD, not a silent skip.** When an edge the classifier marked for inclusion
310
+ * belongs to a resource that has not opted in, the export REFUSES and names it. Silently dropping
311
+ * it would produce an access bundle that is incomplete without saying so — a disclosure failure
312
+ * wearing the appearance of a successful response, which is the same class of lie as the routed
313
+ * export operations this capability replaced. Refusing is a one-line fix per resource; a silent
314
+ * omission is undetectable.
315
+ *
316
+ * NOT derived from `portabilityPolicy`: declaring where fields came from (Art. 20 scoping) and
317
+ * consenting to be disclosed at all are different decisions, and a resource may legitimately want
318
+ * the first without the second.
319
+ */
320
+ exportSubject?: ResourceSystemAccessMode,
321
+ };
322
+
323
+ /**
324
+ * Resource-level opt-in to the **impersonalization-on-erasure** capability: on erasure the
325
+ * resource is impersonalized-and-retained (personal fields scrubbed, row kept for a legal/audit
326
+ * obligation) instead of hard-deleted. When set, the factory injects a `retentionStatus` marker
327
+ * and derives the `updateMany` + `seeRetained` system-access grants.
328
+ *
329
+ * RESOURCE-level (intrinsic, trigger-agnostic). The per-EDGE trigger is
330
+ * `onParentDelete.strategy = IMPERSONALIZE_AND_RETAIN`; the per-FIELD scrub is `.impersonalizeWith()`.
331
+ *
332
+ * **LIVE — opting in has real effect today.** The marker + derived grants, the in-place scrub writer,
333
+ * the `IMPERSONALIZE_AND_RETAIN` cascade mode and the hidden-by-default read filter all exist and are
334
+ * enforced. A RETAINED row is invisible to reads, lists, counts and CHART aggregates, and immutable
335
+ * to ordinary writes, on BOTH persistence adapters; the only door is the audited see-through path.
336
+ *
337
+ * Runtime-proven, not asserted — and scoped precisely, because an earlier revision of this block
338
+ * over-claimed it. Against a real MongoDB, the erasure orchestrator reaches its terminal path and its
339
+ * receipt is truthful over a registered subset of resources
340
+ * (`subject-erasure-completion.mongo.integration.test.ts`); the retention OUTCOME and a SECOND erasure
341
+ * are observed (`subject-impersonalization-retention-outcome.mongo.integration.test.ts`); and a
342
+ * retained row is absent from a real application chart over real HTTP
343
+ * (Your Application `e2e/chart-retention-hide.e2e.ts`).
344
+ *
345
+ * What is NOT proven: that an erasure completes over the FULL `onParentDelete` closure, and that
346
+ * external (provider-side) effects run. The completion lane deliberately requires
347
+ * `declinedEdges.length > 0`, so it asserts a state in which some edges were NOT executed, and
348
+ * `externalEffects` is stubbed empty. Do not read "runtime-proven" here as end-to-end completeness.
349
+ *
350
+ * (This block previously read "Contract only in this phase … No record is impersonalized-and-retained
351
+ * yet." That was true when written and became false without being revisited — it is the public
352
+ * authoring contract an app developer reads before declaring this policy, so it is corrected here
353
+ * rather than left to mislead.)
354
+ *
355
+ * ⚠️ NOT the anonymous-user concept (`isAnonymizable` is pre-auth ownership transposition — the
356
+ * opposite direction). Reuse of that mechanism, never its name.
357
+ */
358
+ /**
359
+ * WHO a row of this resource is with respect to an erasure, and where that person's session lives.
360
+ * The companion of {@link ResourceRetentionPolicy}: retention says what happens to the ROW and whether
361
+ * the row holds personal data at all; this says **whose SESSION an erasure of it must end**.
362
+ *
363
+ * The two are independent, and reading this one as "is the row about a person" is the mistake that
364
+ * cost `NO_PRINCIPAL` its previous name — see {@link ResourceDataSubjectKind}. A CRM contact holds
365
+ * personal data (`RETAIN_AND_IMPERSONALIZE`) and has no session (`NO_PRINCIPAL`); an invoice holds
366
+ * none (`RETAIN_ONLY`) and also has no session. Same value here, opposite compliance meaning, and the
367
+ * retention mode is what tells them apart.
368
+ *
369
+ * Required on every resource declaring a {@link ResourceRetentionPolicy}, because those are exactly
370
+ * the resources that can be passed to `eraseSubjectAsSystem` as a subject (the orchestrator refuses a
371
+ * subject with no retention policy). Undeclared fails at config build rather than defaulting: the safe
372
+ * default is unknowable — guessing `NO_PRINCIPAL` silently drops a real person's revocation, and
373
+ * guessing a linked principal revokes the wrong people. See {@link ResourceDataSubjectKind} for why
374
+ * the linkage can never be inferred from the presence of a user foreign key.
375
+ */
376
+ export interface ResourceDataSubjectPolicy {
377
+ /** Whose login session an erasure of this row must end — never whether the row is about a person. */
378
+ kind: ResourceDataSubjectKind;
379
+ /**
380
+ * The field naming the `USERS` row whose session an erasure of this row must end.
381
+ *
382
+ * REQUIRED when {@link kind} is `LINKED_PRINCIPAL`, and FORBIDDEN otherwise — under
383
+ * `SELF_PRINCIPAL` the row's own id is the principal, and under `NO_PRINCIPAL` there is no
384
+ * principal at all, so a field there would be a contradiction rather than redundancy. Both
385
+ * directions are enforced at config build.
386
+ */
387
+ sessionPrincipalField?: string;
388
+ }
389
+
390
+ export interface ResourceRetentionPolicy {
391
+ /**
392
+ * WHAT happens to a row of this resource when its subject is erased.
393
+ *
394
+ * Both modes retain the row (kept, marked `RETAINED`, hidden from normal reads and immutable,
395
+ * readable only through the audited see-through path). They differ on whether the row's own FIELDS
396
+ * additionally need scrubbing — which is a genuinely separate question, because a record can be
397
+ * legally retainable while holding no personal data of its own (a financial row that merely POINTS
398
+ * at a person). Fusing the two forced such a resource to either invent a fake scrub or forgo
399
+ * retention entirely; keeping them distinct is what makes "retain, nothing to scrub" expressible.
400
+ */
401
+ mode: ErasureRetentionMode;
402
+ }
403
+
404
+ /**
405
+ * Resource-level DEFAULT for where this resource's field values came from — the axis that decides
406
+ * GDPR Art. 20 (portability) scope. Per-field overrides are `.portabilityProvenance()`.
407
+ *
408
+ * ## Why a resource-level default exists at all
409
+ *
410
+ * Art. 20 is intrinsically a per-FIELD question: one row routinely mixes data the subject supplied
411
+ * (`firstName`) with data the controller produced about them (a computed score, a server-assigned
412
+ * status). But requiring a decorator on EVERY field of every resource would make the capability
413
+ * unadoptable, and an unadopted disclosure capability is worse than a coarse one — it means
414
+ * portability requests cannot be answered at all.
415
+ *
416
+ * So the declaration is two-level: this default carries the resource's common case in one line, and
417
+ * only fields that DIFFER from it need a decorator. A `USER_PROFILES` resource is
418
+ * `SUBJECT_PROVIDED` by default with a handful of derived exceptions; an `AUDIT_LOGS` resource is
419
+ * `DERIVED` throughout with none.
420
+ *
421
+ * ## Why it is optional, and what happens without it
422
+ *
423
+ * Omitting it entirely is legitimate: **Art. 15 (access) never consults provenance**, so an
424
+ * application can answer access requests in full before annotating anything. Only an Art. 20
425
+ * portability export needs the axis, and for a resource where neither the field nor this default
426
+ * declares one, that export REFUSES rather than guessing — see
427
+ * `SubjectExportFieldScope.UNDECLARED` for why neither guess is the safe one.
428
+ *
429
+ * ⚠️ NOT `retentionPolicy`. That says what happens to a value on ERASURE (destroy vs retain-and-
430
+ * scrub); this says where the value ORIGINATED, for a DISCLOSURE decision. A field is commonly
431
+ * `SUBJECT_PROVIDED` here and masked on erasure there — orthogonal axes on the same value.
432
+ */
433
+ export interface ResourcePortabilityPolicy {
434
+ /**
435
+ * The provenance every field of this resource is assumed to carry unless its own
436
+ * `.portabilityProvenance()` says otherwise.
437
+ */
438
+ defaultProvenance: DataPortabilityProvenance;
439
+ }
440
+
441
+ /**
442
+ * Builder parameters for creating a resource configuration.
443
+ * NOTE: databaseSchema has been removed. Backend-only fields are now marked with
444
+ * the isBackendOnly decorator in mainSchema and are stripped at the service layer.
445
+ */
446
+ export type ResourceConfiguration_BuilderParameters<
447
+ TCustomOperationEnum extends EnumLikeType | undefined,
448
+ TCoreOperationEnum extends Partial<CoreResourceOperation> | undefined,
449
+ TMainSchema extends z.ZodTypeAny,
450
+ > = {
451
+ isDisabled?: boolean, // default false
452
+ mainSchema: TMainSchema,
453
+ resourceIdentifier : ResourceType,
454
+ resourceFieldIdentifier : ResourceFieldIdentifier,
455
+ resourceRelationships : ResourceRelationship[],
456
+ inheritenceSchemaDefinition?: ResourceConfiguration_InheritanceSchemaDefinition<EnumLikeType,TMainSchema>,
457
+
458
+ /**
459
+ * Persistence adapter (database type) for this resource.
460
+ * - `mongodb`: MongoDB with Mongoose ORM
461
+ * - `postgresql`: PostgreSQL (SQL adapter)
462
+ *
463
+ * If not specified, uses `appConfig.database.defaultAdapter` — which is the normal case and
464
+ * should stay the normal case.
465
+ *
466
+ * **Declaring a value that DISAGREES with the application default is refused at registration
467
+ * unless {@link ResourceConfiguration_BuilderParameters.persistenceAdapterIsolation} is also
468
+ * declared.** An application is wholly one adapter by default because two adapters cannot
469
+ * share a native transaction; the isolation declaration is the only way past that refusal,
470
+ * and it is a claim about this resource's write topology rather than a way to silence the
471
+ * error. Declaring an adapter that AGREES with the default is always fine and needs nothing.
472
+ */
473
+ persistenceAdapter?: PersistenceAdapterType,
474
+
475
+ /**
476
+ * This resource's declared relationship to cross-adapter atomic write boundaries.
477
+ *
478
+ * Required — and only meaningful — when {@link
479
+ * ResourceConfiguration_BuilderParameters.persistenceAdapter} disagrees with
480
+ * `appConfig.database.defaultAdapter`. Without it, the resources registry refuses the
481
+ * application at startup; with it, the registry admits the resource and LOGS the admitted
482
+ * set, so a mixed configuration is always named and never ambient.
483
+ *
484
+ * Read {@link ResourcePersistenceAdapterIsolation} before declaring one: the member is an
485
+ * assertion about the resource's design that the persistence unit of work will still enforce
486
+ * at every real boundary.
487
+ */
488
+ persistenceAdapterIsolation?: ResourcePersistenceAdapterIsolationType,
489
+
490
+ /**
491
+ * REQUIRED companion declaration when `persistenceAdapter` is `HTTP_API`; forbidden otherwise.
492
+ *
493
+ * Carries everything the external repository needs that the platform does not own: provider
494
+ * reference (credentials resolve through `ExternalProvidersRegistryBackendService`), transport
495
+ * dialect, remote entity, ordered key declaration (id synthesis), identity mode, tenancy
496
+ * stance, erasure stance, and remote-call semantics. The factory enforces presence/absence
497
+ * coherence and content-validates the declaration.
498
+ */
499
+ httpApiBinding?: HttpApiResourceBindingAuthored,
500
+
501
+ /** REQUIRED when `persistenceAdapter` is INTROSPECTION; meaningless otherwise. */
502
+ introspectionBinding?: IntrospectionResourceBinding,
503
+
504
+ /**
505
+ * OPTIONAL inbound ETL pipeline on an ordinary LOCAL resource — "some resources local, some
506
+ * remote, ETL between them" (partial-resource coverage, model v3; PR-3). FORBIDDEN on an
507
+ * HTTP_API-adapter resource: a virtual resource IS the remote side. The factory
508
+ * content-validates the declaration and every mainSchema-dependent coherence rule (the
509
+ * remote-key field is a declared `.isBusinessKey()` + excludeFromCreate/Update STRING; mapped
510
+ * targets exist, accept null unless `required`, and are excludeFromCreate/Update; CLOSED
511
+ * population refuses caller CREATE operations).
512
+ */
513
+ externalDataPipeline?: ExternalDataPipelineDeclarationAuthored,
514
+
515
+ isSystemResource?: boolean, // default false - true for core system resources (organizations, users, etc.), false for tenant-specific resources
516
+
517
+ /**
518
+ * Does this resource's OWN primary-key URL segment name the CALLER, or the SUBJECT?
519
+ *
520
+ * Default `true` (the segment names the caller) — deliberately the SAFE default, so a resource
521
+ * whose author has not considered the question keeps the identity-coherence guard rather than
522
+ * silently losing it.
523
+ *
524
+ * ## Why this cannot be inferred
525
+ *
526
+ * The W3.6 identity-coherence guard (`handleUserJwtAuthentication` →
527
+ * `AUTHORIZATION_USER_ID_MISMATCH`) refuses a request whose URL `userId` differs from the JWT
528
+ * subject. That is exactly right for `USER_SELF` (`/user-self/{userId}` — the segment IS the
529
+ * caller, pinned by the horizontal-IDOR probes) and for child routes under a user
530
+ * (`/users/{userId}/draft-notes` — a PARENT segment naming whose rows these are).
531
+ *
532
+ * It is exactly WRONG for `USERS`, whose own `resourceFieldIdentifier` is also `userId` but whose
533
+ * segment names the TARGET of an administrative action. Both resources are keyed on the same
534
+ * field name, so no structural rule can tell them apart — the framework already had to add
535
+ * `coreResourceShared_FieldIdentifierPriority` to disambiguate the very same collision for FK
536
+ * resolution. This declaration is that disambiguation for IDENTITY.
537
+ *
538
+ * ## What it does and does not change
539
+ *
540
+ * Setting `false` relaxes ONLY the coherence refusal. It does not touch:
541
+ * - `initiatorIds.userId`, which is taken from the JWT and spread LAST precisely so a URL can
542
+ * never spoof the caller (see the `W3.6` comment at that assignment) — so permitting the
543
+ * mismatch cannot produce impersonation;
544
+ * - the contextual-field map, which legitimately carries the ADDRESSED resource's id;
545
+ * - authorization, which still decides whether this caller may run this operation at all.
546
+ *
547
+ * Set `false` only for an administrative resource whose primary key is a person/tenant identifier
548
+ * that a privileged caller is MEANT to address on someone else's behalf.
549
+ */
550
+ primaryKeyIdentifiesInitiator?: boolean,
551
+
552
+ /**
553
+ * Opt-in policy for the ACL-bypassing system-context primitives
554
+ * (`readAsSystem` / `listAsSystem` and the trusted writes `createAsSystem` /
555
+ * `updateAsSystem` / `updateManyAsSystem`). Omitted ⇒ EVERY verb FORBIDDEN
556
+ * (fail-closed): a system-context call on this resource throws unless the
557
+ * matching verb is explicitly set to ALLOWED. Declare ONLY the verb(s) that
558
+ * genuinely need a system bypass, and ensure the calling service enforces an
559
+ * explicit alternative authorization.
560
+ */
561
+ systemAccessPolicy?: ResourceSystemAccessPolicy,
562
+
563
+ /**
564
+ * Declares this resource as the application's SUBJECT-ERASURE REQUEST LANE and binds the fields an
565
+ * evidence collector reads. Omitted ⇒ this resource is not that lane, which is the honest default:
566
+ * most resources are not, and an application that never built an erasure lane has declared none
567
+ * rather than failed a control. See {@link ResourceSubjectErasureLane}.
568
+ */
569
+ subjectErasureLane?: ResourceSubjectErasureLane,
570
+ coreOperations: TCoreOperationEnum[],
571
+ customOperation?: TCustomOperationEnum, // default undefined
572
+ operationsConfiguration : { [K in ValidOperationKeys<TCustomOperationEnum, TCoreOperationEnum>]: OperationConfig_ForKey<K, TMainSchema> }
573
+ /**
574
+ * Configuration for auto-generated operation variants.
575
+ * Controls which READ/LIST variants (summary, context) are auto-generated.
576
+ * All variants are enabled by default.
577
+ */
578
+ autoVariants?: ResourceConfiguration_AutoVariants,
579
+ // NOTE: responseSummaryDto removed - now auto-derived from isSummaryField() decorators in factory
580
+
581
+ /**
582
+ * W7.3a: Marks this resource as accessible to anonymous sessions.
583
+ * When true, the factory auto-generates dual URL paths (USER_SELF + ANONYMOUS)
584
+ * and a STANDALONE relationship to ANONYMOUS_USERS.
585
+ * The resource MUST have a nullable `userId` field.
586
+ */
587
+ isAnonymizable?: boolean,
588
+
589
+ /**
590
+ * W7.3a: Controls how anonymous resources are handled during transposition.
591
+ * Only meaningful when isAnonymizable is true.
592
+ * Defaults to ADD (simple ownership reassignment).
593
+ */
594
+ transpositionPolicy?: ResourceTranspositionPolicy,
595
+
596
+ /**
597
+ * Opt in to impersonalization-on-erasure (retain + scrub instead of hard-delete). When set, the
598
+ * factory injects a `retentionStatus` marker and derives the `updateMany` / `seeRetained`
599
+ * system-access grants. Per-field scrub is `.impersonalizeWith()`; the per-edge trigger is the
600
+ * `IMPERSONALIZE_AND_RETAIN` cascade mode.
601
+ *
602
+ * **LIVE.** Marker injection, grant derivation, the scrub writer, the cascade mode and the
603
+ * hidden-by-default read filter are all enforced today — see `ResourceRetentionPolicy` for the
604
+ * runtime evidence. Declaring this changes behaviour; it is not a forward declaration.
605
+ *
606
+ * Declaring this also REQUIRES {@link dataSubjectPolicy}: a retention-governed resource is exactly
607
+ * one that can be handed to `eraseSubjectAsSystem` as a subject, so it must say whether its rows are
608
+ * a person — and if so, whose session an erasure ends.
609
+ */
610
+ retentionPolicy?: ResourceRetentionPolicy,
611
+
612
+ /**
613
+ * WHO a row of this resource is with respect to an erasure — and, when it is a person, which field
614
+ * names the `USERS` row whose session that erasure must end.
615
+ *
616
+ * Mandatory for any resource declaring a {@link retentionPolicy}; meaningless (and rejected) without
617
+ * one, since a resource with no retention policy can never be an erasure subject. See
618
+ * {@link ResourceDataSubjectPolicy}.
619
+ */
620
+ dataSubjectPolicy?: ResourceDataSubjectPolicy,
621
+
622
+ /**
623
+ * Resource-level DEFAULT provenance for GDPR Art. 20 (portability) scoping; per-field overrides
624
+ * are `.portabilityProvenance()`. Optional — Art. 15 (access) never consults provenance, so an
625
+ * application can answer access requests without declaring this. See
626
+ * {@link ResourcePortabilityPolicy}.
627
+ */
628
+ portabilityPolicy?: ResourcePortabilityPolicy,
629
+ }
630
+ ```
631
+
632
+ ## System-access policy (where `exportSubject` lives)
633
+
634
+ ## Import Origins
635
+
636
+ - `@wildo-ai/saas-models`
637
+
638
+ ## Source Excerpts
639
+
640
+ ### Origin Package: `@wildo-ai/saas-models`
641
+
642
+ ```typescript
643
+ *
644
+ * Access mode for the ACL-bypassing system-context reads
645
+ * (`SystemAccessBackendService.readAsSystem` / `listAsSystem`, from
646
+ * `@wildo-ai/saas-backend-lib`).
647
+ *
648
+ * Those primitives run with a synthesised super-admin execution context and
649
+ * therefore SKIP the caller's scope and role checks entirely. A resource is
650
+ * readable that way ONLY if its resource configuration opts the verb in. Any
651
+ * verb left undeclared defaults to `FORBIDDEN`: a system read of a resource
652
+ * that has not opted in throws `ErrorType.CONFIGURATION` — the framework is
653
+ * fail-closed here by construction.
654
+ */
655
+ export enum ResourceSystemAccessMode {
656
+ /** The verb's system-context primitive is rejected for this resource (default). */
657
+ FORBIDDEN = 'FORBIDDEN',
658
+ /** The verb's system-context primitive is permitted for this resource. */
659
+ ALLOWED = 'ALLOWED',
660
+ }
661
+
662
+ /**
663
+ * Per-resource opt-in policy for the ACL-bypassing system-context primitives
664
+ * on `SystemAccessBackendService`: the reads (`readAsSystem` / `listAsSystem`)
665
+ * and the trusted writes (`createAsSystem` / `updateAsSystem` /
666
+ * `updateManyAsSystem`).
667
+ *
668
+ * A system-context call does not REMOVE the authorization decision — it
669
+ * RELOCATES it from the resource ACL onto the calling service, which MUST
670
+ * enforce an explicit alternative check (e.g. consumable-token or
671
+ * email-ownership matching). Declaring this policy is the data owner's
672
+ * statement that such a bypass is permissible at all, and for which verb. An
673
+ * absent policy — or a verb set to (or left defaulting to) `FORBIDDEN` — makes
674
+ * the primitive throw.
675
+ *
676
+ * The WRITE verbs additionally let a trusted in-process caller persist the
677
+ * fields the client-shaped request DTO strips — `.isBackendOnly()` material
678
+ * (e.g. a credential `passwordHash`) and the context-auto-populated FKs (e.g.
679
+ * `userId` on a system resource that has no HTTP surface to seed it) — by
680
+ * re-attaching exactly those fields after the strict parse. They are the
681
+ * sanctioned path for engine flows like registration that must write system
682
+ * resources directly; opting a verb in is the data owner's acknowledgement that
683
+ * a super-admin-context mutation of this resource is legitimate.
684
+ *
685
+ * Caveats a system-context call inherits (it runs as super-admin), to weigh
686
+ * before opting in:
687
+ * - a READ returns the FULL record — every field, including ones a normal
688
+ * caller's role / field-visibility would hide — so never forward the result
689
+ * verbatim to an under-privileged caller; project only what is safe.
690
+ * - a WRITE bypasses the caller's scope + role ACL, so the calling service
691
+ * owns the authorization decision (only trusted engine code can reach the
692
+ * primitive — it is never exposed to an HTTP payload).
693
+ * - feature flags do not gate it (it is an internal request).
694
+ * - the policy is RESOURCE-LEVEL: for a polymorphic resource it is shared by
695
+ * every scope variant (declare it once on the shared config).
696
+ *
697
+ * Intentionally DISTINCT from `isSystemResource`: marking a resource as
698
+ * framework infrastructure does NOT imply that an ACL bypass is acceptable
699
+ * for its data. Keep the two concepts separate.
700
+ */
701
+ /**
702
+ * Declares that THIS resource is the application's subject-erasure request lane, and how to read it.
703
+ *
704
+ * ## Why the application declares it rather than the framework knowing it
705
+ *
706
+ * The erasure lane is application-owned — four of the five marked sites for
707
+ * `WILDO.PRIVACY.SUBJECT_ERASURE` are in an application, not the engine — and its evidence demand
708
+ * (`evidence-requirement:subject-erasure-execution-record`) says so in terms: *"the row's schema and
709
+ * status vocabulary are the application's, so a collector queries it against that application's
710
+ * specification"*, and its verification step adds *"do NOT assert a specific channel vocabulary:
711
+ * that is one application's modelling choice"*.
712
+ *
713
+ * So a collector may not know that a request is raised through a field called `channel` carrying a
714
+ * value called `SUBJECT`. It has to be TOLD, by the application, in a form it can read. Before this
715
+ * existed, three clauses of that demand had a durable row holding every fact they wanted and no way
716
+ * to find it (#1209): not a missing control, a control nobody could point at.
717
+ *
718
+ * ## It binds FIELDS, never values the framework invents
719
+ *
720
+ * Every member below names something the application already authored. The one value the
721
+ * declaration carries — {@link ResourceSubjectErasureLane.raisedBy}`.subjectValue` — is the
722
+ * application's OWN enum member, quoted back so a reader can tell the two populations apart. The
723
+ * framework supplies no vocabulary here and must never grow one.
724
+ *
725
+ * ## What is deliberately NOT declared
726
+ *
727
+ * The SCHEDULE. C3 asks that requests be executed on the declared schedule, and that schedule is
728
+ * already on the executing operation's `CRON_JOB` variant (`cronExpression`) — declaring it again
729
+ * here would be a second copy that can only ever disagree with the one the scheduler reads.
730
+ * `executionOperationIdentifier` names the operation; the schedule is read from it.
731
+ */
732
+ export type ResourceSubjectErasureLane = {
733
+ /**
734
+ * How a row says WHO raised the request — the subject exercising their own right, or the
735
+ * controller acting on their behalf. C1's whole obligation is that the two are distinguishable.
736
+ */
737
+ raisedBy: {
738
+ /** The field carrying it. Must be a persisted field of this resource. */
739
+ fieldName: string,
740
+ /**
741
+ * The value of that field meaning the SUBJECT raised it themselves. Every other value is read as
742
+ * controller-raised — stated this way round because a lane may grow a second controller channel
743
+ * without the declaration going stale, whereas enumerating the controller values could not.
744
+ */
745
+ subjectValue: string,
746
+ },
747
+ /**
748
+ * The field carrying WHICH user raised a controller-raised request.
749
+ *
750
+ * Omitting it is a positive claim, not a gap: it says this lane admits no controller-raised
751
+ * request at all. A collector reads it that way and a row carrying a non-subject value then
752
+ * contradicts the declaration, which is a finding about the application rather than about the
753
+ * evidence.
754
+ */
755
+ requesterFieldName?: string,
756
+ /** The field carrying the justification a controller-raised request was made on, where the lane records one. */
757
+ justificationFieldName?: string,
758
+ /** The field carrying the instant the request was executed or failed. C3 judges execution against it. */
759
+ completedAtFieldName: string,
760
+ /** The field carrying what the execution did. Its vocabulary is the application's. */
761
+ outcomeFieldName: string,
762
+ /**
763
+ * The operation a SUBJECT uses to withdraw their own pending request (C2). Named rather than
764
+ * inferred: "the operation that cancels" is not derivable from an operation vocabulary, and
765
+ * guessing it would make the evidence depend on a naming convention no application agreed to.
766
+ */
767
+ withdrawalOperationIdentifier: string,
768
+ /**
769
+ * How a WITHDRAWN row is recognisable afterwards — the same shape as {@link raisedBy}, and for the
770
+ * same reason: the vocabulary is the application's.
771
+ *
772
+ * C2 asks for the withdrawal door AND for "any cancelled rows", and those are two different
773
+ * questions. The door is answered from {@link withdrawalOperationIdentifier} — is the operation
774
+ * reachable to a subject while the request is pending — and needs no data at all. The rows need a
775
+ * marker, and there is nothing to derive one from: withdrawal and execution both leave a request in
776
+ * a terminal state, so a reader that knows only `completedAtFieldName` cannot tell "the subject
777
+ * changed their mind" from "the sweep ran".
778
+ *
779
+ * OPTIONAL, because an application may not model withdrawal as a value at all — it may delete the
780
+ * row, or move it. Omitting it says the count is unavailable, and a collector reports that rather
781
+ * than guessing; it never turns into a zero, which would read as "nobody withdrew anything".
782
+ *
783
+ * Note an EMPTY withdrawal set is explicitly not a deficiency in the demand — people do not have
784
+ * to change their minds — so this exists to make the number REPORTABLE, never to make it a target.
785
+ */
786
+ withdrawnMarker?: {
787
+ /** The field carrying it. Must be a persisted field of this resource. */
788
+ fieldName: string,
789
+ /** The value of that field meaning the SUBJECT withdrew the request before it executed. */
790
+ withdrawnValue: string,
791
+ },
792
+ /** The scheduled operation that executes due requests. Its `cronExpression` IS the declared schedule. */
793
+ executionOperationIdentifier: string,
794
+ };
795
+
796
+ export type ResourceSystemAccessPolicy = {
797
+ /** Governs `readAsSystem`. Omitted ⇒ FORBIDDEN. */
798
+ read?: ResourceSystemAccessMode,
799
+ /** Governs `listAsSystem`. Omitted ⇒ FORBIDDEN. */
800
+ list?: ResourceSystemAccessMode,
801
+ /** Governs `createAsSystem`. Omitted ⇒ FORBIDDEN. */
802
+ create?: ResourceSystemAccessMode,
803
+ /** Governs `updateAsSystem`. Omitted ⇒ FORBIDDEN. */
804
+ update?: ResourceSystemAccessMode,
805
+ /** Governs `updateManyAsSystem`. Omitted ⇒ FORBIDDEN. */
806
+ updateMany?: ResourceSystemAccessMode,
807
+ // NOTE: there is deliberately NO `delete` verb here — there is no `deleteAsSystem` primitive. A row is
808
+ // removed either through its own DELETE operation ACL (e.g. an owner-facing `API_CALL` DELETE under the
809
+ // USER_SELF owner filter) or by the `onParentDelete` composition cascade (which deletes at the raw
810
+ // repository layer, variant-agnostic — see `deleteChildrenImmediate`). If you find yourself reaching
811
+ // for `systemAccessPolicy.delete`, model the removal as one of those two instead.
812
+ /**
813
+ * Governs the impersonalization see-through reads (`readRetainedAsSystem` /
814
+ * `listRetainedAsSystem`) — the privileged, audited path that reveals
815
+ * `retentionStatus = RETAINED` rows hidden-by-default. Omitted ⇒ FORBIDDEN.
816
+ * Auto-derived to `ALLOWED` by the factory when a resource opts into
817
+ * `retentionPolicy`; never authored by hand in the common case.
818
+ *
819
+ * **LIVE, and REACHABLE.** `readRetainedAsSystem` / `listRetainedAsSystem` exist and are enforced:
820
+ * the verb is asserted fail-closed, a privileged human role is required, and every reveal emits a
821
+ * human-attributed `RETAINED_DATA_ACCESS` audit event.
822
+ *
823
+ * "Reachable" is the half that was missing until #490, and the distinction is worth keeping. The
824
+ * primitives were correct and enforced from the day M5b landed — and had **no caller**, so the only
825
+ * route an operator actually had to a retained record was a database console: the unaudited path
826
+ * they were built to replace. `users | read_retained` is the operator surface that closes it, an
827
+ * authenticated `APP_ADMIN_SUPER_ADMIN` operation carrying a mandatory justification.
828
+ *
829
+ * A resource that derives this grant and exposes no such operation is reachable by nothing. That
830
+ * is a defensible state — not every retention resource needs an operator door — but it should be a
831
+ * decision rather than an oversight, and `retained-see-through-operator-surface.test.ts` is what
832
+ * makes it one.
833
+ *
834
+ * (This block previously said the primitives were "wired in a later phase" — false since M5b.)
835
+ */
836
+ seeRetained?: ResourceSystemAccessMode,
837
+
838
+ /**
839
+ * May this resource's rows be swept into a SUBJECT EXPORT bundle (GDPR Art. 15 / Art. 20)?
840
+ *
841
+ * Fail-closed by omission, like every other verb here. A subject export reads across the whole
842
+ * child-direction graph of its subject, so without an explicit opt-in a resource could be
843
+ * disclosed to a data subject because it merely sits on an edge — nobody having decided that its
844
+ * contents are appropriate to hand over.
845
+ *
846
+ * **The refusal is LOUD, not a silent skip.** When an edge the classifier marked for inclusion
847
+ * belongs to a resource that has not opted in, the export REFUSES and names it. Silently dropping
848
+ * it would produce an access bundle that is incomplete without saying so — a disclosure failure
849
+ * wearing the appearance of a successful response, which is the same class of lie as the routed
850
+ * export operations this capability replaced. Refusing is a one-line fix per resource; a silent
851
+ * omission is undetectable.
852
+ *
853
+ * NOT derived from `portabilityPolicy`: declaring where fields came from (Art. 20 scoping) and
854
+ * consenting to be disclosed at all are different decisions, and a resource may legitimately want
855
+ * the first without the second.
856
+ */
857
+ exportSubject?: ResourceSystemAccessMode,
858
+ };
859
+ ```