@wildo-ai/framework-knowledge 1.1.1 → 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 (223) 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 +271 -8
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.loader.d.ts +19 -0
  6. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.loader.js +32 -0
  8. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  9. package/dist/esm/framework-knowledge.schemas.d.ts +13 -2
  10. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  11. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +45 -0
  13. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
  16. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +6 -7
  17. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +6 -6
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
  21. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -2
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -4
  25. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -2
  27. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +3 -9
  29. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -3
  31. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +10 -6
  33. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +25 -4
  35. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -5
  37. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -3
  39. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +4 -2
  41. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +4 -2
  43. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -2
  45. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -14
  47. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +3 -5
  49. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  50. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +3 -4
  51. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  52. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +2 -8
  53. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -2
  55. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  56. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +2 -8
  57. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -2
  59. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  60. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +52 -0
  61. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
  62. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
  63. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
  64. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +75 -0
  65. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
  66. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +91 -0
  67. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
  68. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +29 -0
  69. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
  70. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +28 -0
  71. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
  72. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -45
  73. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +4 -54
  75. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +30 -0
  77. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
  78. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +25 -0
  79. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
  80. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -9
  81. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -5
  83. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
  85. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
  87. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
  89. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
  91. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -9
  93. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -2
  95. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  96. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +2 -8
  97. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -2
  99. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  100. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -8
  101. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -2
  103. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  104. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +2 -8
  105. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +5 -4
  107. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -4
  109. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -2
  111. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +4 -6
  113. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +25 -5
  115. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  116. package/dist/knowledge/manifest.json +6 -7
  117. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +7 -47
  118. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +6 -13
  119. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +1 -82
  120. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +11 -6
  121. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -5
  122. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
  123. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +3 -4
  124. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -735
  125. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -7
  126. package/dist/knowledge/playbooks/refinement.document-facts/method.md +16 -123
  127. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -8
  128. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +10 -4
  129. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +10 -4
  130. package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -2
  131. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +12 -5
  132. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +10 -4
  133. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
  134. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
  135. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
  136. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +39 -21
  137. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
  138. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -4
  139. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +1 -1
  140. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +11 -5
  141. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -2
  142. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +11 -5
  143. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +10 -4
  144. package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
  145. package/dist/knowledge/references/example.config.app-shell.full.md +4 -0
  146. package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
  147. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
  148. package/dist/knowledge/references/platform.config.saas.md +0 -50
  149. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
  150. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -6
  151. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
  152. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -109
  153. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -137
  154. package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
  155. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
  156. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
  157. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
  158. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +1 -1
  159. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -36
  160. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
  161. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
  162. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -1
  163. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -1
  164. package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
  165. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  166. package/dist/knowledge/registries/framework-topics.json +11 -48
  167. package/dist/knowledge/registries/playbooks.json +11 -74
  168. package/dist/knowledge/registries/source-tags.json +538 -622
  169. package/dist/knowledge/skills/INDEX.md +0 -1
  170. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
  171. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -26
  172. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
  173. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
  174. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +21 -36
  175. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +19 -49
  176. package/dist/knowledge/skills/config-app-shell/SKILL.md +8 -6
  177. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +11 -6
  178. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -50
  179. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
  180. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -36
  181. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -36
  182. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -36
  183. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -109
  184. package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
  185. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
  186. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -2
  187. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -157
  188. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -109
  189. package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
  190. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
  191. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
  192. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
  193. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
  194. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
  195. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
  196. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -1
  197. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -109
  198. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -1
  199. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -36
  200. package/dist/knowledge/topic-index.json +128 -285
  201. package/dist/tsconfig.build.tsbuildinfo +1 -1
  202. package/dist/tsconfig.tsbuildinfo +1 -1
  203. package/package.json +4 -4
  204. package/dist/esm/.builder.pid +0 -9
  205. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
  206. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -66
  207. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
  208. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -40
  209. package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
  210. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -42
  211. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
  212. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -69
  213. package/dist/knowledge/references/placement-plan.config.md +0 -330
  214. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
  215. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
  216. package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
  217. package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
  218. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
  219. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
  220. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
  221. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
  222. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
  223. /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
@@ -43,28 +43,35 @@
43
43
  {
44
44
  "family": "market-snapshot",
45
45
  "schemaRef": "saas-specifications:MarketSnapshot",
46
+ "placement": ".wildo-saas/journey/<journeyId>/market-snapshot/",
46
47
  "description": "The same market snapshot, refined so every benefit names its delivering feature refs."
47
48
  },
48
49
  {
49
50
  "family": "feature-drafts",
50
51
  "schemaRef": "saas-specifications:FeatureSpecificationDrafts",
52
+ "placement": ".wildo-saas/journey/<journeyId>/feature-drafts/",
51
53
  "description": "A collection of runner-addressed, ref-less FeatureSpecificationDraft payloads for capabilities without runtime definitions."
52
54
  }
53
55
  ],
