@wildo-ai/framework-knowledge 1.1.8 → 1.1.10

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 (480) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
  5. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
  7. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  8. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
  9. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  10. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
  11. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
  12. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
  14. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
  15. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +20 -4
  17. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  18. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  19. package/dist/esm/framework-knowledge.definitions.js +95 -5
  20. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  21. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  22. package/dist/esm/index.d.ts.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  24. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
  28. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +41 -3
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +175 -14
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  40. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
  43. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
  45. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +4 -2
  47. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +90 -13
  49. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
  51. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
  53. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
  55. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
  57. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  59. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  61. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
  63. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
  65. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  69. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  72. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
  74. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
  78. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +91 -43
  80. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +41 -0
  82. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +43 -0
  84. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
  85. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +200 -0
  86. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
  87. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +203 -0
  88. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
  89. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +81 -0
  90. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
  91. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +93 -0
  92. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
  93. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
  94. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  95. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
  96. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  97. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
  99. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
  101. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
  103. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
  105. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
  113. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  116. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
  117. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  118. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  121. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  123. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  124. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  125. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  126. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
  127. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  128. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
  129. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  130. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +71 -2
  131. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  132. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  133. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  134. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  135. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
  137. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  138. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
  139. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  140. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
  141. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  142. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
  143. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  144. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
  146. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +41 -17
  148. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  149. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  150. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  151. package/dist/knowledge/manifest.json +8 -8
  152. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
  153. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  154. package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
  155. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
  156. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  157. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  158. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +261 -34
  159. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
  160. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -59
  161. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  162. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
  163. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
  164. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
  165. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
  166. package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
  167. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
  168. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  169. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  170. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +129 -17
  171. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
  172. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
  173. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
  174. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
  175. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
  176. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  177. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
  178. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
  179. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
  180. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  181. package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
  182. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
  183. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  184. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  185. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  186. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  187. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +75 -37
  188. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
  189. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
  190. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -0
  191. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
  192. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
  193. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +99 -0
  194. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
  195. package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
  196. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -0
  197. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  198. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  199. package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
  200. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
  201. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  202. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  203. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
  204. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
  205. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
  206. package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
  207. package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
  208. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
  209. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  210. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  211. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  212. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  213. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  214. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
  215. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  216. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  217. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
  218. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  219. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  220. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  221. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  222. package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
  223. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
  224. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
  225. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +29 -0
  226. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
  227. package/dist/knowledge/references/brand.name-choice.config.md +144 -0
  228. package/dist/knowledge/references/brand.name-screening.config.md +308 -0
  229. package/dist/knowledge/references/build-plan.task-graph.config.md +119 -11
  230. package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
  231. package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
  232. package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
  233. package/dist/knowledge/references/capability-composition.config.md +67 -4
  234. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  235. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  236. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  237. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
  238. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  239. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
  240. package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
  241. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  242. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  243. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  244. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  245. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  246. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  247. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  248. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
  249. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  250. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  251. package/dist/knowledge/references/experience-plan.config.md +60 -7
  252. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  253. package/dist/knowledge/references/market.snapshot.validation.md +1 -1
  254. package/dist/knowledge/references/placement-plan.config.md +43 -0
  255. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  256. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  257. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  258. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  259. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  260. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  261. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  262. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  263. package/dist/knowledge/references/saas.backend.email.send.md +77 -0
  264. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  265. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
  266. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  267. package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
  268. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  269. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
  270. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
  271. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
  272. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
  273. package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
  274. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
  275. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
  276. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  277. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
  278. package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
  279. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
  280. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
  281. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
  282. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  283. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  284. package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
  285. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
  286. package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
  287. package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
  288. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  289. package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
  290. package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
  291. package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
  292. package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
  293. package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
  294. package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
  295. package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
  296. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  297. package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
  298. package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
  299. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  300. package/dist/knowledge/references/website-plan.config.md +26 -0
  301. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
  302. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
  303. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  304. package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
  305. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
  306. package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
  307. package/dist/knowledge/references/zod.factories.code.md +1 -0
  308. package/dist/knowledge/references/zod.factories.duration.md +1 -0
  309. package/dist/knowledge/references/zod.factories.money.md +1 -0
  310. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  311. package/dist/knowledge/registries/framework-topics.json +374 -1
  312. package/dist/knowledge/registries/playbooks.json +76 -28
  313. package/dist/knowledge/registries/source-tags.json +1513 -898
  314. package/dist/knowledge/rules/live-context-door.md +5 -2
  315. package/dist/knowledge/skills/INDEX.md +5 -2
  316. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  317. package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
  318. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  319. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  320. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  321. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
  322. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
  323. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  324. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
  325. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
  326. package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
  327. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
  328. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
  329. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
  330. package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
  331. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
  332. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
  333. package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
  334. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  335. package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
  336. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
  337. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
  338. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
  339. package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
  340. package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
  341. package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
  342. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  343. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
  344. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  345. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  346. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  347. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
  348. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
  349. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
  350. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
  351. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
  352. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
  353. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
  354. package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
  355. package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
  356. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
  357. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
  358. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
  359. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
  360. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  361. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  362. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  363. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  364. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  365. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
  366. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
  367. package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
  368. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
  369. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  370. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  371. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  372. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  373. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  374. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  375. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  376. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  377. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
  378. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
  379. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  380. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
  381. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  382. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
  383. package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
  384. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  385. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
  386. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
  387. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
  388. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
  389. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  390. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
  391. package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
  392. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
  393. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
  394. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
  395. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
  396. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
  397. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  398. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
  399. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
  400. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  401. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
  402. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
  403. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
  404. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
  405. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
  406. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  407. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
  408. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
  409. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
  410. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
  411. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  412. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  413. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  414. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
  415. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
  416. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
  417. package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
  418. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  419. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
  420. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  421. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
  422. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
  423. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
  424. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  425. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
  426. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  427. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
  428. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  429. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  430. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  431. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  432. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  433. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  434. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
  435. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  436. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  437. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
  438. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
  439. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
  440. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
  441. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
  442. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
  443. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
  444. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
  445. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
  446. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
  447. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
  448. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
  449. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
  450. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
  451. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
  452. package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
  453. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
  454. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
  455. package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
  456. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
  457. package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
  458. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
  459. package/dist/knowledge/skills/website-section-faq/SKILL.md +21 -1
  460. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
  461. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +21 -1
  462. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
  463. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +25 -2
  464. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
  465. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
  466. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
  467. package/dist/knowledge/skills/website-section-hero/SKILL.md +33 -10
  468. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
  469. package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
  470. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
  471. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +27 -2
  472. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
  473. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +16 -4
  474. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
  475. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
  476. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
  477. package/dist/knowledge/topic-index.json +1590 -292
  478. package/dist/tsconfig.build.tsbuildinfo +1 -1
  479. package/dist/tsconfig.tsbuildinfo +1 -1
  480. package/package.json +4 -4
