@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,4 +1,4 @@
1
- # Market Analysis — the umbrella
1
+ # Market Analysis — Produce Method (v1 scaffold)
2
2
 
3
3
  ### Target Application Framing
4
4
 
@@ -12,53 +12,167 @@ Read and apply these patterns from the application-developer point of view:
12
12
  - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
13
 
14
14
 
15
- This playbook produces nothing itself. It coordinates three children and the market
16
- snapshot is landed by one of them.
17
-
18
- ## The children, and why the order is not written here
19
-
20
- - **`top_down.market-research`** gathers evidence from the public web and returns a
21
- condensed, source-attributed brief. Read-only: it can fetch and search, and it
22
- cannot write anything.
23
- - **`top_down.market-evidence-adequacy`** reads that evidence and answers one
24
- question — is this enough to derive a snapshot from? — returning a verdict and, when
25
- it is not, the specific gaps.
26
- - **`top_down.market-snapshot-produce`** derives and lands the `market-snapshot`
27
- family. It becomes eligible only once the gate has returned `adequate`.
28
-
29
- Nothing above is a sequence. Each child declares what it needs, and the runtime
30
- re-computes what may run after every round. Research needs only the vision. The gate
31
- needs research to have returned. Produce needs the gate to have returned `adequate` —
32
- not merely to have run.
33
-
34
- That is what makes the loop a loop: when the gate says `insufficient`, produce simply
35
- stays ineligible, research stays available, and the sensible next move is another
36
- research round **aimed at the gaps the gate named**. Nobody wrote "if insufficient,
37
- go back" anywhere; it falls out of the preconditions.
38
-
39
- ## Composing an objective for a child
40
-
41
- Each dispatch carries an objective composed for that round. This is the part that is
42
- invented rather than authored, and it is where the value is:
43
-
44
- - The **first** research round should be broad — the category, who competes, what they
45
- charge, how buyers talk.
46
- - A **later** round should be narrow and should name the gap: *"the first round found
47
- no published pricing for the two mid-market competitors; find it, or establish that
48
- it is quote-only."* Repeating the first objective produces the first answer again.
49
- - Where a round can be **split**, split it. Four lanes asking about category,
50
- competitors, pricing and buyer language separately return more than one lane asked
51
- everything at once — each returns a condensation, and the breadth is the point.
52
-
53
- ## When to stop
54
-
55
- Stop when the snapshot has landed. Stop also when the gate has named the same gap
56
- twice and the second round could not close it — that gap is not going to be closed by
57
- a third attempt, and a snapshot marked honestly incomplete is worth more than a loop
58
- that spends its ceiling. Say which, in your rationale.
59
-
60
- ## What the creator reviews
61
-
62
- The landed `market-snapshot`, exactly as before — it still passes the deterministic
63
- `market-snapshot-valid` gate, and the creator still approves the result. What changed
64
- is only that its claims now rest on pages someone read.
15
+ > **This is a v1 scaffold methodology.** It is a working first cut meant to
16
+ > be iterated. The authoring order, research posture, and the "produce vs.
17
+ > refine" rules below are deliberately explicit so they can be tuned against
18
+ > real runs — treat them as a starting rubric, not a frozen contract. The
19
+ > *analytical depth* of the market work (research rigor, competitive
20
+ > teardown, quantified FIT/Kano scoring) is intentionally shallow here and is
21
+ > deepened in a later phase; do not perfect it in this playbook.
22
+
23
+ ## What this playbook does
24
+
25
+ You are the **market analyst**. Your one job is to produce — or refine an
26
+ existing — **MarketSnapshot** for this product: the single artifact that
27
+ declares *who the product is for*, *what they are trying to get done*, and
28
+ *how the product is positioned* to them. You reason top-down from the
29
+ product idea (there is no code yet in this phase); you do not model the
30
+ domain, author resources, or write features — later playbooks consume your
31
+ snapshot to do that.
32
+
33
+ A MarketSnapshot is assembled from these slices, each owned by a dedicated
34
+ `market_*` app-knowledge skill (see References). You author them in
35
+ dependency order because later slices reference earlier refs:
36
+
37
+ 1. **Category** — the one market category the product competes in, plus the
38
+ rejected adjacent categories. (`market-category`)
39
+ 2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic
40
+ segments the product is sold to. (`market-icp`)
41
+ 3. **Personas** — the human roles inside each ICP, including buying-group
42
+ members. Every ICP needs at least one persona. (`market-persona`)
43
+ 4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for
44
+ the personas: what they are trying to do, what blocks them, what a win
45
+ looks like. (`market-jobs-pains-gains`)
46
+ 5. **Tones of voice** — the named brand voices the product speaks in.
47
+ (`market-tone-of-voice`)
48
+ 6. **Benefits** — the outcome claims the product delivers, weighted against
49
+ the pains/gains they relieve/create. (`market-add-feature-benefit`)
50
+ 7. **Positionings** — the per-ICP marketing-truth promise. Author one per
51
+ ICP that the product actually targets. (`market-positioning-authoring`)
52
+ 8. **Reach surfaces** — the go-to-market context: channels, competing
53
+ alternatives, buying triggers + per-ICP buying journeys, proofs, and the
54
+ objections proofs answer. (`market-channels`, `market-alternatives`,
55
+ `market-triggers-and-journey`, `market-proof-and-objection`)
56
+ 9. **Message templates** — reusable prompt templates that render from the
57
+ snapshot above. Author last; they reference the earlier slices.
58
+ (`market-message-templates-authoring`)
59
+
60
+ Author only the slices the product's stage warrants — a first pass may stop
61
+ after positionings and leave the phase-3/4 reach surfaces empty (they
62
+ default to `[]`). A snapshot with a category, at least one ICP, its
63
+ personas, the jobs/pains/gains triplet, and at least one positioning is a
64
+ legitimate v1; the reach surfaces and message templates are additive.
65
+
66
+ ## Where the snapshot lives
67
+
68
+ The MarketSnapshot for this journey is placed under
69
+ `.wildo-saas/journey/<journeyId>/market-snapshot/`. That is the artifact this
70
+ playbook owns and the rest of the top-down phase reads. When the product's
71
+ definition later stabilises, the snapshot is what seeds the durable market
72
+ specification under `./specifications/` — but at this phase it is a journey
73
+ artifact, not yet app source.
74
+
75
+ ## Produce vs. refine — read state first
76
+
77
+ This playbook is **idempotent** on the journey's market artifact. Before
78
+ authoring anything:
79
+
80
+ 1. Read the current journey state and scope through the `journey-status`
81
+ skill (it owns the read; do not re-derive it here) — that tells you which
82
+ scope the snapshot must be complete *for*.
83
+ 2. Check whether a MarketSnapshot already exists for this journey by reading
84
+ the artifact at this playbook's own placement path,
85
+ `.wildo-saas/journey/<journeyId>/market-snapshot/`. Its presence or
86
+ absence selects the mode below.
87
+
88
+ - **No snapshot yet** — produce a fresh one, authoring the slices in the
89
+ order above.
90
+ - **A snapshot exists** — *refine* it: read every slice, keep what still
91
+ holds, and only add/correct the slices the current steering notes or new
92
+ research call for. Never silently discard authored refs — a downstream
93
+ positioning or benefit may depend on an ICP or persona ref, and dropping
94
+ it orphans them (the validator will catch this, but honest refinement
95
+ should not create the orphan in the first place).
96
+
97
+ ## Research posture (scaffold depth)
98
+
99
+ Ground each slice in evidence, not invention. At this scaffold depth the
100
+ research is whatever the executing agent can gather about the product's
101
+ category, competitors, and buyers; capture the *shape* faithfully (real
102
+ category, real competing alternatives, plausible ICPs and personas) rather
103
+ than aspirational fiction. Where you are inferring rather than citing, say so
104
+ in the slice's authored prose so a later, deeper research pass can tighten
105
+ it. Do **not** build a research pipeline or block on external tooling here —
106
+ richer web-research capability is a later-phase concern; this playbook
107
+ consumes whatever the agent already knows plus the creator's steering.
108
+
109
+ ## Quality gate
110
+
111
+ Your emitted snapshot is checked by the deterministic `market-snapshot-valid`
112
+ gate (`validateMarketSnapshot`) before anything downstream consumes it. It
113
+ enforces the cross-slice invariants — orphan refs (a positioning naming a
114
+ missing ICP, a benefit naming a missing pain/gain), an ICP with no persona,
115
+ influence cycles, duplicate edges, proofs without support, message-template
116
+ placeholder mismatches, and more. Duplicate or malformed refs and
117
+ `ERROR`-severity issues are hard failures; the snapshot does not advance
118
+ until they clear. `WARN`-severity issues (e.g. stale-authored, a missing
119
+ positioning for a targeted ICP) do not block but should be resolved. Read
120
+ `market-snapshot-validation` for the full issue catalogue and emit a clean
121
+ snapshot the first time.
122
+
123
+ ## Scaffold-depth boundary (deferred to a later depth phase)
124
+
125
+ Keep this playbook at scaffold depth. The following are explicitly **out of
126
+ scope here** and are deepened in the methodology-depth phase, not now:
127
+
128
+ - **Deep competitive teardown** — the reach surfaces capture *that* an
129
+ alternative exists and *why* a buyer might pick it; a quantified,
130
+ feature-by-feature competitor matrix is later-phase work.
131
+ - **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads
132
+ the deterministic FIT scorer; at scaffold depth you consume it to sanity-
133
+ check benefit weighting, not to drive a precise prioritization model. The
134
+ prioritization seam stays pluggable (see the capability-map playbook).
135
+ - **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are
136
+ authored as framing, not as a sized, sourced market model.
137
+
138
+ If you find yourself perfecting any of the above, stop and leave the slice at
139
+ scaffold depth — depth is a dedicated later pass done once, holistically.
140
+
141
+ ## What you emit
142
+
143
+ A single MarketSnapshot at `.wildo-saas/journey/<journeyId>/market-snapshot/`,
144
+ assembled from the slices above via their `market_*` skills, passing the
145
+ `market-snapshot-valid` gate. The creator reviews the result (approval posture
146
+ `approve_result`) before it is accepted as the journey's market intent.
147
+
148
+ ## References
149
+
150
+ - `.claude/skills/journey-status/SKILL.md` — read the current journey state
151
+ and scope before authoring.
152
+ - `.claude/skills/market-authoring-overview/SKILL.md` — the orchestrator for
153
+ the whole market slice; read it first to see how the slices fit together.
154
+ - `.claude/skills/market-category/SKILL.md` — author the singular market
155
+ category.
156
+ - `.claude/skills/market-icp/SKILL.md` — author the Ideal Customer Profiles.
157
+ - `.claude/skills/market-persona/SKILL.md` — author the personas per ICP.
158
+ - `.claude/skills/market-jobs-pains-gains/SKILL.md` — author the Strategyzer
159
+ jobs/pains/gains triplet.
160
+ - `.claude/skills/market-tone-of-voice/SKILL.md` — author the named brand
161
+ voices.
162
+ - `.claude/skills/market-add-feature-benefit/SKILL.md` — author the benefit
163
+ claims and their pain/gain weighting.
164
+ - `.claude/skills/market-positioning-authoring/SKILL.md` — author the per-ICP
165
+ positioning promise.
166
+ - `.claude/skills/market-channels/SKILL.md` — author the reach channels.
167
+ - `.claude/skills/market-alternatives/SKILL.md` — author the competing
168
+ alternatives.
169
+ - `.claude/skills/market-triggers-and-journey/SKILL.md` — author buying
170
+ triggers and per-ICP buying journeys.
171
+ - `.claude/skills/market-proof-and-objection/SKILL.md` — author proofs and
172
+ the objections they answer.
173
+ - `.claude/skills/market-message-templates-authoring/SKILL.md` — author the
174
+ reusable message templates (last).
175
+ - `.claude/skills/market-scoring-interpretation/SKILL.md` — interpret the
176
+ deterministic FIT scorer to sanity-check benefit weighting.
177
+ - `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation
178
+ issue catalogue the quality gate enforces.
@@ -1,10 +1,14 @@
1
1
  {
2
2
  "ref": "top_down.market-analysis",
3
- "version": "0.2.0",
3
+ "version": "0.1.0",
4
4
  "phase": "top_down",
5
- "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.",
5
+ "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.",
6
6
  "functionalTopics": [],
7
7
  "preconditions": [
8
+ {
9
+ "kind": "phase_is",
10
+ "phase": "top_down"
11
+ },
8
12
  {
9
13
  "kind": "artifact_valid",
10
14
  "selector": {
@@ -17,31 +21,47 @@
17
21
  "family": "vision-brief"
18
22
  }
19
23
  ],
20
- "outputs": [],
21
- "stepOutputs": [],
24
+ "outputs": [
25
+ {
26
+ "family": "market-snapshot",
27
+ "schemaRef": "saas-specifications:MarketSnapshot",
28
+ "placement": ".wildo-saas/journey/<journeyId>/market-snapshot/",
29
+ "description": "The assembled market category, ICP, persona, jobs/pains/gains, benefit, positioning and reach graph validated by validateMarketSnapshot."
30
+ }
31
+ ],
22
32
  "method": {
23
- "guidance": "# Market Analysis — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It coordinates three children and the market\nsnapshot is landed by one of them.\n\n## The children, and why the order is not written here\n\n- **`top_down.market-research`** gathers evidence from the public web and returns a\n condensed, source-attributed brief. Read-only: it can fetch and search, and it\n cannot write anything.\n- **`top_down.market-evidence-adequacy`** reads that evidence and answers one\n question — is this enough to derive a snapshot from? — returning a verdict and, when\n it is not, the specific gaps.\n- **`top_down.market-snapshot-produce`** derives and lands the `market-snapshot`\n family. It becomes eligible only once the gate has returned `adequate`.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. Research needs only the vision. The gate\nneeds research to have returned. Produce needs the gate to have returned `adequate` —\nnot merely to have run.\n\nThat is what makes the loop a loop: when the gate says `insufficient`, produce simply\nstays ineligible, research stays available, and the sensible next move is another\nresearch round **aimed at the gaps the gate named**. Nobody wrote \"if insufficient,\ngo back\" anywhere; it falls out of the preconditions.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. This is the part that is\ninvented rather than authored, and it is where the value is:\n\n- The **first** research round should be broad — the category, who competes, what they\n charge, how buyers talk.\n- A **later** round should be narrow and should name the gap: *\"the first round found\n no published pricing for the two mid-market competitors; find it, or establish that\n it is quote-only.\"* Repeating the first objective produces the first answer again.\n- Where a round can be **split**, split it. Four lanes asking about category,\n competitors, pricing and buyer language separately return more than one lane asked\n everything at once — each returns a condensation, and the breadth is the point.\n\n## When to stop\n\nStop when the snapshot has landed. Stop also when the gate has named the same gap\ntwice and the second round could not close it — that gap is not going to be closed by\na third attempt, and a snapshot marked honestly incomplete is worth more than a loop\nthat spends its ceiling. Say which, in your rationale.\n\n## What the creator reviews\n\nThe landed `market-snapshot`, exactly as before — it still passes the deterministic\n`market-snapshot-valid` gate, and the creator still approves the result. What changed\nis only that its claims now rest on pages someone read.\n",
33
+ "guidance": "# Market Analysis — Produce Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The authoring order, research posture, and the \"produce vs.\n> refine\" rules below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of the market work (research rigor, competitive\n> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **market analyst**. Your one job is to produce — or refine an\nexisting — **MarketSnapshot** for this product: the single artifact that\ndeclares *who the product is for*, *what they are trying to get done*, and\n*how the product is positioned* to them. You reason top-down from the\nproduct idea (there is no code yet in this phase); you do not model the\ndomain, author resources, or write features — later playbooks consume your\nsnapshot to do that.\n\nA MarketSnapshot is assembled from these slices, each owned by a dedicated\n`market_*` app-knowledge skill (see References). You author them in\ndependency order because later slices reference earlier refs:\n\n1. **Category** — the one market category the product competes in, plus the\n rejected adjacent categories. (`market-category`)\n2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic\n segments the product is sold to. (`market-icp`)\n3. **Personas** — the human roles inside each ICP, including buying-group\n members. Every ICP needs at least one persona. (`market-persona`)\n4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for\n the personas: what they are trying to do, what blocks them, what a win\n looks like. (`market-jobs-pains-gains`)\n5. **Tones of voice** — the named brand voices the product speaks in.\n (`market-tone-of-voice`)\n6. **Benefits** — the outcome claims the product delivers, weighted against\n the pains/gains they relieve/create. (`market-add-feature-benefit`)\n7. **Positionings** — the per-ICP marketing-truth promise. Author one per\n ICP that the product actually targets. (`market-positioning-authoring`)\n8. **Reach surfaces** — the go-to-market context: channels, competing\n alternatives, buying triggers + per-ICP buying journeys, proofs, and the\n objections proofs answer. (`market-channels`, `market-alternatives`,\n `market-triggers-and-journey`, `market-proof-and-objection`)\n9. **Message templates** — reusable prompt templates that render from the\n snapshot above. Author last; they reference the earlier slices.\n (`market-message-templates-authoring`)\n\nAuthor only the slices the product's stage warrants — a first pass may stop\nafter positionings and leave the phase-3/4 reach surfaces empty (they\ndefault to `[]`). A snapshot with a category, at least one ICP, its\npersonas, the jobs/pains/gains triplet, and at least one positioning is a\nlegitimate v1; the reach surfaces and message templates are additive.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is placed under\n`.wildo-saas/journey/<journeyId>/market-snapshot/`. That is the artifact this\nplaybook owns and the rest of the top-down phase reads. When the product's\ndefinition later stabilises, the snapshot is what seeds the durable market\nspecification under `./specifications/` — but at this phase it is a journey\nartifact, not yet app source.\n\n## Produce vs. refine — read state first\n\nThis playbook is **idempotent** on the journey's market artifact. Before\nauthoring anything:\n\n1. Read the current journey state and scope through the `journey-status`\n skill (it owns the read; do not re-derive it here) — that tells you which\n scope the snapshot must be complete *for*.\n2. Check whether a MarketSnapshot already exists for this journey by reading\n the artifact at this playbook's own placement path,\n `.wildo-saas/journey/<journeyId>/market-snapshot/`. Its presence or\n absence selects the mode below.\n\n- **No snapshot yet** — produce a fresh one, authoring the slices in the\n order above.\n- **A snapshot exists** — *refine* it: read every slice, keep what still\n holds, and only add/correct the slices the current steering notes or new\n research call for. Never silently discard authored refs — a downstream\n positioning or benefit may depend on an ICP or persona ref, and dropping\n it orphans them (the validator will catch this, but honest refinement\n should not create the orphan in the first place).\n\n## Research posture (scaffold depth)\n\nGround each slice in evidence, not invention. At this scaffold depth the\nresearch is whatever the executing agent can gather about the product's\ncategory, competitors, and buyers; capture the *shape* faithfully (real\ncategory, real competing alternatives, plausible ICPs and personas) rather\nthan aspirational fiction. Where you are inferring rather than citing, say so\nin the slice's authored prose so a later, deeper research pass can tighten\nit. Do **not** build a research pipeline or block on external tooling here —\nricher web-research capability is a later-phase concern; this playbook\nconsumes whatever the agent already knows plus the creator's steering.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. It\nenforces the cross-slice invariants — orphan refs (a positioning naming a\nmissing ICP, a benefit naming a missing pain/gain), an ICP with no persona,\ninfluence cycles, duplicate edges, proofs without support, message-template\nplaceholder mismatches, and more. Duplicate or malformed refs and\n`ERROR`-severity issues are hard failures; the snapshot does not advance\nuntil they clear. `WARN`-severity issues (e.g. stale-authored, a missing\npositioning for a targeted ICP) do not block but should be resolved. Read\n`market-snapshot-validation` for the full issue catalogue and emit a clean\nsnapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Deep competitive teardown** — the reach surfaces capture *that* an\n alternative exists and *why* a buyer might pick it; a quantified,\n feature-by-feature competitor matrix is later-phase work.\n- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads\n the deterministic FIT scorer; at scaffold depth you consume it to sanity-\n check benefit weighting, not to drive a precise prioritization model. The\n prioritization seam stays pluggable (see the capability-map playbook).\n- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are\n authored as framing, not as a sized, sourced market model.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nA single MarketSnapshot at `.wildo-saas/journey/<journeyId>/market-snapshot/`,\nassembled from the slices above via their `market_*` skills, passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's market intent.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state\n and scope before authoring.\n- `.claude/skills/market-authoring-overview/SKILL.md` — the orchestrator for\n the whole market slice; read it first to see how the slices fit together.\n- `.claude/skills/market-category/SKILL.md` — author the singular market\n category.\n- `.claude/skills/market-icp/SKILL.md` — author the Ideal Customer Profiles.\n- `.claude/skills/market-persona/SKILL.md` — author the personas per ICP.\n- `.claude/skills/market-jobs-pains-gains/SKILL.md` — author the Strategyzer\n jobs/pains/gains triplet.\n- `.claude/skills/market-tone-of-voice/SKILL.md` — author the named brand\n voices.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author the benefit\n claims and their pain/gain weighting.\n- `.claude/skills/market-positioning-authoring/SKILL.md` — author the per-ICP\n positioning promise.\n- `.claude/skills/market-channels/SKILL.md` — author the reach channels.\n- `.claude/skills/market-alternatives/SKILL.md` — author the competing\n alternatives.\n- `.claude/skills/market-triggers-and-journey/SKILL.md` — author buying\n triggers and per-ICP buying journeys.\n- `.claude/skills/market-proof-and-objection/SKILL.md` — author proofs and\n the objections they answer.\n- `.claude/skills/market-message-templates-authoring/SKILL.md` — author the\n reusable message templates (last).\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting.\n- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation\n issue catalogue the quality gate enforces.\n",
24
34
  "skillRefs": [
25
35
  "journey-status",
26
- "market-authoring-overview"
27
- ],
28
- "contextSources": [],
29
- "choreography": {
30
- "admits": [
31
- "top_down.market-snapshot-produce",
32
- "top_down.market-research",
33
- "top_down.market-evidence-adequacy"
34
- ],
35
- "maximumIterations": 10,
36
- "maximumLanesPerIteration": 3,
37
- "maximumDepth": 1,
38
- "maximumDurationMs": 2400000
39
- },
40
- "suspendsForClarification": false,
41
- "briefAdequacyGate": false,
42
- "briefAdequacyExcludedSources": []
36
+ "market-authoring-overview",
37
+ "market-category",
38
+ "market-icp",
39
+ "market-persona",
40
+ "market-jobs-pains-gains",
41
+ "market-tone-of-voice",
42
+ "market-add-feature-benefit",
43
+ "market-positioning-authoring",
44
+ "market-channels",
45
+ "market-alternatives",
46
+ "market-triggers-and-journey",
47
+ "market-proof-and-objection",
48
+ "market-message-templates-authoring",
49
+ "market-scoring-interpretation",
50
+ "market-snapshot-validation"
51
+ ]
43
52
  },
53
+ "executor": "companion_agent",
54
+ "qualityGates": [
55
+ {
56
+ "ref": "market-snapshot-valid",
57
+ "kind": "deterministic_validator",
58
+ "validatorRef": "saas-specifications:validateMarketSnapshot",
59
+ "required": true
60
+ }
61
+ ],
44
62
  "approval": "approve_result",
45
- "budget": {},
63
+ "budget": {
64
+ "maxRuns": 3
65
+ },
46
66
  "onFailure": "keep_and_flag"
47
67
  }
@@ -30,12 +30,9 @@ Two distinct layers must remain visible:
30
30
  structurally and semantically valid on its own. The phase gate is ineligible
31
31
  while `vision-brief`, `market-snapshot`, `requirements`, or `roadmap` is not
32
32
  valid. This floor is non-bypassable.
33
- 2. The compiled Evaluation Protocol interprets cross-family coherence from the
34
- landed input families as they stand in the working tree, beside the COMPUTED
35
- coherence report (the declared `coherence_report` context section of your brief — the dangling-reference
36
- and coverage arithmetic is derived exactly and handed in, never re-derived by
37
- the evaluator). It cannot make an invalid family valid or replace missing evidence
38
- with an assumption.
33
+ 2. The compiled Evaluation Protocol interprets cross-family coherence from an
34
+ exact sealed evidence set. It cannot make an invalid family valid or replace
35
+ missing evidence with an assumption.
39
36
 
40
37
  The canonical criterion instructions, evidence identities, verdict guidance,
41
38
  prompt-assembly strategy, and aggregation precedence live in
@@ -64,8 +61,7 @@ without prose-only inference.
64
61
 
65
62
  ## Evaluation
66
63
 
67
- The evaluator receives the compiled protocol, the landed input families, and the
68
- computed coherence report.
64
+ The evaluator receives the compiled protocol and the exact sealed evidence set.
69
65
  It must emit one of `PASS`, `CONCERN`, `GAP`, or `INDETERMINATE` for every
70
66
  criterion, cite the evidence used, and state limitations.
71
67
 
@@ -5,6 +5,10 @@
5
5
  "intent": "Assess whether the validated top-down definition set is cross-artifact coherent enough for the current horizon. Deterministic family validation remains a non-bypassable eligibility floor; this playbook contributes a sealed semantic evaluation and never mutates application truth.",
6
6
  "functionalTopics": [],
7
7
  "preconditions": [
8
+ {
9
+ "kind": "phase_is",
10
+ "phase": "top_down"
11
+ },
8
12
  {
9
13
  "kind": "artifact_valid",
10
14
  "selector": {
@@ -51,22 +55,16 @@
51
55
  }
52
56
  ],
53
57
  "outputs": [],
54
- "stepOutputs": [],
55
58
  "method": {
56
- "guidance": "# Top-Down Phase Gate\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Purpose\n\nThis playbook assesses whether the accepted top-down definition set is coherent\nenough for the current horizon. It authors no application specification and\ndoes not mutate application truth.\n\nThe assessment is incremental and re-runnable. A later change to market,\napplication-feature, requirements, vision, or roadmap state may invalidate\nearlier evidence and make the decision point eligible again.\n\n## Trust structure\n\nTwo distinct layers must remain visible:\n\n1. The deterministic family-validity floor proves that each required family is\n structurally and semantically valid on its own. The phase gate is ineligible\n while `vision-brief`, `market-snapshot`, `requirements`, or `roadmap` is not\n valid. This floor is non-bypassable.\n2. The compiled Evaluation Protocol interprets cross-family coherence from the\n landed input families as they stand in the working tree, beside the COMPUTED\n coherence report (the declared `coherence_report` context section of your brief — the dangling-reference\n and coverage arithmetic is derived exactly and handed in, never re-derived by\n the evaluator). It cannot make an invalid family valid or replace missing evidence\n with an assumption.\n\nThe canonical criterion instructions, evidence identities, verdict guidance,\nprompt-assembly strategy, and aggregation precedence live in\n`playbook.definition.ts`. This method explains how to operate the treatment; it\ndoes not duplicate that executable meaning.\n\n## Evidence preparation\n\nUse `journey-status` to identify the current accepted heads for:\n\n- `vision-brief`\n- `market-snapshot`\n- `requirements`\n- `roadmap`\n- `feature-drafts`\n\nProject only the accepted, current-horizon data required by the five protocol\ncriteria. Seal the projected artifacts and their provenance before evaluation.\nIf the evidence projection cannot account for a mandatory requirement, request\nevidence; do not invoke the evaluator on an incomplete set.\n\nBusiness model is not an input to this treatment version and must not be loaded\ninto its knowledge projection. A later treatment version may add a distinct\nbusiness-model criterion when the structured family contracts can support it\nwithout prose-only inference.\n\n## Evaluation\n\nThe evaluator receives the compiled protocol, the landed input families, and the\ncomputed coherence report.\nIt must emit one of `PASS`, `CONCERN`, `GAP`, or `INDETERMINATE` for every\ncriterion, cite the evidence used, and state limitations.\n\nAggregation uses the protocol’s declared worst-verdict precedence:\n\n`GAP` → `INDETERMINATE` → `CONCERN` → `PASS`\n\n`INDETERMINATE` means that the available evidence is missing, conflicting, or\ntoo uncertain to decide. A transport, model, timeout, or output-validation\nfailure is an evaluator failure and blocks the treatment; it is never rewritten\nas semantic uncertainty.\n\n## Continuation\n\n- `PASS` may continue to the next treatment boundary.\n- `CONCERN` and `GAP` route to revision.\n- `INDETERMINATE` requests additional evidence.\n- a hard-floor failure or evaluator failure blocks.\n\nThis slice deliberately does not activate a runtime evaluator or authority\nmembrane. Human authorization of the top-down → bottom-up transition remains a\nseparate, explicit boundary and must not be inferred from a passing semantic\nassessment. Use `journey-report` to surface the assessment and\n`journey-approve` only when the authority workflow is active.\n\n## Idempotency and bounded work\n\nThe treatment is read-only and safe to repeat against the same accepted heads.\nThe playbook budget limits attempts, evidence requests, and revisions so the\nsystem can reach “good enough for the current horizon” rather than optimizing\nindefinitely. A changed accepted head creates new evidence and therefore a new\nassessment basis.\n",
59
+ "guidance": "# Top-Down Phase Gate\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## Purpose\n\nThis playbook assesses whether the accepted top-down definition set is coherent\nenough for the current horizon. It authors no application specification and\ndoes not mutate application truth.\n\nThe assessment is incremental and re-runnable. A later change to market,\napplication-feature, requirements, vision, or roadmap state may invalidate\nearlier evidence and make the decision point eligible again.\n\n## Trust structure\n\nTwo distinct layers must remain visible:\n\n1. The deterministic family-validity floor proves that each required family is\n structurally and semantically valid on its own. The phase gate is ineligible\n while `vision-brief`, `market-snapshot`, `requirements`, or `roadmap` is not\n valid. This floor is non-bypassable.\n2. The compiled Evaluation Protocol interprets cross-family coherence from an\n exact sealed evidence set. It cannot make an invalid family valid or replace\n missing evidence with an assumption.\n\nThe canonical criterion instructions, evidence identities, verdict guidance,\nprompt-assembly strategy, and aggregation precedence live in\n`playbook.definition.ts`. This method explains how to operate the treatment; it\ndoes not duplicate that executable meaning.\n\n## Evidence preparation\n\nUse `journey-status` to identify the current accepted heads for:\n\n- `vision-brief`\n- `market-snapshot`\n- `requirements`\n- `roadmap`\n- `feature-drafts`\n\nProject only the accepted, current-horizon data required by the five protocol\ncriteria. Seal the projected artifacts and their provenance before evaluation.\nIf the evidence projection cannot account for a mandatory requirement, request\nevidence; do not invoke the evaluator on an incomplete set.\n\nBusiness model is not an input to this treatment version and must not be loaded\ninto its knowledge projection. A later treatment version may add a distinct\nbusiness-model criterion when the structured family contracts can support it\nwithout prose-only inference.\n\n## Evaluation\n\nThe evaluator receives the compiled protocol and the exact sealed evidence set.\nIt must emit one of `PASS`, `CONCERN`, `GAP`, or `INDETERMINATE` for every\ncriterion, cite the evidence used, and state limitations.\n\nAggregation uses the protocol’s declared worst-verdict precedence:\n\n`GAP` → `INDETERMINATE` → `CONCERN` → `PASS`\n\n`INDETERMINATE` means that the available evidence is missing, conflicting, or\ntoo uncertain to decide. A transport, model, timeout, or output-validation\nfailure is an evaluator failure and blocks the treatment; it is never rewritten\nas semantic uncertainty.\n\n## Continuation\n\n- `PASS` may continue to the next treatment boundary.\n- `CONCERN` and `GAP` route to revision.\n- `INDETERMINATE` requests additional evidence.\n- a hard-floor failure or evaluator failure blocks.\n\nThis slice deliberately does not activate a runtime evaluator or authority\nmembrane. Human authorization of the top-down → bottom-up transition remains a\nseparate, explicit boundary and must not be inferred from a passing semantic\nassessment. Use `journey-report` to surface the assessment and\n`journey-approve` only when the authority workflow is active.\n\n## Idempotency and bounded work\n\nThe treatment is read-only and safe to repeat against the same accepted heads.\nThe playbook budget limits attempts, evidence requests, and revisions so the\nsystem can reach “good enough for the current horizon” rather than optimizing\nindefinitely. A changed accepted head creates new evidence and therefore a new\nassessment basis.\n",
57
60
  "skillRefs": [
58
61
  "journey-status",
59
62
  "journey-report",
60
63
  "journey-approve"
61
- ],
62
- "contextSources": [
63
- "coherence_report"
64
- ],
65
- "suspendsForClarification": false,
66
- "briefAdequacyGate": false,
67
- "briefAdequacyExcludedSources": []
64
+ ]
68
65
  },
69
66
  "executor": "companion_agent",
67
+ "qualityGates": [],
70
68
  "approval": "approve_result",
71
69
  "budget": {
72
70
  "maxRuns": 3
@@ -44,12 +44,10 @@ The deterministic minimum-content finding and semantic coherence evaluation are
44
44
  separate contributions. Application composition selects exactly one bounded
45
45
  next action from hard floors, scoped risk, maturity, uncertainty, active
46
46
  resource authority and playbook bounds. A model may explain a proposal but it
47
- cannot override a hard floor or rewrite accepted truth: it writes files into the
48
- working tree and nothing more. Acceptance is a human git commit, so a run leaves
49
- working edits for a person to read and decide on, and protected consequences
50
- still request an operator decision before the run proceeds.
51
-
52
- Git is not a later materialization of an acceptance that happened somewhere else
53
- — it IS the acceptance. Replacing accepted application requirements therefore
54
- means committing over them, with the commit's author and instant standing as who
55
- accepted and when.
47
+ cannot override a hard floor, choose acceptance authority, or mutate accepted
48
+ truth. Under the declared `EXCEPTION_ONLY` supervision posture, an ordinary
49
+ eligible result can be policy-accepted only after the acceptance coordinator
50
+ revalidates its candidate, evaluation, basis, guards and policy revision.
51
+ Protected consequences still request an operator decision. Only the retained
52
+ semantic-delta/CAS landing owner may replace accepted application requirements;
53
+ later Git materialization remains a separate effect.
@@ -5,6 +5,10 @@
5
5
  "intent": "Derive a validated, current-horizon requirements snapshot from accepted vision and market truth. The provider proposes strict semantic content; the trusted runtime stamps family refs/version and keeps provenance, scope, evidence and authority outside model output.",
6
6
  "functionalTopics": [],
7
7
  "preconditions": [
8
+ {
9
+ "kind": "phase_is",
10
+ "phase": "top_down"
11
+ },
8
12
  {
9
13
  "kind": "artifact_valid",
10
14
  "selector": {
@@ -31,22 +35,26 @@
31
35
  {
32
36
  "family": "requirements",
33
37
  "schemaRef": "saas-specifications:RequirementsSnapshot",
38
+ "placement": ".wildo-saas/journey/<journeyId>/requirements/",
34
39
  "description": "The persisted RequirementsSnapshot normalized from strict RequirementsSnapshotGeneration output. It contains at least one functional requirement unless a separately sealed, evidence-bound exceptional disposition has settled authority."
35
40
  }
36
41
  ],
37
- "stepOutputs": [],
38
42
  "method": {
39
- "guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads. Treat those accepted projections as\nthe only application truth: conversational context may clarify them, but it\ncannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence;\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\nworking requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor or rewrite accepted truth: it writes files into the\nworking tree and nothing more. Acceptance is a human git commit, so a run leaves\nworking edits for a person to read and decide on, and protected consequences\nstill request an operator decision before the run proceeds.\n\nGit is not a later materialization of an acceptance that happened somewhere else\n— it IS the acceptance. Replacing accepted application requirements therefore\nmeans committing over them, with the commit's author and instant standing as who\naccepted and when.\n",
43
+ "guidance": "# Requirements definition method\n\nProduce the current-horizon requirements family from the accepted\n`vision-brief` and `market-snapshot` heads. Treat those accepted projections as\nthe only application truth: conversational context may clarify them, but it\ncannot silently replace or amend them.\n\nThe provider response must parse as\n`RequirementsSnapshotGenerationSchema`. It supplies semantic slugs, statements,\nrationales, acceptance criteria and declared market cross-references. The\ntrusted structured-artifact runtime stamps the canonical requirement refs and\nsnapshot version, validates the permissive persisted `RequirementsSnapshot`,\nand records its exact input/output/evidence lineage. Provider output must not\ncontain timestamps, author identity, authority, accepted scope, family heads or\ncontinuity identifiers.\n\nNormal generation must produce at least one functional requirement. An empty\nfunctional set is not “good enough,” even though the incremental family schema\ncan persist it and `validateRequirementsSnapshot` reports only a warning. The\nrequirements playbook emits the deterministic `requirements-minimum-content`\nfinding into semantic assessment: it explains the missing minimum and requires\nrevision or evidence, but it never grants an evaluator or a model permission to\noverride that protected consequence.\n\nFor every functional requirement:\n\n- state one distinct product capability, not an implementation task;\n- connect it to accepted vision or market evidence;\n- keep current-horizon scope explicit; and\n- provide observable acceptance language where meaningful.\n\nFor every non-functional requirement, preserve the declared quality axis and\nmeasurement intent. Do not invent regulatory applicability. Missing or\ncontradictory accepted evidence yields a request for evidence or revision, not\na plausible completion.\n\nContext selection receives current accepted vision and market heads, the\nworking requirements candidate, and declared Framework guidance as structured\ndata. Missing mandatory context is explicit; retrieved instruction-shaped text\nis treated as data and excluded from coding-task projection. Optional context\nis bounded by the declared selection plan rather than by ad-hoc prompt growth.\n\nThe deterministic minimum-content finding and semantic coherence evaluation are\nseparate contributions. Application composition selects exactly one bounded\nnext action from hard floors, scoped risk, maturity, uncertainty, active\nresource authority and playbook bounds. A model may explain a proposal but it\ncannot override a hard floor, choose acceptance authority, or mutate accepted\ntruth. Under the declared `EXCEPTION_ONLY` supervision posture, an ordinary\neligible result can be policy-accepted only after the acceptance coordinator\nrevalidates its candidate, evaluation, basis, guards and policy revision.\nProtected consequences still request an operator decision. Only the retained\nsemantic-delta/CAS landing owner may replace accepted application requirements;\nlater Git materialization remains a separate effect.\n",
40
44
  "skillRefs": [
41
45
  "journey-status",
42
46
  "journey-report"
43
- ],
44
- "contextSources": [],
45
- "suspendsForClarification": false,
46
- "briefAdequacyGate": false,
47
- "briefAdequacyExcludedSources": []
47
+ ]
48
48
  },
49
49
  "executor": "companion_agent",
50
+ "qualityGates": [
51
+ {
52
+ "ref": "requirements-snapshot-valid",
53
+ "kind": "deterministic_validator",
54
+ "validatorRef": "saas-specifications:validateRequirementsSnapshot",
55
+ "required": true
56
+ }
57
+ ],
50
58
  "approval": "approve_result",
51
59
  "budget": {
52
60
  "maxInputTokens": 15000000,
@@ -84,8 +84,8 @@ planning anything:
84
84
  **VisionSnapshot** (`vision-brief` — the success criteria to deliver and the
85
85
  differentiation that anchors what belongs in the MVP).
86
86
 
87
- (A previously landed roadmap arrives in your brief as the `roadmap` input section — refine those
88
- phases rather than re-cutting them blind.)
87
+ // TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)
88
+ // TODO CLI COMMAND: wildo context roadmap (read any existing phases to refine)
89
89
 
90
90
  You **read** `market-snapshot` + `feature-drafts` + `requirements` +
91
91
  `vision-brief`; you **write** the `roadmap` family.
@@ -265,7 +265,7 @@ scaffold depth — depth is a dedicated later pass done once, holistically.
265
265
  ## What you emit
266
266
 
267
267
  One artifact for this journey: the **roadmap** at
268
- `specifications/src/roadmap/index.ts` — a `RoadmapSnapshot` whose `phases`
268
+ `.wildo-saas/journey/<journeyId>/roadmap/` — a `RoadmapSnapshot` whose `phases`
269
269
  are the ordered, MVP-first releases, each with a distinct `sequence`, a coarse
270
270
  `horizon` + `kind`, and its `deliversRequirementRefs` / `deliversSuccessCriterionRefs`
271
271
  wired — passing the `roadmap-valid` gate.