@wildo-ai/framework-knowledge 1.1.2 → 1.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (287) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +228 -6
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
  6. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  8. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -4
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -4
  13. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +4 -4
  15. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -1
  17. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
  19. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -1
  21. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
  23. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +1 -2
  25. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -2
  27. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -3
  29. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +3 -3
  31. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -2
  33. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
  35. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -1
  37. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +0 -1
  39. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +0 -1
  41. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +0 -1
  43. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +0 -1
  45. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +0 -1
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -1
  49. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  50. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
  51. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  52. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +0 -1
  53. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
  55. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  56. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +0 -2
  57. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +2 -2
  59. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  60. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +0 -1
  61. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +0 -1
  63. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -1
  65. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +0 -1
  67. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
  69. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +0 -1
  71. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -1
  73. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +0 -1
  75. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
  77. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -4
  79. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
  81. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
  83. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
  85. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
  87. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -1
  89. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  91. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +0 -1
  93. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
  95. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  96. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +0 -1
  97. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
  99. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  100. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +0 -1
  101. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +0 -1
  103. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  104. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
  105. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  107. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -1
  109. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +0 -1
  111. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  112. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  113. package/dist/knowledge/manifest.json +8 -9
  114. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
  115. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
  116. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
  117. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
  118. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
  119. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
  120. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
  121. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
  122. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
  123. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
  124. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
  125. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
  126. package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
  127. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
  128. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
  129. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
  130. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
  131. package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
  132. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
  133. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
  134. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
  135. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
  136. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
  137. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
  138. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
  139. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
  140. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
  141. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
  142. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
  143. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
  144. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
  145. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
  146. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
  147. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
  148. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
  149. package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
  150. package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
  151. package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
  152. package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
  153. package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
  154. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
  155. package/dist/knowledge/references/platform.config.saas.md +0 -51
  156. package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
  157. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
  158. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
  159. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
  160. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
  161. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
  162. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
  163. package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
  164. package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
  165. package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
  166. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
  167. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
  168. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
  169. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
  170. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
  171. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
  172. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
  173. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
  174. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
  175. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
  176. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
  177. package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
  178. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
  179. package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
  180. package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
  181. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
  182. package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
  183. package/dist/knowledge/registries/framework-topics.json +11 -146
  184. package/dist/knowledge/registries/playbooks.json +18 -154
  185. package/dist/knowledge/registries/source-tags.json +630 -883
  186. package/dist/knowledge/skills/INDEX.md +3 -4
  187. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
  188. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
  189. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
  190. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
  191. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
  192. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
  193. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
  194. package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
  195. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
  196. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
  197. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
  198. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
  199. package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
  200. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
  201. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
  202. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
  203. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
  204. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
  205. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
  206. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
  207. package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
  208. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
  209. package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
  210. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -213
  211. package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
  212. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
  213. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
  214. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
  215. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
  216. package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
  217. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
  218. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
  219. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
  220. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
  221. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
  222. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
  223. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
  224. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
  225. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
  226. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
  227. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
  228. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
  229. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
  230. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
  231. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
  232. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
  233. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
  234. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
  235. package/dist/knowledge/topic-index.json +220 -725
  236. package/dist/tsconfig.build.tsbuildinfo +1 -1
  237. package/dist/tsconfig.tsbuildinfo +1 -1
  238. package/package.json +4 -4
  239. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
  240. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
  241. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
  242. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
  243. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
  244. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
  245. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
  246. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
  247. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
  248. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
  249. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
  250. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
  251. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
  252. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
  253. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
  254. package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
  255. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
  256. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
  257. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
  258. package/dist/knowledge/references/placement-plan.config.md +0 -330
  259. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
  260. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
  261. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
  262. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
  263. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
  264. package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
  265. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
  266. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
  267. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
  268. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
  269. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
  270. package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
  271. package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
  272. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
  273. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
  274. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
  275. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
  276. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
  277. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
  278. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
  279. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
  280. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
  281. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
  282. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
  283. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
  284. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
  285. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
  286. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
  287. /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