@@ -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-business-model-lite-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/business-model-grounding-and-plan-coherence"],"requirementRef":"application-creation:authority-requirement/business-model-result","requirementVersion":1,"riskClassRef":"application-creation:risk/business-model-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/business-model","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/business-model-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/business-model","policyVersion":1},"decisionPointRef":"application-creation:decision-point/business-model-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/business-model-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/business-model","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/business-model-lite-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-business-model-change","triggerRefs":["application-creation:trigger/business-model-lite-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-business-model-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/business-model-grounding-and-plan-coherence"],"hardFloorRef":"application-creation:hard-floor/business-model-lite-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/business-model-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/business-model","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-business-model-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"instruction":"Assess whether the business model is GROUNDED in what the creator actually stated and coherent with the accepted market and requirements truth: every plan traceable to the interview, every targeted ICP present in the market snapshot, every unlocked requirement present in the requirements snapshot, and the revenue model consistent with the plans beneath it. Treat an invented price, an invented tier, or a price the creator said was undecided as a GAP — this family exists to carry the creator's commercial intent, not the evaluator's.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The model is usable but carries explicit commercial uncertainty the creator left open.","GAP":"A plan, price or tier appears that the creator did not state, or a cross-link names an ICP or requirement that does not exist.","INDETERMINATE":"The interview answers or the accepted market/requirements evidence are absent, stale or insufficient.","PASS":"Every plan traces to what the creator stated, and the cross-links resolve against the accepted market and requirements truth."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/business-model","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.business-model"},"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/business-model","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-business-model-inputs-and-candidate","criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":5,"minCount":4,"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-vision-and-business-model-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-business-model-lite-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/business-model-grounding-and-plan-coherence"],"requirementRef":"application-creation:authority-requirement/business-model-result","requirementVersion":1,"riskClassRef":"application-creation:risk/business-model-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/business-model","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/business-model-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/business-model","policyVersion":1},"decisionPointRef":"application-creation:decision-point/business-model-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/business-model-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/business-model","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/business-model-lite-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-business-model-change","triggerRefs":["application-creation:trigger/business-model-lite-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-business-model-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/business-model-grounding-and-plan-coherence"],"hardFloorRef":"application-creation:hard-floor/business-model-lite-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/business-model-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/business-model","definitionVersion":2,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-business-model-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1}],"instruction":"Assess whether the business model is GROUNDED in what the creator actually stated and coherent with the accepted market and requirements truth. First check that `pricingTiers` matches the pricing-tiers answer: \"creator_stated\" when the creator named tiers, \"proposed\" when the creator asked for tiers to be proposed, \"undecided\" when the creator said the tiers are not decided and asked for no proposal. Then, per status: a \"creator_stated\" plan must trace to a tier the creator named; a \"proposed\" plan is legitimate BECAUSE the creator asked for it, and must carry a `proposalBasis` that names an ICP present in the market snapshot and requirements present in the requirements snapshot; an \"undecided\" sketch has no plans, and that is a complete, honest artifact. Across every status: every targeted ICP and unlocked requirement must exist, the revenue model must be consistent with the plans (an empty undecided sketch is consistent with any revenue model), and no plan may carry a price or scaling axis the creator did not state — not even a proposed one. Treat as a GAP: an invented price or scaling axis; a creator-stated plan the creator never named; a status that contradicts the interview (for example \"undecided\" when the creator named tiers, or plans present when the creator neither named nor asked for them); a proposal with no basis. This family exists to carry the creator's commercial intent, not the evaluator's.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The model is faithful to the interview but a cross-link or a proposal basis is weaker than the accepted truth supports. An undecided answer the creator chose is NOT a concern — it is the honest artifact.","GAP":"A price, scaling axis or stated tier appears that the creator did not give; the tiers status contradicts the interview; a proposal has no basis; or a cross-link names an ICP or requirement that does not exist.","INDETERMINATE":"The interview answers or the accepted market/requirements evidence are absent, stale or insufficient.","PASS":"The tiers status matches the interview; every stated plan traces to what the creator named, every proposed plan carries a basis in the accepted market and requirements truth, an undecided sketch carries no plans, no price or scaling axis is invented, and every cross-link resolves."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/business-model","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.business-model"},"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/business-model","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-business-model-inputs-and-candidate","criterionRef":"application-creation:criterion/business-model-grounding-and-plan-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":5,"minCount":4,"requirementRef":"application-creation:evidence-requirement/business-model-grounding-and-plan-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/market-vision-and-business-model-candidate"}],"schemaVersion":1}
@@ -54,6 +54,52 @@ Concretely:
54
54
  - **"Not decided yet" is an answer.** Record what they *did* decide and leave
55
55
  the rest absent. Absence is legible; an invention is not.
56
56
 
