@wildo-ai/framework-knowledge 1.1.2 → 1.1.4

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 (289) 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 +351 -18
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  6. package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
  7. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  8. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  9. package/dist/esm/index.d.ts.map +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -4
  13. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -4
  15. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +4 -4
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -1
  19. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -1
  23. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
  25. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +1 -2
  27. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -2
  29. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -3
  31. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +3 -3
  33. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -2
  35. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
  37. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  38. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -1
  39. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  40. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +0 -1
  41. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +0 -1
  43. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +0 -1
  45. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +0 -1
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +0 -1
  49. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -1
  51. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
  53. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +0 -1
  55. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
  57. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +0 -2
  59. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +2 -2
  61. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +0 -1
  63. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +0 -1
  65. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -1
  67. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +0 -1
  69. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  70. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
  71. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +0 -1
  73. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -1
  75. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +0 -1
  77. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  78. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
  79. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -4
  81. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  82. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
  83. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
  85. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
  87. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  88. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
  89. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  90. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -1
  91. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  93. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +0 -1
  95. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
  97. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +0 -1
  99. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
  101. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +0 -1
  103. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +0 -1
  105. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
  107. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  108. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  109. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  110. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -1
  111. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +0 -1
  113. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  114. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  115. package/dist/knowledge/manifest.json +8 -9
  116. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
  117. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
  118. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
  119. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
  120. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
  121. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
  122. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
  123. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
  124. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
  125. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
  126. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
  127. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
  128. package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
  129. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
  130. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
  131. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
  132. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
  133. package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
  134. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
  135. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
  136. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
  137. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
  138. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
  139. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
  140. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
  141. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
  142. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
  143. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
  144. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
  145. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
  146. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
  147. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
  148. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
  149. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
  150. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
  151. package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
  152. package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
  153. package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
  154. package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
  155. package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
  156. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
  157. package/dist/knowledge/references/platform.config.saas.md +0 -51
  158. package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
  159. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
  160. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
  161. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
  162. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
  163. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
  164. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
  165. package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
  166. package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
  167. package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
  168. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
  169. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
  170. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
  171. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
  172. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
  173. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
  174. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
  175. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
  176. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
  177. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
  178. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
  179. package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
  180. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
  181. package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
  182. package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
  183. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
  184. package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
  185. package/dist/knowledge/registries/framework-topics.json +11 -146
  186. package/dist/knowledge/registries/playbooks.json +18 -154
  187. package/dist/knowledge/registries/source-tags.json +630 -883
  188. package/dist/knowledge/skills/INDEX.md +3 -4
  189. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
  190. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
  191. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
  192. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
  193. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
  194. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
  195. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
  196. package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
  197. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
  198. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
  199. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
  200. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
  201. package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
  202. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
  203. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
  204. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
  205. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
  206. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
  207. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
  208. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
  209. package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
  210. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
  211. package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
  212. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -213
  213. package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
  214. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
  215. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
  216. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
  217. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
  218. package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
  219. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
  220. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
  221. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
  222. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
  223. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
  224. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
  225. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
  226. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
  227. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
  228. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
  229. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
  230. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
  231. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
  232. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
  233. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
  234. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
  235. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
  236. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
  237. package/dist/knowledge/topic-index.json +220 -725
  238. package/dist/tsconfig.build.tsbuildinfo +1 -1
  239. package/dist/tsconfig.tsbuildinfo +1 -1
  240. package/package.json +4 -4
  241. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
  242. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
  243. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
  244. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
  245. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
  246. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
  247. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
  248. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
  249. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
  250. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
  251. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
  252. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
  253. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
  254. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
  255. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
  256. package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
  257. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
  258. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
  259. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
  260. package/dist/knowledge/references/placement-plan.config.md +0 -330
  261. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
  262. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
  263. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
  264. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
  265. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
  266. package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
  267. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
  268. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
  269. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
  270. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
  271. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
  272. package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
  273. package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
  274. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
  275. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
  276. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
  277. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
  278. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
  279. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
  280. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
  281. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
  282. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
  283. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
  284. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
  285. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
  286. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
  287. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
  288. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
  289. /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@wildo-ai/framework-knowledge",
3
- "version": "1.1.2",
3
+ "version": "1.1.4",
4
4
  "license": "SEE LICENSE IN LICENSE",
5
5
  "description": "Published framework knowledge artifacts and typed loaders for Wildo AI",
6
6
  "author": "Wildo AI",
@@ -19,8 +19,8 @@
19
19
  "dist/"
20
20
  ],
21
21
  "dependencies": {
22
- "@wildo-ai/saas-models": "1.1.2",
23
- "@wildo-ai/saas-specifications": "1.1.2"
22
+ "@wildo-ai/saas-models": "1.1.4",
23
+ "@wildo-ai/saas-specifications": "1.1.4"
24
24
  },
25
25
  "scripts": {
26
26
  "build": "tsc -p tsconfig.build.json && node ../../../scripts/run-tsc-alias-safe.mjs --project tsconfig.build.json --dist dist/esm",
@@ -34,7 +34,7 @@
34
34
  },