@@ -1,34 +1,16 @@
1
1
  {
2
2
  "name": "playbooks",
3
3
  "metadata": {
4
- "generatedAt": "2026-09-05T12:54:53.265Z",
4
+ "generatedAt": "2026-08-29T22:33:33.791Z",
5
5
  "description": "Compiled meta-workflow playbooks (app-creation methodology definitions)."
6
6
  },
7
7
  "entries": {
8
- "bottom_up.assemble-verify": {
9
- "ref": "bottom_up.assemble-verify",
10
- "version": "0.2.0",
11
- "phase": "bottom_up",
12
- "executor": "deterministic_cli",
13
- "intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over the application's four workspace packages (specifications, shared-lib, backend-api, frontend) OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty for v0.2: the check set is the whole-application TYPECHECK across the four packages — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated. A boot probe, the whole test suite, `wildo config validate` and OpenAPI/docs regeneration are NOT in this set: each needs a running stack or a companion affordance that does not exist, and declaring them here without running them is exactly what made the deleted version of this playbook inert.",
14
- "functionalTopics": [
15
- "assemble_verify_and_iterate"
16
- ],
17
- "skillRefs": [
18
- "journey-status",
19
- "journey-report",
20
- "journey-approve"
21
- ],
22
- "playbookFilePath": "playbooks/bottom_up.assemble-verify/playbook.json",
23
- "methodFilePath": "playbooks/bottom_up.assemble-verify/method.md",
24
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
25
- },
26
8
  "bottom_up.build-decompose": {
27
9
  "ref": "bottom_up.build-decompose",
28
- "version": "0.2.0",
10
+ "version": "0.1.0",
29
11
  "phase": "bottom_up",
30
12
  "executor": "companion_agent",
31
- "intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (labels / i18n, email templates, seeds) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / single-flight-lock / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. v1 scaffold methodology — a typed build-task-graph contract, a dependency-DAG solver, and a collection validator are a later depth phase, not here.",
13
+ "intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (labels / i18n, email templates, seeds) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / single-flight-lock / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. v1 scaffold methodology — a typed build-task-graph contract, a dependency-DAG solver, and a collection validator are a later depth phase, not here.",
32
14
  "functionalTopics": [],
33
15
  "skillRefs": [
34
16
  "journey-status",
@@ -49,7 +31,7 @@
49
31
  "ref": "bottom_up.build-dispatch",
50
32
  "version": "0.1.0",
51
33
  "phase": "bottom_up",
52
- "executor": "coding_agent",
34
+ "executor": "composite",
53
35
  "intent": "Bottom-up build dispatch — the SECOND build-execution playbook, the pivot from DECOMPOSING the build (the build-plan task graph) to DISPATCHING it: turning one ordered task into an actually-run, verified coding-agent run under the D4 dispatch contract. Reads the approved TYPED build-plan (`BuildPlanTaskGraph` — each task carries a closed target kind, ONE MetaWorkflow_FunctionalTopic, its skill refs, and DECLARED prerequisite task refs) and the current journey state, selects the NEXT READY task (`selectReadyBuildPlanTasks`: every declared prerequisite has landed — resolved by the host, never inferred from prose; SINGLE-FLIGHT — exactly ONE workspace-mutating run at a time), and dispatches exactly that typed task: (1) the runner builds the context pack (task brief + the task's skill pointers + the relevant journey/definition artifacts + introspected app reality + repo paths); (2) it runs ONE prompt turn against the coding agent over the Agent Client Protocol, in a session rooted at the app workspace (cwd = app root, so CLAUDE.md / .claude skills load naturally), answering the agent's permission requests within the execution profile's declared ceiling and refusing anything above it or outside the task's mutation scope; (3) it captures the change-set around the run (git baseline/post-run worktree snapshots → per-file attribution → a structured GitChangeSetCapture recorded on the task row); (4) it runs the VERIFY gate OUTSIDE the coding agent (a deterministic typecheck the runner maps onto the dispatch verification hook — pnpm exec tsc --noEmit — the trust-but-verify floor); (5) it records the result + applies the onFailure disposition (keep_and_flag: a failed/timed-out run keeps its captured change-set flagged for human triage, never a silent half-applied state). Then loop to the next ready task. This playbook PRODUCES the per-task dispatch contract + execution semantics; it authors no schemas and generates no code (the coding agent does that at dispatch time). It does NOT decompose the plan (that is the build-decompose playbook, upstream — it owns the task graph) and does NOT solve multi-agent SCALE — parallelism across several coding agents, the concurrency schedule, and interleaving the companion generation steps at scale are the downstream scale playbook. v1 scaffold: the single-flight dispatch contract; multi-agent parallelism, a run-completion serializer, and a revert_changeset failure path are later phases (revert is a MUTATING git op outside the read-only change-set carve-out, deliberately deferred).",
54
36
  "functionalTopics": [],
55
37
  "skillRefs": [
@@ -76,7 +58,7 @@
76
58
  "ref": "bottom_up.build-scale",
77
59
  "version": "0.1.0",
78
60
  "phase": "bottom_up",
79
- "executor": "coding_agent",
61
+ "executor": "composite",
80
62
  "intent": "Bottom-up build scale — the THIRD and final build-execution playbook, the pivot from dispatching ONE task safely (the single-flight dispatch contract) to running the build at SCALE: parallelism across several coding agents, the concurrency schedule, and interleaving the companion-owned generation steps concurrently with coding runs. Reads the approved build-plan (the ordered coding-agent task graph, each task carrying a target, ONE MetaWorkflow_FunctionalTopic, its skill(s), and prose prerequisite ordering) and the current journey state, and answers the SCALE questions the single-flight dispatch playbook deliberately left open: (1) derive the ready-SET (a wave / frontier of tasks whose prose prerequisites have ALL SUCCEEDED — not merely been attempted); (2) decide the parallelism degree (how many coding agents run at once) and the worktree-isolation model that keeps each concurrent run's change-set cleanly attributable; (3) schedule the waves respecting the DEPENDS_ON ordering the build-plan encodes; (4) interleave the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) concurrently with coding runs at the points their inputs exist — those steps run through their deterministic companion endpoints, NOT the coding-agent single-flight lock, so they genuinely overlap coding runs; (5) reconcile wave completion across the concurrent runs (all tasks in the frontier SUCCEEDED before the next wave opens) and apply onFailure across siblings + downstream. Then advance to the next wave and loop. Each parallel slot INVOKES the single-flight dispatch contract (the build-dispatch playbook, upstream — select-next / context-pack / one ACP prompt turn / change-set capture / verify-outside / record + onFailure); this playbook does NOT re-specify those per-task mechanics and does NOT re-decompose the plan (the build-decompose playbook owns the task graph) and authors no schemas / no code. IMPORTANT HONESTY: the companion runner HARD-ENFORCES single-flight today (a run plan carries at most ONE coding-agent task; a concurrent dispatch is refused; the workspace-mutation lock + the lock-free cursor + the missing run-outcome observation loop all assume one dispatch at a time). So this v1 scale METHOD is the DECLARATIVE TARGET a runner-serializer slice will realize — on the current runner the waves DEGRADE to sequential single-flight dispatch. And even the deterministic companion-generation steps, though they do not take the coding single-flight lock, cannot SAFELY overlap an active coding run today: the coding run's change-set is captured as a whole-worktree time-window diff, so a generation step writing files inside that window is misattributed to the coding run (the same whole-worktree pollution that forbids two concurrent coding agents) — so the generation steps also serialize outside an active coding-capture window today, and genuine concurrency (coding-parallel OR generation-overlap) both arrive only with the git worktree-per-agent isolation runner task. v1 scaffold: a multi-CODING_AGENT run-completion serializer, git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock are companion-runner mechanism filed as runner tasks, NOT built here; a priority/work-stealing scheduler and cost-optimal packing are a later depth phase.",
81
63
  "functionalTopics": [],
82
64
  "skillRefs": [
@@ -127,6 +109,7 @@
127
109
  "ref": "bottom_up.foundation",
128
110
  "version": "0.2.0",
129
111
  "phase": "bottom_up",
112
+ "executor": "composite",
130
113
  "intent": "Bottom-up foundation — turn the approved domain plan + the top-down definition set into a configured, bootable application skeleton. Reads the domain-plan (the module decomposition + per-module resource inventory) and the vision-brief (whose compliance/vision constraints drive which engine capabilities to enable), then: (1) authors ./wildo.saas.config.ts for real — the engine capabilities (derived from compliance/vision), the modules (from the domain plan), and the providers (matched to the declared capabilities); (2) materializes the app skeleton (app/ shared-lib/ backend-api/ specifications/ + the module registries); (3) installs app-knowledge; (4) runs the deterministic bring-up — wildo setup --non-interactive, then wildo local init. This is a v1 SCAFFOLD METHOD describing the foundation SEQUENCE: skeleton materialization and app-knowledge installation remain deferred greenfield tooling, while headless setup and verified local initialization are registered commands once the app structure exists. It emits NO artifact: the deliverable is the app itself (the authored config + materialized skeleton + verified initialization), and the reasons behind each capability/module/provider choice are recorded as comments in the config the next reader opens. The foundation-manifest family it used to emit was retired 2026-08-25 with the app-creation verification/digest aspect. Runs after the domain plan is approved and the journey is in the bottom_up phase.",
131
114
  "functionalTopics": [
132
115
  "configure_application_foundation"
@@ -142,28 +125,9 @@
142
125
  "methodFilePath": "playbooks/bottom_up.foundation/method.md",
143
126
  "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
144
127
  },
145
- "bottom_up.placement-plan": {
146
- "ref": "bottom_up.placement-plan",
147
- "version": "0.1.0",
148
- "phase": "bottom_up",
149
- "executor": "companion_agent",
150
- "intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
151
- "functionalTopics": [
152
- "shape_user_experience"
153
- ],
154
- "skillRefs": [
155
- "settings-placement-authoring",
156
- "config-app-shell",
157
- "config-navigation",
158
- "journey-status"
159
- ],
160
- "playbookFilePath": "playbooks/bottom_up.placement-plan/playbook.json",
161
- "methodFilePath": "playbooks/bottom_up.placement-plan/method.md",
162
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
163
- },
164
128
  "refinement.compliance-document-candidate": {
165
129
  "ref": "refinement.compliance-document-candidate",
166
- "version": "0.2.0",
130
+ "version": "0.1.0",
167
131
  "phase": "refinement",
168
132
  "executor": "companion_agent",
169
133
  "intent": "Propose structured privacy-notice or service-terms candidate content from the application's accepted document facts. The companion agent may draft prose but cannot invent a fact, decide a legal question, approve, release or publish the document: every clause it writes is checked against the `document-facts` family, and a clause asserting a fact the application never declared is refused before it becomes a file.",
@@ -191,7 +155,7 @@
191
155
  },
192
156
  "top_down.brand-identity": {
193
157
  "ref": "top_down.brand-identity",
194
- "version": "0.1.1",
158
+ "version": "0.1.0",
195
159
  "phase": "top_down",
196
160
  "executor": "companion_agent",
197
161
  "intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name, the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
@@ -266,53 +230,12 @@
266
230
  "filePath": "playbooks/top_down.capability-map/structured-artifact-action.json"
267
231
  }
268
232
  },
269
- "top_down.compliance-analysis": {
270
- "ref": "top_down.compliance-analysis",
271
- "version": "0.1.3",
272
- "phase": "top_down",
273
- "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.",
274
- "functionalTopics": [],
275
- "skillRefs": [
276
- "journey-status"
277
- ],
278
- "playbookFilePath": "playbooks/top_down.compliance-analysis/playbook.json",
279
- "methodFilePath": "playbooks/top_down.compliance-analysis/method.md",
280
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
281
- },
282
- "top_down.compliance-conception": {
283
- "ref": "top_down.compliance-conception",
284
- "version": "0.1.0",
285
- "phase": "top_down",
286
- "executor": "companion_agent",
287
- "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.",
288
- "functionalTopics": [],
289
- "skillRefs": [
290
- "journey-status"
291
- ],
292
- "playbookFilePath": "playbooks/top_down.compliance-conception/playbook.json",
293
- "methodFilePath": "playbooks/top_down.compliance-conception/method.md",
294
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
295
- },
296
- "top_down.compliance-evidence-adequacy": {
297
- "ref": "top_down.compliance-evidence-adequacy",
298
- "version": "0.1.1",
299
- "phase": "top_down",
300
- "executor": "companion_agent",
301
- "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.",
302
- "functionalTopics": [],
303
- "skillRefs": [
304
- "journey-status"
305
- ],
306
- "playbookFilePath": "playbooks/top_down.compliance-evidence-adequacy/playbook.json",
307
- "methodFilePath": "playbooks/top_down.compliance-evidence-adequacy/method.md",
308
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
309
- },
310
233
  "top_down.compliance-posture": {
311
234
  "ref": "top_down.compliance-posture",
312
- "version": "0.2.1",
235
+ "version": "0.1.0",
313
236
  "phase": "top_down",
314
237
  "executor": "companion_agent",
315
- "intent": "Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric. Its regimes used to be derived from nine interview answers plus a model's recollection; it now runs as the artifact-producing child of the `top_down.compliance-analysis` composite, only once an adequacy gate has read the gathered regime evidence and returned ADEQUATE.",
238
+ "intent": "Compliance-posture pass: a focused elicitation that determines which legal, regulatory, contractual and external-assurance regimes the product operates under by reasoning over its jurisdictions, the classes of data it handles, its sector and customer commitments — and records each applicable regime as a `compliance`-kind constraint (prose statement) on the product's VisionSnapshot (the `vision-brief` artifact family). This SHARPENS the compliance seam the vision-elicitation step named in passing; it does NOT re-elicit the whole vision. SCAFFOLD depth: compliance stays PROSE constraints here — the deep per-regime obligation model (control catalogs, data-residency matrices, obligation graphs) is a deferred later concern, not built here. v1 scaffold methodology — iterate the regime-derivation rubric.",
316
239
  "functionalTopics": [],
317
240
  "skillRefs": [
318
241
  "journey-status"
@@ -321,71 +244,12 @@
321
244
  "methodFilePath": "playbooks/top_down.compliance-posture/method.md",
322
245
  "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
323
246
  },
324
- "top_down.compliance-research": {
325
- "ref": "top_down.compliance-research",
326
- "version": "0.1.0",
327
- "phase": "top_down",
328
- "executor": "research_agent",
329
- "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.",
330
- "functionalTopics": [],
331
- "skillRefs": [
332
- "journey-status"
333
- ],
334
- "playbookFilePath": "playbooks/top_down.compliance-research/playbook.json",
335
- "methodFilePath": "playbooks/top_down.compliance-research/method.md",
336
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
337
- },
338
247
  "top_down.market-analysis": {
339
248
  "ref": "top_down.market-analysis",
340
- "version": "0.2.0",
341
- "phase": "top_down",
342
- "intent": "Produce the market snapshot by gathering EVIDENCE, judging whether it is enough, and deriving the snapshot 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.",
343
- "functionalTopics": [],
344
- "skillRefs": [
345
- "journey-status",
346
- "market-authoring-overview"
347
- ],
348
- "playbookFilePath": "playbooks/top_down.market-analysis/playbook.json",
349
- "methodFilePath": "playbooks/top_down.market-analysis/method.md",
350
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
351
- },
352
- "top_down.market-evidence-adequacy": {
353
- "ref": "top_down.market-evidence-adequacy",
354
249
  "version": "0.1.0",
355
250
  "phase": "top_down",
356
251
  "executor": "companion_agent",
357
- "intent": "Judge whether the evidence gathered so far is ENOUGH to derive a market snapshot 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.",
358
- "functionalTopics": [],
359
- "skillRefs": [
360
- "journey-status",
361
- "market-snapshot-validation"
362
- ],
363
- "playbookFilePath": "playbooks/top_down.market-evidence-adequacy/playbook.json",
364
- "methodFilePath": "playbooks/top_down.market-evidence-adequacy/method.md",
365
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
366
- },
367
- "top_down.market-research": {
368
- "ref": "top_down.market-research",
369
- "version": "0.1.0",
370
- "phase": "top_down",
371
- "executor": "research_agent",
372
- "intent": "Gather EVIDENCE about the product's market from the public web — the category as it is actually named, who sells into it, what they charge, and what buyers say — and return a condensed, source-attributed brief. 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.",
373
- "functionalTopics": [],
374
- "skillRefs": [
375
- "journey-status",
376
- "market-category",
377
- "market-alternatives"
378
- ],
379
- "playbookFilePath": "playbooks/top_down.market-research/playbook.json",
380
- "methodFilePath": "playbooks/top_down.market-research/method.md",
381
- "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1"
382
- },
383
- "top_down.market-snapshot-produce": {
384
- "ref": "top_down.market-snapshot-produce",
385
- "version": "0.1.0",
386
- "phase": "top_down",
387
- "executor": "companion_agent",
388
- "intent": "Derive a validated market snapshot from the vision and from the EVIDENCE a sibling research step gathered — the artifact-producing child of the `top_down.market-analysis` composite. The provider proposes the market graph; the trusted runtime stamps entity refs/version and keeps provenance, authority and accepted-family mutation outside model output. Its intent used to claim derivation from \"sealed research evidence\" while nothing supplied any; it now runs only once an adequacy gate has read the evidence and returned ADEQUATE.",
252
+ "intent": "Derive a validated market snapshot from accepted vision truth and sealed research evidence. The provider proposes the market graph; the trusted runtime stamps entity refs/version and keeps provenance, authority and accepted-family mutation outside model output.",
389
253
  "functionalTopics": [],
390
254
  "skillRefs": [
391
255
  "journey-status",
@@ -405,23 +269,23 @@
405
269
  "market-scoring-interpretation",
406
270
  "market-snapshot-validation"
407
271
  ],
408
- "playbookFilePath": "playbooks/top_down.market-snapshot-produce/playbook.json",
409
- "methodFilePath": "playbooks/top_down.market-snapshot-produce/method.md",
272
+ "playbookFilePath": "playbooks/top_down.market-analysis/playbook.json",
273
+ "methodFilePath": "playbooks/top_down.market-analysis/method.md",
410
274
  "sourceFormat": "EFFECT_FREE_TYPESCRIPT_MODULE_V1",
411
275
  "evaluationProtocol": {
412
276
  "protocolRef": "application-creation:evaluation-protocol/market-analysis",
413
277
  "protocolVersion": 1,
414
- "filePath": "playbooks/top_down.market-snapshot-produce/evaluation-protocol.json"
278
+ "filePath": "playbooks/top_down.market-analysis/evaluation-protocol.json"
415
279
  },
416
280
  "evaluationTreatment": {
417
281
  "definitionRef": "application-creation:evaluation-treatment/market-analysis",
418
282
  "definitionVersion": 1,
419
- "filePath": "playbooks/top_down.market-snapshot-produce/evaluation-treatment.json"
283
+ "filePath": "playbooks/top_down.market-analysis/evaluation-treatment.json"
420
284
  },
421
285
  "structuredArtifactAction": {
422
286
  "definitionRef": "application-creation:structured-artifact-action/market-analysis",
423
287
  "definitionVersion": 1,
424
- "filePath": "playbooks/top_down.market-snapshot-produce/structured-artifact-action.json"
288
+ "filePath": "playbooks/top_down.market-analysis/structured-artifact-action.json"
425
289
  }
426
290
  },
427
291
  "top_down.phase-gate": {
@@ -482,7 +346,7 @@
482
346
  },
483
347
  "top_down.scope-roadmap": {
484
348
  "ref": "top_down.scope-roadmap",
485
- "version": "0.1.1",
349
+ "version": "0.1.0",
486
350
  "phase": "top_down",
487
351
  "executor": "companion_agent",
488
352
  "intent": "Turn the accepted capability map into a non-vacuous current-horizon RoadmapSnapshot. Phases explicitly sequence and group accepted requirements and vision success criteria without pretending that FIT is build-order authority or inventing unsupported delivery commitments.",
@@ -530,7 +394,7 @@
530
394
  },
531
395
  "top_down.vision-elicitation": {
532
396
  "ref": "top_down.vision-elicitation",
533
- "version": "0.1.1",
397
+ "version": "0.1.0",
534
398
  "phase": "top_down",
535
399
  "executor": "companion_agent",
536
400
  "intent": "Elicit a complete current-horizon product vision from sealed creator input and application context. The provider proposes semantic content; the trusted runtime stamps refs/version and keeps provenance, authority and accepted-family mutation outside model output.",