@wildo-ai/framework-knowledge 1.1.2 → 1.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (289) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +351 -18
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  6. package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
  7. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  8. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  9. package/dist/esm/index.d.ts.map +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -4
  13. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -4
  15. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +4 -4
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -1
  19. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -1
  23. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
  25. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +1 -2
  27. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -2
  29. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -3
  31. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +3 -3
  33. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -2
  35. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
  37. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  38. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -1
  39. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  40. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +0 -1
  41. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +0 -1
  43. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +0 -1
  45. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +0 -1
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +0 -1
  49. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -1
  51. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
  53. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +0 -1
  55. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
  57. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +0 -2
  59. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +2 -2
  61. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +0 -1
  63. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +0 -1
  65. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -1
  67. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +0 -1
  69. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  70. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
  71. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +0 -1
  73. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -1
  75. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +0 -1
  77. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  78. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
  79. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -4
  81. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  82. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
  83. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
  85. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
  87. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  88. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
  89. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  90. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -1
  91. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  93. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +0 -1
  95. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
  97. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +0 -1
  99. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
  101. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +0 -1
  103. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +0 -1
  105. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
  107. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  108. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  109. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  110. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -1
  111. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +0 -1
  113. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  114. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  115. package/dist/knowledge/manifest.json +8 -9
  116. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
  117. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
  118. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
  119. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
  120. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
  121. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
  122. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
  123. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
  124. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
  125. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
  126. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
  127. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
  128. package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
  129. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
  130. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
  131. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
  132. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
  133. package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
  134. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
  135. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
  136. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
  137. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
  138. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
  139. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
  140. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
  141. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
  142. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
  143. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
  144. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
  145. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
  146. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
  147. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
  148. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
  149. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
  150. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
  151. package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
  152. package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
  153. package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
  154. package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
  155. package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
  156. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
  157. package/dist/knowledge/references/platform.config.saas.md +0 -51
  158. package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
  159. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
  160. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
  161. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
  162. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
  163. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
  164. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
  165. package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
  166. package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
  167. package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
  168. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
  169. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
  170. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
  171. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
  172. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
  173. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
  174. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
  175. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
  176. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
  177. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
  178. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
  179. package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
  180. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
  181. package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
  182. package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
  183. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
  184. package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
  185. package/dist/knowledge/registries/framework-topics.json +11 -146
  186. package/dist/knowledge/registries/playbooks.json +18 -154
  187. package/dist/knowledge/registries/source-tags.json +630 -883
  188. package/dist/knowledge/skills/INDEX.md +3 -4
  189. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
  190. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
  191. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
  192. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
  193. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
  194. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
  195. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
  196. package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
  197. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
  198. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
  199. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
  200. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
  201. package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
  202. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
  203. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
  204. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
  205. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
  206. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
  207. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
  208. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
  209. package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
  210. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
  211. package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
  212. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -213
  213. package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
  214. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
  215. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
  216. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
  217. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
  218. package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
  219. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
  220. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
  221. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
  222. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
  223. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
  224. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
  225. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
  226. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
  227. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
  228. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
  229. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
  230. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
  231. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
  232. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
  233. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
  234. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
  235. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
  236. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
  237. package/dist/knowledge/topic-index.json +220 -725
  238. package/dist/tsconfig.build.tsbuildinfo +1 -1
  239. package/dist/tsconfig.tsbuildinfo +1 -1
  240. package/package.json +4 -4
  241. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
  242. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
  243. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
  244. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
  245. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
  246. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
  247. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
  248. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
  249. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
  250. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
  251. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
  252. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
  253. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
  254. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
  255. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
  256. package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
  257. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
  258. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
  259. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
  260. package/dist/knowledge/references/placement-plan.config.md +0 -330
  261. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
  262. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
  263. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
  264. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
  265. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
  266. package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
  267. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
  268. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
  269. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
  270. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
  271. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
  272. package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
  273. package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
  274. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
  275. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
  276. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
  277. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
  278. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
  279. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
  280. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
  281. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
  282. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
  283. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
  284. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
  285. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
  286. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
  287. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
  288. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
  289. /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