57
+ ## Where the tiers came from: `pricingTiers`
58
+
59
+ The tiers answer has exactly three honest readings, and you record which one it
60
+ was. This status is what lets an empty sketch be an answer instead of a gap.
61
+
62
+ | The creator said | `pricingTiers` | `plans` |
63
+ |---|---|---|
64
+ | named one or more tiers ("one tier" counts) | `creator_stated` | exactly the tiers they named, `proposalBasis: null` on each |
65
+ | asked for tiers to be proposed ("propose them", "derive them from the market research") | `proposed` | your proposal, each plan with a `proposalBasis` |
66
+ | the tiers are not decided, and asked for no proposal | `undecided` | **empty** |
67
+
68
+ A creator who says "not decided — let the plan propose them" has asked for a
69
+ proposal: that is `proposed`, not `undecided`. Read the whole answer, not its
70
+ first words.
71
+
72
+ ### An undecided sketch is complete
73
+
74
+ `undecided` with no plans, plus the `revenueModel` they chose, IS the artifact.
75
+ Do not add a placeholder tier to make it look fuller. The revenue model still
76
+ tells every reader how the product makes money, so an empty `plans` never means
77
+ "free" or "no billing".
78
+
79
+ ### A proposal is work the creator delegated, and it stays marked as one
80
+
81
+ When the creator asks for a proposal, deriving tiers is the job, not an
82
+ invention. Derive them from what the inputs hold:
83
+
84
+ - **one tier per ICP that would pay differently.** The market snapshot's ICPs
85
+ are the segments; a tier exists because a segment needs a different package,
86
+ never because three tiers is customary. An anti-target the vision excludes
87
+ gets no tier.
88
+ - **what separates each tier is a set of requirements.** Put the requirement
89
+ refs it unlocks in `includesRequirementRefs`, and say in `includes` what it
90
+ holds back relative to the tier beside it.
91
+ - **`proposalBasis` names the evidence**: the ICP ref it serves and the
92
+ requirements that distinguish it ("serves icp-indie-maker; holds back the
93
+ team-planning requirements the Team tier unlocks"). A proposal with no basis
94
+ is a tier nobody can check.
95
+ - **A proposal still never sets a price or a scaling axis.** Unless the creator
96
+ stated one, `pricePoint`, `billingPeriod` and `pricingModel` are `null` on a
97
+ proposed plan exactly as on a stated one. The creator delegated the tiers, not
98
+ the prices.
99
+
100
+ The creator accepts or revises the proposal at the approval step; you do not
101
+ need to be cautious on their behalf by proposing nothing.
102
+
57
103
  ## What you DO derive
58
104
 
59
105
  Two things, and both are cross-links rather than content:
@@ -106,9 +152,10 @@ One output, the `business-model` family. The contract is strict:
106
152
  creator described. If they described something genuinely outside the set, pick
107
153
  the nearest and explain the mismatch in the plans' prose — do not stretch a
108
154
  member past its meaning.
109
- - **At least one plan.** A business model with no plans carries no information a
110
- reader could act on. If the creator sells exactly one thing, that is one plan,
111
- fully described.
155
+ - **`pricingTiers` is required**, and it decides how many plans there are (see
156
+ the table above). `creator_stated` and `proposed` carry at least one plan;
157
+ `undecided` carries none. If the creator sells exactly one thing, that is one
158
+ `creator_stated` plan, fully described.
112
159
  - **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted
113
160
  runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.
114
161
  - **Every optional field is nullable and required.** Send `null` where the
@@ -117,12 +164,19 @@ One output, the `business-model` family. The contract is strict:
117
164
 
118
165
  ## Verification before you answer
119
166
 
120
- - [ ] Every `pricePoint` traces to something the creator actually wrote.
121
- - [ ] Every plan traces to a tier they described. No tier count was rounded up.
167
+ - [ ] `pricingTiers` is the reading of the tiers answer from the table above.
168
+ - [ ] Every `pricePoint` and `pricingModel` traces to something the creator
169
+ actually wrote — on a proposed plan too.
170
+ - [ ] Every `creator_stated` plan traces to a tier they described. No tier count
171
+ was rounded up.
172
+ - [ ] Every `proposed` plan carries a `proposalBasis` naming an ICP and the
173
+ requirements that separate it; every `creator_stated` plan carries none.
174
+ - [ ] An `undecided` sketch has no plans, and no placeholder was added.
122
175
  - [ ] Every `targetIcpRefs` entry exists in the market snapshot.
123
176
  - [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.
124
177
  - [ ] No ICP the vision constraints exclude is targeted.
125
178
  - [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`
126
179
  classification with no free plan, or a `subscription` with only a one-off
127
- purchase, is incoherent.
180
+ purchase, is incoherent. An `undecided` sketch with no plans is coherent
181
+ with any revenue model.
128
182
  - [ ] Nothing in the artifact answers a question the creator left open.
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "top_down.business-model",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "top_down",
5
- "intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
5
+ "intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model, where its pricing tiers came from (stated by the creator, proposed at the creator's request, or not decided yet), and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_valid",
@@ -39,12 +39,12 @@
39
39
  {
40
40
  "family": "business-model",
41
41
  "schemaRef": "saas-specifications:BusinessModelLiteSnapshot",
42
- "description": "A validated revenue-model classification plus at least one pricing plan, each cross-linked to the market ICPs it targets and the requirements it unlocks."
42
+ "description": "A validated revenue-model classification, the status of the pricing tiers (creator-stated, proposed for the creator's review, or undecided), and the pricing plans that status implies — none when undecided — each cross-linked to the market ICPs it targets and the requirements it unlocks."
43
43
  }
44
44
  ],
45
45
  "stepOutputs": [],
46
46
  "method": {
47
- "guidance": "# Business Model — Commercial Intent 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.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **At least one plan.** A business model with no plans carries no information a\n reader could act on. If the creator sells exactly one thing, that is one plan,\n fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] Every `pricePoint` traces to something the creator actually wrote.\n- [ ] Every plan traces to a tier they described. No tier count was rounded up.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
47
+ "guidance": "# Business Model — Commercial Intent 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.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## Where the tiers came from: `pricingTiers`\n\nThe tiers answer has exactly three honest readings, and you record which one it\nwas. This status is what lets an empty sketch be an answer instead of a gap.\n\n| The creator said | `pricingTiers` | `plans` |\n|---|---|---|\n| named one or more tiers (\"one tier\" counts) | `creator_stated` | exactly the tiers they named, `proposalBasis: null` on each |\n| asked for tiers to be proposed (\"propose them\", \"derive them from the market research\") | `proposed` | your proposal, each plan with a `proposalBasis` |\n| the tiers are not decided, and asked for no proposal | `undecided` | **empty** |\n\nA creator who says \"not decided — let the plan propose them\" has asked for a\nproposal: that is `proposed`, not `undecided`. Read the whole answer, not its\nfirst words.\n\n### An undecided sketch is complete\n\n`undecided` with no plans, plus the `revenueModel` they chose, IS the artifact.\nDo not add a placeholder tier to make it look fuller. The revenue model still\ntells every reader how the product makes money, so an empty `plans` never means\n\"free\" or \"no billing\".\n\n### A proposal is work the creator delegated, and it stays marked as one\n\nWhen the creator asks for a proposal, deriving tiers is the job, not an\ninvention. Derive them from what the inputs hold:\n\n- **one tier per ICP that would pay differently.** The market snapshot's ICPs\n are the segments; a tier exists because a segment needs a different package,\n never because three tiers is customary. An anti-target the vision excludes\n gets no tier.\n- **what separates each tier is a set of requirements.** Put the requirement\n refs it unlocks in `includesRequirementRefs`, and say in `includes` what it\n holds back relative to the tier beside it.\n- **`proposalBasis` names the evidence**: the ICP ref it serves and the\n requirements that distinguish it (\"serves icp-indie-maker; holds back the\n team-planning requirements the Team tier unlocks\"). A proposal with no basis\n is a tier nobody can check.\n- **A proposal still never sets a price or a scaling axis.** Unless the creator\n stated one, `pricePoint`, `billingPeriod` and `pricingModel` are `null` on a\n proposed plan exactly as on a stated one. The creator delegated the tiers, not\n the prices.\n\nThe creator accepts or revises the proposal at the approval step; you do not\nneed to be cautious on their behalf by proposing nothing.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **`pricingTiers` is required**, and it decides how many plans there are (see\n the table above). `creator_stated` and `proposed` carry at least one plan;\n `undecided` carries none. If the creator sells exactly one thing, that is one\n `creator_stated` plan, fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] `pricingTiers` is the reading of the tiers answer from the table above.\n- [ ] Every `pricePoint` and `pricingModel` traces to something the creator\n actually wrote — on a proposed plan too.\n- [ ] Every `creator_stated` plan traces to a tier they described. No tier count\n was rounded up.\n- [ ] Every `proposed` plan carries a `proposalBasis` naming an ICP and the\n requirements that separate it; every `creator_stated` plan carries none.\n- [ ] An `undecided` sketch has no plans, and no placeholder was added.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent. An `undecided` sketch with no plans is coherent\n with any revenue model.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
48
48
  "skillRefs": [],
49
49
  "skillBodyRefs": [],
50
50
  "elicitation": {
@@ -60,27 +60,32 @@
60
60
  "freemium",
61
61
  "marketplace_commission",
62
62
  "advertising"
63
- ]
63
+ ],
64
+ "depth": "essential"
64
65
  },
65
66
  {
66
67
  "ref": "pricing-tiers",
67
- "question": "What tiers or packages do you plan to sell? Name each one and say who it is for. Answer \"one tier\" if there is only one.",
68
- "kind": "free_text"
68
+ "question": "What tiers or packages do you plan to sell? Name each one and say who it is for — answer \"one tier\" if there is only one. Answer \"not decided yet\" if you have not chosen, or \"propose them\" to have tiers proposed from the market research and requirements for you to review (a proposal never sets a price).",
69
+ "kind": "free_text",
70
+ "depth": "detail"
69
71
  },
70
72
  {
71
73
  "ref": "pricing-scaling-axis",
72
74
  "question": "What does the price scale with — seats, usage, a flat fee, or is it negotiated per customer? Answer \"not decided yet\" if you have not chosen.",
73
- "kind": "free_text"
75
+ "kind": "free_text",
76
+ "depth": "detail"
74
77
  },
75
78
  {
76
79
  "ref": "price-points",
77
80
  "question": "Do you already have price points in mind for those tiers? Give them as you would write them (\"$29 / user / month\", \"contact us\"). Answer \"not decided yet\" if not — a tier with no price is still a real plan.",
78
- "kind": "free_text"
81
+ "kind": "free_text",
82
+ "depth": "detail"
79
83
  },
80
84
  {
81
85
  "ref": "free-tier",
82
86
  "question": "Is there a free tier or trial? If so, what does it include, and what is deliberately held back for the paid tiers?",
83
- "kind": "free_text"
87
+ "kind": "free_text",
88
+ "depth": "detail"
84
89
  }
85
90
  ]
86
91
  },
@@ -171,17 +171,18 @@ Keep this playbook at scaffold depth. Explicitly **out of scope here**:
171
171
  The scoring seam stays pluggable — do NOT build or tune a scoring or
172
172
  build-order model in this playbook.
173
173
  - **Deep feature-spec drafts.** A draft here is a first-cut capability contract
174
- (purpose / roles / use-when). Rich operation inventories, interaction
175
- semantics, and UX are the bottom-up build phase's job, not the capability map.
176
- - **Requirement pain/gain traceability.** A requirement today cross-refs ICPs and
177
- jobs but NOT market pains/gains, so the "this requirement delivers
178
- `gain-X`" trace that would let capability mapping run benefit → requirement →
179
- feature *deterministically* is lossy (expressible only in prose). Whether the
180
- requirements family should gain a pain/gain edge is a filed depth-phase
181
- question — do NOT reshape the requirements contract here.
174
+ (purpose / roles / use-when). Rich operation inventories and UX are the
175
+ bottom-up build phase's job, not the capability map. The business verbs a
176
+ capability implies (accept, issue, close) are NOT deferred: the domain plan
177
+ declares them as lifecycles, so state them where a capability rests on them.
178
+ - **Requirement gain traceability.** A requirement cross-refs ICPs, jobs and the
179
+ market PAINS it relieves (`painRefs`), but not the gains it delivers, so a
180
+ "this requirement delivers `gain-X`" trace is expressible only in prose. Use
181
+ `painRefs` where a capability answers a pain; do NOT reshape the requirements
182
+ contract here to add a gain edge.
182
183
 
183
184
  If you find yourself perfecting any of the above, stop and leave the slice at
184
- scaffold depth — depth is a dedicated later pass done once, holistically.
185
+ scaffold depth.
185
186
 
186
187
  ## What you emit
187
188
 
@@ -51,7 +51,7 @@
51
51
  ],
52
52
  "stepOutputs": [],
53
53
  "method": {
54
- "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'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.\n\nThen you **assess fit** for the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below). This does not set build priority.\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 from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it.\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\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 Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.\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). You do\nnot run the scorer and must not estimate its output: the per-ICP FIT scores are\ncomputed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each\nbenefit's authored Kano category. Read them there and use them to sanity-check the\ncapability set — a `0` carrying a stated reason is structural (an anti-target, or no\nbenefit covering that ICP), not a measurement of poor fit. 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 The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.\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\nValidate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.\n\nA draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.\n\nValidation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.\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- **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\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `market-add-feature-benefit` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `spec-feature-update` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `market-scoring-interpretation` — 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- `market-snapshot-validation` — the full validation issue\n catalogue the quality gate enforces.\n",
54
+ "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'>`). Use the **Draft path** in `spec-feature-update`; its runtime workflow is for a later implementation task. The draft wrapper carries `featureRef`, while the nested prose payload remains ref-less.\n\nThen you **assess fit** for the resulting feature set with a FIT-scoring + Kano\nstep — kept pluggable and versioned (see \"The scoring seam\" below). This does not set build priority.\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 from what this run is given — the loaded\n specifications and the workspace sections of your brief — and do not re-derive it.\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\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 Use the **Draft path** in `spec-feature-update`, including its wrapper and export contract. Do not run its runtime-enum, definition, policy or profile steps. Keep this a capability contract, not an implementation.\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). You do\nnot run the scorer and must not estimate its output: the per-ICP FIT scores are\ncomputed for you and arrive in the declared `market_fit_scores` context section of your brief, beside each\nbenefit's authored Kano category. Read them there and use them to sanity-check the\ncapability set — a `0` carrying a stated reason is structural (an anti-target, or no\nbenefit covering that ICP), not a measurement of poor fit. 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 The combined output validator checks benefit references against existing feature identities plus the proposed draft wrappers. Supply `existingFeatureRefs` from the actual existing definitions when using `validateCapabilityMapOutputSet` directly; never invent references to make validation pass.\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\nValidate the connected output with `validateCapabilityMapOutputSet`. It parses the output shape, joins existing feature references with proposed draft identities, checks the market snapshot, and calls `validateFeatureSpecificationDrafts` for duplicate identities and each draft's prose contract. The result reports issues from both destinations.\n\nA draft payload is ref-less; its wrapper still supplies the stable `featureRef` needed for these checks. Missing feature links are not exempt merely because runtime definitions have not been created. Market pain/gain/job references and positioning/threshold checks still apply; read `market-snapshot-validation` for their detailed meanings.\n\nValidation is not product review or evidence that the capability has been implemented. Inspect the proposed benefit links and draft intent together before accepting the proposal.\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 and UX are the\n bottom-up build phase's job, not the capability map. The business verbs a\n capability implies (accept, issue, close) are NOT deferred: the domain plan\n declares them as lifecycles, so state them where a capability rests on them.\n- **Requirement gain traceability.** A requirement cross-refs ICPs, jobs and the\n market PAINS it relieves (`painRefs`), but not the gains it delivers, so a\n \"this requirement delivers `gain-X`\" trace is expressible only in prose. Use\n `painRefs` where a capability answers a pain; do NOT reshape the requirements\n contract here to add a gain edge.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth.\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\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n- `market-add-feature-benefit` — author/adjust the benefit\n claims and wire their `deliveredByFeatureRefs` edges.\n- `spec-feature-update` — author the spec-first\n `FeatureSpecificationDraft`(s) for the new delivering features.\n- `market-scoring-interpretation` — 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- `market-snapshot-validation` — the full validation issue\n catalogue the quality gate enforces.\n",
55
55
  "skillRefs": [
56
56
  "market-add-feature-benefit",
57
57
  "market-scoring-interpretation",
@@ -27,52 +27,72 @@
27
27
  {
28
28
  "ref": "handles-regulated-data",
29
29
  "question": "Does the product store, process, or transmit personal data or otherwise regulated data (health, financial, biometric, children's, government) — either from end users or on behalf of customers?",
30
- "kind": "confirm"
30
+ "kind": "confirm",
31
+ "depth": "detail",
32
+ "regulatedDomain": true
31
33
  },
32
34
  {
33
35
  "ref": "data-classes",
34
36
  "question": "Which classes of sensitive data does the product touch? List them (e.g. names/emails, health records, payment card data, government IDs, precise location, employee data). Answer \"none\" if it handles no personal or sensitive data.",
35
- "kind": "free_text"
37
+ "kind": "free_text",
38
+ "depth": "detail",
39
+ "regulatedDomain": true
36
40
  },
37
41
  {
38
42
  "ref": "vendor-establishment",
39
43
  "question": "Where is the VENDOR established — the legal entity (or intended entity) operating the product, its country/region, and where is the product hosted or planned to be hosted? Territorial-scope tests (GDPR Art. 3, UK GDPR, CCPA \"doing business\") turn on the vendor's establishment and conduct, not only on where users live. Answer \"not yet decided\" for whatever is genuinely open.",
40
- "kind": "free_text"
44
+ "kind": "free_text",
45
+ "depth": "essential",
46
+ "regulatedDomain": true
41
47
  },
42
48
  {
43
49
  "ref": "jurisdictions",
44
50
  "question": "In which jurisdictions do your users live and your data reside or transit (e.g. EU/EEA, UK, US, California, Canada, specific countries)? This is what drives which privacy regimes apply.",
45
- "kind": "free_text"
51
+ "kind": "free_text",
52
+ "depth": "essential",
53
+ "regulatedDomain": true
46
54
  },
47
55
  {
48
56
  "ref": "sector",
49
57
  "question": "Does the product operate in a regulated sector with its own rules (healthcare, finance/banking, insurance, education, government, telecoms)? Name the sector, or answer \"none\".",
50
- "kind": "free_text"
58
+ "kind": "free_text",
59
+ "depth": "detail",
60
+ "regulatedDomain": true
51
61
  },
52
62
  {
53
63
  "ref": "gdpr-applies",
54
64
  "question": "Do you serve EU/EEA (or UK) individuals or process their personal data? (This is the primary trigger for GDPR / UK GDPR.)",
55
- "kind": "confirm"
65
+ "kind": "confirm",
66
+ "depth": "detail",
67
+ "regulatedDomain": true
56
68
  },
57
69
  {
58
70
  "ref": "hipaa-applies",
59
71
  "question": "Do you handle US protected health information as, or on behalf of, a covered entity or business associate? (This is the primary trigger for HIPAA.)",
60
- "kind": "confirm"
72
+ "kind": "confirm",
73
+ "depth": "detail",
74
+ "regulatedDomain": true
61
75
  },
62
76
  {
63
77
  "ref": "external-assurance-applies",
64
78
  "question": "Do enterprise customers (or your own security posture) require an independent attestation or certification covering security / availability / confidentiality of the service? Name the requested target only as an external source requirement.",
65
- "kind": "confirm"
79
+ "kind": "confirm",
80
+ "depth": "detail",
81
+ "regulatedDomain": true
66
82
  },
67
83
  {
68
84
  "ref": "data-residency",
69
85
  "question": "Are there data-residency or sovereignty requirements — must certain data stay within a region or country (e.g. EU-only hosting, in-country storage)? Describe them, or answer \"none\".",
70
- "kind": "free_text"
86
+ "kind": "free_text",
87
+ "depth": "detail",
88
+ "regulatedDomain": true
71
89
  },
72
90
  {
73
91
  "ref": "additional-regimes",
74
92
  "question": "Any other legal regimes, sector frameworks, government programs, or contractual security commitments that apply? List the externally named sources, or answer \"none\".",
75
- "kind": "free_text"
93
+ "kind": "free_text",
94
+ "depth": "detail",
95
+ "regulatedDomain": true
76
96
  }
77
97
  ]
78
98
  },
@@ -43,7 +43,9 @@
43
43
  {
44
44
  "ref": "undetermined-and-gaps",
45
45
  "question": "What is genuinely undetermined — something you cannot answer today without more work? List them. These become explicit UNDETERMINED applicability or stated limitations rather than silent omissions.",
46
- "kind": "free_text"
46
+ "kind": "free_text",
47
+ "depth": "essential",
48
+ "regulatedDomain": true
47
49
  }
48
50
  ]
49
51
  },
