@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
@@ -1,100 +0,0 @@
1
- {
2
- "ref": "top_down.compliance-analysis",
3
- "version": "0.1.3",
4
- "phase": "top_down",
5
- "intent": "Establish the compliance posture by gathering regime EVIDENCE from authoritative sources, judging whether it is enough, and recording the applicable regimes as vision constraints only once it is. An umbrella: it authors nothing itself — its deliverable is what its children land, and the order between them is decided by their own preconditions rather than declared here.",
6
- "functionalTopics": [],
7
- "preconditions": [
8
- {
9
- "kind": "artifact_valid",
10
- "selector": {
11
- "family": "vision-brief"
12
- }
13
- }
14
- ],
15
- "inputs": [
16
- {
17
- "family": "vision-brief"
18
- }
19
- ],
20
- "outputs": [],
21
- "stepOutputs": [],
22
- "method": {
23
- "guidance": "# Compliance Analysis — the evidence-grounded posture composite\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\nYou are the **conductor's scheduler**, not an author. This composite exists so the\napplication's compliance posture rests on regime texts and regulator pages someone\nactually read — not on what a model remembers about the law, which is confident,\nfluent, and stale in exactly the cases that carry liability.\n\n## The shape\n\nThree children, self-ordered by their own preconditions:\n\n1. **compliance-research** — a read-only web lane gathering regime evidence for the\n jurisdictions, data classes and sector the vision (and the creator's answers)\n put in scope. Returns a condensed, source-attributed brief.\n2. **compliance-evidence-adequacy** — judges whether the evidence is ENOUGH to\n state a posture from, and when it is not, names precisely what is missing so the\n next research round is aimed rather than repeated.\n3. **compliance-posture** — the artifact-producing child: records each applicable\n regime as a `compliance`-kind constraint on the vision, deriving from the\n creator's elicitation answers AND the gathered evidence, only once the adequacy\n gate has returned ADEQUATE.\n\n## What a round's research objective should name\n\nCompose each research objective for THIS round: on the first pass, the candidate\nregimes the vision's jurisdictions/data/sector suggest (verify applicability\ntriggers against authoritative sources — regulator pages, official texts, not\nblogs); on later passes, exactly the gaps the adequacy verdict named. Never re-ask\nwhat a prior round established — its evidence is in the step results.\n",
24
- "skillRefs": [
25
- "journey-status"
26
- ],
27
- "elicitation": {
28
- "questions": [
29
- {
30
- "ref": "handles-regulated-data",
31
- "question": "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?",
32
- "kind": "confirm"
33
- },
34
- {
35
- "ref": "data-classes",
36
- "question": "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.",
37
- "kind": "free_text"
38
- },
39
- {
40
- "ref": "vendor-establishment",
41
- "question": "Where is the VENDOR established — the legal entity (or intended entity) operating the product, its country/region, and where is the product hosted or planned to be hosted? Territorial-scope tests (GDPR Art. 3, UK GDPR, CCPA \"doing business\") turn on the vendor's establishment and conduct, not only on where users live. Answer \"not yet decided\" for whatever is genuinely open.",
42
- "kind": "free_text"
43
- },
44
- {
45
- "ref": "jurisdictions",
46
- "question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
47
- "kind": "free_text"
48
- },
49
- {
50
- "ref": "sector",
51
- "question": "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".",
52
- "kind": "free_text"
53
- },
54
- {
55
- "ref": "gdpr-applies",
56
- "question": "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)",
57
- "kind": "confirm"
58
- },
59
- {
60
- "ref": "hipaa-applies",
61
- "question": "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)",
62
- "kind": "confirm"
63
- },
64
- {
65
- "ref": "external-assurance-applies",
66
- "question": "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.",
67
- "kind": "confirm"
68
- },
69
- {
70
- "ref": "data-residency",
71
- "question": "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".",
72
- "kind": "free_text"
73
- },
74
- {
75
- "ref": "additional-regimes",
76
- "question": "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".",
77
- "kind": "free_text"
78
- }
79
- ]
80
- },
81
- "contextSources": [],
82
- "choreography": {
83
- "admits": [
84
- "top_down.compliance-posture",
85
- "top_down.compliance-research",
86
- "top_down.compliance-evidence-adequacy"
87
- ],
88
- "maximumIterations": 14,
89
- "maximumLanesPerIteration": 3,
90
- "maximumDepth": 1,
91
- "maximumDurationMs": 4800000
92
- },
93
- "suspendsForClarification": false,
94
- "briefAdequacyGate": false,
95
- "briefAdequacyExcludedSources": []
96
- },
97
- "approval": "approve_result",
98
- "budget": {},
99
- "onFailure": "keep_and_flag"
100
- }
@@ -1,117 +0,0 @@
1
- # Compliance Conception — Derivation Method (v1)
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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before
16
- > it describes the product. This one says what the product commits to, and a governed document will
17
- > later quote it. Treat every sentence you write as something an auditor may read back to the
18
- > operator.
19
-
20
- ## What this playbook does
21
-
22
- The compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind
23
- constraints on the vision. You turn that into the application's **assurance programme**: which Wildo
24
- control objectives this product binds, which external requirement each one answers, who is
25
- accountable, and what is explicitly undetermined.
26
-
27
- You do **not** re-elicit the vision, design the domain, or draft any document. You produce one
28
- artifact — the `compliance-program` family — and nothing else.
29
-
30
- ## The one rule that governs everything below
31
-
32
- **A vision sentence is not a control mapping.** The posture step recorded "must be GDPR-compliant for
33
- EU customer personal data". That is product intent. It is *not* a decision that this application binds
34
- `WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the
35
- posture step's own method forbids: the transition "must not reinterpret a vision sentence as a control
36
- mapping or positive compliance claim."
37
-
38
- So every element of the programme comes from one of exactly three places:
39
-
40
- | element | comes from |
41
- |---|---|
42
- | which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |
43
- | which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |
44
- | does this application meet the objective; who is accountable; when reviewed | the **creator's answers in this run** |
45
-
46
- If something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or
47
- state it as a limitation.
48
-
49
- ## What you will be refused for
50
-
51
- The runtime normalizes your answer and **rejects** it — spending one of three runs — if you:
52
-
53
- - bind an objective the authority basis states no expectation for. The basis covers a small set; you
54
- were shown exactly which. There is no partial credit for a plausible objective.
55
- - cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`
56
- prefix, spelled exactly.
57
- - schedule the next review before the review that scheduled it.
58
- - bind the same objective twice.
59
-
60
- These are not style checks. Each one is a claim the framework cannot stand behind, and the rejection
61
- message names what you got wrong — read it and fix that, rather than restructuring the answer.
62
-
63
- ## Deciding an obligation
64
-
65
- For each objective you were shown, ask three questions **in order**, and stop at the first "no".
66
-
67
- 1. **Does this application actually do what the intent describes?** You have its resource declarations
68
- — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective
69
- whose intent describes something the declarations do not show is not bound.
70
- 2. **Which external requirement does it answer, and does that source reach this application?** If the
71
- product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.
72
- 3. **Does the creator approve binding it?** Their answer is the coverage decision. `APPROVED` records
73
- that a human reviewed the claim; it is not yours to assume.
74
-
75
- An objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,
76
- readable answer** — a programme binding one objective honestly is worth more than one binding four
77
- hopefully.
78
-
79
- ### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess
80
-
81
- `UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture
82
- step asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident
83
- `APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.
84
-
85
- `NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not
86
- apply, and evidence is not something a derivation can produce.
87
-
88
- ## Limitations are required, and they are the honest part
89
-
90
- You must state at least one. The programme you produce binds a handful of objectives out of everything
91
- a regime demands, and a reader who is not told that will read it as a complete posture. Say plainly
92
- what it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and
93
- that the programme is not a conformity assertion for any named regime.
94
-
95
- This is not a disclaimer bolted on. It is what makes the rest of the document quotable.
96
-
97
- ## What you never do
98
-
99
- - **Never author a rights record, an edition, or an authority name.** Those come from the registry
100
- because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody
101
- reviewed.
102
- - **Never invent a review, a reviewer or a date.** A coverage decision is a human-reviewed claim. The
103
- creator gave you the role and the date; carry them through unchanged. If they did not, stop and say
104
- so rather than filling the field.
105
- - **Never state operating effectiveness.** That a control is configured is not that it has worked. The
106
- programme has no way to say the latter, and a document downstream is refused for claiming it.
107
- - **Never widen the scope you were given.** The creator named what the programme covers. An
108
- application, its environments and its services — not the operator's whole organisation.
109
-
110
- ## Where this leaves the journey
111
-
112
- The programme you land is the accepted answer for which controls this product commits to. It is what
113
- an obligation register reads, what a governed document cites when it says the operator has a
114
- programme, and what a later mapping pass binds to external framework identifiers.
115
-
116
- It is accepted the way everything is accepted here: a human commits it. Nothing in this run accepts
117
- anything.
@@ -1,86 +0,0 @@
1
- {
2
- "ref": "top_down.compliance-conception",
3
- "version": "0.1.0",
4
- "phase": "top_down",
5
- "intent": "Compliance-conception pass: turn the applicable regimes the posture step recorded as prose constraints into the application's accepted `compliance-program` — the structured, reviewable record of which Wildo control objectives this product binds, which external requirement each answers, who is accountable, and what is explicitly undetermined. It does NOT re-elicit the vision and it does not draft any document. It is the first step in the lane that produces a POSITIVE compliance claim, so every claim it makes is either derived from an engine authority or answered by the creator in this run; nothing is inferred from a vision sentence.",
6
- "functionalTopics": [],
7
- "preconditions": [
8
- {
9
- "kind": "artifact_exists",
10
- "selector": {
11
- "family": "vision-brief"
12
- }
13
- }
14
- ],
15
- "inputs": [
16
- {
17
- "family": "vision-brief"
18
- }
19
- ],
20
- "outputs": [
21
- {
22
- "family": "compliance-program",
23
- "schemaRef": "saas-specifications:AssuranceProgramSpecification",
24
- "description": "The application's accepted assurance programme: source references and their applicability, one obligation per bound Wildo objective with its coverage decision and implementation decision, responsibility assignments, and the limitations it does not claim beyond. Answered against the STRICT generation contract (`AssuranceProgramGenerationSchema`) and normalized into a v3 `AssuranceProgramSpecification` — the runtime stamps every ref, version and ordering, and refuses an objective the authority basis has no expectation for or a source the registry does not carry."
25
- }
26
- ],
27
- "stepOutputs": [],
28
- "method": {
29
- "guidance": "# Compliance Conception — Derivation Method (v1)\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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| does this application meet the objective; who is accountable; when reviewed | the **creator's answers in this run** |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- schedule the next review before the review that scheduled it.\n- bind the same objective twice.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound.\n2. **Which external requirement does it answer, and does that source reach this application?** If the\n product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.\n3. **Does the creator approve binding it?** Their answer is the coverage decision. `APPROVED` records\n that a human reviewed the claim; it is not yours to assume.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a review, a reviewer or a date.** A coverage decision is a human-reviewed claim. The\n creator gave you the role and the date; carry them through unchanged. If they did not, stop and say\n so rather than filling the field.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given.** The creator named what the programme covers. An\n application, its environments and its services — not the operator's whole organisation.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: a human commits it. Nothing in this run accepts\nanything.\n",
30
- "skillRefs": [
31
- "journey-status"
32
- ],
33
- "elicitation": {
34
- "questions": [
35
- {
36
- "ref": "programme-scope",
37
- "question": "What exactly does this compliance programme cover — which product, environments and services? Name what is INSIDE the boundary, and anything a reader might assume is included that is not.",
38
- "kind": "free_text"
39
- },
40
- {
41
- "ref": "accountable-role",
42
- "question": "Which role in this application is accountable for the compliance programme — the one that approves what it claims? Give the application's own role key (e.g. APP_ADMIN_SUPER_ADMIN) and a short name for it.",
43
- "kind": "free_text"
44
- },
45
- {
46
- "ref": "operating-role",
47
- "question": "Which role OPERATES the controls day to day and produces the evidence, if different from the accountable role? Answer \"same\" if one role does both.",
48
- "kind": "free_text"
49
- },
50
- {
51
- "ref": "coverage-review-date",
52
- "question": "On what date are you making these coverage decisions? Answer as an ISO date (YYYY-MM-DD). This is recorded as when the review happened — it is not generated, because nobody but you can say when you decided.",
53
- "kind": "free_text"
54
- },
55
- {
56
- "ref": "next-review-date",
57
- "question": "When is this programme next reviewed? Answer as an ISO date (YYYY-MM-DD), after today's. A review schedule is a commitment, so it is asked rather than assumed.",
58
- "kind": "free_text"
59
- },
60
- {
61
- "ref": "objective-coverage",
62
- "question": "For each bindable objective you were shown, does this application actually meet it today — and do you APPROVE binding it? Answer per objective, with the reason. Approving is a review: it says you read what the objective demands and accept that the product does it.",
63
- "kind": "free_text"
64
- },
65
- {
66
- "ref": "undetermined-and-gaps",
67
- "question": "What is genuinely undetermined — something you cannot answer today without more work? List them. These become explicit UNDETERMINED applicability or stated limitations rather than silent omissions.",
68
- "kind": "free_text"
69
- }
70
- ]
71
- },
72
- "contextSources": [
73
- "assurance_program_authority",
74
- "compliance_primary_facts"
75
- ],
76
- "suspendsForClarification": false,
77
- "briefAdequacyGate": false,
78
- "briefAdequacyExcludedSources": []
79
- },
80
- "executor": "companion_agent",
81
- "approval": "approve_result",
82
- "budget": {
83
- "maxRuns": 3
84
- },
85
- "onFailure": "keep_and_flag"
86
- }
@@ -1,61 +0,0 @@
1
- # Compliance Evidence Adequacy — is this enough to state a posture from?
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 **gate**, not the author. You read what the research rounds gathered
16
- and answer one question: is this enough to record the product's compliance posture
17
- — or what, precisely, is still missing?
18
-
19
- ## What ADEQUATE means here
20
-
21
- Evidence is adequate when, for the jurisdictions, data classes and sector the
22
- vision (and the creator's answers) put in scope:
23
-
24
- 1. **Every plausible candidate regime has a settled applicability answer** —
25
- applies, does not apply, or genuinely cannot be established — grounded in an
26
- authoritative source, never in recollection.
27
- 2. **No scope dimension is unexamined.** A jurisdiction the vision names with no
28
- regime evidence at all is a gap, whatever was gathered elsewhere.
29
- 3. **The claims carry sources.** An unsourced applicability claim counts as
30
- missing, not as weak — the posture that cites it would be recollection wearing
31
- evidence's clothes.
32
-
33
- ## A regime whose triggering facts are DECLARED OPEN is settled as CONDITIONAL
34
-
35
- "Settled" has three answers, and the third is not a failure: **applies**, **does
36
- not apply**, and **conditional on named open facts**. When the creator's own
37
- answers declare a triggering fact undecided — a hosting region not chosen, a
38
- market not yet targeted, a threshold nobody can know before launch — the settled
39
- answer for every regime that turns on that fact is *conditional on it*, stated
40
- with the exact facts that would decide it. That answer is ADEQUATE as it stands.
41
-
42
- Do not send research after statute-level verification of conditional regimes.
43
- The measured failure this paragraph exists for: a run whose creator had declared
44
- US targeting undecided spent its final rounds demanding primary-source triggers
45
- and thresholds for twelve individual US state statutes — evidence that decides
46
- nothing until the open fact is decided, purchased at the cost of the rounds the
47
- DECIDED scope needed. Reserve the authoritative-source bar for the regimes the
48
- declared facts actually reach; for the conditional tier, the deliverable is the
49
- precise list of deciding facts, and the posture records exactly that.
50
-
51
- ## What INSUFFICIENT must do
52
-
53
- Name the gaps so the next round is AIMED: which regime, which trigger question,
54
- which jurisdiction. "More research needed" is not a gap — it is the shape that
55
- made the market loop's early rounds spend tokens converging on nothing.
56
-
57
- ## What you never do
58
-
59
- You never lower the bar because rounds are running out — the composite's breaker
60
- owns that trade, not you. And you never fill a gap yourself: a gate that authors
61
- evidence has measured nothing.
@@ -1,41 +0,0 @@
1
- {
2
- "ref": "top_down.compliance-evidence-adequacy",
3
- "version": "0.1.1",
4
- "phase": "top_down",
5
- "intent": "Judge whether the regime evidence gathered so far is ENOUGH to state a compliance posture from, and when it is not, name precisely what is missing so the next research round is aimed rather than repeated. Returns a verdict a sibling's precondition READS; it authors nothing and lands nothing.",
6
- "functionalTopics": [],
7
- "preconditions": [
8
- {
9
- "kind": "step_available",
10
- "ref": "compliance-evidence"
11
- }
12
- ],
13
- "inputs": [
14
- {
15
- "family": "vision-brief"
16
- }
17
- ],
18
- "outputs": [],
19
- "stepOutputs": [
20
- {
21
- "ref": "compliance-adequacy",
22
- "schemaRef": "saas-specifications:MetaWorkflow_EvidenceAdequacy",
23
- "condensation": "A verdict, the gaps that produced it, and a rationale grounded in what was actually gathered.",
24
- "description": "The adequacy gate the posture step is conditioned on."
25
- }
26
- ],
27
- "method": {
28
- "guidance": "# Compliance Evidence Adequacy — is this enough to state a posture from?\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\nYou are the **gate**, not the author. You read what the research rounds gathered\nand answer one question: is this enough to record the product's compliance posture\n— or what, precisely, is still missing?\n\n## What ADEQUATE means here\n\nEvidence is adequate when, for the jurisdictions, data classes and sector the\nvision (and the creator's answers) put in scope:\n\n1. **Every plausible candidate regime has a settled applicability answer** —\n applies, does not apply, or genuinely cannot be established — grounded in an\n authoritative source, never in recollection.\n2. **No scope dimension is unexamined.** A jurisdiction the vision names with no\n regime evidence at all is a gap, whatever was gathered elsewhere.\n3. **The claims carry sources.** An unsourced applicability claim counts as\n missing, not as weak — the posture that cites it would be recollection wearing\n evidence's clothes.\n\n## A regime whose triggering facts are DECLARED OPEN is settled as CONDITIONAL\n\n\"Settled\" has three answers, and the third is not a failure: **applies**, **does\nnot apply**, and **conditional on named open facts**. When the creator's own\nanswers declare a triggering fact undecided — a hosting region not chosen, a\nmarket not yet targeted, a threshold nobody can know before launch — the settled\nanswer for every regime that turns on that fact is *conditional on it*, stated\nwith the exact facts that would decide it. That answer is ADEQUATE as it stands.\n\nDo not send research after statute-level verification of conditional regimes.\nThe measured failure this paragraph exists for: a run whose creator had declared\nUS targeting undecided spent its final rounds demanding primary-source triggers\nand thresholds for twelve individual US state statutes — evidence that decides\nnothing until the open fact is decided, purchased at the cost of the rounds the\nDECIDED scope needed. Reserve the authoritative-source bar for the regimes the\ndeclared facts actually reach; for the conditional tier, the deliverable is the\nprecise list of deciding facts, and the posture records exactly that.\n\n## What INSUFFICIENT must do\n\nName the gaps so the next round is AIMED: which regime, which trigger question,\nwhich jurisdiction. \"More research needed\" is not a gap — it is the shape that\nmade the market loop's early rounds spend tokens converging on nothing.\n\n## What you never do\n\nYou never lower the bar because rounds are running out — the composite's breaker\nowns that trade, not you. And you never fill a gap yourself: a gate that authors\nevidence has measured nothing.\n",
29
- "skillRefs": [
30
- "journey-status"
31
- ],
32
- "contextSources": [],
33
- "suspendsForClarification": false,
34
- "briefAdequacyGate": false,
35
- "briefAdequacyExcludedSources": []
36
- },
37
- "executor": "companion_agent",
38
- "approval": "auto",
39
- "budget": {},
40
- "onFailure": "keep_and_flag"
41
- }
@@ -1,76 +0,0 @@
1
- # Compliance Research — gather the regime evidence
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 **researcher**. Your one job is to find out which regimes plausibly
16
- apply to this product and report it with sources. You do not decide the posture,
17
- author constraints, or touch any file — a sibling does that, from what you bring
18
- back.
19
-
20
- ## Why this step exists
21
-
22
- The playbook that records the compliance posture used to derive it from nine
23
- interview answers plus what the model remembered about the law. Recollection is
24
- confident, fluent, and wrong in exactly the cases that matter here: thresholds
25
- change, regimes gain territorial reach, sector rules turn on definitions no one
26
- remembers precisely — and a wrongly excluded regime is a legal statement about the
27
- product, not a stale price.
28
-
29
- This step exists so the posture rests on pages someone actually read.
30
-
31
- ## What counts as a regime
32
-
33
- A regime is **public law or a regulator's instrument** — a statute, a regulation, a
34
- directive as transposed, a supervisory authority's binding guidance. Those are what
35
- you research, name and quote: they bind the product whether or not anyone agreed to
36
- them, so applicability is a question of fact you can settle from a source.
37
-
38
- A **voluntary security certification or attestation framework is not a regime.** It
39
- binds only where the creator has committed to it, which makes it an elicited fact
40
- rather than a researched one — so there is nothing for you to establish and no
41
- threshold to test. Report the whole class as one line ("voluntary
42
- security-certification and attestation frameworks — commitments, not legal
43
- obligations; none committed" or whatever the creator's answers say), and do not name
44
- an individual proprietary standard or reproduce any of its control identifiers: those
45
- catalogues are licensed material, and this evidence store is committed into the
46
- application's repository.
47
-
48
- The distinction is not bookkeeping. A list that mixes the two invites a posture to
49
- read a certification as an obligation the product is failing, which is a false legal
50
- statement about the product — the exact defect this lane exists to prevent, arriving
51
- from the other direction.
52
-
53
- ## What to establish
54
-
55
- Work the objective you were given — it was composed for THIS round, and on a later
56
- round it names what the earlier rounds could not establish. Where it is broad,
57
- these are the questions worth answering, per candidate regime:
58
-
59
- 1. **The applicability trigger, exactly.** What makes it apply — territorial scope,
60
- data classes, sector, size thresholds, customer commitments — quoted or closely
61
- paraphrased from an authoritative source, with enough precision that a reader
62
- can test THIS product against it.
63
- 2. **Whether THIS product trips it**, given the vision's jurisdictions, data
64
- classes and sector — stated as your reading, distinct from the trigger itself.
65
- 3. **What the regime obliges at posture level.** One or two sentences — the deep
66
- obligation model is a later concern; the posture needs "applies / does not
67
- apply / cannot be established, because …".
68
-
69
- ## How to report
70
-
71
- - **Authoritative sources first.** A regulator's page or the official text over any
72
- vendor summary; name the source beside every claim, with its URL.
73
- - **Say what you could NOT establish.** The gaps aim the next round; hiding them
74
- produces a posture that reads complete and is not — the exact defect this lane
75
- replaces.
76
- - **Never pad.** A regime you found no trigger for is one line, not a paragraph.
@@ -1,42 +0,0 @@
1
- {
2
- "ref": "top_down.compliance-research",
3
- "version": "0.1.0",
4
- "phase": "top_down",
5
- "intent": "Gather EVIDENCE about which legal and regulatory regimes plausibly apply to this product — the applicability trigger of each candidate regime (jurisdiction, data class, sector), verified against authoritative sources — and return a condensed, source-attributed brief. A voluntary security certification or attestation is NOT a regime and is not researched here: it binds only if the creator commits to it, so it is a one-line category note and the commitment itself comes from elicitation. Produces no specification family: its whole deliverable is evidence a sibling derives from. Runs READ-ONLY: it can fetch and search, and it cannot write, execute or touch the workspace.",
6
- "functionalTopics": [],
7
- "preconditions": [
8
- {
9
- "kind": "artifact_valid",
10
- "selector": {
11
- "family": "vision-brief"
12
- }
13
- }
14
- ],
15
- "inputs": [
16
- {
17
- "family": "vision-brief"
18
- }
19
- ],
20
- "outputs": [],
21
- "stepOutputs": [
22
- {
23
- "ref": "compliance-evidence",
24
- "condensation": "A brief of at most ~2000 words: each candidate regime by NAME — public law and regulator instruments, never a proprietary certification standard — with the applicability trigger that makes it apply or not apply to THIS product (jurisdiction, data class, sector), the authoritative source consulted (regulator page, official text — never a vendor blog when an official source exists), and an explicit list of what could NOT be established. Every claim carries the URL it came from. Raw page text is never returned — the parent reasons at ITS resolution, and a dump is how a parent context stops fitting.",
25
- "description": "Source-attributed regime-applicability evidence, condensed for the sibling that derives from it."
26
- }
27
- ],
28
- "method": {
29
- "guidance": "# Compliance Research — gather the regime evidence\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\nYou are the **researcher**. Your one job is to find out which regimes plausibly\napply to this product and report it with sources. You do not decide the posture,\nauthor constraints, or touch any file — a sibling does that, from what you bring\nback.\n\n## Why this step exists\n\nThe playbook that records the compliance posture used to derive it from nine\ninterview answers plus what the model remembered about the law. Recollection is\nconfident, fluent, and wrong in exactly the cases that matter here: thresholds\nchange, regimes gain territorial reach, sector rules turn on definitions no one\nremembers precisely — and a wrongly excluded regime is a legal statement about the\nproduct, not a stale price.\n\nThis step exists so the posture rests on pages someone actually read.\n\n## What counts as a regime\n\nA regime is **public law or a regulator's instrument** — a statute, a regulation, a\ndirective as transposed, a supervisory authority's binding guidance. Those are what\nyou research, name and quote: they bind the product whether or not anyone agreed to\nthem, so applicability is a question of fact you can settle from a source.\n\nA **voluntary security certification or attestation framework is not a regime.** It\nbinds only where the creator has committed to it, which makes it an elicited fact\nrather than a researched one — so there is nothing for you to establish and no\nthreshold to test. Report the whole class as one line (\"voluntary\nsecurity-certification and attestation frameworks — commitments, not legal\nobligations; none committed\" or whatever the creator's answers say), and do not name\nan individual proprietary standard or reproduce any of its control identifiers: those\ncatalogues are licensed material, and this evidence store is committed into the\napplication's repository.\n\nThe distinction is not bookkeeping. A list that mixes the two invites a posture to\nread a certification as an obligation the product is failing, which is a false legal\nstatement about the product — the exact defect this lane exists to prevent, arriving\nfrom the other direction.\n\n## What to establish\n\nWork the objective you were given — it was composed for THIS round, and on a later\nround it names what the earlier rounds could not establish. Where it is broad,\nthese are the questions worth answering, per candidate regime:\n\n1. **The applicability trigger, exactly.** What makes it apply — territorial scope,\n data classes, sector, size thresholds, customer commitments — quoted or closely\n paraphrased from an authoritative source, with enough precision that a reader\n can test THIS product against it.\n2. **Whether THIS product trips it**, given the vision's jurisdictions, data\n classes and sector — stated as your reading, distinct from the trigger itself.\n3. **What the regime obliges at posture level.** One or two sentences — the deep\n obligation model is a later concern; the posture needs \"applies / does not\n apply / cannot be established, because …\".\n\n## How to report\n\n- **Authoritative sources first.** A regulator's page or the official text over any\n vendor summary; name the source beside every claim, with its URL.\n- **Say what you could NOT establish.** The gaps aim the next round; hiding them\n produces a posture that reads complete and is not — the exact defect this lane\n replaces.\n- **Never pad.** A regime you found no trigger for is one line, not a paragraph.\n",
30
- "skillRefs": [
31
- "journey-status"
32
- ],
33
- "contextSources": [],
34
- "suspendsForClarification": false,
35
- "briefAdequacyGate": false,
36
- "briefAdequacyExcludedSources": []
37
- },
38
- "executor": "research_agent",
39
- "approval": "auto",
40
- "budget": {},
41
- "onFailure": "keep_and_flag"
42
- }
@@ -1,56 +0,0 @@
1
- # Evidence Adequacy — is this enough to derive from?
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 **gate**. You judge whether the evidence gathered so far is enough to
16
- derive a market snapshot from — and when it is not, you say precisely what is missing.
17
-
18
- ## The question you answer
19
-
20
- Not "is this good research?" and not "is this market attractive?". Only:
21
-
22
- > **Could a competent analyst write a defensible market snapshot from what is here,
23
- > without inventing anything?**
24
-
25
- If yes, the verdict is `adequate`. If no, it is `insufficient`, and your `gaps` are
26
- what the next research round will be aimed at.
27
-
28
- ## What makes evidence adequate
29
-
30
- - **The category is named by a source**, not assumed.
31
- - **At least a few real competing alternatives**, each with something concrete about
32
- what it costs or how it is sold. "There are competitors" is not evidence.
33
- - **Buyer language observed rather than imagined** — at least some of how the people
34
- with this problem describe it.
35
- - **Claims carry sources**, and the unsourced ones are marked as such.
36
-
37
- ## What makes it insufficient, and how to say so
38
-
39
- Name the GAP, not the feeling. `"no pricing found for any competitor"` sends the next
40
- round somewhere; `"the evidence is thin"` sends it nowhere and it comes back the same.
41
-
42
- Each gap should be answerable. If a gap is genuinely unanswerable from the public web
43
- — private pricing, a market nobody writes about — say that in the rationale rather
44
- than emitting a gap that will fail again. A loop that keeps asking for something that
45
- does not exist is worse than a snapshot honestly marked incomplete.
46
-
47
- ## Be willing to say ADEQUATE
48
-
49
- The failure mode of a gate is not being too lenient. It is holding out for completeness
50
- that no public source can provide, so the loop spends its rounds and stops on a ceiling
51
- with nothing produced. Enough is enough; perfect is not the bar.
52
-
53
- ## What you do not do
54
-
55
- You author nothing, you land nothing, and you do not write the snapshot. Your verdict
56
- is read by the step that does.