54
- "stepOutputs": [],
55
56
  "method": {
56
- "guidance": "# Capability Map — Benefit → Feature Pivot 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 be\n> iterated. The mapping order, the draft-authoring posture, and the\n> prioritization rubric below are deliberately explicit so they can be tuned\n> against real runs — treat them as a starting rubric, not a frozen contract.\n> The *analytical depth* of the capability work (quantified FIT / Kano scoring\n> precision, a real prioritization model) 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 **capability architect**. This playbook is the **pivot**: it turns\nthe *value proposition* (what the product promises the market) into *product\ncapability* (the features that actually deliver those promises). Value-proposition\nsharpening already produced a **MarketSnapshot** whose benefits carry weighted\nrelieves/creates/advances edges and per-ICP Kano categories. Your one job is to\nanswer, for every benefit: **which feature delivers this, and does that feature\nexist yet?** — and then record the answer in two places:\n\n1. **The benefit → feature edge** — on the SAME MarketSnapshot, wire every\n benefit's `deliveredByFeatureRefs[]` to the feature(s) that deliver it. This\n edge is the authoritative capability-mapping link (`FeatureBenefitConfig.\n deliveredByFeatureRefs`, required and non-empty): a benefit that is not\n deliverable by any feature is not a real capability. (`market-add-feature-benefit`)\n2. **The spec-first feature drafts** — for every feature the map introduces that\n has **no code registry entry yet**, author a `FeatureSpecificationDraft`\n (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —\n all in prose). These are **spec-first**: you author them BEFORE the runtime\n `FeatureDefinition` exists; the factory injects the `ref` later from the\n runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). The\n cross-registry validators are deliberately **fail-soft while the feature\n registry is empty** — so authoring the spec before the code does NOT\n crash-loop the app. (`spec-feature-update`)\n\nThen you **prioritize** the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below).\n\nThis is a **focused pivot pass**, distinct from value-proposition sharpening\n(which weighted the benefits) and from scope/roadmap (which slots the features\ninto releases). Where value-proposition made the benefits sharp, you make each\nbenefit *deliverable* and give every new capability its first spec.\n\n## Read state first — the two families you read, the two you write\n\nThis playbook is **idempotent** and a *refinement*: a MarketSnapshot must\nalready exist (the `artifact_exists` precondition enforces it). Before mapping\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here).\n2. Read the existing **MarketSnapshot** (the benefits and their weighting),\n the **requirements** (`requirements` family — the functional/non-functional\n requirements the features must satisfy), and the **VisionSnapshot**\n (`vision-brief` — the differentiation anchor). You map capability against the\n real market intent, the real requirements, and the real differentiation — not\n from scratch.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context market-snapshot (read the benefits to map + any existing feature edges)\n\nYou **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**\nthe refined `market-snapshot` (edge wired) and the `feature-drafts` family (the\nnew drafts).\n\n## The mapping loop (benefit by benefit)\n\nFor each benefit in the snapshot:\n\n1. **Identify the delivering feature(s).** Ask what capability the product must\n have for this benefit's claim to be true. Prefer *one clear feature per\n benefit*; a benefit may legitimately need more than one, and one feature may\n deliver several benefits.\n2. **Reuse before you create.** If a delivering feature already appears on\n another benefit's `deliveredByFeatureRefs`, or already has a draft from an\n earlier run, **reuse that same feature ref** — never mint a second ref for the\n same capability. Reusing refs is what keeps the map coherent and lets the\n downstream scope/roadmap playbook slot each feature exactly once.\n3. **Wire the edge.** Add the feature ref(s) to the benefit's\n `deliveredByFeatureRefs[]`. Every benefit must end with a non-empty edge —\n the gate fails a benefit with an empty `deliveredByFeatureRefs` as\n `EMPTY_BENEFIT_DELIVERED_BY` (ERROR).\n4. **Draft the new feature (spec-first).** If the feature is new (no code\n registry entry, no prior draft), author its `FeatureSpecificationDraft` into\n the `feature-drafts` family. A draft is the **prose subset** of a feature\n spec: a business-language `purpose`, its `businessRole` / optional\n `lifecycleRole`, `useWhen` / `avoidWhen`, optional `businessConstraints`, and\n the `availabilityRole` (how the feature gates / packages). **Author ONLY these\n prose fields.** Do NOT author a `ref` — the factory injects it later from the\n runtime feature identifier, which is why a draft is authored ref-less. Do NOT\n wire `codeHandling` (it links a spec back to a runtime enum member +\n collection entry that does not exist yet at this phase) — the code-handling\n provenance is added when the feature is actually built, not now.\n `spec-feature-update` is the field-shape authority for a feature spec; here\n you use its prose surface only. Keep it a *capability contract*, not an\n implementation. (`spec-feature-update`)\n5. **Trace to requirements + vision.** A feature only earns its place if it\n delivers a benefit that traces to the vision's differentiation AND satisfies\n real requirements. When a benefit's delivering feature has no requirement\n behind it, that is a signal to either add the requirement upstream or drop the\n claim — not to invent a feature the product does not need.\n\n## The scoring seam — FIT + Kano, kept PLUGGABLE and VERSIONED\n\nAssess the mapped capability set with a **FIT-scoring + Kano** step, and let that\nassessment inform how the capabilities get prioritized.\n\n**FIT is a fit signal, NOT a priority ranking — do not conflate them.**\n`computeFeatureFitScoreForICP` answers one narrow question: *how well does this\nfeature serve this ICP* on a deterministic 0–100 scale (edge `degree` × the ICP's\nown edge weight). It deliberately does NOT answer \"which feature do we build\nfirst\" — that is prioritization, a separate, deferred concern. Combine the FIT\nscore with the per-ICP Kano category (`THRESHOLD` = table-stakes, `PERFORMANCE` =\nmore-is-better, `DELIGHTER` = upside) to read *table-stakes vs. upside per\nsegment* — a fit judgement, not a build-order. Bending the FIT score into a\nbuild-order ranking yields wrong answers (this is the locked FIT-vs-priority\nvocabulary the `market-scoring-interpretation` skill enforces).\n\n**This step is a pluggable, versioned interface — bind to it, never embed it.**\nThe scoring / prioritization methodology is expected to change substantially in a\nlater phase, so this playbook references the scoring *interface* (via the\n`market-scoring-interpretation` skill) and consumes its output; it does **not**\nre-implement the scoring math and does **not** hard-couple to any specific scoring\nfunction (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). Treat\nthe scorer as a swappable black box: feed it the snapshot, read back the per-ICP\nFIT scores + Kano categories, and use them to sanity-check the capability set. If\nyou find yourself hand-writing a scoring formula, tuning weights to hit a target\nresult, or building an actual build-order prioritization model, **stop** — that is\nthe depth phase's job, and hard-coding it here would break the pluggability\ncontract (OQ-6).\n\nAt scaffold depth this is a *fit sanity check on the capability set*, not a\ndefended prioritization. The headline gap it surfaces: a table-stakes capability\n(a `THRESHOLD` benefit for a `CORE`/`EXPANSION` ICP) whose delivering feature has\nno draft.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite edges or drafts that are already\n correct. Only add/correct where a benefit lacks a delivering feature, a new\n benefit appeared, or a draft is genuinely wrong.\n- **Never orphan a ref.** A benefit points at feature refs; those refs must have\n a draft (for new features) or a real registry entry (once code exists).\n Removing a feature that a benefit still delivers, or a draft a benefit still\n points at, orphans the edge. Feature-ref orphans are only resolution-checked\n once a feature registry is passed to the validator (not at this phase — the\n registry is empty and the check is fail-soft), so honest refinement must not\n create the orphan in the first place.\n- **One capability, one ref.** When two benefits are delivered by the same\n capability, they share the feature ref — do not fork it.\n\n## Quality gate\n\nThe refined MarketSnapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\ncapability-mapping invariants it enforces:\n\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must be deliverable. This is the headline check this\n playbook clears.\n- **`ORPHAN_REF` (ERROR)** — a benefit naming a missing pain/gain/job (feature-ref\n orphans are only checked once a feature registry is passed — not at this phase).\n- The value-proposition invariants inherited from the prior pass\n (`MISSING_POSITIONING_FOR_ICP`, `THRESHOLD_BENEFIT_WITHOUT_JOB`,\n `MULTIPLE_THRESHOLDS_PER_ICP_JOB`) still apply — do not regress them.\n\nRead `market-snapshot-validation` for the full issue catalogue.\n\nThe `feature-drafts` family has **no snapshot-level deterministic gate at this\nphase** — the only feature-spec validator is per-item and needs a ref-bearing\nconfig, which a spec-first draft deliberately omits. Author each draft to the\n`spec-feature-update` skill's contract (which carries the per-draft validity\ncheck); the collection-level gate is a filed depth-phase item (see below).\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **A real prioritization model.** The FIT/Kano step here is a *fit* sanity\n check, not a defended, weighted, capacity-fitted *prioritization* (RICE/WSJF\n and the like are later-phase — and FIT is not priority, see the scoring seam).\n The scoring seam stays pluggable — do NOT build or tune a scoring or\n build-order model in this playbook.\n- **Deep feature-spec drafts.** A draft here is a first-cut capability contract\n (purpose / roles / use-when). Rich operation inventories, interaction\n semantics, and UX are the bottom-up build phase's job, not the capability map.\n- **A snapshot-level `feature-drafts` validator.** No deterministic validator\n exists yet for a *collection* of spec-first drafts (the per-item\n `validateFeatureSpecification` needs a ref, which drafts omit). Authoring the\n collection-level gate — and deciding whether draft prioritization output is\n itself a gated artifact — is depth-phase work.\n- **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and\n jobs but NOT market pains/gains, so the \"this requirement delivers\n `gain-X`\" trace that would let capability mapping run benefit → requirement →\n feature *deterministically* is lossy (expressible only in prose). Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase\n question — do NOT reshape the requirements contract here.\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\nTwo artifacts for this journey:\n\n1. The SAME **MarketSnapshot** at `specifications/src/market/index.ts`,\n with every benefit's `deliveredByFeatureRefs` edge wired to its delivering\n feature(s), passing the `market-snapshot-valid` gate.\n2. The **feature-drafts** at `specifications/src/feature-drafts/index.ts` —\n one spec-first `FeatureSpecificationDraft` per new delivering feature.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's capability map.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm a `market-snapshot` already exists to map from.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `.claude/skills/spec-feature-update/SKILL.md` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — the FIT/Kano scoring\n interface: interpret the deterministic scorer's ranking to sanity-check the\n capability set (pluggable seam — consume it, do not re-implement it).\n- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation issue\n catalogue the quality gate enforces.\n",
57
+ "guidance": "# Capability Map — Benefit → Feature Pivot 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 be\n> iterated. The mapping order, the draft-authoring posture, and the\n> prioritization rubric below are deliberately explicit so they can be tuned\n> against real runs — treat them as a starting rubric, not a frozen contract.\n> The *analytical depth* of the capability work (quantified FIT / Kano scoring\n> precision, a real prioritization model) 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 **capability architect**. This playbook is the **pivot**: it turns\nthe *value proposition* (what the product promises the market) into *product\ncapability* (the features that actually deliver those promises). Value-proposition\nsharpening already produced a **MarketSnapshot** whose benefits carry weighted\nrelieves/creates/advances edges and per-ICP Kano categories. Your one job is to\nanswer, for every benefit: **which feature delivers this, and does that feature\nexist yet?** — and then record the answer in two places:\n\n1. **The benefit → feature edge** — on the SAME MarketSnapshot, wire every\n benefit's `deliveredByFeatureRefs[]` to the feature(s) that deliver it. This\n edge is the authoritative capability-mapping link (`FeatureBenefitConfig.\n deliveredByFeatureRefs`, required and non-empty): a benefit that is not\n deliverable by any feature is not a real capability. (`market-add-feature-benefit`)\n2. **The spec-first feature drafts** — for every feature the map introduces that\n has **no code registry entry yet**, author a `FeatureSpecificationDraft`\n (purpose, businessRole, lifecycleRole, useWhen/avoidWhen, availabilityRole —\n all in prose). These are **spec-first**: you author them BEFORE the runtime\n `FeatureDefinition` exists; the factory injects the `ref` later from the\n runtime identifier, so a draft is authored ref-less (`Omit<…, 'ref'>`). The\n cross-registry validators are deliberately **fail-soft while the feature\n registry is empty** — so authoring the spec before the code does NOT\n crash-loop the app. (`spec-feature-update`)\n\nThen you **prioritize** the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below).\n\nThis is a **focused pivot pass**, distinct from value-proposition sharpening\n(which weighted the benefits) and from scope/roadmap (which slots the features\ninto releases). Where value-proposition made the benefits sharp, you make each\nbenefit *deliverable* and give every new capability its first spec.\n\n## Read state first — the two families you read, the two you write\n\nThis playbook is **idempotent** and a *refinement*: a MarketSnapshot must\nalready exist (the `artifact_exists` precondition enforces it). Before mapping\nanything:\n\n1. Read the current journey state and scope through the `journey-status` skill\n (it owns the read; do not re-derive it here).\n2. Read the existing **MarketSnapshot** (the benefits and their weighting),\n the **requirements** (`requirements` family — the functional/non-functional\n requirements the features must satisfy), and the **VisionSnapshot**\n (`vision-brief` — the differentiation anchor). You map capability against the\n real market intent, the real requirements, and the real differentiation — not\n from scratch.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context market-snapshot (read the benefits to map + any existing feature edges)\n\nYou **read** `market-snapshot` + `requirements` + `vision-brief`; you **write**\nthe refined `market-snapshot` (edge wired) and the `feature-drafts` family (the\nnew drafts).\n\n## The mapping loop (benefit by benefit)\n\nFor each benefit in the snapshot:\n\n1. **Identify the delivering feature(s).** Ask what capability the product must\n have for this benefit's claim to be true. Prefer *one clear feature per\n benefit*; a benefit may legitimately need more than one, and one feature may\n deliver several benefits.\n2. **Reuse before you create.** If a delivering feature already appears on\n another benefit's `deliveredByFeatureRefs`, or already has a draft from an\n earlier run, **reuse that same feature ref** — never mint a second ref for the\n same capability. Reusing refs is what keeps the map coherent and lets the\n downstream scope/roadmap playbook slot each feature exactly once.\n3. **Wire the edge.** Add the feature ref(s) to the benefit's\n `deliveredByFeatureRefs[]`. Every benefit must end with a non-empty edge —\n the gate fails a benefit with an empty `deliveredByFeatureRefs` as\n `EMPTY_BENEFIT_DELIVERED_BY` (ERROR).\n4. **Draft the new feature (spec-first).** If the feature is new (no code\n registry entry, no prior draft), author its `FeatureSpecificationDraft` into\n the `feature-drafts` family. A draft is the **prose subset** of a feature\n spec: a business-language `purpose`, its `businessRole` / optional\n `lifecycleRole`, `useWhen` / `avoidWhen`, optional `businessConstraints`, and\n the `availabilityRole` (how the feature gates / packages). **Author ONLY these\n prose fields.** Do NOT author a `ref` — the factory injects it later from the\n runtime feature identifier, which is why a draft is authored ref-less. Do NOT\n wire `codeHandling` (it links a spec back to a runtime enum member +\n collection entry that does not exist yet at this phase) — the code-handling\n provenance is added when the feature is actually built, not now.\n `spec-feature-update` is the field-shape authority for a feature spec; here\n you use its prose surface only. Keep it a *capability contract*, not an\n implementation. (`spec-feature-update`)\n5. **Trace to requirements + vision.** A feature only earns its place if it\n delivers a benefit that traces to the vision's differentiation AND satisfies\n real requirements. When a benefit's delivering feature has no requirement\n behind it, that is a signal to either add the requirement upstream or drop the\n claim — not to invent a feature the product does not need.\n\n## The scoring seam — FIT + Kano, kept PLUGGABLE and VERSIONED\n\nAssess the mapped capability set with a **FIT-scoring + Kano** step, and let that\nassessment inform how the capabilities get prioritized.\n\n**FIT is a fit signal, NOT a priority ranking — do not conflate them.**\n`computeFeatureFitScoreForICP` answers one narrow question: *how well does this\nfeature serve this ICP* on a deterministic 0–100 scale (edge `degree` × the ICP's\nown edge weight). It deliberately does NOT answer \"which feature do we build\nfirst\" — that is prioritization, a separate, deferred concern. Combine the FIT\nscore with the per-ICP Kano category (`THRESHOLD` = table-stakes, `PERFORMANCE` =\nmore-is-better, `DELIGHTER` = upside) to read *table-stakes vs. upside per\nsegment* — a fit judgement, not a build-order. Bending the FIT score into a\nbuild-order ranking yields wrong answers (this is the locked FIT-vs-priority\nvocabulary the `market-scoring-interpretation` skill enforces).\n\n**This step is a pluggable, versioned interface — bind to it, never embed it.**\nThe scoring / prioritization methodology is expected to change substantially in a\nlater phase, so this playbook references the scoring *interface* (via the\n`market-scoring-interpretation` skill) and consumes its output; it does **not**\nre-implement the scoring math and does **not** hard-couple to any specific scoring\nfunction (`computeFeatureFitScoreForICP` today, a different scorer tomorrow). Treat\nthe scorer as a swappable black box: feed it the snapshot, read back the per-ICP\nFIT scores + Kano categories, and use them to sanity-check the capability set. If\nyou find yourself hand-writing a scoring formula, tuning weights to hit a target\nresult, or building an actual build-order prioritization model, **stop** — that is\nthe depth phase's job, and hard-coding it here would break the pluggability\ncontract (OQ-6).\n\nAt scaffold depth this is a *fit sanity check on the capability set*, not a\ndefended prioritization. The headline gap it surfaces: a table-stakes capability\n(a `THRESHOLD` benefit for a `CORE`/`EXPANSION` ICP) whose delivering feature has\nno draft.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite edges or drafts that are already\n correct. Only add/correct where a benefit lacks a delivering feature, a new\n benefit appeared, or a draft is genuinely wrong.\n- **Never orphan a ref.** A benefit points at feature refs; those refs must have\n a draft (for new features) or a real registry entry (once code exists).\n Removing a feature that a benefit still delivers, or a draft a benefit still\n points at, orphans the edge. Feature-ref orphans are only resolution-checked\n once a feature registry is passed to the validator (not at this phase — the\n registry is empty and the check is fail-soft), so honest refinement must not\n create the orphan in the first place.\n- **One capability, one ref.** When two benefits are delivered by the same\n capability, they share the feature ref — do not fork it.\n\n## Quality gate\n\nThe refined MarketSnapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. The\ncapability-mapping invariants it enforces:\n\n- **`EMPTY_BENEFIT_DELIVERED_BY` (ERROR)** — a benefit's `deliveredByFeatureRefs[]`\n is empty; every benefit must be deliverable. This is the headline check this\n playbook clears.\n- **`ORPHAN_REF` (ERROR)** — a benefit naming a missing pain/gain/job (feature-ref\n orphans are only checked once a feature registry is passed — not at this phase).\n- The value-proposition invariants inherited from the prior pass\n (`MISSING_POSITIONING_FOR_ICP`, `THRESHOLD_BENEFIT_WITHOUT_JOB`,\n `MULTIPLE_THRESHOLDS_PER_ICP_JOB`) still apply — do not regress them.\n\nRead `market-snapshot-validation` for the full issue catalogue.\n\nThe `feature-drafts` family has **no snapshot-level deterministic gate at this\nphase** — the only feature-spec validator is per-item and needs a ref-bearing\nconfig, which a spec-first draft deliberately omits. Author each draft to the\n`spec-feature-update` skill's contract (which carries the per-draft validity\ncheck); the collection-level gate is a filed depth-phase item (see below).\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. Explicitly **out of scope here**:\n\n- **A real prioritization model.** The FIT/Kano step here is a *fit* sanity\n check, not a defended, weighted, capacity-fitted *prioritization* (RICE/WSJF\n and the like are later-phase — and FIT is not priority, see the scoring seam).\n The scoring seam stays pluggable — do NOT build or tune a scoring or\n build-order model in this playbook.\n- **Deep feature-spec drafts.** A draft here is a first-cut capability contract\n (purpose / roles / use-when). Rich operation inventories, interaction\n semantics, and UX are the bottom-up build phase's job, not the capability map.\n- **A snapshot-level `feature-drafts` validator.** No deterministic validator\n exists yet for a *collection* of spec-first drafts (the per-item\n `validateFeatureSpecification` needs a ref, which drafts omit). Authoring the\n collection-level gate — and deciding whether draft prioritization output is\n itself a gated artifact — is depth-phase work.\n- **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and\n jobs but NOT market pains/gains, so the \"this requirement delivers\n `gain-X`\" trace that would let capability mapping run benefit → requirement →\n feature *deterministically* is lossy (expressible only in prose). Whether the\n requirements family should gain a pain/gain edge is a filed depth-phase\n question — do NOT reshape the requirements contract here.\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\nTwo artifacts for this journey:\n\n1. The SAME **MarketSnapshot** at `.wildo-saas/journey/<journeyId>/market-snapshot/`,\n with every benefit's `deliveredByFeatureRefs` edge wired to its delivering\n feature(s), passing the `market-snapshot-valid` gate.\n2. The **feature-drafts** at `.wildo-saas/journey/<journeyId>/feature-drafts/` —\n one spec-first `FeatureSpecificationDraft` per new delivering feature.\n\nThe creator reviews the result (approval posture `approve_result`) before it is\naccepted as the journey's capability map.\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read the current journey state and\n scope, and confirm a `market-snapshot` already exists to map from.\n- `.claude/skills/market-add-feature-benefit/SKILL.md` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `.claude/skills/spec-feature-update/SKILL.md` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `.claude/skills/market-scoring-interpretation/SKILL.md` — the FIT/Kano scoring\n interface: interpret the deterministic scorer's ranking to sanity-check the\n capability set (pluggable seam — consume it, do not re-implement it).\n- `.claude/skills/market-snapshot-validation/SKILL.md` — the full validation issue\n catalogue the quality gate enforces.\n",
57
58
  "skillRefs": [
58
59
  "journey-status",
59
60
  "market-add-feature-benefit",
60
61
  "market-scoring-interpretation",
61
62
  "market-snapshot-validation",
62
63
  "spec-feature-update"
63
- ],
64
- "contextSources": [],
65
- "suspendsForClarification": false
64
+ ]
66
65
  },