@@ -28,7 +28,10 @@
28
28
  {
29
29
  "family": "vision-brief",
30
30
  "schemaRef": "saas-specifications:VisionSnapshot",
31
- "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."
31
+ "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.",
32
+ "aspects": [
33
+ "vision.constraint"
34
+ ]
32
35
  }
33
36
  ],
34
37
  "stepOutputs": [],
@@ -42,7 +42,10 @@ The chain, each leaf gated by the families the ones before it land:
42
42
  Beside the chain, needing the vision (and the business model, for the register) and
43
43
  needed by nothing downstream of this lane:
44
44
 
45
- - **`top_down.brand-identity`** — the visual identity, from the creator's answers.
45
+ - **`top_down.brand-naming`** — a nested lane: proposes names and runs a minimal trademark
46
+ screening of each, landing the `brand-name-screening`. Needs the market snapshot.
47
+ - **`top_down.brand-identity`** — the visual identity, from the creator's answers. Its
48
+ `brand-name` is a CHOICE among the screened names, so it runs after the naming lane.
46
49
  - **`top_down.risk-register`** — the register the assurance mechanisms read.
47
50
 
48
51
  Nothing above is a sequence. Each child declares what it needs, and the runtime
@@ -55,8 +58,10 @@ whatever is not.
55
58
  The selector is shown the accepted truth for the families this lane declares — the