@@ -1,42 +0,0 @@
1
- {
2
- "ref": "top_down.market-evidence-adequacy",
3
- "version": "0.1.0",
4
- "phase": "top_down",
5
- "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.",
6
- "functionalTopics": [],
7
- "preconditions": [
8
- {
9
- "kind": "step_available",
10
- "ref": "market-evidence"
11
- }
12
- ],
13
- "inputs": [
14
- {
15
- "family": "vision-brief"
16
- }
17
- ],
18
- "outputs": [],
19
- "stepOutputs": [
20
- {
21
- "ref": "evidence-adequacy",
22
- "schemaRef": "saas-specifications:MetaWorkflow_EvidenceAdequacy",
23
- "condensation": "A verdict, the gaps that produced it, and a rationale grounded in what was actually gathered.",
24
- "description": "The adequacy gate the produce step is conditioned on."
25
- }
26
- ],
27
- "method": {
28
- "guidance": "# Evidence Adequacy — is this enough to derive from?\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou are the **gate**. You judge whether the evidence gathered so far is enough to\nderive a market snapshot from — and when it is not, you say precisely what is missing.\n\n## The question you answer\n\nNot \"is this good research?\" and not \"is this market attractive?\". Only:\n\n> **Could a competent analyst write a defensible market snapshot from what is here,\n> without inventing anything?**\n\nIf yes, the verdict is `adequate`. If no, it is `insufficient`, and your `gaps` are\nwhat the next research round will be aimed at.\n\n## What makes evidence adequate\n\n- **The category is named by a source**, not assumed.\n- **At least a few real competing alternatives**, each with something concrete about\n what it costs or how it is sold. \"There are competitors\" is not evidence.\n- **Buyer language observed rather than imagined** — at least some of how the people\n with this problem describe it.\n- **Claims carry sources**, and the unsourced ones are marked as such.\n\n## What makes it insufficient, and how to say so\n\nName the GAP, not the feeling. `\"no pricing found for any competitor\"` sends the next\nround somewhere; `\"the evidence is thin\"` sends it nowhere and it comes back the same.\n\nEach gap should be answerable. If a gap is genuinely unanswerable from the public web\n— private pricing, a market nobody writes about — say that in the rationale rather\nthan emitting a gap that will fail again. A loop that keeps asking for something that\ndoes not exist is worse than a snapshot honestly marked incomplete.\n\n## Be willing to say ADEQUATE\n\nThe failure mode of a gate is not being too lenient. It is holding out for completeness\nthat no public source can provide, so the loop spends its rounds and stops on a ceiling\nwith nothing produced. Enough is enough; perfect is not the bar.\n\n## What you do not do\n\nYou author nothing, you land nothing, and you do not write the snapshot. Your verdict\nis read by the step that does.\n",
29
- "skillRefs": [
30
- "journey-status",
31
- "market-snapshot-validation"
32
- ],
33
- "contextSources": [],
34
- "suspendsForClarification": false,
35
- "briefAdequacyGate": false,
36
- "briefAdequacyExcludedSources": []
37
- },
38
- "executor": "companion_agent",
39
- "approval": "auto",
40
- "budget": {},
41
- "onFailure": "keep_and_flag"
42
- }
@@ -1,68 +0,0 @@
1
- # Market Research — gather the evidence
2
-
3
- ### Target Application Framing
4
-
5
- This knowledge is for configuring behavior in the target application.
6
- Wildo is the framework surface being used, not the product being built.
7
-
8
- Read and apply these patterns from the application-developer point of view:
9
-
10
- - how the application should configure the relevant app-level file
11
- - how the application should use framework-provided factories, enums, and helpers
12
- - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
-
14
-
15
- You are the **researcher**. Your one job is to find out what is actually true about this
16
- product's market and report it with sources. You do not design the product, model
17
- its domain, choose a positioning, or author any file — a sibling does that, from
18
- what you bring back.
19
-
20
- ## Why this step exists
21
-
22
- The playbook that produces the market snapshot used to gather its own evidence, and
23
- it had no way to. Its executor was a structured-generation call with no tools, so
24
- "research" meant whatever the model already remembered — which is confident, fluent,
25
- and wrong in exactly the cases that matter, because prices change, competitors
26
- appear, and category language moves.
27
-
28
- This step exists so that the snapshot rests on pages someone actually read.
29
-
30
- ## What to find
31
-
32
- Work the objective you were given. It is not a fixed checklist: it was composed for
33
- THIS round, and on a second round it will name what the first round could not find.
34
- Where the objective is broad, these are the questions worth answering:
35
-
36
- 1. **The category as sources name it.** Not the category we would like to be in —
37
- the words buyers and competitors actually use. Note the alternatives you rejected
38
- and why.
39
- 2. **Who competes**, including the ones that are not products: a spreadsheet, an
40
- agency, doing nothing. For each, what it costs where that is published.
41
- 3. **Price shape.** Per seat, per usage, tiered, quote-only. Ranges and what a
42
- published entry price is.
43
- 4. **Buyer language.** How the people with the problem describe it in their own
44
- words, from forums, reviews, job posts, changelogs.
45
-
46
- ## How to report
47
-
48
- - **Every factual claim carries the URL you read it from.** A claim without one is
49
- worse than an absent claim, because the reader cannot tell which it is.
50
- - **Say what you could NOT find.** The gaps are what the next round is aimed at, and
51
- an unstated gap silently becomes an assumption downstream.
52
- - **Report disagreement.** Where sources conflict, say so, say which you consider
53
- more authoritative, and say why. Do not pick one silently.
54
- - **Distinguish what you READ from what you INFER.** Inference is legitimate;
55
- presenting it as a finding is not.
56
-
57
- ## Condensation is part of the job
58
-
59
- Return a brief, not a transcript. The sibling that reads this reasons at its own
60
- resolution, and a parent flooded with raw page text is a parent that cannot hold the
61
- problem. Roughly 2000 words: findings, sources, gaps. If a page mattered, say what it
62
- said and link it — do not paste it.
63
-
64
- ## What you cannot do
65
-
66
- You have no write access, no shell, and no path into the workspace. This is enforced,
67
- not requested. If the objective seems to ask for a file, it does not — report what you
68
- found and let the sibling author it.
@@ -1,44 +0,0 @@
1
- {
2
- "ref": "top_down.market-research",
3
- "version": "0.1.0",
4
- "phase": "top_down",
5
- "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.",
6
- "functionalTopics": [],
7
- "preconditions": [
8
- {
9
- "kind": "artifact_valid",
10
- "selector": {
11
- "family": "vision-brief"
12
- }
13
- }
14
- ],
15
- "inputs": [
16
- {
17
- "family": "vision-brief"
18
- }
19
- ],
20
- "outputs": [],
21
- "stepOutputs": [
22
- {
23
- "ref": "market-evidence",
24
- "condensation": "A brief of at most ~2000 words: the category as sources name it, the competing alternatives found with what each charges, the buyer language observed, and an explicit list of what could NOT be sourced. Every claim carries the URL it came from. Raw page text is never returned — the parent reasons at ITS resolution, and a dump is how a parent context stops fitting.",
25
- "description": "Source-attributed market evidence, condensed for the sibling that derives from it."
26
- }
27
- ],
28
- "method": {
29
- "guidance": "# Market Research — gather the evidence\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nYou are the **researcher**. Your one job is to find out what is actually true about this\nproduct's market and report it with sources. You do not design the product, model\nits domain, choose a positioning, or author any file — a sibling does that, from\nwhat you bring back.\n\n## Why this step exists\n\nThe playbook that produces the market snapshot used to gather its own evidence, and\nit had no way to. Its executor was a structured-generation call with no tools, so\n\"research\" meant whatever the model already remembered — which is confident, fluent,\nand wrong in exactly the cases that matter, because prices change, competitors\nappear, and category language moves.\n\nThis step exists so that the snapshot rests on pages someone actually read.\n\n## What to find\n\nWork the objective you were given. It is not a fixed checklist: it was composed for\nTHIS round, and on a second round it will name what the first round could not find.\nWhere the objective is broad, these are the questions worth answering:\n\n1. **The category as sources name it.** Not the category we would like to be in —\n the words buyers and competitors actually use. Note the alternatives you rejected\n and why.\n2. **Who competes**, including the ones that are not products: a spreadsheet, an\n agency, doing nothing. For each, what it costs where that is published.\n3. **Price shape.** Per seat, per usage, tiered, quote-only. Ranges and what a\n published entry price is.\n4. **Buyer language.** How the people with the problem describe it in their own\n words, from forums, reviews, job posts, changelogs.\n\n## How to report\n\n- **Every factual claim carries the URL you read it from.** A claim without one is\n worse than an absent claim, because the reader cannot tell which it is.\n- **Say what you could NOT find.** The gaps are what the next round is aimed at, and\n an unstated gap silently becomes an assumption downstream.\n- **Report disagreement.** Where sources conflict, say so, say which you consider\n more authoritative, and say why. Do not pick one silently.\n- **Distinguish what you READ from what you INFER.** Inference is legitimate;\n presenting it as a finding is not.\n\n## Condensation is part of the job\n\nReturn a brief, not a transcript. The sibling that reads this reasons at its own\nresolution, and a parent flooded with raw page text is a parent that cannot hold the\nproblem. Roughly 2000 words: findings, sources, gaps. If a page mattered, say what it\nsaid and link it — do not paste it.\n\n## What you cannot do\n\nYou have no write access, no shell, and no path into the workspace. This is enforced,\nnot requested. If the objective seems to ask for a file, it does not — report what you\nfound and let the sibling author it.\n",
30
- "skillRefs": [
31
- "journey-status",
32
- "market-category",
33
- "market-alternatives"
34
- ],
35
- "contextSources": [],
36
- "suspendsForClarification": false,
37
- "briefAdequacyGate": false,
38
- "briefAdequacyExcludedSources": []
39
- },
40
- "executor": "research_agent",
41
- "approval": "auto",
42
- "budget": {},
43
- "onFailure": "keep_and_flag"
44
- }
@@ -1,239 +0,0 @@
1
- # Market Analysis — Produce Method (v1 scaffold)
2
-
3
- ### Target Application Framing
4
-
5
- This knowledge is for configuring behavior in the target application.
6
- Wildo is the framework surface being used, not the product being built.
7
-
8
- Read and apply these patterns from the application-developer point of view:
9
-
10
- - how the application should configure the relevant app-level file
11
- - how the application should use framework-provided factories, enums, and helpers
12
- - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
-
14
-
15
- > **This is a v1 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
- ## The shape you return is FLAT, not nested
34
-
35
- Read this before the slice list below, because the slices read like a hierarchy and the object is
36
- not one.
37
-
38
- A MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,
39
- `pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,
40
- `triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at
41
- each other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,
42
- …). An ICP does not CONTAIN its jobs; it names them:
43
-
44
- ```
45
- jobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level
46
- icps: [ { ref: 'icp-small-team',
47
- jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it
48
- ```
49
-
50
- ⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were
51
- rejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,
52
- `triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and
53
- wrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full
54
- generation was spent discovering the shape. The slice ordering below is a THINKING order — what to
55
- work out first — never the structure of the answer.
56
-
57
- A MarketSnapshot is assembled from these slices, each owned by a dedicated
58
- `market_*` app-knowledge skill (see References). You author them in
59
- dependency order because later slices reference earlier refs:
60
-
61
- 1. **Category** — the one market category the product competes in, plus the
62
- rejected adjacent categories. (`market-category`)
63
- 2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic
64
- segments the product is sold to. (`market-icp`)
65
- 3. **Personas** — the human roles inside each ICP, including buying-group
66
- members. Every ICP needs at least one persona. (`market-persona`)
67
- 4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for
68
- the personas: what they are trying to do, what blocks them, what a win
69
- looks like. (`market-jobs-pains-gains`)
70
- 5. **Tones of voice** — the named brand voices the product speaks in.
71
- (`market-tone-of-voice`)
72
- 6. **Benefits** — the outcome claims the product delivers, weighted against
73
- the pains/gains they relieve/create. (`market-add-feature-benefit`)
74
- 7. **Positionings** — the per-ICP marketing-truth promise. Author one per
75
- ICP that the product actually targets. (`market-positioning-authoring`)
76
- 8. **Reach surfaces** — the go-to-market context: channels, competing
77
- alternatives, buying triggers + per-ICP buying journeys, proofs, and the
78
- objections proofs answer. (`market-channels`, `market-alternatives`,
79
- `market-triggers-and-journey`, `market-proof-and-objection`)
80
- 9. **Message templates** — reusable prompt templates that render from the
81
- snapshot above. Author last; they reference the earlier slices.
82
- (`market-message-templates-authoring`)
83
-
84
- Author only the slices the product's stage warrants — a first pass may stop
85
- after positionings and leave the phase-3/4 reach surfaces empty (they
86
- default to `[]`). A snapshot with a category, at least one ICP, its
87
- personas, the jobs/pains/gains triplet, and at least one positioning is a
88
- legitimate v1; the reach surfaces and message templates are additive.
89
-
90
- ## Where the snapshot lives
91
-
92
- The MarketSnapshot for this journey is placed under
93
- `specifications/src/market/index.ts`. That is the artifact this
94
- playbook owns and the rest of the top-down phase reads. When the product's
95
- definition later stabilises, the snapshot is what seeds the durable market
96
- specification under `./specifications/` — but at this phase it is a journey
97
- artifact, not yet app source.
98
-
99
- ## Produce vs. refine — read state first
100
-
101
- This playbook is **idempotent** on the journey's market artifact. Before
102
- authoring anything:
103
-
104
- 1. Read the current journey state and scope through the `journey-status`
105
- skill (it owns the read; do not re-derive it here) — that tells you which
106
- scope the snapshot must be complete *for*.
107
- 2. Check whether a MarketSnapshot already exists by reading the artifact at the
108
- `market-snapshot` family's landing path, `specifications/src/market/index.ts`.
109
- The path belongs to the FAMILY, not to this playbook — every playbook that
110
- writes a market snapshot writes that same file. Its presence or absence
111
- selects the mode below.
112
-
113
- - **No snapshot yet** — produce a fresh one, authoring the slices in the
114
- order above.
115
- - **A snapshot exists** — *refine* it: read every slice, keep what still
116
- holds, and only add/correct the slices the current steering notes or new
117
- research call for. Never silently discard authored refs — a downstream
118
- positioning or benefit may depend on an ICP or persona ref, and dropping
119
- it orphans them (the validator will catch this, but honest refinement
120
- should not create the orphan in the first place).
121
-
122
- ## Provenance — record where a claim came from
123
-
124
- You are given the evidence a sibling research step gathered, with the URLs it read.
125
- Where an entity's content rests on one of those sources, RECORD that URL on the entity
126
- — in the schema's own provenance fields, which exist for exactly this:
127
-
128
- | field | for |
129
- |---|---|
130
- | `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |
131
- | `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |
132
- | `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |
133
-
134
- ⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.
135
- That was wrong, and the correction is recorded rather than quietly applied because the
136
- run that exposed it did better than the instruction: handed the evidence, the model
137
- put 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the
138
- generic metadata block it had been pointed at. Typed provenance is machine-readable
139
- and the generic block is prose; prefer the specific field every time one exists.
140
-
141
- This is not bookkeeping. Measured on this playbook's first composite run
142
- (2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that
143
- dimension, indistinguishable from the single-call version it replaced — the judge
144
- called the older one's evidence "self-referential statements such as 'The vision
145
- specifies…'". A sourced claim and an invented one must not look the same in what you
146
- land, because nobody downstream can tell them apart afterwards.
147
-
148
- So:
149
-
150
- - An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.
151
- - An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for
152
- a hypothesis, not `HIGH` because it reads well.
153
- - An entity the evidence did not cover is still authorable, and says so.
154
-
155
- Omit `authoredMetadata` only where the content is so self-evident that provenance
156
- would be noise. A competitor's price is never that.
157
-
158
- ## Research posture (scaffold depth)
159
-
160
- Ground each slice in evidence, not invention. At this scaffold depth the
161
- research is whatever the executing agent can gather about the product's
162
- category, competitors, and buyers; capture the *shape* faithfully (real
163
- category, real competing alternatives, plausible ICPs and personas) rather
164
- than aspirational fiction. Where you are inferring rather than citing, say so
165
- in the slice's authored prose so a later, deeper research pass can tighten
166
- it. Do **not** build a research pipeline or block on external tooling here —
167
- richer web-research capability is a later-phase concern; this playbook
168
- consumes whatever the agent already knows plus the creator's steering.
169
-
170
- ## Quality gate
171
-
172
- Your emitted snapshot is checked by the deterministic `market-snapshot-valid`
173
- gate (`validateMarketSnapshot`) before anything downstream consumes it. It
174
- enforces the cross-slice invariants — orphan refs (a positioning naming a
175
- missing ICP, a benefit naming a missing pain/gain), an ICP with no persona,
176
- influence cycles, duplicate edges, proofs without support, message-template
177
- placeholder mismatches, and more. Duplicate or malformed refs and
178
- `ERROR`-severity issues are hard failures; the snapshot does not advance
179
- until they clear. `WARN`-severity issues (e.g. stale-authored, a missing
180
- positioning for a targeted ICP) do not block but should be resolved. Read
181
- `market-snapshot-validation` for the full issue catalogue and emit a clean
182
- snapshot the first time.
183
-
184
- ## Scaffold-depth boundary (deferred to a later depth phase)
185
-
186
- Keep this playbook at scaffold depth. The following are explicitly **out of
187
- scope here** and are deepened in the methodology-depth phase, not now:
188
-
189
- - **Deep competitive teardown** — the reach surfaces capture *that* an
190
- alternative exists and *why* a buyer might pick it; a quantified,
191
- feature-by-feature competitor matrix is later-phase work.
192
- - **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads
193
- the deterministic FIT scorer; at scaffold depth you consume it to sanity-
194
- check benefit weighting, not to drive a precise prioritization model. The
195
- prioritization seam stays pluggable (see the capability-map playbook).
196
- - **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are
197
- authored as framing, not as a sized, sourced market model.
198
-
199
- If you find yourself perfecting any of the above, stop and leave the slice at
200
- scaffold depth — depth is a dedicated later pass done once, holistically.
201
-
202
- ## What you emit
203
-
204
- A single MarketSnapshot at `specifications/src/market/index.ts`,
205
- assembled from the slices above via their `market_*` skills, passing the
206
- `market-snapshot-valid` gate. The creator reviews the result (approval posture
207
- `approve_result`) before it is accepted as the journey's market intent.
208
-
209
- ## References
210
-
211
- - `.claude/skills/journey-status/SKILL.md` — read the current journey state
212
- and scope before authoring.
213
- - `.claude/skills/market-authoring-overview/SKILL.md` — the orchestrator for
214
- the whole market slice; read it first to see how the slices fit together.
215
- - `.claude/skills/market-category/SKILL.md` — author the singular market
216
- category.
217
- - `.claude/skills/market-icp/SKILL.md` — author the Ideal Customer Profiles.
218
- - `.claude/skills/market-persona/SKILL.md` — author the personas per ICP.
219
- - `.claude/skills/market-jobs-pains-gains/SKILL.md` — author the Strategyzer
220
- jobs/pains/gains triplet.
221
- - `.claude/skills/market-tone-of-voice/SKILL.md` — author the named brand
222
- voices.
223
- - `.claude/skills/market-add-feature-benefit/SKILL.md` — author the benefit
224
- claims and their pain/gain weighting.
225
- - `.claude/skills/market-positioning-authoring/SKILL.md` — author the per-ICP
226
- positioning promise.
227
- - `.claude/skills/market-channels/SKILL.md` — author the reach channels.
228
- - `.claude/skills/market-alternatives/SKILL.md` — author the competing
229
- alternatives.
230
- - `.claude/skills/market-triggers-and-journey/SKILL.md` — author buying
231
- triggers and per-ICP buying journeys.
232
- - `.claude/skills/market-proof-and-objection/SKILL.md` — author proofs and
233
- the objections they answer.
234
- - `.claude/skills/market-message-templates-authoring/SKILL.md` — author the
235
- reusable message templates (last).
236
- - `.claude/skills/market-scoring-interpretation/SKILL.md` — interpret the
237
- deterministic FIT scorer to sanity-check benefit weighting.
238
- - `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation
239
- issue catalogue the quality gate enforces.
@@ -1,67 +0,0 @@
1
- {
2
- "ref": "top_down.market-snapshot-produce",
3
- "version": "0.1.0",
4
- "phase": "top_down",
5
- "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.",
6
- "functionalTopics": [],
7
- "preconditions": [
8
- {
9
- "kind": "artifact_valid",
10
- "selector": {
11
- "family": "vision-brief"
12
- }
13
- },
14
- {
15
- "kind": "step_available",
16
- "ref": "evidence-adequacy",
17
- "requires": {
18
- "path": "verdict",
19
- "equals": "adequate"
20
- }
21
- }
22
- ],
23
- "inputs": [
24
- {
25
- "family": "vision-brief"
26
- }
27
- ],
28
- "outputs": [
29
- {
30
- "family": "market-snapshot",
31
- "schemaRef": "saas-specifications:MarketSnapshot",
32
- "description": "The assembled market category, ICP, persona, jobs/pains/gains, benefit, positioning and reach graph validated by validateMarketSnapshot."
33
- }
34
- ],
35
- "stepOutputs": [],
36
- "method": {
37
- "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\n## The shape you return is FLAT, not nested\n\nRead this before the slice list below, because the slices read like a hierarchy and the object is\nnot one.\n\nA MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,\n`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at\neach other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,\n…). An ICP does not CONTAIN its jobs; it names them:\n\n```\njobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level\nicps: [ { ref: 'icp-small-team',\n jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it\n```\n\n⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were\nrejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and\nwrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full\ngeneration was spent discovering the shape. The slice ordering below is a THINKING order — what to\nwork out first — never the structure of the answer.\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`specifications/src/market/index.ts`. 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 by reading the artifact at the\n `market-snapshot` family's landing path, `specifications/src/market/index.ts`.\n The path belongs to the FAMILY, not to this playbook — every playbook that\n writes a market snapshot writes that same file. Its presence or absence\n 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## Provenance — record where a claim came from\n\nYou are given the evidence a sibling research step gathered, with the URLs it read.\nWhere an entity's content rests on one of those sources, RECORD that URL on the entity\n— in the schema's own provenance fields, which exist for exactly this:\n\n| field | for |\n|---|---|\n| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |\n| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |\n| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |\n\n⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.\nThat was wrong, and the correction is recorded rather than quietly applied because the\nrun that exposed it did better than the instruction: handed the evidence, the model\nput 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the\ngeneric metadata block it had been pointed at. Typed provenance is machine-readable\nand the generic block is prose; prefer the specific field every time one exists.\n\nThis is not bookkeeping. Measured on this playbook's first composite run\n(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that\ndimension, indistinguishable from the single-call version it replaced — the judge\ncalled the older one's evidence \"self-referential statements such as 'The vision\nspecifies…'\". A sourced claim and an invented one must not look the same in what you\nland, because nobody downstream can tell them apart afterwards.\n\nSo:\n\n- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.\n- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for\n a hypothesis, not `HIGH` because it reads well.\n- An entity the evidence did not cover is still authorable, and says so.\n\nOmit `authoredMetadata` only where the content is so self-evident that provenance\nwould be noise. A competitor's price is never that.\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 `specifications/src/market/index.ts`,\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",
38
- "skillRefs": [
39
- "journey-status",
40
- "market-authoring-overview",
41
- "market-category",
42
- "market-icp",
43
- "market-persona",
44
- "market-jobs-pains-gains",
45
- "market-tone-of-voice",
46
- "market-add-feature-benefit",
47
- "market-positioning-authoring",
48
- "market-channels",
49
- "market-alternatives",
50
- "market-triggers-and-journey",
51
- "market-proof-and-objection",
52
- "market-message-templates-authoring",
53
- "market-scoring-interpretation",
54
- "market-snapshot-validation"
55
- ],
56
- "contextSources": [],
57
- "suspendsForClarification": false,
58
- "briefAdequacyGate": false,
59
- "briefAdequacyExcludedSources": []
60
- },
61
- "executor": "companion_agent",
62
- "approval": "approve_result",
63
- "budget": {
64
- "maxRuns": 3
65
- },
66
- "onFailure": "keep_and_flag"
67
- }