67
66
  "executor": "companion_agent",
67
+ "qualityGates": [
68
+ {
69
+ "ref": "capability-map-output-set-valid",
70
+ "kind": "deterministic_validator",
71
+ "validatorRef": "saas-specifications:validateCapabilityMapOutputSet",
72
+ "required": true
73
+ }
74
+ ],
68
75
  "approval": "approve_result",
69
76
  "budget": {
70
77
  "maxRuns": 3
@@ -25,10 +25,10 @@
25
25
  {
26
26
  "family": "vision-brief",
27
27
  "schemaRef": "saas-specifications:VisionSnapshot",
28
+ "placement": ".wildo-saas/journey/<journeyId>/vision-brief/",
28
29
  "description": "The same VisionSnapshot the vision-elicitation step seeded, refined in place: this playbook adds/updates the `constraints[]` entries whose `kind` is `compliance`, each a prose `statement` naming an applicable regime and the data / jurisdiction it governs. Other vision entities (idea, problem, mission, success criteria, non-compliance constraints) are left untouched. Validated by validateVisionSnapshot."
29
30
  }
30
31
  ],
31
- "stepOutputs": [],
32
32
  "method": {
33
33
  "guidance": "# Compliance Posture — Derivation 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.** The regime-derivation rubric below\n> (which triggers imply which regime, how much to capture) is a deliberately\n> explicit first cut meant to be tuned against real runs. Treat it as a\n> starting rubric, not a frozen contract. Crucially, it derives compliance\n> **posture at scaffold depth** — prose constraints, not a per-regime\n> obligation model.\n\n## What this playbook does\n\nYou determine the product's **compliance posture** — which regulatory regimes\nit must be built to satisfy — and record each as a `compliance`-kind constraint\non the existing vision. The vision-elicitation step already named the\ncompliance _seam_ in passing (a single \"we handle EU personal data\" line). Your\njob is the focused, deliberate pass over that seam: reason from the product's\njurisdictions, the classes of data it handles, and its sector to the concrete\nset of regimes, and write each one down as its own constraint with a clear\nprose statement.\n\nYou do **not** re-elicit the whole vision, design the domain, or draft\nrequirements. You touch exactly one slice of the `VisionSnapshot`: its\n`constraints[]` entries of `kind: compliance`. Everything else on the snapshot\n— the idea, the problem, the mission, the success criteria, the\nnon-compliance constraints — you leave exactly as you found it.\n\n## The scaffold-depth boundary (read this before you start)\n\nAt this stage compliance is captured as **prose constraints only**. Each\napplicable regime becomes one constraint entry whose `statement` names the\nregime and the data / jurisdiction it governs — e.g. _\"Must be GDPR-compliant\nfor EU/EEA customer personal data.\"_ That is the whole deliverable.\n\nDo **not** build, and do not try to author into the snapshot:\n\n- per-regime control catalogs or obligation graphs (legal-article mappings,\n sector safeguards, external-assurance criteria),\n- data-flow / residency matrices,\n- retention schedules, DPA registries, or audit-config derivations.\n\nThat deep per-regime obligation model is a deliberately deferred later concern.\nIf you catch yourself modelling controls or obligations, **stop** — you have\nleft scaffold depth. Naming the regime seam accurately here is exactly what\nlets that later, deeper step engage. Getting the _set of applicable regimes_\nright, in prose, is the win.\n\n### Transition to structured compliance conception\n\nThis playbook does not write the dedicated `compliance-program` family. Its\naccepted vision constraints are precursor facts for a later, separately\napproved compliance-conception step. That step may initialize or revise the\noptional structured family only after it resolves exact source versions and\nrights records, declarative application scope, applicability authority, Wildo\nobjective bindings, implementation choices, responsibilities, documentation\nrequirements and explicit gaps.\n\nThe transition is not an automatic conversion and must not reinterpret a\nvision sentence as a control mapping or positive compliance claim. Preserve\nthe vision constraint as product intent, record any missing detail as\n`UNDETERMINED` or an explicit gap, and accept the structured family through the\nnormal semantic-delta authority. Runtime organizations, assignees, evidence,\ncontrol occurrences and assessments remain outside both artifacts.\n\n## The derivation posture\n\n- **Derive, then confirm — do not just transcribe.** The typed questions on\n this playbook (`method.elicitation`) gather the raw triggers: jurisdictions,\n data classes, sector, and direct yes/no reads on the common regimes. Your\n value is reasoning from those triggers to the regime set, then reflecting\n each derived regime back to the creator for confirmation. If EU users +\n personal data are present, GDPR applies whether or not the creator named it;\n surface that, don't wait to be told.\n- **Regime derivation rubric (v1).** Use these as the starting triggers, and\n follow up where an answer is thin:\n - **GDPR / UK GDPR** — serving EU/EEA (or UK) individuals, or processing\n their personal data. Triggered by jurisdiction (EU/EEA/UK) + any personal\n data.\n - **HIPAA** — handling US protected health information as, or on behalf of, a\n covered entity or business associate. Triggered by health data + US\n healthcare context.\n - **External assurance commitments** — enterprise customers or the product's own security posture\n require an independent attestation or certification over security / availability /\n confidentiality. Often contractual rather than statutory — capture the requested target as\n externally supplied source metadata when the go-to-market depends on it.\n - **Data residency / sovereignty** — a requirement that certain data stay\n within a region or country. Triggered by residency answers or sector rules;\n record as its own compliance constraint even when it rides alongside GDPR.\n - **Sector & additional regimes** — payment-card, consumer-privacy, children's-data,\n government-security, contractual-assurance and sector-code obligations. Add each that\n the triggers imply; preserve the exact named source only in the later source registry.\n - When the triggers are genuinely absent (no personal data, no regulated\n sector), the honest posture is _no compliance constraints_ — say so and add\n none. Do not invent a regime to look thorough.\n- **One regime, one constraint.** Keep regimes as separate constraint entries\n rather than one omnibus \"must be compliant\" line — the set is read\n downstream, and a merged statement loses which regimes are actually in play.\n\n## What you emit\n\nYou refine the **existing** `VisionSnapshot` in place. Concretely, you\nadd or update entries in `constraints[]`:\n\n- Each applicable regime is one entry with `kind: compliance`.\n- Each entry has a stable kebab-case `ref` prefixed `constraint-`\n (e.g. `constraint-gdpr-eu-personal-data`,\n `constraint-hipaa-us-phi`, `constraint-external-assurance-security`,\n `constraint-data-residency-eu`), unique across the whole `constraints[]` set.\n- Each entry's `statement` is a prose sentence naming the regime and the data /\n jurisdiction it governs. Where the creator gave the source of the limit\n (a customer contract, a specific law), capture it as the constraint's\n rationale.\n\nLeave every non-`compliance` constraint, and every other vision entity,\nuntouched.\n\n**Idempotent — refine, do not duplicate.** Read the vision first. If compliance\nconstraints already exist (the vision-elicitation step, or a prior run of this\nplaybook, may have written some), reconcile against them: update a statement\nthat is now sharper, add a regime that was missed, and remove one only if the\ncreator confirms it never applied. **Match existing constraints by the REGIME\ntheir `statement` names, not by their `ref` slug** — the vision-elicitation step\nwrites compliance prose without following this playbook's ref convention, so a\nGDPR line it left may sit under any slug (`constraint-gdpr`,\n`constraint-eu-data`, …). When you refine a regime that is already present,\n**reuse that entry's existing `ref`** so it updates in place rather than\nforking; only mint a fresh `constraint-<regime>-<scope>` slug for a regime that\nis genuinely new. Re-running this playbook on an already-posture'd vision must\nconverge to one entry per regime, never accumulate near-duplicate\n`constraint-gdpr-*` entries.\n\n## Quality gate\n\nYour refined snapshot is checked by the deterministic `vision-snapshot-valid`\ngate (`validateVisionSnapshot`) before it commits — the same gate the\nvision-elicitation step uses, because you write to the same family. Duplicate\nrefs and malformed refs (a constraint ref that is not kebab-case with the\n`constraint-` prefix) are hard **errors**; the gate rejects them. Emit clean,\nunique refs the first time. Note that a vision with no compliance constraints\nis perfectly valid — an honestly unregulated product should pass the gate with\nnone.\n\n## Approval\n\nThe refined `VisionSnapshot` is presented to the creator for approval before it\nbecomes the committed `vision-brief`. Show the derived compliance posture back\nin plain prose — the list of regimes, each with the data / jurisdiction it\ngoverns and why it applies — and let the creator confirm or correct it.\nCompliance drives real downstream engine capability, audit, and retention\nchoices, so it is worth one explicit human sign-off that the regime set is\nright.\n\n## Runtime context\n\nBefore you start, read the current journey state and scope, and read the\nexisting vision so you refine its compliance constraints rather than writing a\nfresh, disconnected set.\n\n// TODO CLI COMMAND: wildo context journey-status (read current journey scope + artifacts)\n// TODO CLI COMMAND: wildo context vision-brief (read the existing vision + its current constraints)\n\n## References\n\n- `.claude/skills/journey-status/SKILL.md` — read current journey state and\n scope before deriving, and to see the `vision-brief` (and its existing\n compliance constraints) you refine.\n",
34
34
  "skillRefs": [
@@ -82,11 +82,17 @@
82
82
  "kind": "free_text"
83
83
  }
84
84
  ]