56
59
  vision whole, the others as a map of what exists — and the children that may run.
57
60
 
58
- - **Missing beats present.** A family already on record is not re-derived, unless a
59
- family it was derived from has been re-derived in this run.
61
+ - **Missing beats present.** A child already on record whose inputs have not changed
62
+ since it landed is not offered at all. Every option is marked FIRST RUN, or REFRESH
63
+ with the input that moved and the run that moved it. Prefer first runs; take a
64
+ refresh when the change it names matters to that child.
60
65
  - **Independent children share a round.** The brand identity and the risk register
61
66
  ride beside the chain; several research lanes with genuinely different objectives
62
67
  return more than one asked everything.
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "top_down.definition",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "top_down",
5
- "intent": "Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand identity and the risk register beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves' preconditions and never a list. Select what is MISSING from the accepted truth shown to you: a family already on record is not re-derived unless a family it was derived from has been re-derived in this run. Run independent children in the same round (brand identity and the risk register beside the chain; several research lanes with different objectives). Run the phase gate once the roadmap is on record, and STOP after it has run — its verdict is this lane's closing decision, and it is not re-run in the same run. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the definition.",
5
+ "intent": "Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand naming (screened name proposals), the brand identity and the risk register beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves' preconditions and never a list. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. Prefer first runs; take a refresh when its changed input matters to it. Run independent children in the same round (brand naming or the brand identity, and the risk register beside the chain; several research lanes with different objectives). Run the phase gate once the roadmap is on record, and STOP after it has run — its verdict is this lane's closing decision, and it is not re-run in the same run. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the definition.",
6
6
  "preconditions": [],
