@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
@@ -63,83 +63,22 @@ Open `frontend/src/config/navigation.config.ts`.
63
63
 
64
64
  ### Step 2: Read constraints
65
65
 
66
- `references/how-navigation-resolves.md`
67
- `references/navigation-configuration-map.md`
68
- `references/framework-navigation-vocabulary-api.md`
69
66
  `references/navigation-zones.md`
70
67
  `references/framework-navigation-layout-api.md`
71
- `references/framework-navigation-zone-declaration-api.md`
72
68
 
73
69
  Understand the **resolution order** (per-resource override → per-relationship
74
70
  override → viewport override → zone transitions → framework fallback)
75
71
  before changing any block — edits to a higher tier silently override
76
72
  lower-tier rules.
77
73
 
78
- ### Step 2b: Read a second zone's declaration before adding one
79
-
80
- Most of `ZoneConfig` decides nothing until a SECOND zone exists. A single-zone
81
- layout accepts `onEmpty`, `minWidth`, `maxWidth` and `responsiveCollapse` and
82
- gives no feedback about whether any of them was understood, because none of
83
- them can apply. Adding a secondary zone makes all four live at once.
84
-
85
- Three of them behave in ways the field name does not imply:
86
-
87
- - **`orientation` names the DIVIDER, not the stacking axis.** `VERTICAL` is a
88
- vertical divider, which puts the panes SIDE BY SIDE; `HORIZONTAL` puts the
89
- second pane below. The schema example says so and it is the opposite of what
90
- most panel libraries mean by "direction".
91
- - **`minWidth` is a floor only when the zone cannot collapse.** A collapsible
92
- panel treats a minimum as a SNAP THRESHOLD: dragging past it closes the pane
93
- rather than stopping. Declaring `minWidth` is what asks for a floor.
94
- - **`ratio` is a percentage and the bounds are pixels**, so the two agree at one
95
- container width only. Below the crossover the ratio is clamped up to the
96
- floor — the pane opens at its minimum rather than at the share you wrote.
97
-
98
- ### Step 2c: Choose the LEVEL before choosing the value
99
-
100
- Navigation is configured at four levels — application layout, zone, destination view, destination
101
- operation — and the same behaviour is expressible at more than one of them. Picking the wrong level is
102
- the most common mistake here, because it works for the surface in front of you and quietly changes
103
- every other one.
104
-
105
- `references/navigation-configuration-map.md` is the inventory. The test is **who disagrees**:
106
-
107
- - every destination behaves this way → the **zone**
108
- - every zone behaves this way → the **layout**
109
- - one destination disagrees with the application it lives in → that **destination**
110
- - it only differs on small screens → a **viewport** discriminator at whichever level above
111
-
112
- ### Step 3: Decide whether this is a LAYOUT rule or an EXCEPTION
113
-
114
- A `NavigationLayout` states what happens for a whole application: from this
115
- zone, this operation resolves to this transition. Some destinations genuinely
116
- disagree with the application they live in — a canvas whose detail must float
117
- over it rather than take 40% of it, a list that wants its detail pane to
118
- persist while a reviewer steps through rows.
119
-
120
- Express that as a per-operation override, never as component state:
121
-
122
- `references/framework-navigation-operation-override-api.md`
123
-
124
- The declaration lives on the operation and is resolved BEFORE the zone's own
125
- transition map, so one operation departs from the layout without the layout
126
- knowing. `fromZone` narrows it further when the same operation should behave
127
- differently depending on where it was reached from.
128
-
129
- The alternative an author reaches for — holding the selection in `useState` and
130
- rendering a panel beside the content — produces something that looks identical
131
- and has none of the framework's behaviour: no URL, no back navigation, no zone
132
- semantics, no responsive collapse. If a detail surface cannot be linked to, that
133
- is the tell.
134
-
135
- ### Step 4: Edit the layout
74
+ ### Step 3: Edit the layout
136
75
 
137
76
  Mirror the canonical zone-first shape: every zone declares `contentModel`,
138
77
  `transitions`, and `appearance`. The `appLevel` and `fromOverlay` blocks
139
78
  are first-class siblings to `zones`, not nested inside them. Viewport
140
79
  overrides are top-level keyed by `ViewportBreakpoint.*`.
141
80
 
142
- ### Step 5: Align consumers
81
+ ### Step 4: Align consumers
143
82
 
144
83
  If new zones are introduced, update `views-app-level` registrations so
145
84
  launcher items can target them. Per-resource overrides in