85
- },
86
- "contextSources": [],
87
- "suspendsForClarification": false
85
+ }
88
86
  },
89
87
  "executor": "companion_agent",
88
+ "qualityGates": [
89
+ {
90
+ "ref": "vision-snapshot-valid",
91
+ "kind": "deterministic_validator",
92
+ "validatorRef": "saas-specifications:validateVisionSnapshot",
93
+ "required": true
94
+ }
95
+ ],
90
96
  "approval": "approve_result",
91
97
  "budget": {
92
98
  "maxRuns": 3
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, or presents unsupported claims as truth.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, or presents unsupported claims as truth.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-analysis"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-market-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1,"riskClassRef":"application-creation:risk/market-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1},"decisionPointRef":"application-creation:decision-point/market-analysis-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/market-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/market-definition-change","triggerRefs":["application-creation:trigger/market-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-market-analysis-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"hardFloorRef":"application-creation:hard-floor/market-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/market-analysis","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, or presents unsupported claims as truth.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-market-input-and-candidate","criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/accepted-vision-research-and-market-candidate"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-market-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1,"riskClassRef":"application-creation:risk/market-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1},"decisionPointRef":"application-creation:decision-point/market-analysis-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/market-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/market-definition-change","triggerRefs":["application-creation:trigger/market-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-market-analysis-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"hardFloorRef":"application-creation:hard-floor/market-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/market-analysis","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, or presents unsupported claims as truth.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-analysis"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-market-input-and-candidate","criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/accepted-vision-research-and-market-candidate"}],"schemaVersion":1}
@@ -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,8 +1,8 @@
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
8
  {
@@ -21,29 +21,47 @@
21
21
  "family": "vision-brief"
22
22
  }