7
7
  "inputs": [
8
8
  {
@@ -44,7 +44,7 @@
44
44
  }
45
45
  ],
46
46
  "method": {
47
- "guidance": "# The Definition Lane — 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 drives the leaves that DEFINE the\napplication — what it is, for whom, against which market, delivering which\nrequirements, in which order, sold how — and it ends on the phase gate's verdict,\nwhich is the lane's closing decision.\n\n## The children, and why the order is not written here\n\nThe chain, each leaf gated by the families the ones before it land:\n\n- **`top_down.vision-elicitation`** — the vision brief, from the creator's own\n answers. No precondition: the lane starts here on a fresh application.\n- **`top_down.market-analysis`** — a NESTED LANE, not a leaf: it gathers web evidence,\n judges whether it is enough, and lands the `market-snapshot` only once the verdict is\n `adequate`, re-searching against the gaps the gate named for as long as it needs. Its\n evidence loop is its own business; this lane sees only that a market snapshot landed.\n- **`top_down.value-proposition`** — refines the same snapshot: benefits, tones of\n voice, one positioning pillar per targeted ICP.\n- **`top_down.requirements-definition`** — the requirements, from vision and market.\n- **`top_down.capability-map`** — benefit → feature edges on the snapshot, and the\n feature drafts.\n- **`top_down.business-model`** — revenue model and pricing plans, from the creator's\n pricing intent.\n- **`top_down.scope-roadmap`** — the phases that deliver or defer the requirements and\n the success criteria.\n- **`top_down.phase-gate`** — five criteria over the coherence report. Lands nothing;\n its verdict is what this lane ends on.\n\nBeside the chain, needing the vision (and the business model, for the register) and\nneeded by nothing downstream of this lane:\n\n- **`top_down.brand-identity`** — the visual identity, from the creator's answers.\n- **`top_down.risk-register`** — the register the assurance mechanisms read.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. That is what makes the lane re-runnable\non an application where most of it exists: whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next children\n\nThe selector is shown the accepted truth for the families this lane declares — the\nvision whole, the others as a map of what exists — and the children that may run.\n\n- **Missing beats present.** A family already on record is not re-derived, unless a\n family it was derived from has been re-derived in this run.\n- **Independent children share a round.** The brand identity and the risk register\n ride beside the chain; several research lanes with genuinely different objectives\n return more than one asked everything.\n- **A child whose interview is unanswered is not offered.** The dossier answers the\n creator's questions per leaf; a leaf the dossier does not cover waits for the creator,\n and the lane runs everything else it can.\n- **The phase gate runs once, last, then the lane stops.** It lands nothing and returns\n nothing the runtime can mark delivered, so the round history is the record that it\n ran.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. For a research child the\nmarket umbrella's rule holds: the first round broad, a later round naming the gap the\ngate named. For a chain leaf the objective names what changed upstream since its output\nlast landed — a re-derived market snapshot, a revised vision — so the leaf refines\nrather than restarts.\n\n## When to stop\n\nStop when the phase gate has run: its verdict is the decision. Stop also when nothing\neligible advances the definition — every remaining child is waiting for the creator, or\nthe evidence gate has named the same gap twice and a further round could not close it.\nSay which, in the rationale.\n\n## What the phase gate's verdict re-opens\n\nThe lane declares this table, and the runtime applies it: a GAP on one of the first four\ncriteria offers the mapped leaf again, even though it already landed in this run. When a\nleaf you have already seen land is eligible again after the gate, that is this loop-back,\nnot churn. Re-run that leaf against the gate's rationale for the faulted criterion, then run\nthe gate again. A PASS re-opens nothing, and CONCERN or INDETERMINATE re-open nothing\neither: re-deriving a leaf does not answer advice, and it does not produce evidence.\n\n| criterion | re-opens |\n|---|---|\n| requirement coverage | `top_down.scope-roadmap` |\n| success-criterion coverage | `top_down.scope-roadmap` |\n| capability completeness | `top_down.capability-map` |\n| positioning / ICP coherence | `top_down.value-proposition` |\n| compliance presence | the compliance lane, which this lane does not admit — the root re-opens it, from this lane's exported verdict |\n\n## What the creator reviews\n\nThe definition set, family by family, exactly as each leaf's own review guide says —\nand the phase gate's verdict, which is the one decision this lane ends on: accept the\ndefinition, or send it back to the leaf the verdict names.\n",
47
+ "guidance": "# The Definition Lane — 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 drives the leaves that DEFINE the\napplication — what it is, for whom, against which market, delivering which\nrequirements, in which order, sold how — and it ends on the phase gate's verdict,\nwhich is the lane's closing decision.\n\n## The children, and why the order is not written here\n\nThe chain, each leaf gated by the families the ones before it land:\n\n- **`top_down.vision-elicitation`** — the vision brief, from the creator's own\n answers. No precondition: the lane starts here on a fresh application.\n- **`top_down.market-analysis`** — a NESTED LANE, not a leaf: it gathers web evidence,\n judges whether it is enough, and lands the `market-snapshot` only once the verdict is\n `adequate`, re-searching against the gaps the gate named for as long as it needs. Its\n evidence loop is its own business; this lane sees only that a market snapshot landed.\n- **`top_down.value-proposition`** — refines the same snapshot: benefits, tones of\n voice, one positioning pillar per targeted ICP.\n- **`top_down.requirements-definition`** — the requirements, from vision and market.\n- **`top_down.capability-map`** — benefit → feature edges on the snapshot, and the\n feature drafts.\n- **`top_down.business-model`** — revenue model and pricing plans, from the creator's\n pricing intent.\n- **`top_down.scope-roadmap`** — the phases that deliver or defer the requirements and\n the success criteria.\n- **`top_down.phase-gate`** — five criteria over the coherence report. Lands nothing;\n its verdict is what this lane ends on.\n\nBeside the chain, needing the vision (and the business model, for the register) and\nneeded by nothing downstream of this lane:\n\n- **`top_down.brand-naming`** — a nested lane: proposes names and runs a minimal trademark\n screening of each, landing the `brand-name-screening`. Needs the market snapshot.\n- **`top_down.brand-identity`** — the visual identity, from the creator's answers. Its\n `brand-name` is a CHOICE among the screened names, so it runs after the naming lane.\n- **`top_down.risk-register`** — the register the assurance mechanisms read.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. That is what makes the lane re-runnable\non an application where most of it exists: whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next children\n\nThe selector is shown the accepted truth for the families this lane declares — the\nvision whole, the others as a map of what exists — and the children that may run.\n\n- **Missing beats present.** A child already on record whose inputs have not changed\n since it landed is not offered at all. Every option is marked FIRST RUN, or REFRESH\n with the input that moved and the run that moved it. Prefer first runs; take a\n refresh when the change it names matters to that child.\n- **Independent children share a round.** The brand identity and the risk register\n ride beside the chain; several research lanes with genuinely different objectives\n return more than one asked everything.\n- **A child whose interview is unanswered is not offered.** The dossier answers the\n creator's questions per leaf; a leaf the dossier does not cover waits for the creator,\n and the lane runs everything else it can.\n- **The phase gate runs once, last, then the lane stops.** It lands nothing and returns\n nothing the runtime can mark delivered, so the round history is the record that it\n ran.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. For a research child the\nmarket umbrella's rule holds: the first round broad, a later round naming the gap the\ngate named. For a chain leaf the objective names what changed upstream since its output\nlast landed — a re-derived market snapshot, a revised vision — so the leaf refines\nrather than restarts.\n\n## When to stop\n\nStop when the phase gate has run: its verdict is the decision. Stop also when nothing\neligible advances the definition — every remaining child is waiting for the creator, or\nthe evidence gate has named the same gap twice and a further round could not close it.\nSay which, in the rationale.\n\n## What the phase gate's verdict re-opens\n\nThe lane declares this table, and the runtime applies it: a GAP on one of the first four\ncriteria offers the mapped leaf again, even though it already landed in this run. When a\nleaf you have already seen land is eligible again after the gate, that is this loop-back,\nnot churn. Re-run that leaf against the gate's rationale for the faulted criterion, then run\nthe gate again. A PASS re-opens nothing, and CONCERN or INDETERMINATE re-open nothing\neither: re-deriving a leaf does not answer advice, and it does not produce evidence.\n\n| criterion | re-opens |\n|---|---|\n| requirement coverage | `top_down.scope-roadmap` |\n| success-criterion coverage | `top_down.scope-roadmap` |\n| capability completeness | `top_down.capability-map` |\n| positioning / ICP coherence | `top_down.value-proposition` |\n| compliance presence | the compliance lane, which this lane does not admit — the root re-opens it, from this lane's exported verdict |\n\n## What the creator reviews\n\nThe definition set, family by family, exactly as each leaf's own review guide says —\nand the phase gate's verdict, which is the one decision this lane ends on: accept the\ndefinition, or send it back to the leaf the verdict names.\n",
48
48
  "skillRefs": [],
49
49
  "skillBodyRefs": [],
50
50
  "contextSources": [],
@@ -60,6 +60,7 @@
60
60
  "top_down.requirements-definition",
61
61
  "top_down.market-analysis",
62
62
  "top_down.vision-elicitation",
63
+ "top_down.brand-naming",
63
64
  "top_down.brand-identity",
64
65
  "top_down.risk-register"
65
66
  ],