@@ -259,20 +198,8 @@ What is **not** in this block (and shouldn't be):
259
198
 
260
199
  ## References
261
200
 
262
- - `references/navigation-configuration-map.md` — **the inventory**: every configurable aspect, which of
263
- - `references/framework-content-width-api.md` — the three width caps between a zone and a line of text, who owns each, and the reading-measure tier a display template declares.
264
- the four levels it is declared at, what it decides, and which fields the runtime does not read
265
- - `references/how-navigation-resolves.md` — **read first**: the five-tier resolution order, where each
266
- transition puts content, the URL contract, what a layout may declare that the runtime does not read,
267
- and the fields whose names read backwards
268
- - `references/framework-navigation-vocabulary-api.md` — the transition verbs and the surface
269
- vocabularies the layout schema is written in
270
201
  - `references/navigation-zones.md` — zone / transition concepts for authors
271
202
  - `references/framework-navigation-layout-api.md` — engine `NavigationLayoutSchema` / `NavigationLayout`
272
- - `references/framework-navigation-zone-declaration-api.md` — what ONE zone declares: `onEmpty`,
273
- `zoneContentMaxWidth` / `zoneContentFillsHeight`, drag bounds, responsive collapse
274
- - `references/framework-navigation-operation-override-api.md` — the per-operation EXCEPTION: a
275
- different transition, appearance or overlay behaviour for one operation
276
203
 
277
204
  ## Verification
278
205
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: config-saas
3
- description: Edit `wildo.saas.config.ts` for modules, services, engineCapabilities, provider scopes, providerConfigurations, bootstrap, data-service prefixes, and the application's compliance declarations. Use when the user says "add the <module-name> module", "wire a new minion/worker", "enable the <capability> capability", "switch the email provider to <x>", "turn on billing/organizations", "record our legal entity", "declare which jurisdictions we operate in", "set the retention schedule", or any change at the SaaS root that re-shapes app composition or states what is legally true of the application.
3
+ description: Edit `wildo.saas.config.ts` for modules, services, engineCapabilities, provider scopes, providerConfigurations, bootstrap, and data-service prefixes. Use when the user says "add the <module-name> module", "wire a new minion/worker", "enable the <capability> capability", "switch the email provider to <x>", "turn on billing/organizations", or any change at the SaaS root that re-shapes app composition rather than touching a single resource.
4
4
  ---
5
5
 
6
6
  # Config SaaS
@@ -47,9 +47,6 @@ this file as ground truth — the only place where the app declares
47
47
  - Switching runtime provider scope or provider-specific non-secret config
48
48
  - Adding a new minion / worker / library
49
49
  - Changing data-service prefixes (mongodb / redis / rabbitmq / s3)
50
- - Declaring the application's legal posture — the operating entity, the jurisdictions it
51
- operates in, the retention schedule, the AI-use posture, client storage, or per-provider
52
- compliance choices (see `references/compliance-declarations.md`)
53
50
 
54
51
  ## When NOT to Use
55
52
 
@@ -76,7 +73,7 @@ entries for shape; rely on TypeScript to validate keys.
76
73
 
77
74
  `wildo.saas.config.ts` declares the application topology: services, modules,
78
75
  libraries, workers, minions, engine capabilities, provider scopes, and the `specifications` package
79
- path. The `specifications/` package carries the specification layer that
76
+ path. The `specifications/` package carries the semantic-delta layer that
80
77
  explains what that topology means.
81
78
 
82
79
  When you change `wildo.saas.config.ts` or infrastructure config files, update
@@ -161,7 +158,6 @@ What is **not** in this block (and shouldn't be):
161
158
  - `references/saas-config-scope.md` — what belongs in root SaaS config
162
159
  - `references/framework-wildo-saas-config-api.md` — `WildoSaasConfigSchema` / inferred types
163
160
  - `references/framework-provider-capabilities-api.md` — engine slots and provider capability vocabulary, including durable email selection
164
- - `references/compliance-declarations.md` — the six compliance declarations, and why an ABSENT one is never a negative answer
165
161
 
166
162
  ## Verification
167
163
 
@@ -171,8 +167,6 @@ What is **not** in this block (and shouldn't be):
171
167
  - [ ] Every provider used by a runtime scope has a matching declaration in `providers.scopes`
172
168
  - [ ] `services` keys referenced by `modules[*].services` actually exist in `services`
173
169
  - [ ] Companion sees the updated module list (re-run companion introspection)
174
- - [ ] No compliance declaration carries an invented value — every one is either the operator's
175
- own answer or absent (absent is reported as an open gap; invented is published as fact)
176
170
 
177
171
  ### Grep invariants
178
172
 
@@ -185,7 +179,6 @@ Run from the app root:
185
179
  | **Module entries ↔ module folders agree** (must return empty) | `comm -3 <(rg -oN "^\s+'\K[a-z-]+(?='\s*:\s*\{)" wildo.saas.config.ts \| sort -u) <(ls -1 shared-lib/src/modules/ \| sort -u)` |
186
180
  | Minion / worker paths exist | `rg -oN "path:\s+'\K[^']+" wildo.saas.config.ts \| while read p; do test -d "$p" \|\| echo "MISSING: $p"; done` |
187
181
  | Each engine capability declares `enabled:` | `rg -n "EngineCapability\.[A-Z_]+\]:\s*\{" wildo.saas.config.ts \| wc -l` then `rg -c "enabled:" wildo.saas.config.ts` |
188
- | **No placeholder in a compliance declaration** (must return empty) | `rg -n "TODO\|TBD\|PLACEHOLDER\|example\.com\|Acme" wildo.saas.config.ts` |
189
182
 
190
183
  The third invariant (modules ↔ folders) is the high-signal one — a
191
184
  module declared in config without a matching folder breaks `pnpm dev`
@@ -199,10 +192,6 @@ silently in some pipelines and blocks others on startup.
199
192
  | "Inline the AI provider key here" | Provider secrets MUST stay in secrets/env. Config only declares **policy** (which providers are allowed); the credentials sit in `wildo-secrets` or env. |
200
193
  | "Skip `dataServices.*` prefixes — defaults work" | Defaults collide across apps in shared infra; the prefix declaration is what isolates state per app/environment. |
201
194
  | "I'll add a new key not in the schema, the framework will pick it up" | The schema is the contract — unknown keys are dropped or error. Add the field through the framework first if a new dimension is needed. |
202
- | "Put a placeholder entity name in now and fix it later" | A produced document quotes it as fact. An absent declaration is reported as an open gap a reader can see; an invented one is published. Leave it out. |
203
- | "The identity needs every field, so I'll wait until I have them all" | Every part is independently declarable — record the half you know. Waiting is how the answer ends up edited into a document that a regeneration then replaces. |
204
- | "No `operatingJurisdictions` means the app is domestic-only" | Absent means nobody answered. It is not a jurisdiction claim, and no consumer may read it as one. |
205
- | "The framework warned it knows nothing about a jurisdiction, so drop it" | The application still operates there. Removing it hides a known unknown that belongs in the document's limitations. |
206
195
 
207
196
  ## Red Flags
208
197
 
@@ -210,12 +199,6 @@ silently in some pipelines and blocks others on startup.
210
199
  - Minion / worker entry pointing at a non-existent `path` (catch with the **Minion / worker paths exist** check — must return no `MISSING:` lines).
211
200
  - Engine capability block lacking `enabled:` (catch with the **Each engine capability declares `enabled:`** check — counts must match).
212
201
  - Frontend service with no `frontendType` (implicit defaults are framework-version-dependent; declare it explicitly).
213
- - A compliance declaration containing a placeholder, an example domain or a plausible-looking
214
- invented address (catch with the **No placeholder in a compliance declaration** grep — must return empty).
215
- - `roleAllocations` collapsed to a single role when the product both hosts customer records and
216
- holds its own account data — that is two roles over two populations, and one is misstated.
217
- - A `jurisdictionSlug` declared with no `basis`, or a basis that restates the slug ("operates in the EU")
218
- — the basis exists to say established/selling/holding-data, which imply different obligations.
219
202
 
220
203
  ## Related Skills
221
204
 
@@ -66,13 +66,11 @@ export enum EngineCapability {
66
66
  * extraction into `AI_LLM` would have made one `selection[AI_LLM].primary` decide all three,
67
67
  * which is exactly the defect that split `AI_EMBEDDINGS` out of `AI_LLM`.
68
68
  *
69
- * ## Not to be confused with PDF GENERATION
69
+ * ## Not to be confused with `DOCUMENT_GENERATION`
70
70
  *
71
- * PDF generation — templates and data become bytes — is the `pdfTemplates` surface, done
72
- * in-process and with no provider slot of its own. This is the opposite direction: bytes become
73
- * text. The two are unrelated and nothing routes between them. (There WAS an
74
- * `EngineCapability.DOCUMENT_GENERATION` that this paragraph used to name; it was withdrawn
75
- * because no provider capability could ever fill it.)
71
+ * `DOCUMENT_GENERATION` is PDF *generation* — templates and data become bytes. This is the
72
+ * opposite direction: bytes become text. The names are adjacent and the capabilities are
73
+ * unrelated; nothing routes between them.
76
74
  *
77
75
  * ## Absence is benign, and that is load-bearing
78
76
  *
@@ -99,26 +97,8 @@ export enum EngineCapability {
99
97
  */
100
98
  AI_CODING_AGENT = 'AI_CODING_AGENT',
101
99
 
102
- /*
103
- * WITHDRAWN 2026-09-03: `DOCUMENT_GENERATION` and `ANTIVIRUS_SCANNING` were members here and are
104
- * not any more. Neither could ever be filled — `PROVIDER_CAPABILITY_TO_ENGINE_CAPABILITY` had no
105
- * entry pointing at either, so no provider capability token could claim the slot — while both were
106
- * classified `SELECT_ONE`, which asserts that exactly one provider must be selected. Selecting one
107
- * of zero candidates is not a resolution mode.
108
- *
109
- * Both capabilities are real and both are delivered elsewhere, which is why withdrawing the slots
110
- * costs nothing: antivirus scanning is `InfraCapability.ANTIVIRUS_SCANNING`, fulfilled by ClamAV
111
- * and consumed by `FileScanningBackendService`; PDF generation is the in-process `pdfTemplates`
112
- * surface, with `InfraCapability.DOCUMENT_RENDERING` (Gotenberg) provisioned beside it. Neither
113
- * has an external provider, and neither is planned to.
114
- *
115
- * Removing `ANTIVIRUS_SCANNING` also removes a collision: the identical spelling named an engine
116
- * slot nothing could fill AND a live infra capability, in two packages, so a reader grepping the
117
- * word landed in whichever they searched first.
118
- *
119
- * If a hosted AV or document-rendering vendor is ever adopted, the member comes back WITH its
120
- * `PROVIDER_CAPABILITY_TO_ENGINE_CAPABILITY` entry and its own JSDoc in the same change.
121
- */
100
+ DOCUMENT_GENERATION = 'DOCUMENT_GENERATION',
101
+ ANTIVIRUS_SCANNING = 'ANTIVIRUS_SCANNING',
122
102
 
123
103
  FRONTEND_ERROR_MONITORING = 'FRONTEND_ERROR_MONITORING',
124
104
  FRONTEND_PRODUCT_ANALYTICS = 'FRONTEND_PRODUCT_ANALYTICS',
@@ -186,10 +166,9 @@ export const BUILTIN_PROVIDER_CAPABILITY = {
186
166
  * a read of a PDF's existing text layer. Maps to `EngineCapability.AI_DOCUMENT_EXTRACTION`.
187
167
  *
188
168
  * A NEW token was genuinely required rather than convenient: `IMAGE_GENERATION` is an OUTPUT
189
- * capability (text → image), and PDF *generation* — the `pdfTemplates` surface — is this
190
- * capability's exact opposite. Nothing in the existing vocabulary claimed the document-INPUT
191
- * slot. (This paragraph used to name `EngineCapability.DOCUMENT_GENERATION`; that member was
192
- * withdrawn because no provider capability could fill it.)
169
+ * capability (text → image), and `EngineCapability.DOCUMENT_GENERATION` is PDF *generation*,
170
+ * which is this capability's exact opposite. Nothing in the existing vocabulary claimed the
171
+ * document-INPUT slot.
193
172
  *
194
173
  * Distinct from `LLM_CHAT` even where a vendor serves both from one API key: the work is
195
174
  * different (a page-layout model, billed per page, with no sampling parameters), and fusing
@@ -96,57 +96,6 @@ export const WildoSaasConfigSchema = z.strictObject({
96
96
  bootstrap: AppBootstrapSchema.optional(),
97
97
  dataServices: AppDataServicesSchema,
98
98
 
99
- /**
100
- * How long this application keeps each class of data, and why.
101
- *
102
- * Declared HERE, beside `dataServices`, because the two describe the same thing from opposite ends:
103
- * `dataServices` says which stores exist, and this says how long what is in them is kept. Both are
104
- * application-wide operator decisions rather than per-resource authoring.
105
- *
106
- * Optional as a whole, and partial within itself. An application that has decided nothing omits it;
107
- * one that has decided only its customer-data period declares only that. Absence is never read as
108
- * "kept forever" — a compliance document states the classes that ARE declared and marks the rest as
109
- * needing an operator decision, which is what lets the document be produced today rather than
110
- * waiting on a number nobody has yet.
111
- *
112
- * Two consumers, and the second is why the classes are the STORES: a privacy notice's retention
113
- * paragraph (issue #89, which is why this exists), and the backup-and-restore inventory a remote
114
- * environment still has none of (issue #8) — one declaration answers both instead of two that drift.
115
- */
116
- dataRetention: ApplicationRetentionScheduleSchema.optional(),
117
-
118
- /**
119
- * Whether each AI capability this application enables DECIDES something about a person, and who
120
- * reviews it if so.
121
- *
122
- * A capability establishes that AI is in use and for what function; it cannot establish consequence,
123
- * because the same `AI_LLM` backs a summariser that decides nothing and a screener that decides a
124
- * great deal (issue #92).
125
- *
126
- * Optional and partial, like `dataRetention` — but the silence here is the more dangerous one. A
127
- * notice describing AI use without addressing consequence does not read as "unknown", it reads as
128
- * "nothing significant happens", which silently claims an exemption. So an enabled AI capability with
129
- * no entry is REPORTED as outstanding rather than assumed harmless.
130
- */
131
- aiUsePosture: ApplicationAiUsePostureSchema.optional(),
132
-
133
- /**
134
- * What this application stores in a visitor's browser, per FRONTEND SURFACE — the itemised table a
135
- * cookie notice IS (issue #91).
136
- *
137
- * Per surface because a public marketing site and the authenticated application set different things,
138
- * and one merged list would be wrong for both. The FRAMEWORK's own cookies are not declared here:
139
- * every application inherits them and none authored them, so they are answered by
140
- * `ENGINE_CLIENT_STORAGE_ENTRIES` and reported separately.
141
- *
142
- * Optional and partial. A surface with no entry has not been inventoried and is reported as such; an
143
- * empty ARRAY is the different, positive answer — this surface sets nothing of its own.
144
- */
145
- clientStorage: ApplicationClientStorageInventorySchema.optional(),
146
- operatingJurisdictions: ApplicationOperatingJurisdictionsSchema.optional(),
147
- operatorComplianceIdentity: ApplicationOperatorComplianceIdentitySchema.optional(),
148
- providerComplianceChoices: ApplicationProviderComplianceChoicesSchema.optional(),
149
-
150
99
  /**
151
100
  * Module registries the app pulls modules from. Each entry pairs a
152
101
  * stable id (used by lockfile entries + the `--registry <id>` CLI
@@ -39,13 +39,6 @@ export const StripeBackendProvider: BackendProviderModule = {
39
39
  ref: "stripe",
40
40
  displayNameLabelKey: buildProviderDisplayNameLabelKey('stripe'),
41
41
  },
42
- // WHO can run this, and where its vendor processes — read by the compliance-document lane to
43
- // decide whether this provider is a third-party recipient at all (issue #130).
44
- complianceProfile: {
45
- deploymentModels: [ProviderDeploymentModel.VENDOR_HOSTED],
46
- processingRegions: ['us-east-1', 'eu-west-1'],
47
- vendorLegalEntityName: 'Stripe, Inc.',
48
- },
49
42
  providerCapabilities: [
50
43
  BUILTIN_PROVIDER_CAPABILITY.BILLING,
51
44
  ],
@@ -73,8 +73,7 @@ File: `backend-api/src/modules/<module>/addons/flows-actors/*.ts`. The system mu
73
73
  be `kind: ACTOR` with an actor whose `executionMode` is `AGENTIC` and a bound
74
74
  `agentRef`. If it renders an in-app chat, it already qualifies — build it via
75
75
  `flows-actors-chat-assistant`. Verify what will be advertised:
76
- (There is no live introspection query for A2A exposure yet — verify against the agent/flow
77
- declarations in `shared-lib` themselves.)
76
+ // TODO CLI COMMAND: wildo context flows-actors --a2a-exposable
78
77
 
79
78
  ### Step 2: Enable external auth (OIDC provider + OAuth client)
80
79
  External agents get a token from YOUR app's OIDC provider. For **user-delegated**
@@ -102,10 +102,9 @@ export interface A2A_AgentCard {
102
102
 
103
103
  ## The A2A task surface (`tasks/get` / `tasks/cancel`)
104
104
 
105
- Read this when an external agent needs to start work it will come back for. A turn that pauses
106
- for human approval also becomes a task: it reaches `input-required`, persists the decision it is
107
- waiting on, and leaves that state once its execution moves on. Both paths into a task are live,
108
- so an integration you build now can encounter either.
105
+ Read this when an external agent needs to start work it will come back for. (A turn that
106
+ pauses for human approval also becomes a task — but that pausing runtime is a LATER phase and
107
+ is not live today, so nothing you build now can reach it.)
109
108
 
110
109
  The key thing to understand is **when a task exists at all** — most turns never create
111
110
  one, and that is deliberate rather than a gap.
@@ -857,7 +857,6 @@ export interface SpecificationsCompanionExports<
857
857
  TRequirementsSnapshot = RequirementsSnapshot,
858
858
  TRoadmapSnapshot = RoadmapSnapshot,
859
859
  TBuildPlanTaskGraph = BuildPlanTaskGraph,
860
- TPlacementPlan = PlacementPlan,
861
860
  TDomainPlanOutputSet = DomainPlanOutputSet,
862
861
  TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
863
862
  // Appended STRICTLY LAST (positional generics — never insert mid-list):
@@ -885,14 +884,6 @@ export interface SpecificationsCompanionExports<
885
884
  // Appended STRICTLY LAST: release-process selection is a separate accepted
886
885
  // decision, never an implicit default of routing or document necessity.
887
886
  TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
888
- // Appended STRICTLY LAST: WHO else processes personal data, under what legal
889
- // identity and where (issue #88). Optional, and the optionality is the design:
890
- // a partial register is useful and its holes are REPORTED per provider against
891
- // the application's configured set, rather than blocking anything.
892
- TProcessorRegister = ApplicationProcessorRegister,
893
- // Appended STRICTLY LAST: the human half of the document facts, in its own
894
- // family, because the derived one is REGENERATED whole (#192).
895
- TAuthoredDocumentFactSpecification = ApplicationAuthoredDocumentFactSpecification,
896
887
  > {
897
888
  resourceSpecifications: TResourceSpecifications;
898
889
  applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
@@ -1123,22 +1114,6 @@ export interface SpecificationsCompanionExports<
1123
1114
  * `validateBuildPlanTaskGraph` on the value before wiring it here.
1124
1115
  */
1125
1116
  buildPlanSpecification?: TBuildPlanTaskGraph;
1126
- /**
1127
- * Application **placement** specification — WHERE every settings destination,
1128
- * resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
1129
- * `_core/placement-plan/`).
1130
- *
1131
- * Produced by the `bottom_up.placement-plan` playbook as an expert-panel
1132
- * DELIBERATION rather than a creator elicitation: the creator does not choose
1133
- * placement, so each decision carries a `rationale` that answers "why is this
1134
- * here?" without re-running the panel. Consumed by build-decompose, which
1135
- * turns it into the coding tasks that author `settings-hub.config.ts` and
1136
- * `app-shell.config.ts`.
1137
- *
1138
- * Optional until an application reaches the bottom-up phase; app bootstraps
1139
- * should run `validatePlacementPlan` on the value before wiring it here.
1140
- */
1141
- placementPlanSpecification?: TPlacementPlan;
1142
1117
  /**
1143
1118
  * Application **domain-plan** specification — the atomic module decomposition
1144
1119
  * PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
@@ -1277,37 +1252,6 @@ export interface SpecificationsCompanionExports<
1277
1252
  * Omitting it is honest: unresolved document facts remain visible gaps.
1278
1253
  */
1279
1254
  documentFactSpecification?: TDocumentFactSpecification;
1280
- /**
1281
- * Accepted application governed-document facts **only a human may establish** — a creator decision
1282
- * or a qualified review (`document-facts-authored`).
1283
- *
1284
- * The same shape as the slot above, and a separate family on purpose. `refinement.document-facts`
1285
- * rewrites the derived file whole, so a human decision sharing that file is destroyed on the next
1286
- * run with nothing to notice: there is no compare-and-swap here, deliberately
1287
- * (`.claude/rules/one-source-of-truth.md` Rule 0). Two families put the two writers out of each
1288
- * other's reach.
1289
- *
1290
- * No producer may write this family — it has no generation contract, and that absence is the design
1291
- * rather than an omission.
1292
- *
1293
- * A reader wanting "the application's facts" needs BOTH slots. `collectComplianceDocumentFactAvailability`
1294
- * is variadic for exactly that reason.
1295
- */
1296
- authoredDocumentFactSpecification?: TAuthoredDocumentFactSpecification;
1297
- /**
1298
- * WHO else processes this application's personal data — legal identity, processing region and the
1299
- * processor's own subprocessors (issue #88).
1300
- *
1301
- * A configured provider already establishes THAT a third party is involved and what function it
1302
- * performs. None of that is what a privacy notice's recipient statement needs, and an
1303
- * international-transfer statement cannot be made at all without a region.
1304
- *
1305
- * Optional, and its holes are reported rather than blocking: the companion compares this register
1306
- * against the application's CONFIGURED providers and names each one that is undeclared, so a partial
1307
- * register is useful and an empty one still produces an actionable document. An absent entry means
1308
- * nobody has established that processor's identity — never that the provider is unused.
1309
- */
1310
- processorRegister?: TProcessorRegister;
1311
1255
  /**
1312
1256
  * Accepted application-declared semantic causality between whole
1313
1257
  * specification-family states. This is not the registry's physical
@@ -763,7 +763,6 @@ export interface SpecificationsCompanionExports<
763
763
  TRequirementsSnapshot = RequirementsSnapshot,
764
764
  TRoadmapSnapshot = RoadmapSnapshot,
765
765
  TBuildPlanTaskGraph = BuildPlanTaskGraph,
766
- TPlacementPlan = PlacementPlan,
767
766
  TDomainPlanOutputSet = DomainPlanOutputSet,
768
767
  TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
769
768
  // Appended STRICTLY LAST (positional generics — never insert mid-list):
@@ -791,14 +790,6 @@ export interface SpecificationsCompanionExports<
791
790
  // Appended STRICTLY LAST: release-process selection is a separate accepted
792
791
  // decision, never an implicit default of routing or document necessity.
793
792
  TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
794
- // Appended STRICTLY LAST: WHO else processes personal data, under what legal
795
- // identity and where (issue #88). Optional, and the optionality is the design:
796
- // a partial register is useful and its holes are REPORTED per provider against
797
- // the application's configured set, rather than blocking anything.
798
- TProcessorRegister = ApplicationProcessorRegister,
799
- // Appended STRICTLY LAST: the human half of the document facts, in its own
800
- // family, because the derived one is REGENERATED whole (#192).
801
- TAuthoredDocumentFactSpecification = ApplicationAuthoredDocumentFactSpecification,
802
793
  > {
803
794
  resourceSpecifications: TResourceSpecifications;
804
795
  applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
@@ -1029,22 +1020,6 @@ export interface SpecificationsCompanionExports<
1029
1020
  * `validateBuildPlanTaskGraph` on the value before wiring it here.
1030
1021
  */
1031
1022
  buildPlanSpecification?: TBuildPlanTaskGraph;
1032
- /**
1033
- * Application **placement** specification — WHERE every settings destination,
1034
- * resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
1035
- * `_core/placement-plan/`).
1036
- *
1037
- * Produced by the `bottom_up.placement-plan` playbook as an expert-panel
1038
- * DELIBERATION rather than a creator elicitation: the creator does not choose
1039
- * placement, so each decision carries a `rationale` that answers "why is this
1040
- * here?" without re-running the panel. Consumed by build-decompose, which
1041
- * turns it into the coding tasks that author `settings-hub.config.ts` and
1042
- * `app-shell.config.ts`.
1043
- *
1044
- * Optional until an application reaches the bottom-up phase; app bootstraps
1045
- * should run `validatePlacementPlan` on the value before wiring it here.
1046
- */
1047
- placementPlanSpecification?: TPlacementPlan;
1048
1023
  /**
1049
1024
  * Application **domain-plan** specification — the atomic module decomposition
1050
1025
  * PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
@@ -1183,37 +1158,6 @@ export interface SpecificationsCompanionExports<
1183
1158
  * Omitting it is honest: unresolved document facts remain visible gaps.
1184
1159
  */
1185
1160
  documentFactSpecification?: TDocumentFactSpecification;
1186
- /**
1187
- * Accepted application governed-document facts **only a human may establish** — a creator decision
1188
- * or a qualified review (`document-facts-authored`).
1189
- *
1190
- * The same shape as the slot above, and a separate family on purpose. `refinement.document-facts`
1191
- * rewrites the derived file whole, so a human decision sharing that file is destroyed on the next
1192
- * run with nothing to notice: there is no compare-and-swap here, deliberately
1193
- * (`.claude/rules/one-source-of-truth.md` Rule 0). Two families put the two writers out of each
1194
- * other's reach.
1195
- *
1196
- * No producer may write this family — it has no generation contract, and that absence is the design
1197
- * rather than an omission.
1198
- *
1199
- * A reader wanting "the application's facts" needs BOTH slots. `collectComplianceDocumentFactAvailability`
1200
- * is variadic for exactly that reason.
1201
- */
1202
- authoredDocumentFactSpecification?: TAuthoredDocumentFactSpecification;
1203
- /**
1204
- * WHO else processes this application's personal data — legal identity, processing region and the
1205
- * processor's own subprocessors (issue #88).
1206
- *
1207
- * A configured provider already establishes THAT a third party is involved and what function it
1208
- * performs. None of that is what a privacy notice's recipient statement needs, and an
1209
- * international-transfer statement cannot be made at all without a region.
1210
- *
1211
- * Optional, and its holes are reported rather than blocking: the companion compares this register
1212
- * against the application's CONFIGURED providers and names each one that is undeclared, so a partial
1213
- * register is useful and an empty one still produces an actionable document. An absent entry means
1214
- * nobody has established that processor's identity — never that the provider is unused.
1215
- */
1216
- processorRegister?: TProcessorRegister;
1217
1161
  /**
1218
1162
  * Accepted application-declared semantic causality between whole
1219
1163
  * specification-family states. This is not the registry's physical
@@ -212,7 +212,6 @@ export const specificationsCompanionExports: SpecificationsCompanionExports<
212
212
  * decisions remain private runtime state.
213
213
  */
214
214
  documentFactSpecification: applicationDocumentFactSpecification,
215
- authoredDocumentFactSpecification: applicationAuthoredDocumentFactSpecification,
216
215
  /**
217
216
  * The accepted typed build plan (`build-plan` family, `BuildPlanTaskGraph`).
218
217
  * The bottom-up dispatch playbook's coding owner reads it from the verified
@@ -68,7 +68,6 @@ export interface SpecificationsCompanionExports<
68
68
  TRequirementsSnapshot = RequirementsSnapshot,
69
69
  TRoadmapSnapshot = RoadmapSnapshot,
70
70
  TBuildPlanTaskGraph = BuildPlanTaskGraph,
71
- TPlacementPlan = PlacementPlan,
72
71
  TDomainPlanOutputSet = DomainPlanOutputSet,
73
72
  TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
74
73
  // Appended STRICTLY LAST (positional generics — never insert mid-list):
@@ -96,14 +95,6 @@ export interface SpecificationsCompanionExports<
96
95
  // Appended STRICTLY LAST: release-process selection is a separate accepted
97
96
  // decision, never an implicit default of routing or document necessity.
98
97
  TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
99
- // Appended STRICTLY LAST: WHO else processes personal data, under what legal
100
- // identity and where (issue #88). Optional, and the optionality is the design:
101
- // a partial register is useful and its holes are REPORTED per provider against
102
- // the application's configured set, rather than blocking anything.
103
- TProcessorRegister = ApplicationProcessorRegister,
104
- // Appended STRICTLY LAST: the human half of the document facts, in its own
105
- // family, because the derived one is REGENERATED whole (#192).
106
- TAuthoredDocumentFactSpecification = ApplicationAuthoredDocumentFactSpecification,
107
98
  > {
108
99
  resourceSpecifications: TResourceSpecifications;
109
100
  applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
@@ -334,22 +325,6 @@ export interface SpecificationsCompanionExports<
334
325
  * `validateBuildPlanTaskGraph` on the value before wiring it here.
335
326
  */
336
327
  buildPlanSpecification?: TBuildPlanTaskGraph;
337
- /**
338
- * Application **placement** specification — WHERE every settings destination,
339
- * resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
340
- * `_core/placement-plan/`).
341
- *
342
- * Produced by the `bottom_up.placement-plan` playbook as an expert-panel
343
- * DELIBERATION rather than a creator elicitation: the creator does not choose
344
- * placement, so each decision carries a `rationale` that answers "why is this
345
- * here?" without re-running the panel. Consumed by build-decompose, which
346
- * turns it into the coding tasks that author `settings-hub.config.ts` and
347
- * `app-shell.config.ts`.
348
- *
349
- * Optional until an application reaches the bottom-up phase; app bootstraps
350
- * should run `validatePlacementPlan` on the value before wiring it here.
351
- */
352
- placementPlanSpecification?: TPlacementPlan;
353
328
  /**
354
329
  * Application **domain-plan** specification — the atomic module decomposition
355
330
  * PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
@@ -488,37 +463,6 @@ export interface SpecificationsCompanionExports<
488
463
  * Omitting it is honest: unresolved document facts remain visible gaps.
489
464
  */
490
465
  documentFactSpecification?: TDocumentFactSpecification;
491
- /**
492
- * Accepted application governed-document facts **only a human may establish** — a creator decision
493
- * or a qualified review (`document-facts-authored`).
494
- *
495
- * The same shape as the slot above, and a separate family on purpose. `refinement.document-facts`
496
- * rewrites the derived file whole, so a human decision sharing that file is destroyed on the next
497
- * run with nothing to notice: there is no compare-and-swap here, deliberately
498
- * (`.claude/rules/one-source-of-truth.md` Rule 0). Two families put the two writers out of each
499
- * other's reach.
500
- *
501
- * No producer may write this family — it has no generation contract, and that absence is the design
502
- * rather than an omission.
503
- *
504
- * A reader wanting "the application's facts" needs BOTH slots. `collectComplianceDocumentFactAvailability`
505
- * is variadic for exactly that reason.
506
- */
507
- authoredDocumentFactSpecification?: TAuthoredDocumentFactSpecification;
508
- /**
509
- * WHO else processes this application's personal data — legal identity, processing region and the
510
- * processor's own subprocessors (issue #88).
511
- *
512
- * A configured provider already establishes THAT a third party is involved and what function it
513
- * performs. None of that is what a privacy notice's recipient statement needs, and an
514
- * international-transfer statement cannot be made at all without a region.
515
- *
516
- * Optional, and its holes are reported rather than blocking: the companion compares this register
517
- * against the application's CONFIGURED providers and names each one that is undeclared, so a partial
518
- * register is useful and an empty one still produces an actionable document. An absent entry means
519
- * nobody has established that processor's identity — never that the provider is unused.
520
- */
521
- processorRegister?: TProcessorRegister;
522
466
  /**
523
467
  * Accepted application-declared semantic causality between whole
524
468
  * specification-family states. This is not the registry's physical
@@ -38,7 +38,7 @@ Locate the surfaces that may need editing using these app-relative globs:
38
38
  | Frontend UI behavior | `frontend/src/modules/*/resources/*/*.ui-behavior.tsx` |
39
39
  | Specification | `specifications/src/modules/*/resources/*.resource.specification.ts` |
40
40
  | Backend (rare) | `backend-api/src/modules/*/resources/*/*.resource-handlers.ts` |
41
- | i18n labels | `frontend/src/i18n/**/*.json` (list the keys currently needed: `wildo context info frontend-labels-needed-info`) |
41
+ | i18n labels | `frontend/src/i18n/**/*.json` (or whatever `wildo context` writes for the project) |
42
42
 
43
43
  If the project diverges from this layout, find the resource by grepping
44
44
  for the `R.<RESOURCE>` enum value or for the existing field's
@@ -172,8 +172,8 @@ Minimum label impact:
172
172
  - `<resource>.<fieldName>.label`
173
173
  - `<resource>.<fieldName>.<enumValue>` for each enum value
174
174
 
175
- Use the existing project placement pattern; `wildo context info frontend-labels-needed-info`
176
- lists the label keys the frontend currently needs, with their placement metadata.
175
+ Use the existing project placement pattern or the future `wildo context` i18n
176
+ commands when they are available.
177
177
 
178
178
  ### Re-run Translation When Text Changes
179
179