23
23
  ],
24
- "outputs": [],
25
- "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
+ ],
26
32
  "method": {
27
- "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",
28
34
  "skillRefs": [
29
35
  "journey-status",
30
- "market-authoring-overview"
31
- ],
32
- "contextSources": [],
33
- "choreography": {
34
- "admits": [
35
- "top_down.market-snapshot-produce",
36
- "top_down.market-research",
37
- "top_down.market-evidence-adequacy"
38
- ],
39
- "maximumIterations": 10,
40
- "maximumLanesPerIteration": 3,
41
- "maximumDepth": 1,
42
- "maximumDurationMs": 2400000
43
- },
44
- "suspendsForClarification": false
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
+ ]
45
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
+ ],
46
62
  "approval": "approve_result",
47
- "budget": {},
63
+ "budget": {
64
+ "maxRuns": 3
65
+ },
48
66
  "onFailure": "keep_and_flag"
49
67
  }
@@ -55,20 +55,16 @@
55
55
  }
56
56
  ],
57
57
  "outputs": [],
58
- "stepOutputs": [],
59
58
  "method": {
60
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",
61
60
  "skillRefs": [
62
61
  "journey-status",
63
62
  "journey-report",
64
63
  "journey-approve"
65
- ],
66
- "contextSources": [
67
- "coherence_report"
68
- ],
69
- "suspendsForClarification": false
64
+ ]
70
65
  },
71
66
  "executor": "companion_agent",
67
+ "qualityGates": [],
72
68
  "approval": "approve_result",
73
69
  "budget": {
74
70
  "maxRuns": 3