@@ -108,7 +109,8 @@
108
109
  "top_down.value-proposition"
109
110
  ]
110
111
  }
111
- ]
112
+ ],
113
+ "closingMove": "top_down.phase-gate"
112
114
  },
113
115
  "suspendsForClarification": false,
114
116
  "briefAdequacyGate": false,
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.expert-personas",
3
- "version": "0.1.0",
3
+ "version": "0.2.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed is left alone (a human-edited charter is never overwritten), and a role whose shaping inputs have not landed yet is REPORTED as waiting rather than failing the run. Before this step existed the panel's staffing was not a journey step at all — every deliberated playbook failed closed at bind time on an application whose charters nobody had curled in by hand (#572).",
6
6
  "preconditions": [
@@ -23,9 +23,23 @@
23
23
  },
24
24
  {
25
25
  "family": "market-snapshot"
26
+ },
27
+ {
28
+ "family": "requirements"
29
+ },
30
+ {
31
+ "family": "business-model"
32
+ },
33
+ {
34
+ "family": "brand-brief"
35
+ }
36
+ ],
37
+ "outputs": [
38
+ {
39
+ "family": "expert-personas",
40
+ "description": "One accepted charter per expert role a convened panel seats (written by the companion's expert-persona accept as a charter module per role plus the personas aggregator, never by the generic landing renderer). A role whose shaping inputs have not landed is reported as waiting and staffed by a later run."
26
41
  }
27
42
  ],
