@wildo-ai/framework-knowledge 1.1.2 → 1.1.3

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 (287) 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 +228 -6
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
  6. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  8. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -4
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -4
  13. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +4 -4
  15. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -1
  17. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
  19. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -1
  21. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
  23. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +1 -2
  25. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -2
  27. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -3
  29. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +3 -3
  31. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -2
  33. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
  35. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -1
  37. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +0 -1
  39. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +0 -1
  41. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +0 -1
  43. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +0 -1
  45. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +0 -1
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -1
  49. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  50. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
  51. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  52. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +0 -1
  53. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
  55. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  56. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +0 -2
  57. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +2 -2
  59. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  60. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +0 -1
  61. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +0 -1
  63. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -1
  65. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +0 -1
  67. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
  69. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +0 -1
  71. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -1
  73. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +0 -1
  75. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
  77. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -4
  79. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
  81. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
  83. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
  85. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
  87. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -1
  89. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  91. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +0 -1
  93. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
  95. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  96. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +0 -1
  97. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
  99. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  100. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +0 -1
  101. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +0 -1
  103. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  104. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
  105. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  107. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -1
  109. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +0 -1
  111. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  112. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  113. package/dist/knowledge/manifest.json +8 -9
  114. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
  115. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
  116. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
  117. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
  118. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
  119. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
  120. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
  121. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
  122. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
  123. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
  124. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
  125. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
  126. package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
  127. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
  128. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
  129. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
  130. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
  131. package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
  132. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
  133. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
  134. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
  135. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
  136. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
  137. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
  138. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
  139. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
  140. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
  141. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
  142. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
  143. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
  144. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
  145. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
  146. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
  147. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
  148. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
  149. package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
  150. package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
  151. package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
  152. package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
  153. package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
  154. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
  155. package/dist/knowledge/references/platform.config.saas.md +0 -51
  156. package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
  157. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
  158. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
  159. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
  160. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
  161. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
  162. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
  163. package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
  164. package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
  165. package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
  166. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
  167. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
  168. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
  169. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
  170. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
  171. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
  172. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
  173. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
  174. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
  175. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
  176. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
  177. package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
  178. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
  179. package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
  180. package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
  181. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
  182. package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
  183. package/dist/knowledge/registries/framework-topics.json +11 -146
  184. package/dist/knowledge/registries/playbooks.json +18 -154
  185. package/dist/knowledge/registries/source-tags.json +630 -883
  186. package/dist/knowledge/skills/INDEX.md +3 -4
  187. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
  188. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
  189. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
  190. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
  191. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
  192. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
  193. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
  194. package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
  195. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
  196. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
  197. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
  198. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
  199. package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
  200. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
  201. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
  202. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
  203. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
  204. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
  205. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
  206. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
  207. package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
  208. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
  209. package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
  210. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -213
  211. package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
  212. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
  213. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
  214. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
  215. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
  216. package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
  217. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
  218. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
  219. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
  220. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
  221. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
  222. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
  223. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
  224. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
  225. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
  226. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
  227. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
  228. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
  229. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
  230. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
  231. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
  232. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
  233. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
  234. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
  235. package/dist/knowledge/topic-index.json +220 -725
  236. package/dist/tsconfig.build.tsbuildinfo +1 -1
  237. package/dist/tsconfig.tsbuildinfo +1 -1
  238. package/package.json +4 -4
  239. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
  240. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
  241. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
  242. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
  243. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
  244. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
  245. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
  246. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
  247. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
  248. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
  249. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
  250. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
  251. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
  252. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
  253. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
  254. package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
  255. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
  256. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
  257. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
  258. package/dist/knowledge/references/placement-plan.config.md +0 -330
  259. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
  260. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
  261. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
  262. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
  263. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
  264. package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
  265. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
  266. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
  267. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
  268. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
  269. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
  270. package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
  271. package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
  272. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
  273. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
  274. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
  275. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
  276. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
  277. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
  278. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
  279. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
  280. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
  281. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
  282. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
  283. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
  284. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
  285. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
  286. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
  287. /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
@@ -96,14 +96,13 @@ navigation, design tokens.
96
96
 
97
97
  | Skill | Trigger phrases |
98
98
  | -------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
99
- | **`config-saas`** — edit `wildo.saas.config.ts` for modules, services, capabilities, and the compliance declarations (operating entity, jurisdictions, retention, AI posture, client storage, provider choices) | "edit wildo.saas.config.ts", "add a module to SaaS config", "wire a new capability at root", "register a service at the app level", "record our legal entity", "declare which jurisdictions we operate in", "set the retention schedule", "who is the data controller" |
99
+ | **`config-saas`** — edit `wildo.saas.config.ts` for modules, services, capabilities | "edit wildo.saas.config.ts", "add a module to SaaS config", "wire a new capability at root", "register a service at the app level" |
100
100
  | **`config-saas-backend`** — edit `saas-config.backend.ts`: auth posture, user types, passkey RP, email From, frontend-service login exposure | "change the password policy", "enable magic link / MFA / passkeys", "add a user type", "nobody can log in", "authentication_method_not_supported", "set the From address" |