35
35
  "devDependencies": {
36
36
  "@types/node": "^24.0.15",
37
- "@wildo-ai/saas-backend-lib": "1.1.2",
37
+ "@wildo-ai/saas-backend-lib": "1.1.4",
38
38
  "rimraf": "^6.0.1",
39
39
  "tsc-alias": "1.8.16",
40
40
  "tsc-watch": "7.2.1",
@@ -1 +0,0 @@
1
- {"attributionNotices":["Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record."],"evaluatedAt":"2026-09-05T12:54:53.265Z","mapped":[{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-accountable-role-retention","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Every scope keeps at least one usable administrator: a removal, demotion or deactivation that would strand an application or a tenant is refused, concurrent reductions are serialized so two of them cannot pass each other, a data-protection erasure proceeds only on an explicit acknowledgement that records the breach it causes, and any scope that has already been stranded is reported at startup.","objectiveRef":"WILDO.ACCESS.ADMINISTRATIVE_CONTINUITY","title":"Retain an administrator for every scope"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-of-access-decisions","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Access-control decisions, refusals included, are attributable and reviewable; repeated refusals stay detectable without the record itself becoming an availability risk; and a failure of the recording pipeline is detectable and attributable to the specific action it lost.","objectiveRef":"WILDO.ACCESS.AUTHORIZATION_DECISION_AUDIT","title":"Record access decisions, refusals included"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-access-authorization-recording","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"}],"intent":"Platform-tier administration of a tenant is never ambient: a crossing is admitted only by an explicitly enumerated operation variant, requires an elevation that was requested rather than assumed and — where the tenant demands it — approved by that tenant, is recorded as a distinct event naming the tenant reached, and an undeclared crossing fails closed.","objectiveRef":"WILDO.ACCESS.CROSS_TENANT_ADMINISTRATION","title":"Declare every crossing of a tenant boundary"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-least-privilege-enforcement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-least-privilege-authority-limit","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A principal can never grant authority it does not itself hold — role assignment and machine-credential minting are bounded by the caller’s own ceiling — and a non-controller surface facing an external caller applies the same declared operation-role gate the controller tier applies, through the same predicate, before a self-service verb, a retrieval corpus or an agent-facing tool is reached.","objectiveRef":"WILDO.ACCESS.LEAST_PRIVILEGE","title":"Grant no more authority than the action needs"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-workforce-access-termination","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-account-disable-on-relationship-end","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Access rights, and the credentials that assert them, are withdrawn when the relationship conferring them ends, and restoring access is as attributable as removing it.","objectiveRef":"WILDO.ACCESS.LIFECYCLE","title":"Withdraw and restore access attributably"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-temporary-account-expiry","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"An access restriction declared as time-boxed is lifted when its window elapses, through the same guarded authority that imposed it, so a measure taken as temporary cannot silently become permanent.","objectiveRef":"WILDO.ACCESS.LIFECYCLE_TIME_BOUND","title":"Release a time-boxed restriction automatically"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hipaa-security-privileged-access-review","reviewedAt":"2026-08-13T08:57:58.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-access-review","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Privileged access is explicitly scoped, periodically reviewed, decided by authorized people and retained as traceable evidence without implying remediation completion.","objectiveRef":"WILDO.ACCESS.PRIVILEGED_REVIEW","title":"Review privileged access"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-privileged-grant-evidence","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Every grant, widening, narrowing and revocation of privilege — a role, a unit-scoped membership, a discretionary entitlement or a subscription-derived one — leaves durable evidence of the assignment’s full life, not merely of its current state.","objectiveRef":"WILDO.ACCESS.PRIVILEGE_EVIDENCE","title":"Keep evidence of a privileged assignment’s whole life"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-processing-confidentiality","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-information-flow-confinement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Reads and writes are narrowed to the tenant, unit subtree or parent row the caller’s own grant reaches; the conferring grant is recorded alongside the decision, a unit grant expands to exactly its declared subtree and no further, and a tenant cannot lift a narrowing the platform imposed on it.","objectiveRef":"WILDO.ACCESS.SCOPE_CONFINEMENT","title":"Confine a query to the scope the caller reached it by"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-accountability-demonstration","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-attributable-event-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A security-relevant action records who performed it, and never disguises an unattributable action as an ordinary automated one; read-through access to an external system carries the real initiating user through the shared service principal, and an outbound deletion there names the subject it served and the system it reached.","objectiveRef":"WILDO.AUDIT.ATTRIBUTION","title":"Name who performed a security-relevant action"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-record-context-binding","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"The actor and tenant an audit row names survive the trusted-system write that persists it, and a log record names which application and which environment produced it — so a record cannot silently lose or change the principal, tenant or deployment it belongs to.","objectiveRef":"WILDO.AUDIT.CONTEXT_ATTRIBUTION","title":"Bind a record to the context it actually ran in"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-audit-record-content-and-protection","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A privileged action on a resource is attributable, and the authorization effect it had is reconstructable from the record itself rather than re-derived from role tables afterwards; the configuration deciding what the trail captures is governed as part of the trail.","objectiveRef":"WILDO.AUDIT.EVIDENCE_INTEGRITY","title":"Govern the audit trail as evidence in its own right"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://doi.org/10.6028/NIST.CSWP.29","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-security-event-logging","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Authentication, authorization, privilege, credential and security-configuration changes each emit a typed auditable event; non-human privileged access is audited or refused; and the absence of the audit delivery path is surfaced at boot rather than tolerated silently.","objectiveRef":"WILDO.AUDIT.SECURITY_EVENT","title":"Emit a typed event for every security-relevant change"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-transaction-authorization-separation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"An increase in a credit balance is reachable only through a system or payment-gated door, so no ordinary principal can grant itself economic value.","objectiveRef":"WILDO.BILLING.CREDIT_GRANT_INTEGRITY","title":"Gate a credit grant to system or payment authority"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-transmission-confidentiality","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"}],"intent":"Material a schema declares backend-only does not cross the client boundary, except at a single first exposure that is itself audited.","objectiveRef":"WILDO.DATA.CONFIDENTIALITY","title":"Keep backend-only material off the client boundary"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-information-integrity-verification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A uniqueness or integrity control the schema declares is proven to exist in the datastore before the application serves traffic, rather than assumed to have been created.","objectiveRef":"WILDO.DATA.INTEGRITY_CONSTRAINTS","title":"Prove a declared constraint exists before serving traffic"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-erasure-with-retention-carve-out","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-media-sanitization-and-disposal","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Destruction of an identity, a tenant or its data is a deliberate, attributable, evidenced decision, reversible until its declared window elapses and then carried out on schedule; an erased-but-retained record is hidden from, and immutable to, every ORDINARY access path — the only door is an audited see-through read — and its derived copies are excluded by a live check against the parent row rather than by waiting for a sweep.","objectiveRef":"WILDO.DATA.SECURE_LIFECYCLE","title":"Destroy data deliberately, on a recorded schedule"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-shared-resource-isolation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A caller cannot widen its own query scope: tenancy narrowing is derived from the resolved execution context and never offered as a parameter — to a client, to an agent, or to a retrieval surface — and where the read is a similarity search the predicate is evaluated INSIDE the traversal rather than over its results, then re-checked by an authorized read of the owning row.","objectiveRef":"WILDO.DATA.TENANT_ISOLATION","title":"Derive tenancy from the caller, never from the request"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-transaction-recovery-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A resource declares its persistence isolation before it may sit on a non-default adapter, and a configuration whose cross-resource writes could not be atomic is refused when the registry is built rather than discovered under load.","objectiveRef":"WILDO.DATA.TRANSACTIONAL_INTEGRITY","title":"Refuse a configuration that cannot write atomically"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-entitlement-change-authority","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Feature and entitlement writes are reachable only through an operator-gated door, so a principal cannot widen what it is entitled to.","objectiveRef":"WILDO.ENTITLEMENT.NO_SELF_GRANT","title":"Keep an entitlement write operator-gated"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-identify-service-identity-verification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A client identity is bound to a domain the client demonstrably controls, and both a client identity created by a party that authenticated to nothing and every refused client assertion are recorded.","objectiveRef":"WILDO.IDENTITY.CLIENT_IDENTITY_ASSERTION","title":"Bind a client identity to a verifiable assertion"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-credential-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-credential-state-transitions","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Issuance, refresh, rotation, revocation and expiry of a credential are explicit attributable transitions; credential theft is detected and answered by invalidation; and a revocation actually terminates the sessions and tokens it names rather than merely marking a record.","objectiveRef":"WILDO.IDENTITY.CREDENTIAL_LIFECYCLE","title":"Make every credential state transition explicit"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-delegated-access-authorization","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A third party acts for a user only on that user’s recorded authorization: approval, refusal, persistence and failure of the delegated exchange are each audited, proof of possession is enforced on the exchange, and the issued token carries no more than the grant declared.","objectiveRef":"WILDO.IDENTITY.DELEGATED_AUTHORIZATION","title":"Let a user authorize third-party access deliberately"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-automated-account-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"Where an application opts in, a directory becomes the authority for accounts and for unit membership — which is an authorization grant, not a label — and the switches conferring that authority are declared explicitly rather than implied by the presence of a connection.","objectiveRef":"WILDO.IDENTITY.DIRECTORY_PROVISIONING","title":"Honour the directory as the provisioning authority"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-account-enable-disable-authority","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A change to whether a principal may authenticate runs through one guarded, evidenced authority: the status carrying it is excluded from ordinary updates, so the change cannot arrive as a side effect of an unrelated write.","objectiveRef":"WILDO.IDENTITY.LIFECYCLE","title":"Record every change to whether a principal may authenticate"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hipaa-security-authentication-controls","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"}],"intent":"Enrolled second factors are verified through one authority that is replay-resistant and timing-safe, so no caller builds a second, weaker door onto the same credential.","objectiveRef":"WILDO.IDENTITY.MULTI_FACTOR","title":"Verify enrolled second factors through one authority"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-redirect-target-constraint","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A registered OAuth redirect target is constrained to a safe absolute URL, closing the open-redirect and stored-XSS delegation primitive a permissive target would otherwise create.","objectiveRef":"WILDO.IDENTITY.REDIRECT_TARGET_VALIDATION","title":"Constrain a registered redirect target"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-govern-authentication-posture-change","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"How principals may authenticate — the MFA, password, lockout, methods, step-up and session posture, whether single sign-on is enforced, which identity provider is trusted, and whether its assertions are actually verified — is explicitly configured, and every genuine change to that posture is detected at startup and evidenced once, from the runtime that puts it into effect.","objectiveRef":"WILDO.IDENTITY.SESSION_ASSURANCE","title":"Decide, and record changes to, the assurance a session carries"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-concurrent-session-control","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A principal holds a bounded number of concurrent sessions, and the eviction enforcing that bound retires the OLDEST refresh chain — the property that pushes a stolen chain out instead of a legitimate one.","objectiveRef":"WILDO.IDENTITY.SESSION_CONCURRENCY_LIMIT","title":"Bound the concurrent sessions a principal holds"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-cryptographic-key-establishment-and-management","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A rotated signing key can be given an explicit retirement instant, after which it stops being advertised and stops verifying tokens — so an aged or compromised prior key need not stay trusted until someone edits configuration.","objectiveRef":"WILDO.IDENTITY.SIGNING_KEY_LIFECYCLE","title":"Bound the lifetime of a retired signing key"},{"citations":[{"attributionNotice":"Identify HHS as the authority and link to the current official source; no HHS content bytes are bundled under this record.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html","contentUsePermission":"REQUIRES_ADDITIONAL_RIGHTS","metadataCitationAuthorized":true,"requirementRef":"source-requirement:hhs-security-person-or-entity-reverification","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:paul-cayon-assurance-owner","rightsRef":"rights:hhs-reference-only-v1","sourceRef":"source:hhs-hipaa-security-rule","sourceTitle":"HIPAA Security Rule"},{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-reauthentication-for-privileged-action","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A high-impact action requires a fresh re-proof of identity, over any factor the principal actually holds, and that ceremony cannot be satisfied by a credential presented for a different purpose.","objectiveRef":"WILDO.IDENTITY.STEP_UP_AUTHENTICATION","title":"Re-prove identity before a high-impact action"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-assertion-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"An ID token’s protocol and security claims are authored by the server alone, from one named reserved-claim set, so a caller cannot smuggle a reserved claim in through supplied extras.","objectiveRef":"WILDO.IDENTITY.TOKEN_INTEGRITY","title":"Author a token’s protocol claims on the server only"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-detect-outbound-connection-monitoring","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"Outbound traffic leaves through a single named egress per capability, and every physical call is recorded — provider, model, usage and outcome for a provider call, the initiating actor for an administrative probe — so a reviewer can enumerate what was sent and when.","objectiveRef":"WILDO.INTEGRATION.OUTBOUND_ACTIVITY_AUDIT","title":"Attribute every outbound connection the application makes"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-authority-not-inferred-from-state","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A self-reported lifecycle stage confers no capability and cannot cross a scope boundary; authority comes only from a decision an authorized party actually made.","objectiveRef":"WILDO.LIFECYCLE.STAGE_IS_NOT_AUTHORITY","title":"Confer no capability from a self-reported stage"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-error-handling-diagnostics","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A constraint conflict is reported with the identity that was violated rather than as an opaque datastore failure, so an operator can tell a benign duplicate from an unexpected collision.","objectiveRef":"WILDO.OPERATIONS.CONFLICT_DIAGNOSTICS","title":"Report a conflict by the identity it violated"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-declared-interface-integrity","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A declared, API-reachable operation stays reachable and is actually implemented: an interface must not report success for an action it did not perform, and a named verb must not silently widen into an unconstrained write over fields its resource never exposed for update.","objectiveRef":"WILDO.OPERATIONS.EXECUTION_INTEGRITY","title":"Never report success for an action that was not performed"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-denial-of-service-resource-bounds","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"An unauthenticated request consumes a bounded amount of resource, and an over-limit request is answered as a client error rather than surfacing as a server failure.","objectiveRef":"WILDO.OPERATIONS.RESOURCE_LIMIT","title":"Bound what an unauthenticated request may consume"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-bulk-disclosure-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"A bulk export of a resource collection is a recorded event naming the resource exported, the operation it was taken from, and the format it was rendered in.","objectiveRef":"WILDO.PRIVACY.COLLECTION_DATA_EXPORT","title":"Record a bulk export of a resource collection"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-consent-demonstrability","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"A consent decision — given, changed or withdrawn — is recorded exactly once and never lost to a race, naming the previous and the resulting value; every verb able to change consent routes through one emission point, and resetting a subject’s privacy preferences is itself such a decision.","objectiveRef":"WILDO.PRIVACY.CONSENT_RECORD","title":"Record a consent decision exactly once"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-data-minimisation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Only the data a declared purpose requires leaves its boundary: an external processor receives the payload and nothing identifying the requester or its row, observability surfaces receive summaries rather than the raw content, and a device-stored pseudonymous identifier is collected only under an explicit application opt-in — absent that policy, not at all — and can be withdrawn or narrowed afterwards.","objectiveRef":"WILDO.PRIVACY.DATA_MINIMIZATION","title":"Send only what the declared purpose requires"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-records-of-processing-categories","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"The application declares, on the field itself, which CATEGORIES of personal data it holds — never inferred from the field’s name, because an inventory assembled by pattern-matching identifiers is a guess whose misses go silently undisclosed.","objectiveRef":"WILDO.PRIVACY.PERSONAL_DATA_INVENTORY","title":"Declare in the schema which fields hold personal data"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-storage-limitation","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Declared row-retention windows are enforced, and a configuration whose derived copies of subject text could outlive the row they came from — unreachable by the erasure seams — is refused at startup.","objectiveRef":"WILDO.PRIVACY.STORAGE_LIMITATION","title":"Keep data no longer than its declared window"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-subject-access-portability","reviewedAt":"2026-08-03T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Authorized subject access and portability exports are purpose-specific, resource-opted-in, subject-isolated and auditable: the export event names the purpose, the subject, the resource types included, the record count and the fields withheld as derived.","objectiveRef":"WILDO.PRIVACY.SUBJECT_DATA_EXPORT","title":"Export subject data safely"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-erasure-and-restriction","reviewedAt":"2026-09-01T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"A subject’s erasure request is recorded on intake whether the subject or the controller raised it, may be withdrawn by the subject while it is pending, is executed on the declared schedule, and terminates the erased person’s sessions.","objectiveRef":"WILDO.PRIVACY.SUBJECT_ERASURE","title":"Execute a subject erasure request, and evidence it"},{"citations":[{"attributionNotice":"Acknowledge EUR-Lex/European Union as source, identify modifications, do not distort meaning and do not imply endorsement.","authorityKind":"LAW_OR_REGULATION","canonicalLocator":"https://eur-lex.europa.eu/eli/reg/2016/679/oj","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:gdpr-processor-engagement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:eur-lex-legal-document-reuse-v1","sourceRef":"source:eu-gdpr-2016-679","sourceTitle":"Regulation (EU) 2016/679 (General Data Protection Regulation)"}],"intent":"Routing data to an external service makes that service a processor of it, so such routing is opt-in by construction: nothing leaves unless the application selects a provider for that capability, and with no selection the work is served locally with no egress at all.","objectiveRef":"WILDO.PRIVACY.THIRD_PARTY_PROCESSING","title":"Name the processors that data is routed to"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-authenticator-storage-protection","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"The shape of a provider’s secret contract is tracked so that drift in it is detectable, without ever persisting the secret values themselves.","objectiveRef":"WILDO.SECRETS.CONTRACT_INTEGRITY","title":"Detect drift in a values-free secret contract"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-authenticator-disclosure-record","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"The first disclosure of server-minted secret material is an attributable, audited event.","objectiveRef":"WILDO.SECRETS.DISCLOSURE_AUDIT","title":"Audit the first disclosure of minted secret material"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://www.nist.gov/cyberframework","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-csf-protect-fail-secure-behaviour","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-csf-2.0","sourceTitle":"The NIST Cybersecurity Framework (CSF) 2.0"}],"intent":"A control that cannot be evaluated refuses what it guards, and stays diagnosable while doing so: untrusted input is rejected whole rather than partly sanitized, and a validator whose dependency is unavailable fails closed without its degradation being mistaken for a rejected signature.","objectiveRef":"WILDO.SECURITY.FAIL_CLOSED","title":"Refuse rather than degrade when a control cannot run"},{"citations":[{"attributionNotice":"Credit the National Institute of Standards and Technology and preserve any publication-specific notice; do not imply NIST endorsement.","authorityKind":"GOVERNMENT_PUBLICATION","canonicalLocator":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","contentUsePermission":"ALLOWED","metadataCitationAuthorized":true,"requirementRef":"source-requirement:nist-800-53-configuration-settings-enforcement","reviewedAt":"2026-09-02T00:00:00.000Z","reviewedByRef":"reviewer:wildo-assurance-authority","rightsRef":"rights:nist-public-information-v1","sourceRef":"source:nist-sp-800-53-rev-5-release-5.2.0","sourceTitle":"Security and Privacy Controls for Information Systems and Organizations"}],"intent":"A server-owned field has exactly one named authority that writes it, and that authority is proven at boot rather than assumed — so no second path can set the field and no reader has to work out which value is current.","objectiveRef":"WILDO.SOFTWARE.AUTHORITY_INTEGRITY","title":"Give every server-owned field exactly one named authority"}],"mappingRef":"assurance-external-mapping:wildo-safe-baseline-v1","mappingVersion":1,"normativeSourceContentIncluded":false,"tailoringCaveat":"A control catalog requires tailoring, implementation and assessment; catalog inclusion is not proof of operation. This mapping records which external source each Wildo objective was reviewed against. It is not a conformity assertion, it claims no operating effectiveness, and it reproduces no normative source text.","unmapped":[]}
@@ -1,51 +0,0 @@
1
- # Assemble & verify — does the built application hold together?
2
-
3
- This is the last bottom-up step. Everything before it AUTHORED the application; this one asks
4
- whether what was authored is one working program.
5
-
6
- ## What this playbook does
7
-
8
- It runs a fixed set of deterministic checks against the application's workspace packages, outside
9
- any coding agent, and reports one outcome per check. It changes nothing.
10
-
11
- The check set is host-owned, not authored here. A playbook names semantic check references; turning
12
- one into an executable command is reviewed host work, which is why a new check cannot be introduced
13
- by editing this file.
14
-
15
- ## What it verifies today, and what it does not
16
-
17
- **It verifies** that the application typechecks as a whole — `specifications`, `shared-lib`,
18
- `backend-api` and `frontend`. That is the question no earlier step answers: the dispatch lane
19
- typechecks the one package a task mutated, so a build can consist entirely of green tasks and still
20
- not compile as a program. Cross-package breakage is the characteristic failure of a build assembled
21
- from independent tasks, and this is where it surfaces.
22
-
23
- **It does not** boot the application, run its test suite, validate its configuration, or regenerate
24
- OpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist
25
- yet. They are absent rather than declared-and-skipped on purpose: the previous version of this
26
- playbook declared all of them, ran none, and carried a long disclaimer saying so — a check that is
27
- announced and not executed is worse than one that is missing, because a reader counts it.
28
-
29
- ## Reading the result
30
-
31
- Three outcomes, and they mean different things:
32
-
33
- - **every check passed** — the application assembles. This is the signal the phase gate wants.
34
- - **a check failed** — the application does not assemble. The failure names the package; remediation
35
- is a refinement re-dispatch, not this playbook.
36
- - **an infrastructure error** — the check could not be RUN. This is reported separately and must not
37
- be read as a failure: "the application does not typecheck" and "we could not run the typecheck"
38
- lead you to entirely different places, and only the first is the application's fault.
39
-
40
- A dry run resolves the check set and executes nothing, so it tells you what would be verified
41
- without paying for it.
42
-
43
- ## Quality gate
44
-
45
- The gate is the check set itself, run by the host. There is no declared gate restating it — a second
46
- description of a live check is exactly what the retired `qualityGates` field was.
47
-
48
- ## Acceptance
49
-
50
- The creator reviews the reported outcomes. As everywhere in this lane, the run accepts nothing: a
51
- human commit is the only acceptance there has ever been.
@@ -1,43 +0,0 @@
1
- {
2
- "ref": "bottom_up.assemble-verify",
3
- "version": "0.2.0",
4
- "phase": "bottom_up",
5
- "intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over the application's four workspace packages (specifications, shared-lib, backend-api, frontend) OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty for v0.2: the check set is the whole-application TYPECHECK across the four packages — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated. A boot probe, the whole test suite, `wildo config validate` and OpenAPI/docs regeneration are NOT in this set: each needs a running stack or a companion affordance that does not exist, and declaring them here without running them is exactly what made the deleted version of this playbook inert.",
6
- "functionalTopics": [
7
- "assemble_verify_and_iterate"
8
- ],
9
- "preconditions": [
10
- {
11
- "kind": "artifact_exists",
12
- "selector": {
13
- "family": "build-plan"
14
- }
15
- }
16
- ],
17
- "inputs": [
18
- {
19
- "family": "build-plan"
20
- }
21
- ],
22
- "outputs": [],
23
- "stepOutputs": [],
24
- "method": {
25
- "guidance": "# Assemble & verify — does the built application hold together?\n\nThis is the last bottom-up step. Everything before it AUTHORED the application; this one asks\nwhether what was authored is one working program.\n\n## What this playbook does\n\nIt runs a fixed set of deterministic checks against the application's workspace packages, outside\nany coding agent, and reports one outcome per check. It changes nothing.\n\nThe check set is host-owned, not authored here. A playbook names semantic check references; turning\none into an executable command is reviewed host work, which is why a new check cannot be introduced\nby editing this file.\n\n## What it verifies today, and what it does not\n\n**It verifies** that the application typechecks as a whole — `specifications`, `shared-lib`,\n`backend-api` and `frontend`. That is the question no earlier step answers: the dispatch lane\ntypechecks the one package a task mutated, so a build can consist entirely of green tasks and still\nnot compile as a program. Cross-package breakage is the characteristic failure of a build assembled\nfrom independent tasks, and this is where it surfaces.\n\n**It does not** boot the application, run its test suite, validate its configuration, or regenerate\nOpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist\nyet. They are absent rather than declared-and-skipped on purpose: the previous version of this\nplaybook declared all of them, ran none, and carried a long disclaimer saying so — a check that is\nannounced and not executed is worse than one that is missing, because a reader counts it.\n\n## Reading the result\n\nThree outcomes, and they mean different things:\n\n- **every check passed** — the application assembles. This is the signal the phase gate wants.\n- **a check failed** — the application does not assemble. The failure names the package; remediation\n is a refinement re-dispatch, not this playbook.\n- **an infrastructure error** — the check could not be RUN. This is reported separately and must not\n be read as a failure: \"the application does not typecheck\" and \"we could not run the typecheck\"\n lead you to entirely different places, and only the first is the application's fault.\n\nA dry run resolves the check set and executes nothing, so it tells you what would be verified\nwithout paying for it.\n\n## Quality gate\n\nThe gate is the check set itself, run by the host. There is no declared gate restating it — a second\ndescription of a live check is exactly what the retired `qualityGates` field was.\n\n## Acceptance\n\nThe creator reviews the reported outcomes. As everywhere in this lane, the run accepts nothing: a\nhuman commit is the only acceptance there has ever been.\n",
26
- "skillRefs": [
27
- "journey-status",
28
- "journey-report",
29
- "journey-approve"
30
- ],
31
- "contextSources": [],
32
- "suspendsForClarification": false,
33
- "briefAdequacyGate": false,
34
- "briefAdequacyExcludedSources": []
35
- },
36
- "executor": "deterministic_cli",
37
- "approval": "approve_result",
38
- "budget": {
39
- "maxDurationMs": 3600000,
40
- "maxRuns": 40
41
- },
42
- "onFailure": "keep_and_flag"
43
- }
@@ -1,185 +0,0 @@
1
- # Placement Plan — Where Each Thing Belongs in the Shell, and Why
2
-
3
- ### Target Application Framing
4
-
5
- This knowledge is for configuring behavior in the target application.
6
- Wildo is the framework surface being used, not the product being built.
7
-
8
- Read and apply these patterns from the application-developer point of view:
9
-
10
- - how the application should configure the relevant app-level file
11
- - how the application should use framework-provided factories, enums, and helpers
12
- - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
-
14
-
15
- > **This is a v1 methodology.** The criteria below are deliberately explicit so
16
- > they can be tuned against real runs. What is NOT provisional is the shape of the
17
- > output: a decision per subject, on a named surface, with a rationale.
18
-
19
- ## Where you are in the journey
20
-
21
- You run in the **bottom-up phase**, after the **domain plan** exists and **before**
22
- the build is decomposed. By now the application knows what its modules and resources
23
- ARE; what nobody has decided is **where any of it appears**.
24
-
25
- That order matters and was corrected during authoring. Placing things *after* the
26
- build plan reads natural — you would know every task — but `bottom_up.build-decompose`
27
- is what PRODUCES the build plan and it consumes this one to emit the placement tasks.
28
- Requiring its output would be a cycle. It is also the better order on its own merits:
29
- placement is a design decision that should INFORM the decomposition, not trail it. You
30
- do not need the task graph to know that a `deals` resource will have a list.
31
-
32
- That question used to have no owner. The framework shipped a placed settings rail,
33
- so an application could not add, remove, reorder or rename a section without the
34
- framework agreeing — and the application's own config file did not tell you what a
35
- user would see. Placement is now the application's, which means somebody has to
36
- decide it. That is this playbook.
37
-
38
- ## What this playbook does
39
-
40
- You produce a **placement plan**: for every subject, one decision per surface.
41
-
42
- A **subject** is one of three things:
43
-
44
- - an **engine settings destination**, named by its ref from the engine catalog
45
- (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS
46
- (its target, its required roles, its entitlement); it owns nothing about where it
47
- goes;
48
- - a **resource operation** — a resource's LIST, its READ, a custom verb;
49
- - an **application view** — composite, chart, execution, full-custom.
50
-
51
- A **surface** is one of four:
52
-
53
- | surface | grouped by | authoring home |
54
- |---|---|---|
55
- | `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |
56
- | `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |
57
- | `USER_MENU` | flat | the user dropdown's settings entries |
58
- | `COMMAND_MENU` | flat | the command palette |
59
-
60
- A subject may legitimately be placed on **several** surfaces — billing is a settings
61
- rail section AND answers to the command palette. One decision per (subject, surface);
62
- two placements of one subject on ONE surface is a contradiction and the validator
63
- refuses it.
64
-
65
- ## Decline explicitly; never omit
66
-
67
- Every decision is `PLACED` or `DECLINED`, and **both require a rationale**.
68
-
69
- This is the rule most worth getting right. A subject recorded as `DECLINED` is a
70
- decision a later reader can disagree with. A subject simply missing from the plan is
71
- a **coverage gap** — nobody looked. If those two were the same thing, "we considered
72
- the audit log and this app has no compliance audience" would be indistinguishable
73
- from forgetting the audit log existed.
74
-
75
- So: if a destination should not appear anywhere in this application, say so, and say
76
- why.
77
-
78
- ## The criteria, in the order you apply them
79
-
80
- 1. **Scope correctness.** A thing that acts on the whole organization does not sit
81
- among a person's own preferences, and the reverse. This is first because it is
82
- the only criterion that is objectively *wrong* rather than debatable.
83
- 2. **Findability.** Would the user who wants this look here FIRST — unprompted?
84
- Not "would they accept it once shown". Those are different tests and only the
85
- first one predicts behaviour.
86
- 3. **Grouping coherence.** Everything in a group answers one question a user
87
- actually asks. A group that needs "and other things" in its name is two groups.
88
- 4. **Convention fit.** Users arrive with expectations already formed by comparable
89
- products. A novel arrangement must EARN the cost of surprising them.
90
- 5. **Depth discipline.** One more level of nesting must buy more than it costs. A
91
- section reachable only after three guesses is not placed, it is hidden.
92
-
93
- Reject placements justified by implementation convenience ("it renders there
94
- already"), by the shape of the data model rather than the user's task, or by symmetry
95
- for its own sake. Surfacing something everywhere is a **cost**, not thoroughness.
96
-
97
- ## Groups carry a purpose, and the purpose is load-bearing
98
-
99
- When you declare a group, state its `purpose` in product terms. It is not decoration:
100
- it is what grounds the generated `settings_hub.categories.<ref>.label` and
101
- `sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents
102
- filler from the ref alone — which is exactly how a sidebar section came to be
103
- described as "various tools and utilities".
104
-
105
- ## What you do NOT do
106
-
107
- - **You do not author configuration.** Turning a decision into
108
- `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane
109
- dispatches through the `settings-placement-authoring` skill. If you catch yourself
110
- writing a config key, a file path or a label string, stop.
111
- - **You do not invent destination refs.** They come from the engine catalog and the
112
- workspace, read as workspace truth. A ref you invented resolves to nothing and the
113
- validator refuses it as an unknown subject.
114
- - **You do not decide what a destination MEANS.** Its target, roles and entitlement
115
- are the engine's. You decide only where it sits.
116
- - **You do not re-open the build plan.** What is being built is settled.
117
-
118
- ## Verification
119
-
120
- - Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.
121
- - No subject placed twice on one surface.
122
- - Every grouped placement names a group this plan declares, for that same surface.
123
- - Every group has something in it.
124
- - Every decision, both arms, carries a rationale that would satisfy a reader who
125
- disagrees with it.
126
-
127
- ## WHO decides — a panel, not you alone and not the creator
128
-
129
- **The creator does not choose placement.** This playbook convenes an expert panel and
130
- takes its winner.
131
-
132
- Concretely, on every run: three candidate arrangements are generated independently
133
- against this brief, each schema-valid before anyone sees it and each told to take a
134
- genuinely different position; the **information-architect** derives the rubric (it
135
- owns the domain); it and the **design-system-guardian** review every candidate; the
136
- guardian coordinates, shortlists, and synthesises a winner. What lands is that winner.
137
-
138
- Two consequences for how you write:
139
-
140
- - **Take a position and commit to it.** You are one candidate among three, and the
141
- panel cannot compare three hedged arrangements. State what your arrangement makes
142
- WORSE — an arrangement with no cost has not been thought about, and the reviewers
143
- are instructed to notice.
144
- - **The rationale on each decision is the durable part.** It is what a creator asking
145
- "why is Billing under Organization?" reads, and it is the only trace of the argument
146
- once the winner has landed.
147
-
148
- **Fail-closed on charters.** Every panel role needs a committed charter, and the
149
- companion indexes agents at startup — a charter accepted after boot has no agent until
150
- a restart, and the error says exactly that. The run does NOT quietly degrade to a
151
- single generation: an artifact carrying a panel's authority over a decision no panel
152
- saw is the worst outcome available here, so fewer than two usable candidates returns
153
- to the ordinary retry instead.
154
-
155
- ## And when the placement is wrong
156
-
157
- Two different things can change, and conflating them is how a plan starts lying.
158
-
159
- **The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually
160
- renders. A creator who disagrees edits it directly. That works today, needs no companion,
161
- and is a git commit, which is the accepted state.
162
-
163
- **The plan** is the decision record, and it is what a later reader consults to ask why.
164
- It can be changed two ways:
165
-
166
- - **Re-run this playbook.** The panel deliberates again and the landing REPLACES the
167
- existing file. Nothing refuses it; that is the design.
168
- - **Edit the landed plan.** It is an application-owned source like any other.
169
-
170
- Either way, a decision that no longer reflects the panel must say so. Set its `origin`
171
- to `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are
172
- required together — the schema refuses a `REVISED` decision with nothing superseded, and
173
- refuses a `DELIBERATED` one that supersedes something, because no panel run produces
174
- either shape.
175
-
176
- **Why the artifact carries this when git already records the change.** Git knows who
177
- changed the line, when, and with what message, and that is not being duplicated here. What
178
- git cannot tell someone READING the file — in an editor, asking "why is Billing under
179
- Account?" — is that this particular decision is no longer the panel's. Without it, the
180
- `rationale` field goes on asserting panel reasoning for a decision the panel never took,
181
- and there is no way to notice.
182
-
183
- Do not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that
184
- repeats the decision's own text word for word satisfies the schema and tells a reader
185
- nothing; the validator reports it as an authoring warning.
@@ -1,64 +0,0 @@
1
- {
2
- "ref": "bottom_up.placement-plan",
3
- "version": "0.1.0",
4
- "phase": "bottom_up",
5
- "intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
6
- "functionalTopics": [
7
- "shape_user_experience"
8
- ],
9
- "preconditions": [
10
- {
11
- "kind": "artifact_exists",
12
- "selector": {
13
- "family": "domain-plan"
14
- }
15
- }
16
- ],
17
- "inputs": [
18
- {
19
- "family": "domain-plan"
20
- },
21
- {
22
- "family": "requirements"
23
- }
24
- ],
25
- "outputs": [
26
- {
27
- "family": "placement-plan",
28
- "schemaRef": "saas-specifications:PlacementPlan",
29
- "description": "The placement decision — `groups[]` (the containers that should exist on the grouped surfaces, each with the product purpose behind it) plus `decisions[]` (one per subject PER SURFACE: a stable `decisionRef`, the `PlacementSubject` being placed — an engine settings destination by ref, a resource operation, or an app view — a `PlacementDisposition` of PLACED or DECLINED, the surface-discriminated `PlacementAddress` when placed, and a REQUIRED `rationale` on both arms). Each decision also carries a REQUIRED `origin` — `DELIBERATED` or `REVISED` — which the trusted runtime stamps `DELIBERATED`; it is not representable in the provider-facing generation shape, because a panel run IS the panel's judgement and a model cannot declare its own output a human revision. A later edit that changes a decision sets `origin: REVISED` and records the panel's own reasoning in `supersedes.rationale`, so the artifact stops asserting panel reasoning for a decision the panel never took. Typed by the `_core` `placement-plan` family (`PlacementPlan`); the provider answers the strict `PlacementPlanGeneration` shape and the trusted runtime stamps refs and version. `validatePlacementPlan` is the deterministic validator: one subject placed twice on the SAME surface is a hard floor (the plan contradicts itself), while an empty group and an order collision are authoring warnings. Its coverage checks run only when the caller supplies the destination catalog, so a run without one reports no coverage result rather than a clean one. The plan carries no file path, config key or label string — those belong to the coding task that authors the config."
30
- }
31
- ],
32
- "stepOutputs": [],
33
- "method": {
34
- "guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** They come from the engine catalog and the\n workspace, read as workspace truth. A ref you invented resolves to nothing and the\n validator refuses it as an unknown subject.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every group has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
35
- "skillRefs": [
36
- "settings-placement-authoring",
37
- "config-app-shell",
38
- "config-navigation",
39
- "journey-status"
40
- ],
41
- "contextSources": [
42
- "workspace_truth"
43
- ],
44
- "suspendsForClarification": false,
45
- "briefAdequacyGate": false,
46
- "briefAdequacyExcludedSources": [],
47
- "deliberation": {
48
- "workDomain": "information_architecture",
49
- "reviewerRoleRefs": [
50
- "information-architect",
51
- "design-system-guardian"
52
- ],
53
- "coordinatorRoleRef": "design-system-guardian",
54
- "rubricDeriverRoleRef": "information-architect",
55
- "candidateCount": 3
56
- }
57
- },
58
- "executor": "companion_agent",
59
- "approval": "approve_result",
60
- "budget": {
61
- "maxRuns": 3
62
- },
63
- "onFailure": "keep_and_flag"
64
- }
@@ -1,41 +0,0 @@
1
- # Compliance Analysis — the evidence-grounded posture composite
2
-
3
- ### Target Application Framing
4
-
5
- This knowledge is for configuring behavior in the target application.
6
- Wildo is the framework surface being used, not the product being built.
7
-
8
- Read and apply these patterns from the application-developer point of view:
9
-
10
- - how the application should configure the relevant app-level file
11
- - how the application should use framework-provided factories, enums, and helpers
12
- - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
-
14
-
15
- You are the **conductor's scheduler**, not an author. This composite exists so the
16
- application's compliance posture rests on regime texts and regulator pages someone
17
- actually read — not on what a model remembers about the law, which is confident,
18
- fluent, and stale in exactly the cases that carry liability.
19
-
20
- ## The shape
21
-
22
- Three children, self-ordered by their own preconditions:
23
-
24
- 1. **compliance-research** — a read-only web lane gathering regime evidence for the
25
- jurisdictions, data classes and sector the vision (and the creator's answers)
26
- put in scope. Returns a condensed, source-attributed brief.
27
- 2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to
28
- state a posture from, and when it is not, names precisely what is missing so the
29
- next research round is aimed rather than repeated.
30
- 3. **compliance-posture** — the artifact-producing child: records each applicable
31
- regime as a `compliance`-kind constraint on the vision, deriving from the
32
- creator's elicitation answers AND the gathered evidence, only once the adequacy
33
- gate has returned ADEQUATE.
34
-
35
- ## What a round's research objective should name
36
-
37
- Compose each research objective for THIS round: on the first pass, the candidate
38
- regimes the vision's jurisdictions/data/sector suggest (verify applicability
39
- triggers against authoritative sources — regulator pages, official texts, not
40
- blogs); on later passes, exactly the gaps the adequacy verdict named. Never re-ask
41
- what a prior round established — its evidence is in the step results.