28
- "outputs": [],
29
43
  "stepOutputs": [],
30
44
  "method": {
31
45
  "guidance": "# Expert personas — staff the panels the catalog convenes\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## What this step does\n\nSeveral steps of the creation journey are DECIDED BY A PANEL rather than by a single generation:\n`bottom_up.placement-plan` convenes an information architect and a design-system guardian, the logo\ngeneration step convenes an art director, a brand strategist and a design-system guardian. A panel is\nbuilt from **expert-persona charters** — one committed charter per framework expert role, derived from\nthis application's own vision, market, requirements, business model and brand, so a reviewer speaks\nfor THIS product rather than for a generic one.\n\nThis step derives and accepts those charters. It is runner-owned: no prompt is composed here. For every\nrole the catalog convenes (read off every playbook's `method.deliberation` and off the generation\nsteps' own panels), it runs the companion's derive → accept flow — a DRAFT, a CRITIQUE by a dedicated\ncritic, and a FINALIZE pass when the critique asks for one — then promotes the proposal into\n`specifications/src/personas/<role>.charter.generated.ts`, regenerates the aggregator and wires the\n`expertPersonaCharters` companion-exports slot.\n\n## What it will not do\n\n- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never\n replaced; the accept step refuses and the run reports it.\n- **Re-derive a committed charter.** A role that already has a committed charter is left alone; ask for a\n re-derivation explicitly through the companion's `expert-personas/derive` route if the application's\n definition moved enough to warrant one.\n- **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with\n no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.\n\n## Cost, so it is scheduled knowingly\n\nA derivation is an agentic three-pass protocol over the application's own artifacts: measured at about\n200 seconds per role on a real application. Five roles is a quarter of an hour. Submit the run detached.\n\n## What you read\n\nThe current journey state this run is given, to see which families have landed and\ntherefore which roles are derivable now.\n\n## Verification\n\n- `specifications/src/personas/` holds one `*.charter.generated.ts` per role the run reports as derived,\n and `index.ts` lists every one of them.\n- `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.\n- The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.\n",
@@ -45,8 +45,11 @@ the nested prose payload stays ref-less.
45
45
  it; do not fork it.
46
46
  - **Name the requirements each draft serves**, in its purpose or business-role prose, so the roadmap
47
47
  and the build decomposition can trace a capability back to what asked for it.
48
- - **Stay at scaffold depth.** A draft is a first-cut capability contract. Operations, screens and
49
- interaction semantics are the bottom-up build phase's work.
48
+ - **Stay at scaffold depth.** A draft is a first-cut capability contract. Screens and the
49
+ operations that implement it are the bottom-up build phase's work. But say what the capability
50
+ DOES in the business's verbs ("a sent quote can be accepted, and accepting it creates a job"):
51
+ the domain plan turns those verbs into lifecycles, and a draft that names none leaves it nothing
52
+ to read.
50
53
 
51
54
  ## Refine, don't re-author
52
55