101
101
  | **`configure-billing`** — enable billing / make a backend-reachable provider resolve across the 5-surface config chain | "enable billing", "turn on Stripe", "billing crash-loops the backend", "wire up subscriptions/checkout", "provider not reachable on the backend", "my provider is authored but the backend can't reach it" |
102
102
  | **`provider-frontend-file-picker`** — add or tune the frontend FILE PICKER provider (browser-bound module + contribution + scope; framework file fields resolve its constraints automatically) | "add a file picker", "let users attach files", "restrict uploads to PDFs", "raise the upload size limit", "file field accepts anything", "picker allows too many files", "wire a file upload provider" |
103
- | **`config-app-shell`** — configure menubar, sidebar, command menu (static commands + omnibox record search), their labels, and whether the PUBLIC (sign-in / sign-up) pages carry the application's identity | "edit the menubar", "change sidebar chrome", "enable the Cmd+K command menu", "add record search to the command palette", "make Cmd+K search todos", "turn on omnibox search", "command-bar label changes", "app shell label edits", "show our logo on the login page", "put the app name on the sign-in screen", "brand the sign-up page", "the login page does not say which product it is" |
104
- | **`settings-placement-authoring`** — author the application's Settings rail: which engine settings destinations are placed, in which category, in what order, under what name. The engine ships destinations and NO arrangement, so a section that is not placed does not appear | "add a settings section", "remove billing from settings", "reorder the settings tabs", "rename a settings section", "put SSO under a different group", "my settings section is not showing", "the settings menu opens the wrong page" |
103
+ | **`config-app-shell`** — configure menubar, sidebar, command menu (static commands + omnibox record search) and their labels | "edit the menubar", "change sidebar chrome", "enable the Cmd+K command menu", "add record search to the command palette", "make Cmd+K search todos", "turn on omnibox search", "command-bar label changes", "app shell label edits" |
105
104
  | **`config-navigation`** — configure navigation layout, zones, transitions, viewport behavior | "change navigation zones", "configure viewport behavior", "tweak nav transitions", "edit navigation layout" |
106
- | **`config-design-system`** — edit design system tokens, theme materials, refractive budget, surfaces, `surfacePolicies`, generated CSS, and the FIRST-PAINT theme behavior declared in `frontend/index.html` | "edit design tokens", "change theme surfaces", "configure glass materials", "set refraction budget", "configure surface policy", "change SHELL main landmark behavior", "update CSS tokens output", "tweak design system config", "the app flashes white before it loads", "dark mode is ignored on the login screen", "editing frontend/index.html", "add a favicon or meta tags to the app page" |
105
+ | **`config-design-system`** — edit design system tokens, theme materials, refractive budget, surfaces, `surfacePolicies`, generated CSS | "edit design tokens", "change theme surfaces", "configure glass materials", "set refraction budget", "configure surface policy", "change SHELL main landmark behavior", "update CSS tokens output", "tweak design system config" |
107
106
 
108
107
  ### Modules & Engine — registration, relationships, companion exports
109
108
 
@@ -64,8 +64,7 @@ Classify → author name → direct the mark → set the visual tone → verify.
64
64
 
65
65
  ### Step 1: Locate / create the brand snapshot
66
66
 
67
- Current landed value, live: `wildo context info specification-artifacts` (find the `brand-brief`
68
- family row — landed state, validator verdict, rendered outline).
67
+ // TODO CLI COMMAND: wildo context spec brand --template brand-all-information
69
68
  Author (or open) `specifications/src/brand/index.ts` — the single
70
69
  `BrandSnapshot` instance, wired to the companion via the `brandSpecification`
71
70
  slot in `specifications/src/companion-exports.ts` (mirrors how
@@ -113,26 +113,12 @@ Never collapse these into one generated file or one `accepted` flag.
113
113
 
114
114
  ### 1. Read the definition and blueprint
115
115
 
116
- **The blueprint for your document is in your brief**, under the heading *"What a … must contain
117
- (ENGINE CATALOG, not your judgement)"*. It lists the facts the document is obliged to address, its
118
- sections in order, and each clause with its inclusion kind. Read it first — everything below is about
119
- answering it.
120
-
121
- Do not go looking for a file. Until 2026-08-30 this step said only "read the contract" and no
122
- blueprint reached the lane at all, so a drafter followed the instruction, learned what a blueprint IS,
123
- and invented the structure anyway. The measured result: a notice addressing NONE of the eight facts
124
- its blueprint requires.
125
-
126
- Read `references/framework-assurance-document-blueprint-contract.md` for how to interpret a question,
127
- condition, claim-guard or checklist field. That page is the contract; your brief is the instance.
116
+ Read `references/framework-assurance-document-blueprint-contract.md` before interpreting any question,
117
+ condition, claim-guard or checklist field.
128
118
 
129
119
  The blueprint describes what the candidate must **address**. It is not legal prose and must never be
130
120
  rendered verbatim as if it were approved terms.
131
121
 
132
- **A required fact you cannot answer does not license dropping its section.** Write the clause, say the
133
- answer is not established, and mark it — step 2 has the exact shape. A missing section is invisible; an
134
- incomplete clause is a gap a reviewer can act on.
135
-
136
122
  ### 2. Read the declared facts
137
123
 
138
124
  Read `specifications/src/document-facts/`, and
@@ -44,11 +44,7 @@ needs and no further.
44
44
 
45
45
  **Derives from** — the application's authored authentication configuration (methods enabled, MFA,
46
46
  password policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored
47
- secrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned
48
- (ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA
49
- capability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was
50
- withdrawn because no provider could fill it, and a derived control statement must never rest on a
51
- slot that cannot be configured.
47
+ secrets, and the `ANTIVIRUS_SCANNING` engine capability where a provider is configured for it.
52
48
 
53
49
  **Completeness** — `DERIVED`, bounded.
54
50
 
@@ -119,15 +115,8 @@ CONTROLLER for the data it holds about the customer's users as account holders.
119
115
  roles with different duties over the same database. Say which is which; do not pick one and apply it
120
116
  to everything.
121
117
 
122
- **The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
123
- `wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
124
- stores about its own people, CONTROLLER for the account data of the people who administer them. It is
125
- a LIST for exactly the reason this fragment gives: those are different roles over the same database,
126
- and a single field would force one of them to be wrong.
127
-
128
- Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
129
- surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
130
- so the remedy is to fill it in rather than to build something. See the legal-basis fragment.
118
+ Where a document needs to attribute a duty and the attribution is not established, that is a
119
+ `NEEDS_DECISION` — never a guess. See the legal-basis fragment.
131
120
 
132
121
 
133
122
  ### Concern: operator identity
@@ -135,25 +124,14 @@ so the remedy is to fill it in rather than to build something. See the legal-bas
135
124
  **Asserts** — who legally operates the service: entity name, registered address, contact route for
136
125
  data-protection questions, and a representative where one is required.
137
126
 
138
- **Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
139
- registered address, the privacy contact route, and an Art. 27 representative where one is required.
140
-
141
- The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
142
- What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
143
- said "no engine change would close it", which was right about derivation and wrong about the home.
144
- The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
145
- who answered by editing the document lost the answer at the next regeneration — the answer has to live
146
- in the application or it does not survive.
147
-
148
- **Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
127
+ **Derives from** — nothing, and nothing could. A legal entity is a fact about the world, not a
128
+ property of a codebase, so this is not a framework gap and no engine change would close it.
149
129
 
150
- ⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
151
- exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
152
- and nobody has. They have different remedies — build something, versus fill something in — and a
153
- reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
130
+ **Completeness** — `NEEDS_DECISION`, always, until the operator supplies it.
154
131
 
155
- **What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
156
- filled in later without redrafting anything around it, which is the reason it is not a blocker.
132
+ **What closes it** — the operator recording the entity, address and contact route. That is the second
133
+ step, and it is cheap: the reason it is not a blocker is precisely that it can be filled in later
134
+ without redrafting anything around it.
157
135
 
158
136
  **Never infer it.** Not from the application name, not from a domain, not from another application,
159
137
  not from model memory. A published legal document naming the wrong entity is worse than one that says
@@ -31,25 +31,14 @@ first draft from reading as either uniformly confident or uniformly empty.
31
31
  **Asserts** — who legally operates the service: entity name, registered address, contact route for
32
32
  data-protection questions, and a representative where one is required.
33
33
 
34
- **Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
35
- registered address, the privacy contact route, and an Art. 27 representative where one is required.
34
+ **Derives from** — nothing, and nothing could. A legal entity is a fact about the world, not a
35
+ property of a codebase, so this is not a framework gap and no engine change would close it.
36
36
 
37
- The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
38
- What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
39
- said "no engine change would close it", which was right about derivation and wrong about the home.
40
- The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
41
- who answered by editing the document lost the answer at the next regeneration — the answer has to live
42
- in the application or it does not survive.
37
+ **Completeness** — `NEEDS_DECISION`, always, until the operator supplies it.
43
38
 
44
- **Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
45
-
46
- ⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
47
- exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
48
- and nobody has. They have different remedies — build something, versus fill something in — and a
49
- reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
50
-
51
- **What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
52
- filled in later without redrafting anything around it, which is the reason it is not a blocker.
39
+ **What closes it** — the operator recording the entity, address and contact route. That is the second
40
+ step, and it is cheap: the reason it is not a blocker is precisely that it can be filled in later
41
+ without redrafting anything around it.
53
42
 
54
43
  **Never infer it.** Not from the application name, not from a domain, not from another application,
55
44
  not from model memory. A published legal document naming the wrong entity is worse than one that says
@@ -65,30 +54,14 @@ with gaps beats blocking: the whole document set would be unproducible until one
65
54
  **Asserts** — the lawful basis for each processing purpose, and whether the operator acts as
66
55
  controller or processor for it.
67
56
 
68
- **Derives from** — `operatorComplianceIdentity.lawfulBases` and `.roleAllocations` in
69
- `wildo.saas.config.ts`.
70
-
71
- The DETERMINATIONS are never derivable — both are legal conclusions about the operator's own
72
- arrangements, and the framework can show WHAT is processed and BY WHICH MECHANISM without establishing
73
- under which basis or in which role. What it now provides is where to record the conclusion, so that a
74
- regeneration reproduces it instead of destroying it.
75
-
76
- **The role is a LIST, not a field, and the produced notice said so before the surface existed:**
77
- *"This notice therefore does not assign a single legal role to all data processed in a workspace."* A
78
- B2B SaaS is typically a processor for the records its customers put in and a controller for its
79
- account holders' own data, simultaneously. `roleAllocations` carries one role per population, and a
80
- document that collapses them into one is wrong about both.
57
+ **Derives from** — nothing. Both are legal determinations about the operator's own arrangements. The
58
+ framework can show WHAT is processed and BY WHICH MECHANISM; it cannot establish under which basis, or
59
+ in which role.
81
60
 
82
- **`LEGITIMATE_INTERESTS` cannot be declared without its assessment** — the schema refuses it. It is
83
- the only Art. 6(1) basis whose lawfulness depends on a balancing test, so the bare claim asserts a
84
- conclusion nobody reached.
85
-
86
- **Completeness** — `DERIVED` when declared; `NEEDS_DECISION` when not. Never `NEEDS_FRAMEWORK`: there
87
- is a surface, so the remedy is to fill it in, not to build something. Name the surface when reporting
88
- the gap.
61
+ **Completeness** — `NEEDS_DECISION`.
89
62
 
90
63
  **What closes it** — the operator determining, per purpose, the basis and the role, ideally with
91
- counsel, and declaring them in `operatorComplianceIdentity`. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for
64
+ counsel. The tenancy fragment describes the SHAPE this usually takes in a B2B SaaS — processor for
92
65
  the data a customer stores about its own people, controller for the data the operator holds about
93
66
  account holders — but describing the common shape is not the same as determining this operator's, and
94
67
  the produced document must not present the first as the second.
@@ -117,20 +90,6 @@ invoice and of a CRM contact, so it never tells you whether a record is about a
117
90
  retention mode does.
118
91
 
119
92
  **Completeness** — `DERIVED` for every resource that declares a retention policy.
120
-
121
- **An erasure-coverage gap does NOT license a claim about whether personal data is held.** The two are
122
- different axes and the facts report them separately: `retentionPolicy` answers *what happens to this
123
- row on erasure*, while a field's `.dataCategories()` answers *what kind of data is in it*. A resource
124
- can declare the second and not the first, and 48 of the engine's 85 do.
125
-
126
- So writing "N resources have no declared erasure treatment, so this notice cannot establish whether
127
- they hold personal data" is an over-reach, and it contradicts the data-categories section of the same
128
- document — which enumerates categories drawn from those very resources. It was produced twice on
129
- 2026-08-30 before this paragraph existed.
130
-
131
- State the gap as what it is: those resources have not declared an erasure TREATMENT, so a notice
132
- cannot say what an erasure does to them. Where the facts also report a category coverage for the same
133
- origin, say what IS established alongside it.
134
93
  `NEEDS_CONFIGURATION` for every resource that does not.
135
94
 
136
95
  **What closes it** — the application's own authors declaring `retentionPolicy` on the resource. Name
@@ -139,43 +98,28 @@ the resources individually: the remedy is per-resource, and a count is not actio
139
98
 
140
99
  ### Concern: data categories
141
100
 
142
- **Asserts** — which CATEGORIES of personal data are held: identity, contact details, credentials,
143
- financial, usage, location, user content, professional, and any GDPR Art. 9 special-category or
144
- Art. 10 criminal-offence data.
101
+ **Asserts** — which CATEGORIES of personal data are held: contact details, identifiers, financial
102
+ data, usage data, and any special-category data.
145
103
 
146
- **Derives from** — each field's `.dataCategories()` declaration, reported per resource and unioned
147
- across the application in the compliance-primary-facts section. One category is DERIVED rather than
148
- declared: `credentials`, from `.isPassword()` / `.isOtp()` / `.isWriteOnlySecret()`, which are
149
- markers the author already wrote.
104
+ **Derives from** — nothing usable today, and the near-miss matters. `Compliance_DataClassification`
105
+ exists and is a four-level SENSITIVITY ladder (public / internal / confidential / restricted) applied
106
+ only to flows-actors configuration. It answers "how protected must this be", not "what kind of
107
+ personal data is this", and using it as a category vocabulary would produce a notice describing
108
+ protection levels where a reader expects data types.
150
109
 
151
- **Nothing is derived from a field NAME.** `email`, `phone` and `dateOfBirth` are suggestive while
152
- `notes` is not, so a category list assembled by pattern-matching identifiers is a guess presented as
153
- an inventory — and its failure mode is silent, because whatever the guess misses is simply not
154
- disclosed. The declaration exists so that never happens.
110
+ Say that explicitly when recording this gap, or the next reader will point at that enum and assume
111
+ the concern is already answered.
155
112
 
156
- **Completeness** — `DERIVED` when the application declares categories; `NEEDS_CONFIGURATION` when it
157
- declares none, or when the facts section lists OUTSTANDING fields.
113
+ **Completeness** — `NEEDS_FRAMEWORK`.
158
114
 
159
- **The two gaps are different and must not be written the same way.**
115
+ **What closes it** — an engine change adding a data-category vocabulary declarable per resource and
116
+ per field — issue #90. Per FIELD is what makes it worth having: a resource-level category
117
+ cannot express that one row holds a name, an email and a payment token, which is exactly what a
118
+ notice must enumerate.
160
119
 
161
- - A resource that declares no category at all may genuinely hold no personal data. Nothing
162
- distinguishes "considered and not applicable" from "never asked", so state that the question is
163
- unanswered — never that the application holds no personal data.
164
- - A field the facts section lists as OUTSTANDING is a provable omission. The application already
165
- declared that field personal by another door — an erasure scrub treatment, a portability
166
- provenance, or a credential marker — so the missing category is an omission, not a judgement.
167
- Name the field and its basis. Do not guess what it contains.
168
-
169
- **Say WHICH special category, not that there is one.** A `special-category:*` value is Art. 9 data
170
- and carries a lawful-basis condition of its own beyond Art. 6; `criminal-offence` is Art. 10, a
171
- separate article with a different condition. "We process special category data" is not a disclosure —
172
- the enum names the kind precisely so a notice can.
173
-
174
- **Do NOT point at `Compliance_DataClassification`.** It exists, it is a four-level SENSITIVITY ladder
175
- (public / internal / confidential / restricted) applied only to flows-actors configuration, and it
176
- answers "how protected must this be" rather than "what kind of personal data is this". Using it here
177
- would produce a notice describing protection levels where a reader expects data types. It is named
178
- explicitly because it is a near-miss a reader will otherwise find and assume answers this concern.
120
+ **Do not derive categories from field names.** `email`, `phone`, `dateOfBirth` are suggestive and
121
+ `notes` is not, and a category list assembled by pattern-matching identifiers is a guess presented as
122
+ an inventory — the failure mode being that whatever the guess misses simply is not disclosed.
179
123
 
180
124
 
181
125
  ### Concern: consent and preferences
@@ -187,34 +131,11 @@ actually controls.
187
131
 
188
132
  - `DataProcessingConsent` (`saas-models` → `compliance/privacy/privacy.shared.schemas.ts`):
189
133
  `NONE` · `BASIC` · `ANALYTICS` · `MARKETING` · `FULL` — a ladder, so a level implies the ones below it.
190
- - `analytics.requiredConsent` (`app-configuration-shared.shared.schemas.ts`, default `ANALYTICS`) —
191
- the minimum consent level for ANALYTICS, and nothing wider.
134
+ - the application's `requiredConsent` (`app-configuration-shared.shared.schemas.ts`, default
135
+ `ANALYTICS`) — the minimum a person must give to use the service.
192
136
  - per-user `dataProcessingConsent` — the level each person actually chose.
193
137
 
194
- ⚠️ **`requiredConsent` is ANALYTICS-SCOPED, and this fragment claimed otherwise until 2026-08-30.**
195
- It read "the minimum a person must give to use the service", which is a different and much larger
196
- claim; the field sits inside `AnalyticsConfigSchema` and governs analytics alone. A drafter following
197
- the old wording would have published that a person must consent to analytics in order to use the
198
- product — false, and false about the one subject where a reader is most likely to act on it.
199
-
200
- - `operatorComplianceIdentity.serviceConsentRequirement` (`wildo.saas.config.ts`) — what a person
201
- must agree to in order to use the service AT ALL, and what that gate covers.
202
-
203
- **`NONE` is a POSITIVE answer and the usual one.** The operator declaring that nothing is gated on
204
- consent has answered the question; a document must state it as settled rather than treating it as an
205
- absence. ABSENT is the different case — nobody was asked — and the brief distinguishes the two.
206
-
207
- **A consent GATE is not a lawful BASIS.** For most B2B SaaS the basis for core processing is CONTRACT:
208
- a person uses the product because their employer signed for it. A notice that reads a gate as a basis
209
- states that their data is processed on consent they could withdraw, which is wrong about the single
210
- most consequential thing in the document. The basis is declared per purpose in `lawfulBases`.
211
-
212
- **Completeness** — `DERIVED` for the analytics gate, the per-user level, and the service-wide
213
- requirement once declared; `NEEDS_DECISION` naming `serviceConsentRequirement` when it is not.
214
-
215
- This was `NEEDS_FRAMEWORK` until 2026-08-30, correctly: there was nowhere to record the answer. Issue
216
- #139 built the surface, so the remedy changed from "someone must build this" to "fill this in" — a
217
- different party and a different task, which is why the two states are never interchangeable.
138
+ **Completeness** — `DERIVED`.
218
139
 
219
140
  **Say the thing readers get wrong.** Consent is one lawful basis among several, and it is not the one
220
141
  most B2B processing rests on. **Never write that all processing rests on consent, and never write
@@ -235,27 +156,17 @@ marked `.impersonalizeWith()`; `RETAIN_ONLY` keeps and freezes a row that holds
235
156
  its own. Reading the per-field treatments tells the document exactly WHICH values are destroyed and
236
157
  which survive, which is a genuinely strong statement most notices cannot make.
237
158
 
238
- **Derives from (the HOW LONG)** — the application's `dataRetention` schedule, declared in its config
239
- over four data classes: `RESOURCE_DATA` (its records), `FILES` (uploaded bytes), `AUDIT_LOGS` (the
240
- tamper-evident trail, kept longest and for a different reason — it is the evidence an operator may
241
- lawfully retain under GDPR Art. 17(3)) and `OPERATIONAL_LOGS`. Each declared class carries a period in
242
- days AND the operator's stated reason for it.
159
+ **Not derivable (the HOW LONG)** — nothing in the framework declares a retention DURATION. A resource
160
+ says what erasure does to it; no declaration says "kept for seven years", and none can be inferred
161
+ from anything present.
243
162
 
244
- The classes are the STORES on purpose: the same declaration answers what a notice must state and what
245
- a backup-and-restore inventory must protect (issue #8).
163
+ **Completeness** — `DERIVED` for the treatment, `NEEDS_FRAMEWORK` for the duration, in the same
164
+ fragment. Do not let the derivable half hide the missing one: a statement about erasure mechanics
165
+ reads to a reader as an answer about retention, so the gap must be stated in the same breath.
246
166
 
247
- **Completeness** — `DERIVED` for the treatment, and for each retention class the application HAS
248
- declared. `NEEDS_DECISION` for each class it has not: the mechanism exists, so what is missing is an
249
- operator's decision rather than an engine change. Do not let the derivable half hide the missing one —
250
- a statement about erasure mechanics reads to a reader as an answer about retention, so both go in the
251
- same breath.
252
-
253
- **What closes it** — the operator deciding a period, and saying why. Not a framework change: issue #89
254
- delivered the declaration surface, so an undeclared class is now an unanswered question rather than an
255
- unaskable one.
256
-
257
- **An UNDECLARED class is not "kept indefinitely" and not "deleted immediately".** It is a decision
258
- nobody has taken, and the document must say exactly that.
167
+ **What closes it** — an engine change adding a declared retention period per resource or data
168
+ category — issue #89. Until then the produced document says the duration is not yet
169
+ established and names what would settle it.
259
170
 
260
171
  **Never write a placeholder period.** "Typically 12 months" in a published notice is a commitment
261
172
  nobody made and nothing enforces.
@@ -270,58 +181,16 @@ nobody made and nothing enforces.
270
181
  That establishes THAT a third party is involved and WHAT FUNCTION it performs — email delivery,
271
182
  storage, payments, LLM inference, observability.
272
183
 
273
- **Derives from (the identities)** — the application's PROCESSOR REGISTER, which your brief renders
274
- under *"Who else processes personal data"*. Per entry: the processor's **legal entity**, the
275
- **regions** it processes in, and its own **subprocessors** with their regions.
276
-
277
- **The register holds two kinds of entry and the brief labels them differently — say which.** A
278
- CONFIGURED PROVIDER entry joins to the application's composition, so it can be checked against it: a
279
- claim about a provider the application does not configure is detectable, and a configured provider
280
- with no entry is reported as UNDECLARED. An AUTHORED entry — a hosting company, a CDN, a support desk
281
- — joins to nothing, because no configuration mentions it. The framework can neither confirm it nor
282
- notice its absence.
283
-
284
- Both are real processors and both belong in the notice. What must not happen is presenting the second
285
- with the authority of the first: an authored entry is the operator's word, and a document that reads
286
- as though the framework verified it overstates what anyone checked.
287
-
288
- **A SELF-HOSTED provider is not a recipient either, and this is the second way to get the section
289
- wrong.** The brief's *"Who RUNS each bound provider"* block splits runtime-bound providers three ways:
290
- THIRD-PARTY RECIPIENTS (vendor-hosted, so data reaches a third party — enumerate these with their
291
- region), OPERATOR-RUN (self-hosted, so no third party receives anything — state them as processing
292
- under the operator's own control, never as recipients), and UNANSWERED.
293
-
294
- An UNANSWERED provider is bound to a runtime with no declared deployment model. **Do not assume
295
- vendor-hosted.** It looks like the cautious reading and it is not: it publishes that a person's data
296
- goes to a third party when nobody said so. Report it as not established, and name the surface —
297
- `providerComplianceChoices` in `wildo.saas.config.ts`.
298
-
299
- **A provider PROFILE is not a recipient.** The brief separates providers BOUND TO A RUNTIME — backend,
300
- companion, workers, minions, a frontend service, which can process the application's data — from
301
- provider profiles with no runtime binding. A profile says how to reach a provider; build-time tooling
302
- lives there, and a coding agent operating on the workspace receives no customer records. Never name a
303
- profile-only provider as a recipient. Naming one reads as caution and is a false statement about
304
- somebody's data, exactly like omitting a real one.
305
-
306
- The section joins the register to the RUNTIME-BOUND providers, so it tells you three different things
307
- and they are not interchangeable:
308
-
309
- - a provider WITH an entry — state its legal entity and regions. `DERIVED`.
310
- - a provider listed **UNDECLARED** — it IS in use and nobody has established who it is. Name the
311
- function it performs (the capability says that) and state that its identity and location are
312
- outstanding. `NEEDS_DECISION`, closed by the operator establishing it.
313
- - a provider listed **STALE** — declared but no longer configured. Do NOT name it as a recipient; it
314
- receives nothing.
315
-
316
- **Completeness** — `DERIVED` per provider that is declared, `NEEDS_DECISION` per provider that is not.
317
- Not `NEEDS_FRAMEWORK` any more: issue #88 delivered the declaration surface, so an undeclared processor
318
- is an unanswered question rather than an unaskable one.
319
-
320
- **Never infer a region from a vendor's brand.** "It is a US company" is not a processing location, and
321
- a transfer statement built on it is a claim about somebody's data made from a guess.
322
-
323
- **Where the register is empty, the honest statement names the FUNCTIONS and admits the identities are
324
- outstanding.**
184
+ **Not derivable** — the three things a reader actually needs: the processor's **legal identity**, the
185
+ **region** it processes in, and its own **subprocessors**. A provider declares none of them.
186
+
187
+ **Completeness** — `NEEDS_FRAMEWORK`, and this is the largest single gap in the produced document. It
188
+ blocks this concern and the international-transfers one for every application, not just this one.
189
+
190
+ **What closes it** — an engine change giving a provider declaration a processor identity, a
191
+ processing region and a subprocessor list — issue #88.
192
+
193
+ **The honest interim statement names the FUNCTIONS and admits the identities are outstanding.**
325
194
  "Third parties process data for email delivery, file storage and payments; their identities and
326
195
  processing locations are not yet established in this document" is true, useful and specific. What is
327
196
  forbidden is the other two moves: inventing a plausible vendor list, and omitting the section — the
@@ -333,36 +202,17 @@ first is false and the second lets a reader assume there are no recipients at al
333
202
  **Asserts** — whether personal data leaves its origin jurisdiction, to where, and under which transfer
334
203
  mechanism.
335
204
 
336
- **Derives from** — the processor register's regions, at BOTH levels: each declared processor and
337
- each processor's own subprocessors. Your brief renders them under *"Personal data reaches processors
338
- in: …"*.
339
-
340
- Both levels, because the chain is what makes a transfer statement hard. An operator in France using a
341
- French vendor that runs on a US cloud HAS a transfer, and reading only the vendor's region misses it.
205
+ **Derives from** — nothing, and it cannot until the recipients-and-processors concern is answered:
206
+ a transfer statement is a statement about WHERE a recipient processes, so a provider declaration that
207
+ carries no region cannot support one.
342
208
 
343
- **The question has three inputs and the framework holds ONE.** Where declared processors process is
344
- derivable. Which jurisdiction is the ORIGIN, and which MECHANISM makes a given transfer lawful, are
345
- legal determinations with a shelf life — adequacy decisions move by court ruling, so a list baked into
346
- the engine would go stale silently and emit a false compliance statement. That is the worst failure
347
- this lane has, so it is deliberately not modelled.
209
+ **Completeness** — `NEEDS_FRAMEWORK`, dependent on that concern rather than independent of it. Say so
210
+ in the produced document; two gaps with one remedy read very differently from two unrelated holes.
348
211
 
349
- **Completeness** — three states, and they are three different claims. Do not round any of them up.
350
-
351
- | the register | what you may state | completeness |
352
- |---|---|---|
353
- | ABSENT | nothing — where data lands is unknown | `NEEDS_CONFIGURATION` |
354
- | declares NO processor | no personal data reaches a third party, so none is transferred THROUGH one | `DERIVED`, with the residual stated |
355
- | declares processors | where data lands, region by region | `DERIVED` for location; the transfer POSITION stays `NEEDS_DECISION` |
356
-
357
- **The residual is not optional wording.** "No processor receives personal data" establishes nothing
358
- about the operator's OWN processing — its infrastructure, its staff, its own establishment. A document
359
- that says "we do not transfer data internationally" on the strength of an empty register has answered
360
- a larger question than it was asked.
361
-
362
- **What closes the rest** — the transfer MECHANISM (adequacy, standard contractual clauses, binding
363
- corporate rules, a derogation), recorded per subprocessor entry by a human informed by research. It is
364
- chosen and documented rather than derived, and it is parked deliberately: transfers arrive late in a
365
- company's life, and building the model before a real case exists would be guessing at its shape.
212
+ **What closes it** — the same engine change as the recipients concern — a processing region on a
213
+ provider declaration, issue #88. The
214
+ transfer MECHANISM (adequacy, standard contractual clauses, derogation) is then a `NEEDS_DECISION`
215
+ layered on top, because a mechanism is chosen and documented rather than derived.
366
216
 
367
217
  **"We do not transfer data internationally" is a claim, not a default.** It may be true, and it is
368
218
  citable when an application has declared it as a fact — but it must never be produced because nothing
@@ -383,21 +233,10 @@ use and for what function.
383
233
  effect** on a person, and whether a human reviews it. Nothing in the framework declares consequence or
384
234
  human-review posture, and neither can be inferred from a capability being enabled.
385
235
 
386
- **Derives from (the consequence)** — the AI POSTURE section of your brief, per ENABLED AI capability:
387
- what it is used for, whether it `NO_DECISION` / `ASSISTS_HUMAN_DECISION` / `DECIDES_AUTONOMOUSLY`, and —
388
- where it decides anything — how a person obtains human intervention.
389
-
390
- An application enabling NO AI capability gets a plain statement to that effect: it performs no AI
391
- processing of personal data. That is a positive, checkable answer, not a gap.
392
-
393
- **Completeness** — `DERIVED` per capability with a declared posture; `NEEDS_DECISION` per capability
394
- listed OUTSTANDING. Not `NEEDS_FRAMEWORK` any more: issue #92 delivered the declaration, so an
395
- undeclared posture is an unanswered question rather than an unaskable one.
236
+ **Completeness** — `NEEDS_FRAMEWORK` for the consequence posture.
396
237
 
397
- **An OUTSTANDING capability is not a harmless one.** This is the one concern where silence is more
398
- dangerous than elsewhere: a notice describing AI use and saying nothing about consequence does not read
399
- as "unknown", it reads as "nothing significant happens here" — which is the exemption, claimed for
400
- free. State the gap explicitly.
238
+ **What closes it** — an engine change letting an AI use declare its consequence and its human-review
239
+ arrangement — issue #92.
401
240
 
402
241
  **Why the distinction carries weight.** Automated decision-making with significant effects attracts
403
242
  specific obligations — information about the logic, and a right to human intervention. A generated
@@ -415,29 +254,19 @@ configured (`FRONTEND_PRODUCT_ANALYTICS`, `LLM_OBSERVABILITY`, `OBSERVABILITY_TE
415
254
  with the consent ladder: `requiredConsent` and per-user `dataProcessingConsent` make
416
255
  `DataProcessingConsent.ANALYTICS` a real, enforced boundary rather than a stated intention.
417
256
 
418
- **Derives from (the inventory)** — the CLIENT STORAGE section of your brief: each cookie and storage
419
- key, its mechanism, purpose, necessity and lifetime, split by who sets it.
257
+ **Not derivable** — the **cookie and client-storage inventory**. Nothing declares which cookies, local
258
+ storage keys or client-side SDKs the frontend sets, what each is for, or how long it persists — the
259
+ exact table a cookie notice consists of.
420
260
 
421
- The FRAMEWORK's own entries are listed first and belong in every application's table — `__wildo_refresh`
422
- and `__wildo_anon_session`, both strictly necessary, both with lifetimes taken from the application's
423
- session configuration. **No application authored these and every application sets them**, so a table
424
- built only from what the application declared would omit the session cookie, which is the entry a
425
- visitor is most certain to have.
261
+ **Completeness** — `DERIVED` for the capability and consent posture, `NEEDS_FRAMEWORK` for the
262
+ inventory.
426
263
 
427
- Then, per frontend surface: its declared entries, an explicit "sets nothing of its own", or
428
- UNINVENTORIED.
264
+ **What closes it** — an engine change declaring client-storage entries per capability and per
265
+ frontend surface — issue #91.
429
266
 
430
- **UNINVENTORIED is not "sets nothing".** The first says nobody catalogued that surface; the second is a
431
- positive statement. Writing the second from the first tells a visitor they are tracked by less than they
432
- are, which is the under-reporting direction a notice must never fail in.
433
-
434
- **Completeness** — `DERIVED` for the capability and consent posture, and for each surface that IS
435
- inventoried; `NEEDS_DECISION` per uninventoried surface. Not `NEEDS_FRAMEWORK` any more: issue #91
436
- delivered the declaration surface, so an uninventoried surface is an unanswered question rather than an
437
- unaskable one.
438
-
439
- Say both halves: which analytics are in use and what consent gates them (strong, derived, enforced), and
440
- what the table still lacks — naming the surfaces, not the concern.
267
+ Say both halves: which analytics are in use and what consent gates them (strong, derived, enforced),
268
+ and that the itemised cookie table is not yet established (honest, and precisely what a cookie notice
269
+ still needs before it can be published).
441
270
 
442
271
 
443
272
  ### Concern: subject rights
@@ -507,12 +336,5 @@ CONTROLLER for the data it holds about the customer's users as account holders.
507
336
  roles with different duties over the same database. Say which is which; do not pick one and apply it
508
337
  to everything.
509
338
 
510
- **The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
511
- `wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
512
- stores about its own people, CONTROLLER for the account data of the people who administer them. It is
513
- a LIST for exactly the reason this fragment gives: those are different roles over the same database,
514
- and a single field would force one of them to be wrong.
515
-
516
- Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
517
- surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
518
- so the remedy is to fill it in rather than to build something. See the legal-basis fragment.
339
+ Where a document needs to attribute a duty and the attribution is not established, that is a
340
+ `NEEDS_DECISION` — never a guess. See the legal-basis fragment.