@wildo-ai/framework-knowledge 1.1.9 → 1.1.11

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 (1163) 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/derived-artifacts.md +4 -2
  5. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  6. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +4 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  8. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +9 -3
  9. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  10. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  11. package/dist/esm/framework-knowledge.definitions.js +543 -80
  12. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  13. package/dist/esm/framework-knowledge.research-provenance.d.ts +88 -0
  14. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
  15. package/dist/esm/framework-knowledge.research-provenance.js +140 -0
  16. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
  17. package/dist/esm/index.d.ts +2 -0
  18. package/dist/esm/index.d.ts.map +1 -1
  19. package/dist/esm/index.js +2 -0
  20. package/dist/esm/index.js.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  22. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +43 -2
  25. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +138 -21
  27. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -1
  30. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  32. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +1 -1
  33. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +17 -9
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +22 -11
  37. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +89 -9
  41. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +6 -5
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +6 -4
  45. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +2 -2
  47. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +7 -2
  49. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  51. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  53. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +28 -6
  55. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +23 -5
  57. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  59. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +9 -3
  61. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  63. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +14 -2
  65. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +1 -1
  67. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +2 -2
  69. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +14 -6
  71. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +2 -1
  73. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +5 -3
  75. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +2 -1
  77. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +11 -9
  79. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +17 -3
  81. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +19 -2
  83. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
  85. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
  87. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -1
  89. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +2 -1
  91. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +9 -3
  94. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  95. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +34 -7
  96. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +39 -13
  98. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  99. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
  100. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  101. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  102. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  103. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +14 -6
  104. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +38 -3
  107. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  109. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  111. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +95 -0
  113. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
  114. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +111 -0
  115. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
  116. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  117. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +15 -3
  118. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  119. package/dist/esm/source-anchor-grammar.d.ts +70 -0
  120. package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
  121. package/dist/esm/source-anchor-grammar.js +114 -0
  122. package/dist/esm/source-anchor-grammar.js.map +1 -0
  123. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  124. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  125. package/dist/knowledge/manifest.json +8 -8
  126. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
  127. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  128. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  129. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  130. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +497 -32
  131. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +44 -3
  132. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +302 -8
  133. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  134. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
  135. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +2 -2
  136. package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
  137. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
  138. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  139. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  140. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +118 -11
  141. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -3
  142. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +41 -10
  143. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +7 -5
  144. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +5 -0
  145. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +1 -1
  146. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +12 -0
  147. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +4 -3
  148. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +79 -1
  149. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  150. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +187 -14
  151. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +23 -3
  152. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +3 -2
  153. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +6 -2
  154. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +99 -24
  155. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  156. package/dist/knowledge/playbooks/refinement.document-facts/method.md +38 -3
  157. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -3
  158. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  159. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +2 -2
  160. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
  161. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
  162. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  163. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  164. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +16 -5
  165. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +3 -3
  166. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +56 -16
  167. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +6 -4
  168. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  169. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  170. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +30 -9
  171. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +5 -3
  172. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +12 -1
  173. package/dist/knowledge/playbooks/top_down.business-model/method.md +6 -0
  174. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +2 -2
  175. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  176. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +2 -2
  177. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +12 -2
  178. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +1 -1
  179. package/dist/knowledge/playbooks/top_down.definition/method.md +7 -2
  180. package/dist/knowledge/playbooks/top_down.definition/playbook.json +5 -4
  181. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
  182. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +18 -4
  183. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  184. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +2 -2
  185. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  186. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  187. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  188. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +5 -3
  189. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  190. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  191. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -1
  192. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  193. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  194. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  195. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  196. package/dist/knowledge/playbooks/top_down.risk-register/method.md +1 -1
  197. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -1
  198. package/dist/knowledge/playbooks/top_down.service-method/method.md +198 -0
  199. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +96 -0
  200. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +23 -0
  201. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +23 -4
  202. package/dist/knowledge/references/acp.execution-profile.md +9 -1
  203. package/dist/knowledge/references/application-maturity.config.md +1 -1
  204. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +55 -0
  205. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +13 -2
  206. package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
  207. package/dist/knowledge/references/backend.inbound-handlers.definition.md +426 -5
  208. package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
  209. package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
  210. package/dist/knowledge/references/brand.name-choice.config.md +20 -3
  211. package/dist/knowledge/references/brand.name-screening.config.md +58 -3
  212. package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
  213. package/dist/knowledge/references/build-plan.task-graph.config.md +292 -7
  214. package/dist/knowledge/references/business-model.pricing-plan.config.md +7 -0
  215. package/dist/knowledge/references/business-model.snapshot.validation.md +18 -0
  216. package/dist/knowledge/references/capability-composition.config.md +4 -3
  217. package/dist/knowledge/references/cli.market.generate-command.md +2 -1
  218. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  219. package/dist/knowledge/references/companion.technical-doc.service.md +166 -32
  220. package/dist/knowledge/references/engine.client-bundle.allow-list.md +14 -0
  221. package/dist/knowledge/references/engine.saas-technical-doc.config.md +1 -1
  222. package/dist/knowledge/references/engine.saas-website.config.md +16 -44
  223. package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
  224. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  225. package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
  226. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  227. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +259 -0
  228. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  229. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +129 -0
  230. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +45 -0
  231. package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
  232. package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
  233. package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
  234. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
  235. package/dist/knowledge/references/example.config.design-system.full.md +40 -116
  236. package/dist/knowledge/references/example.data-seeding.minimal.md +10 -9
  237. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  238. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  239. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
  240. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +70 -14
  241. package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
  242. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
  243. package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
  244. package/dist/knowledge/references/example.infra.environment-config.local.md +24 -0
  245. package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
  246. package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
  247. package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
  248. package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
  249. package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
  250. package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
  251. package/dist/knowledge/references/example.provider.backend-module-shape.md +10 -0
  252. package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
  253. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
  254. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
  255. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -1
  256. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  257. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  258. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  259. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  260. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
  261. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  262. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +60 -22
  263. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +81 -0
  264. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +19 -20
  265. package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
  266. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  267. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  268. package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
  269. package/dist/knowledge/references/example.website.blocks.section.md +20 -0
  270. package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
  271. package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
  272. package/dist/knowledge/references/example.website.demo.append.md +57 -0
  273. package/dist/knowledge/references/example.website.demo.approval.md +47 -0
  274. package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
  275. package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
  276. package/dist/knowledge/references/example.website.demo.connect.md +45 -0
  277. package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
  278. package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
  279. package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
  280. package/dist/knowledge/references/example.website.demo.transform.md +43 -0
  281. package/dist/knowledge/references/example.website.page.manifest.md +2 -6
  282. package/dist/knowledge/references/example.website.section.bento.md +27 -0
  283. package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
  284. package/dist/knowledge/references/example.website.section.factories.md +82 -0
  285. package/dist/knowledge/references/example.website.section.faq.md +17 -0
  286. package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
  287. package/dist/knowledge/references/example.website.section.hero.md +16 -0
  288. package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
  289. package/dist/knowledge/references/example.website.section.marquee.md +26 -0
  290. package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
  291. package/dist/knowledge/references/example.website.section.site-block.md +43 -0
  292. package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
  293. package/dist/knowledge/references/example.website.section.stats.md +23 -0
  294. package/dist/knowledge/references/example.website.section.steps.md +15 -0
  295. package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
  296. package/dist/knowledge/references/example.website.theme.composed.md +69 -0
  297. package/dist/knowledge/references/experience-plan.config.md +76 -7
  298. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +6 -0
  299. package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
  300. package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
  301. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +6 -0
  302. package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
  303. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +64 -0
  304. package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
  305. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +61 -2
  306. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +70 -0
  307. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +253 -0
  308. package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
  309. package/dist/knowledge/references/integration-plan.config.md +21 -1
  310. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  311. package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
  312. package/dist/knowledge/references/minions.tick-contract.md +2 -2
  313. package/dist/knowledge/references/placement-plan.config.md +107 -2
  314. package/dist/knowledge/references/platform.config.environment.deployment.md +9 -1
  315. package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -0
  316. package/dist/knowledge/references/platform.config.platform-key-management.md +206 -0
  317. package/dist/knowledge/references/platform.config.saas.md +106 -14
  318. package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
  319. package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
  320. package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
  321. package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
  322. package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
  323. package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
  324. package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
  325. package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
  326. package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
  327. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
  328. package/dist/knowledge/references/presets.models.surface-variant.md +10 -0
  329. package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
  330. package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
  331. package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
  332. package/dist/knowledge/references/presets.themes.compose-theme.md +46 -0
  333. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  334. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  335. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  336. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  337. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  338. package/dist/knowledge/references/roadmap.phase.config.md +2 -16
  339. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +131 -0
  340. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +77 -11
  341. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +158 -0
  342. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
  343. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  344. package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
  345. package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
  346. package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
  347. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
  348. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  349. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  350. package/dist/knowledge/references/saas.backend.domain-module.md +76 -1
  351. package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
  352. package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
  353. package/dist/knowledge/references/saas.backend.email.send.md +84 -0
  354. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +9 -1
  355. package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
  356. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
  357. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
  358. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
  359. package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
  360. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +207 -0
  361. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
  362. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +300 -3
  363. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +13 -2
  364. package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
  365. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
  366. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
  367. package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
  368. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
  369. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +27 -0
  370. package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
  371. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  372. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
  373. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
  374. package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
  375. package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
  376. package/dist/knowledge/references/saas.backend.system-access-service.md +242 -107
  377. package/dist/knowledge/references/saas.config.content-security-policy.md +1 -2
  378. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  379. package/dist/knowledge/references/saas.data-seeding.definition-input.md +8 -2
  380. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  381. package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
  382. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
  383. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
  384. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
  385. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
  386. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
  387. package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
  388. package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
  389. package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
  390. package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
  391. package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
  392. package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
  393. package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
  394. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +126 -0
  395. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
  396. package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
  397. package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
  398. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +17 -3
  399. package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
  400. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
  401. package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
  402. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +324 -0
  403. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +109 -0
  404. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +61 -0
  405. package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
  406. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
  407. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +149 -0
  408. package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
  409. package/dist/knowledge/references/saas.frontend.resource-label-params.md +54 -0
  410. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +17 -11
  411. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +125 -58
  412. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +13 -7
  413. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  414. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +141 -32
  415. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +64 -2
  416. package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
  417. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
  418. package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
  419. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
  420. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
  421. package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
  422. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
  423. package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
  424. package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
  425. package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
  426. package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
  427. package/dist/knowledge/references/saas.models.audit.trail-config.md +63 -5
  428. package/dist/knowledge/references/{saas.models.auth.service-provider-client-authentication.md → saas.models.auth.relationship-grantor-authentication.md} +54 -48
  429. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
  430. package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
  431. package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
  432. package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
  433. package/dist/knowledge/references/saas.models.config.organization-types.md +42 -82
  434. package/dist/knowledge/references/saas.models.conversation-threads.md +4 -3
  435. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +22 -0
  436. package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
  437. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +27 -0
  438. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +403 -0
  439. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +84 -0
  440. package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -1
  441. package/dist/knowledge/references/saas.models.engine-capabilities.md +28 -0
  442. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
  443. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
  444. package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
  445. package/dist/knowledge/references/saas.models.external-data-pipeline.md +81 -18
  446. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
  447. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +317 -0
  448. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
  449. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
  450. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +147 -0
  451. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
  452. package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
  453. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
  454. package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
  455. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +62 -0
  456. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +314 -0
  457. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
  458. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +62 -0
  459. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
  460. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +1 -0
  461. package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
  462. package/dist/knowledge/references/saas.models.flows.runnable-model.md +255 -0
  463. package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
  464. package/dist/knowledge/references/saas.models.http-api-binding.md +157 -42
  465. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
  466. package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
  467. package/dist/knowledge/references/saas.models.inbound-channels.md +4 -1
  468. package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
  469. package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
  470. package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
  471. package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
  472. package/dist/knowledge/references/saas.models.notifications.targets.md +25 -2
  473. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +63 -9
  474. package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
  475. package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
  476. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +73 -0
  477. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +48 -0
  478. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
  479. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
  480. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +911 -0
  481. package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
  482. package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
  483. package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
  484. package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
  485. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +224 -0
  486. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +277 -0
  487. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +113 -0
  488. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +68 -5
  489. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +67 -2
  490. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
  491. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +278 -40
  492. package/dist/knowledge/references/saas.models.provider-capabilities.md +33 -0
  493. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
  494. package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
  495. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +8 -0
  496. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +37 -0
  497. package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
  498. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
  499. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
  500. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
  501. package/dist/knowledge/references/saas.models.representative-activity.md +65 -0
  502. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +84 -2
  503. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
  504. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +57 -11
  505. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
  506. package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
  507. package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
  508. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
  509. package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
  510. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +99 -2
  511. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
  512. package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
  513. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
  514. package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
  515. package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
  516. package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
  517. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +9 -0
  518. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
  519. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +25 -0
  520. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
  521. package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
  522. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
  523. package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
  524. package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
  525. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  526. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  527. package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -4
  528. package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
  529. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +121 -0
  530. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +3 -2
  531. package/dist/knowledge/references/saas.models.systems-of-record.md +36 -1
  532. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
  533. package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
  534. package/dist/knowledge/references/saas.public-runtime.contract.md +60 -2
  535. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
  536. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
  537. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +275 -13
  538. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
  539. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +9 -0
  540. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +16 -2
  541. package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
  542. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
  543. package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
  544. package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
  545. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +24 -2
  546. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
  547. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +19 -5
  548. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
  549. package/dist/knowledge/references/saas.website.astro.bridge.md +61 -14
  550. package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
  551. package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
  552. package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
  553. package/dist/knowledge/references/saas.website.astro.label-loader.md +41 -9
  554. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  555. package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
  556. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +48 -17
  557. package/dist/knowledge/references/saas.website.astro.site-context.md +30 -8
  558. package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
  559. package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
  560. package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
  561. package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
  562. package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
  563. package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
  564. package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
  565. package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
  566. package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
  567. package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
  568. package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
  569. package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
  570. package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
  571. package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
  572. package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
  573. package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
  574. package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
  575. package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
  576. package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
  577. package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
  578. package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
  579. package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
  580. package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
  581. package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
  582. package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
  583. package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
  584. package/dist/knowledge/references/saas.website.blog.bridge.md +102 -53
  585. package/dist/knowledge/references/saas.website.blog.collection-config.md +76 -24
  586. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
  587. package/dist/knowledge/references/saas.website.blog.frontmatter.md +104 -7
  588. package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
  589. package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
  590. package/dist/knowledge/references/saas.website.blog.index.md +43 -0
  591. package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
  592. package/dist/knowledge/references/saas.website.blog.post-renderer.md +113 -85
  593. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +181 -0
  594. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
  595. package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
  596. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +2 -1
  597. package/dist/knowledge/references/saas.website.config.site-context-loader.md +24 -1
  598. package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
  599. package/dist/knowledge/references/saas.website.consent.context.md +1 -1
  600. package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
  601. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
  602. package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
  603. package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
  604. package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
  605. package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
  606. package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
  607. package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
  608. package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
  609. package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
  610. package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
  611. package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
  612. package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
  613. package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
  614. package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
  615. package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
  616. package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
  617. package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
  618. package/dist/knowledge/references/saas.website.label-keys.format.md +2 -2
  619. package/dist/knowledge/references/saas.website.label-pack.validator.md +7 -8
  620. package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
  621. package/dist/knowledge/references/saas.website.legal.public-document-links.md +91 -0
  622. package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
  623. package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
  624. package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
  625. package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
  626. package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
  627. package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
  628. package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
  629. package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
  630. package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
  631. package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
  632. package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
  633. package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
  634. package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
  635. package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
  636. package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
  637. package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
  638. package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
  639. package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
  640. package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
  641. package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
  642. package/dist/knowledge/references/saas.website.page.context.md +9 -2
  643. package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
  644. package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
  645. package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
  646. package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
  647. package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
  648. package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
  649. package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
  650. package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
  651. package/dist/knowledge/references/saas.website.product.figures.md +320 -0
  652. package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
  653. package/dist/knowledge/references/saas.website.product.panels.md +324 -0
  654. package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
  655. package/dist/knowledge/references/saas.website.refs.section.md +2 -2
  656. package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
  657. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  658. package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
  659. package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
  660. package/dist/knowledge/references/saas.website.runtime.context.md +51 -17
  661. package/dist/knowledge/references/saas.website.section.component.md +21 -19
  662. package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
  663. package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
  664. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  665. package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
  666. package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
  667. package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
  668. package/dist/knowledge/references/saas.website.stacking.md +86 -0
  669. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
  670. package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
  671. package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
  672. package/dist/knowledge/references/service-method.config.md +270 -0
  673. package/dist/knowledge/references/website-plan.config.md +561 -23
  674. package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
  675. package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
  676. package/dist/knowledge/references/website-plan.page-routes.md +39 -0
  677. package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
  678. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +86 -9
  679. package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
  680. package/dist/knowledge/references/zod.decorators.data-categories.md +101 -11
  681. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +82 -6
  682. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +23 -1
  683. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  684. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
  685. package/dist/knowledge/references/zod.decorators.file-schema.md +6 -5
  686. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
  687. package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
  688. package/dist/knowledge/references/zod.decorators.schema-metadata.md +5 -0
  689. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +50 -1
  690. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +44 -5
  691. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +130 -9
  692. package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -7
  693. package/dist/knowledge/references/zod.factories.code.md +18 -8
  694. package/dist/knowledge/references/zod.factories.duration.md +23 -13
  695. package/dist/knowledge/references/zod.factories.money.md +24 -14
  696. package/dist/knowledge/references/zod.factories.phone.md +23 -14
  697. package/dist/knowledge/references/zod.factories.range.md +5 -1
  698. package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
  699. package/dist/knowledge/registries/framework-topics.json +2854 -246
  700. package/dist/knowledge/registries/playbooks.json +57 -36
  701. package/dist/knowledge/registries/source-tags.json +8863 -4569
  702. package/dist/knowledge/rules/database-migration-obligation.md +11 -5
  703. package/dist/knowledge/rules/live-context-door.md +1 -1
  704. package/dist/knowledge/skills/INDEX.md +63 -34
  705. package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
  706. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +203 -0
  707. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
  708. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
  709. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
  710. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
  711. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
  712. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +15 -3
  713. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
  714. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
  715. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
  716. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +341 -0
  717. package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
  718. package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
  719. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
  720. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
  721. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  722. package/dist/knowledge/skills/application-database-migrations/SKILL.md +41 -12
  723. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
  724. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  725. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  726. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  727. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +130 -4
  728. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +90 -0
  729. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +59 -0
  730. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
  731. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +79 -2
  732. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +291 -10
  733. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  734. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
  735. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +223 -0
  736. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
  737. package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
  738. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
  739. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +189 -0
  740. package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
  741. package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
  742. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +132 -2
  743. package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
  744. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
  745. package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
  746. package/dist/knowledge/skills/brand-name-screening/SKILL.md +33 -9
  747. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +78 -6
  748. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +30 -8
  749. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +163 -0
  750. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +295 -0
  751. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
  752. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
  753. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +136 -34
  754. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
  755. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
  756. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +34 -7
  757. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
  758. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +37 -0
  759. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +178 -4
  760. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
  761. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +485 -61
  762. package/dist/knowledge/skills/config-app-shell/SKILL.md +101 -19
  763. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
  764. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
  765. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
  766. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
  767. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +472 -0
  768. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +82 -0
  769. package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
  770. package/dist/knowledge/skills/config-design-system/SKILL.md +271 -166
  771. package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
  772. package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
  773. package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
  774. package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
  775. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +37 -0
  776. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +235 -0
  777. package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
  778. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  779. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
  780. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
  781. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +7 -1
  782. package/dist/knowledge/skills/config-saas/SKILL.md +27 -11
  783. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +62 -4
  784. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +80 -7
  785. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +314 -0
  786. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
  787. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +8 -0
  788. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +1 -2
  789. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1182 -0
  790. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +61 -0
  791. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +56 -11
  792. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
  793. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +106 -14
  794. package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -4
  795. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
  796. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
  797. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +155 -92
  798. package/dist/knowledge/skills/configure-billing/SKILL.md +32 -4
  799. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +10 -0
  800. package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
  801. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
  802. package/dist/knowledge/skills/email-add-template/SKILL.md +72 -9
  803. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  804. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +135 -0
  805. package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
  806. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  807. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  808. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  809. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
  810. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +71 -14
  811. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +95 -13
  812. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +9 -1
  813. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
  814. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +44 -16
  815. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
  816. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
  817. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
  818. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +291 -22
  819. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +70 -14
  820. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +451 -0
  821. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +406 -0
  822. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +201 -0
  823. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +172 -0
  824. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
  825. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +7 -0
  826. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +63 -0
  827. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +324 -7
  828. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +95 -6
  829. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +255 -0
  830. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
  831. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
  832. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +112 -16
  833. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
  834. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +264 -0
  835. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +133 -0
  836. package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
  837. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +109 -9
  838. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +45 -0
  839. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +14 -3
  840. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
  841. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +16 -7
  842. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +29 -18
  843. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +144 -14
  844. package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
  845. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
  846. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
  847. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
  848. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
  849. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +14 -3
  850. package/dist/knowledge/skills/inbound-channels/SKILL.md +66 -8
  851. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +34 -1
  852. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +78 -6
  853. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
  854. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +434 -6
  855. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
  856. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +1 -1
  857. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +24 -13
  858. package/dist/knowledge/skills/infra-environment-config/SKILL.md +113 -3
  859. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +9 -1
  860. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -0
  861. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +294 -0
  862. package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
  863. package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
  864. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
  865. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
  866. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
  867. package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
  868. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
  869. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
  870. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
  871. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
  872. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +6 -1
  873. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +4 -2
  874. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  875. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  876. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  877. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
  878. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  879. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  880. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -3
  881. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +10 -1
  882. package/dist/knowledge/skills/market-generation-cli/SKILL.md +23 -12
  883. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +13 -7
  884. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  885. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  886. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  887. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  888. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  889. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  890. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  891. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +14 -3
  892. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  893. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
  894. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
  895. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +40 -10
  896. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +57 -2
  897. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
  898. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
  899. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +176 -4
  900. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  901. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +9 -0
  902. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +81 -1
  903. package/dist/knowledge/skills/module-relationships/SKILL.md +81 -31
  904. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
  905. package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
  906. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1233 -0
  907. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
  908. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
  909. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +521 -0
  910. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +162 -0
  911. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +145 -0
  912. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  913. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
  914. package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
  915. package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
  916. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +67 -0
  917. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
  918. package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
  919. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +15 -4
  920. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
  921. package/dist/knowledge/skills/provider-backend-package/SKILL.md +138 -4
  922. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +32 -28
  923. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
  924. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +6 -0
  925. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +634 -0
  926. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +70 -0
  927. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +61 -2
  928. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
  929. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +15 -6
  930. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +9 -2
  931. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +47 -5
  932. package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
  933. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
  934. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +37 -14
  935. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
  936. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
  937. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
  938. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
  939. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
  940. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +256 -1
  941. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +81 -37
  942. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
  943. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  944. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
  945. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +167 -61
  946. package/dist/knowledge/skills/resource-add-resource/SKILL.md +63 -6
  947. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +84 -2
  948. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +137 -0
  949. package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
  950. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +131 -7
  951. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
  952. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
  953. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +25 -4
  954. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +323 -0
  955. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +23 -2
  956. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +159 -0
  957. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +162 -2
  958. package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
  959. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
  960. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  961. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +3 -2
  962. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +221 -23
  963. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +108 -2
  964. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +242 -107
  965. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +202 -17
  966. package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
  967. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  968. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +123 -56
  969. package/dist/knowledge/skills/resource-external-data/SKILL.md +280 -64
  970. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
  971. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
  972. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +73 -14
  973. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
  974. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +81 -18
  975. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +238 -49
  976. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
  977. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +145 -0
  978. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
  979. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
  980. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +61 -14
  981. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
  982. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
  983. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +39 -13
  984. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
  985. package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
  986. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +1 -1
  987. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +17 -4
  988. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
  989. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
  990. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +6 -0
  991. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +31 -1
  992. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +8 -2
  993. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +68 -5
  994. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +25 -0
  995. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +39 -9
  996. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
  997. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +571 -0
  998. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  999. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
  1000. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +87 -6
  1001. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
  1002. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +127 -12
  1003. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -4
  1004. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +50 -1
  1005. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +44 -5
  1006. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +119 -64
  1007. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
  1008. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +216 -18
  1009. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +6 -0
  1010. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  1011. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  1012. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  1013. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +185 -80
  1014. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +159 -0
  1015. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +120 -1
  1016. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
  1017. package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
  1018. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +257 -65
  1019. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
  1020. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
  1021. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +151 -1
  1022. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +144 -57
  1023. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +131 -0
  1024. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +57 -31
  1025. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +56 -0
  1026. package/dist/knowledge/skills/seeding-authoring/SKILL.md +155 -40
  1027. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  1028. package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
  1029. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +148 -4
  1030. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  1031. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
  1032. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
  1033. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +42 -11
  1034. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +183 -31
  1035. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +64 -2
  1036. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
  1037. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
  1038. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  1039. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +9 -0
  1040. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  1041. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +17 -9
  1042. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  1043. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  1044. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  1045. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +71 -14
  1046. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  1047. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  1048. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +19 -5
  1049. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +20 -6
  1050. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +20 -3
  1051. package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
  1052. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  1053. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  1054. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +226 -37
  1055. package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
  1056. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +33 -9
  1057. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +12 -3
  1058. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +17 -3
  1059. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +93 -27
  1060. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +264 -78
  1061. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1068 -192
  1062. package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
  1063. package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
  1064. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
  1065. package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
  1066. package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
  1067. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +46 -19
  1068. package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
  1069. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +18 -5
  1070. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +97 -29
  1071. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +77 -66
  1072. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +71 -24
  1073. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
  1074. package/dist/knowledge/skills/website-label-pack/SKILL.md +24 -17
  1075. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +116 -76
  1076. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +43 -14
  1077. package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
  1078. package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
  1079. package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
  1080. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +266 -371
  1081. package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
  1082. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +120 -0
  1083. package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
  1084. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -329
  1085. package/dist/knowledge/skills/website-page-authoring/SKILL.md +170 -66
  1086. package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
  1087. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +27 -3
  1088. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
  1089. package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
  1090. package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
  1091. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +54 -29
  1092. package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
  1093. package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
  1094. package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
  1095. package/dist/knowledge/skills/website-section-contact/SKILL.md +408 -185
  1096. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
  1097. package/dist/knowledge/skills/website-section-cta/SKILL.md +398 -234
  1098. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
  1099. package/dist/knowledge/skills/website-section-faq/SKILL.md +564 -300
  1100. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
  1101. package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
  1102. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +650 -272
  1103. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
  1104. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +577 -261
  1105. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
  1106. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +532 -233
  1107. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
  1108. package/dist/knowledge/skills/website-section-hero/SKILL.md +606 -330
  1109. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
  1110. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
  1111. package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
  1112. package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
  1113. package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
  1114. package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
  1115. package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
  1116. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
  1117. package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
  1118. package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
  1119. package/dist/knowledge/skills/website-section-pricing/SKILL.md +552 -376
  1120. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +77 -0
  1121. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
  1122. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +2 -1
  1123. package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
  1124. package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
  1125. package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
  1126. package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
  1127. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
  1128. package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
  1129. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
  1130. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
  1131. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
  1132. package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
  1133. package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
  1134. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +743 -309
  1135. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
  1136. package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
  1137. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
  1138. package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
  1139. package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
  1140. package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
  1141. package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
  1142. package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
  1143. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +198 -70
  1144. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +575 -57
  1145. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +17 -2
  1146. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +8 -95
  1147. package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
  1148. package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
  1149. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
  1150. package/dist/knowledge/topic-index.json +17305 -8263
  1151. package/dist/tsconfig.build.tsbuildinfo +1 -1
  1152. package/package.json +4 -4
  1153. package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
  1154. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
  1155. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
  1156. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
  1157. package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
  1158. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
  1159. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
  1160. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
  1161. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
  1162. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
  1163. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
@@ -60,6 +60,13 @@ The runtime normalizes your answer and **rejects** it — spending one of three
60
60
  were shown exactly which. There is no partial credit for a plausible objective.
61
61
  - cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`
62
62
  prefix, spelled exactly.
63
+ - answer an obligation under a source its objective was not reviewed under. The authority section
64
+ names, per objective, the sources the basis reviewed it under. You choose one of those; the
65
+ requirements the obligation cites are stamped from the basis, so you do not write them.
66
+ - give a `sourceSlug` for an objective the authority section marks as reviewed under no source by
67
+ design, or omit it for one that was reviewed under a source. Whether an objective answers any
68
+ external source is the basis's decision: such an obligation omits `sourceSlug` and is stamped as
69
+ answering no source.
63
70
  - bind the same objective twice.
64
71
  - bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability
65
72
  it requires is absent, so nothing could ever evidence it.
@@ -79,8 +86,11 @@ For each objective you were shown, ask three questions **in order**, and stop at
79
86
  whose intent describes something the declarations do not show is not bound. Read the computed
80
87
  applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only
81
88
  as `UNDETERMINED`.
82
- 2. **Which external requirement does it answer, and does that source reach this application?** If the
83
- product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.
89
+ 2. **Which source does it answer, and does that source reach this application?** Only a source the
90
+ objective was reviewed under can be answered; which of its requirements apply is the basis's
91
+ review, not yours. If the product serves no EU data subjects, GDPR does not reach it and no
92
+ obligation should cite it. An objective the basis reviews under no source by design answers
93
+ none: skip this question for it, and decide its applicability on the objective alone.
84
94
  3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can
85
95
  defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is
86
96
  the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a
@@ -35,7 +35,7 @@
35
35
  ],
36
36
  "stepOutputs": [],
37
37
  "method": {
38
- "guidance": "# Compliance Conception — Derivation Method (v1)\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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which external requirement does it answer, and does that source reach this application?** If the\n product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is THREE fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated identifier for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. `title` is the role's name as a person reads it (`Application owner`,\n `Control operator`) — what the creator sees wherever the role is named. Two programme roles may map to\n the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
38
+ "guidance": "# Compliance Conception — Derivation Method (v1)\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 the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- answer an obligation under a source its objective was not reviewed under. The authority section\n names, per objective, the sources the basis reviewed it under. You choose one of those; the\n requirements the obligation cites are stamped from the basis, so you do not write them.\n- give a `sourceSlug` for an objective the authority section marks as reviewed under no source by\n design, or omit it for one that was reviewed under a source. Whether an objective answers any\n external source is the basis's decision: such an obligation omits `sourceSlug` and is stamped as\n answering no source.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which source does it answer, and does that source reach this application?** Only a source the\n objective was reviewed under can be answered; which of its requirements apply is the basis's\n review, not yours. If the product serves no EU data subjects, GDPR does not reach it and no\n obligation should cite it. An objective the basis reviews under no source by design answers\n none: skip this question for it, and decide its applicability on the objective alone.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is THREE fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated identifier for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. `title` is the role's name as a person reads it (`Application owner`,\n `Control operator`) — what the creator sees wherever the role is named. Two programme roles may map to\n the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
39
39
  "skillRefs": [],
40
40
  "skillBodyRefs": [],
41
41
  "elicitation": {
@@ -47,6 +47,11 @@ needed by nothing downstream of this lane:
47
47
  - **`top_down.brand-identity`** — the visual identity, from the creator's answers. Its
48
48
  `brand-name` is a CHOICE among the screened names, so it runs after the naming lane.
49
49
  - **`top_down.risk-register`** — the register the assurance mechanisms read.
50
+ - **`top_down.service-method`** — a service firm's method: the services it sells, how each case
51
+ is worked, decided and delivered. Needs the vision alone, so it usually runs first beside the
52
+ chain; offer it again as a REFRESH as the market snapshot, the requirements and the business
53
+ model land, since each sharpens it (the business model is what settles per-case pricing). It
54
+ is not applicable on a B2B SaaS or an internal tool until a feature line needs it.
50
55
 
51
56
  Nothing above is a sequence. Each child declares what it needs, and the runtime
52
57
  re-computes what may run after every round. That is what makes the lane re-runnable
@@ -62,8 +67,8 @@ vision whole, the others as a map of what exists — and the children that may r
62
67
  since it landed is not offered at all. Every option is marked FIRST RUN, or REFRESH
63
68
  with the input that moved and the run that moved it. Prefer first runs; take a
64
69
  refresh when the change it names matters to that child.
65
- - **Independent children share a round.** The brand identity and the risk register
66
- ride beside the chain; several research lanes with genuinely different objectives
70
+ - **Independent children share a round.** The brand identity, the risk register and a
71
+ firm's method ride beside the chain; several research lanes with genuinely different objectives
67
72
  return more than one asked everything.
68
73
  - **A child whose interview is unanswered is not offered.** The dossier answers the
69
74
  creator's questions per leaf; a leaf the dossier does not cover waits for the creator,
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "top_down.definition",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
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 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.",
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, the risk register and the firm's method (its services, decisions and signatories; on a service firm, or wherever a feature line needs it) 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 or the firm's method 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-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",
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- **`top_down.service-method`** — a service firm's method: the services it sells, how each case\n is worked, decided and delivered. Needs the vision alone, so it usually runs first beside the\n chain; offer it again as a REFRESH as the market snapshot, the requirements and the business\n model land, since each sharpens it (the business model is what settles per-case pricing). It\n is not applicable on a B2B SaaS or an internal tool until a feature line needs it.\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, the risk register and a\n firm's method 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": [],
@@ -62,7 +62,8 @@
62
62
  "top_down.vision-elicitation",
63
63
  "top_down.brand-naming",
64
64
  "top_down.brand-identity",
65
- "top_down.risk-register"
65
+ "top_down.risk-register",
66
+ "top_down.service-method"
66
67
  ],
67
68
  "maximumIterations": 20,
68
69
  "maximumLanesPerIteration": 3,
@@ -32,9 +32,14 @@ critic, and a FINALIZE pass when the critique asks for one — then promotes the
32
32
 
33
33
  - **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never
34
34
  replaced; the accept step refuses and the run reports it.
35
- - **Re-derive a committed charter.** A role that already has a committed charter is left alone; ask for a
36
- re-derivation explicitly through the companion's `expert-personas/derive` route if the application's
37
- definition moved enough to warrant one.
35
+ - **Re-derive a current charter.** A committed charter is derived again only when one of its shaping inputs
36
+ changed AFTER it (written by a later run, edited, or committed later): the brand's visual tone, the market, the vision, the requirements, the business
37
+ model, the brand's promoted assets or the design-system configuration, whichever that role reads. The
38
+ board then offers this step as a refresh naming the inputs that moved, and the run reports those roles
39
+ as derived again. Each input is dated from the file the persona reads, so promoting a logo moves only
40
+ the roles that read the promoted assets.
41
+ - **Re-derive a drifted charter a person edited.** It is named in the run's report with the inputs that
42
+ moved, for the person to update by hand.
38
43
  - **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with
39
44
  no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.
40
45
 
@@ -54,3 +59,5 @@ therefore which roles are derivable now.
54
59
  and `index.ts` lists every one of them.
55
60
  - `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.
56
61
  - The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.
62
+ - After the run, the board offers this step as current: no charter is older than an input it reads, apart
63
+ from those a person edited, which the run named, and those still waiting on a family.
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "top_down.expert-personas",
3
- "version": "0.1.0",
3
+ "version": "0.3.0",
4
4
  "phase": "top_down",
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).",
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 and current is left alone, a committed charter older than one of its shaping inputs is derived again (a human-edited one is never overwritten and is named for the person to update, #2819), 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": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -23,12 +23,26 @@
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
- "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
+ "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 current charter.** A committed charter is derived again only when one of its shaping inputs\n changed AFTER it (written by a later run, edited, or committed later): the brand's visual tone, the market, the vision, the requirements, the business\n model, the brand's promoted assets or the design-system configuration, whichever that role reads. The\n board then offers this step as a refresh naming the inputs that moved, and the run reports those roles\n as derived again. Each input is dated from the file the persona reads, so promoting a logo moves only\n the roles that read the promoted assets.\n- **Re-derive a drifted charter a person edited.** It is named in the run's report with the inputs that\n moved, for the person to update by hand.\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- After the run, the board offers this step as current: no charter is older than an input it reads, apart\n from those a person edited, which the run named, and those still waiting on a family.\n",
32
46
  "skillRefs": [],
33
47
  "skillBodyRefs": [],
34
48
  "contextSources": [],
@@ -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
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.feature-drafts",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "top_down",
5
5
  "intent": "Draft the product capabilities an application needs from its accepted requirements and vision, for an application whose line has no market: one spec-first, ref-less feature specification draft per capability the requirements call for, each tracing to the requirements it serves.",
6
6
  "preconditions": [
@@ -37,7 +37,7 @@
37
37
  ],
38
38
  "stepOutputs": [],
39
39
  "method": {
40
- "guidance": "# Feature Drafts — Requirements → Capability Method\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 playbook does\n\nYou are the **capability architect** for an application that has **no market**: an internal tool,\nfor example, built for a team rather than sold to customers. Your one job is to turn the accepted\n**requirements** into the product **capabilities** that deliver them, and to record each capability as\na spec-first **`FeatureSpecificationDraft`** in the `feature-drafts` family.\n\nThere are no market benefits, ICPs or pricing to map from, and none is owed: do not invent a market,\na customer segment or a competitive position. The requirements say what the application must do and\nfor whom inside the organization; the vision says why it exists. Those two are your whole input.\n\n## Read state first\n\n- **Requirements** (functional and non-functional): what the application must do. Every capability\n you draft must serve at least one requirement, and every functional requirement should be served by\n at least one capability. A requirement no capability serves is either a gap to draft or a\n requirement to question, never a silent omission.\n- **Vision**: the problem, the mission and the constraints. Use it to name capabilities in the\n application's own words and to keep them inside its stated scope.\n- **Your prior feature drafts**, when present. Refine them; do not re-author (below).\n\n## Drafting each capability\n\nFor every capability, author a draft with the **Draft path** of `spec-feature-update`: its purpose,\nbusiness role, lifecycle role, when to use it and when not to, and its availability role, all in\nprose. Drafts are **spec-first and ref-less**: you author them before the runtime `FeatureDefinition`\nexists, and the factory injects the `ref` later. The draft wrapper carries the stable `featureRef`;\nthe nested prose payload stays ref-less.\n\n- **One capability, one draft.** When two requirements are served by the same capability, they share\n it; do not fork it.\n- **Name the requirements each draft serves**, in its purpose or business-role prose, so the roadmap\n and the build decomposition can trace a capability back to what asked for it.\n- **Stay at scaffold depth.** A draft is a first-cut capability contract. Operations, screens and\n interaction semantics are the bottom-up build phase's work.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite drafts that are already correct.\n- **Keep refs stable.** A draft's `featureRef` is named by the roadmap and by build tasks; renaming it\n orphans them.\n- Add a draft where a requirement gained a capability, correct one that is genuinely wrong, and\n remove one only when no requirement calls for it any more.\n\n## What you emit\n\nThe **feature-drafts** at `specifications/src/feature-drafts/index.ts`: one `FeatureSpecificationDraft`\nper capability the requirements call for, passing `validateFeatureSpecificationDrafts`.\n\nThe creator reviews the result (approval posture `approve_result`) before it is accepted.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an authoring\ncontract a later coding agent can open. This step has no tools and does not open them; what reaches\nyou is this method, your declared inputs, and the brief's own sections.\n\n- `spec-feature-update`: author the spec-first `FeatureSpecificationDraft`s (the Draft path).\n",
40
+ "guidance": "# Feature Drafts — Requirements → Capability Method\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 playbook does\n\nYou are the **capability architect** for an application that has **no market**: an internal tool,\nfor example, built for a team rather than sold to customers. Your one job is to turn the accepted\n**requirements** into the product **capabilities** that deliver them, and to record each capability as\na spec-first **`FeatureSpecificationDraft`** in the `feature-drafts` family.\n\nThere are no market benefits, ICPs or pricing to map from, and none is owed: do not invent a market,\na customer segment or a competitive position. The requirements say what the application must do and\nfor whom inside the organization; the vision says why it exists. Those two are your whole input.\n\n## Read state first\n\n- **Requirements** (functional and non-functional): what the application must do. Every capability\n you draft must serve at least one requirement, and every functional requirement should be served by\n at least one capability. A requirement no capability serves is either a gap to draft or a\n requirement to question, never a silent omission.\n- **Vision**: the problem, the mission and the constraints. Use it to name capabilities in the\n application's own words and to keep them inside its stated scope.\n- **Your prior feature drafts**, when present. Refine them; do not re-author (below).\n\n## Drafting each capability\n\nFor every capability, author a draft with the **Draft path** of `spec-feature-update`: its purpose,\nbusiness role, lifecycle role, when to use it and when not to, and its availability role, all in\nprose. Drafts are **spec-first and ref-less**: you author them before the runtime `FeatureDefinition`\nexists, and the factory injects the `ref` later. The draft wrapper carries the stable `featureRef`;\nthe nested prose payload stays ref-less.\n\n- **One capability, one draft.** When two requirements are served by the same capability, they share\n it; do not fork it.\n- **Name the requirements each draft serves**, in its purpose or business-role prose, so the roadmap\n and the build decomposition can trace a capability back to what asked for it.\n- **Stay at scaffold depth.** A draft is a first-cut capability contract. Screens and the\n operations that implement it are the bottom-up build phase's work. But say what the capability\n DOES in the business's verbs (\"a sent quote can be accepted, and accepting it creates a job\"):\n the domain plan turns those verbs into lifecycles, and a draft that names none leaves it nothing\n to read.\n\n## Refine, don't re-author\n\n- **Keep what still holds.** Do not rewrite drafts that are already correct.\n- **Keep refs stable.** A draft's `featureRef` is named by the roadmap and by build tasks; renaming it\n orphans them.\n- Add a draft where a requirement gained a capability, correct one that is genuinely wrong, and\n remove one only when no requirement calls for it any more.\n\n## What you emit\n\nThe **feature-drafts** at `specifications/src/feature-drafts/index.ts`: one `FeatureSpecificationDraft`\nper capability the requirements call for, passing `validateFeatureSpecificationDrafts`.\n\nThe creator reviews the result (approval posture `approve_result`) before it is accepted.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an authoring\ncontract a later coding agent can open. This step has no tools and does not open them; what reaches\nyou is this method, your declared inputs, and the brief's own sections.\n\n- `spec-feature-update`: author the spec-first `FeatureSpecificationDraft`s (the Draft path).\n",
41
41
  "skillRefs": [
42
42
  "spec-feature-update"
43
43
  ],
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, or presents unsupported claims as truth.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":2}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Then check the category against what the creator stated, when it is in your evidence: it keeps every workflow stage they named, puts nothing they excluded at its centre, and a category naming a different kind of product from theirs carries a category note starting \"Reframe:\". A dropped stage, a centred exclusion, or an unmarked reframe is a GAP. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, presents unsupported claims as truth, or reframes the product the creator stated without marking it.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-market-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1,"riskClassRef":"application-creation:risk/market-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1},"decisionPointRef":"application-creation:decision-point/market-analysis-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/market-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/market-definition-change","triggerRefs":["application-creation:trigger/market-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-market-analysis-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"hardFloorRef":"application-creation:hard-floor/market-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/market-analysis","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, or presents unsupported claims as truth.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-market-input-and-candidate","criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/accepted-vision-research-and-market-candidate"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-market-snapshot","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1,"riskClassRef":"application-creation:risk/market-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/market-analysis-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/market-analysis","policyVersion":1},"decisionPointRef":"application-creation:decision-point/market-analysis-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":2}],"hardFloorRefs":["application-creation:hard-floor/market-snapshot-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/market-definition-change","triggerRefs":["application-creation:trigger/market-snapshot-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-market-analysis-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/market-evidence-and-vision-coherence"],"hardFloorRef":"application-creation:hard-floor/market-snapshot-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/market-analysis-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/market-analysis","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-market-analysis-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":2}],"instruction":"Assess whether the validated market graph is meaningfully grounded in accepted vision and sealed research evidence, distinguishes facts from hypotheses, and is coherent enough for current-horizon requirements and capability work. Then check the category against what the creator stated, when it is in your evidence: it keeps every workflow stage they named, puts nothing they excluded at its centre, and a category naming a different kind of product from theirs carries a category note starting \"Reframe:\". A dropped stage, a centred exclusion, or an unmarked reframe is a GAP. Do not reward exhaustive taxonomy when the targeting or evidence basis is weak.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The graph is usable but material targeting or evidence uncertainty is explicitly unresolved.","GAP":"The market graph materially contradicts the vision, lacks a usable target, presents unsupported claims as truth, or reframes the product the creator stated without marking it.","INDETERMINATE":"Accepted vision, research evidence or candidate output is absent, stale or insufficient.","PASS":"The market graph is valid, evidence-aware and coherent with the accepted vision."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/market-analysis","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.market-snapshot-produce"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/market-analysis","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-market-input-and-candidate","criterionRef":"application-creation:criterion/market-evidence-and-vision-coherence","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/market-evidence-and-vision-coherence","requirementVersion":2,"schemaVersion":1,"subjectRef":"application-creation:definition-set/accepted-vision-research-and-market-candidate"}],"schemaVersion":1}
@@ -160,6 +160,32 @@ So:
160
160
  Omit `authoredMetadata` only where the content is so self-evident that provenance
161
161
  would be noise. A competitor's price is never that.
162
162
 
163
+ ## The creator's framing binds the category
164
+
165
+ The creator has already said what the product is. Their answers arrive in
166
+ the declared `creator_stated_facts` context section of your brief: the one-liner, the workflow the product
167
+ carries (`core-workflow`), who uses it (`user-groups`) and what is left out
168
+ (`scope-boundary`). Given identical answers, two earlier runs chose two different
169
+ products: one a customer-workflow CRM that left invoicing to other tools, the
170
+ other trade-workflow software with invoicing at its centre and no customer
171
+ follow-up. That choice was never the market step's to make.
172
+
173
+ - **Every stage the creator named stays in the product.** A category under which
174
+ a stated stage disappears (follow-up, say) is the wrong category, not a sharper one.
175
+ - **Nothing the creator left out becomes central.** A category that puts an
176
+ excluded capability (invoicing, say) at its heart contradicts the scope
177
+ boundary. Pick another.
178
+ - **A reframe is MARKED, never silent.** You may name the category in better
179
+ market language than the creator's ("trade-operations CRM" for "a CRM for
180
+ building firms"), as long as the workflow and the boundary still hold. When
181
+ your category's NAME differs from the kind of product the creator named, add
182
+ a `category.notes[]` entry that starts with `Reframe:`. It quotes the creator's
183
+ own framing, names yours, and says why. That note is how the creator sees the
184
+ decision and overturns it. Never list the creator's own framing among
185
+ `rejectedCategories`.
186
+ - When the creator gave no workflow or boundary, frame from the one-liner and the
187
+ problem, and say in the category notes that the shape was inferred.
188
+
163
189
  ## Research posture (scaffold depth)
164
190
 
165
191
  Ground each slice in evidence, not invention. At this scaffold depth the
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.market-snapshot-produce",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "top_down",
5
5
  "intent": "Derive a validated market snapshot from the vision and from the EVIDENCE a sibling research step gathered — the artifact-producing child of the `top_down.market-analysis` composite. The provider proposes the market graph; the trusted runtime stamps entity refs/version and keeps provenance, authority and accepted-family mutation outside model output. Its intent used to claim derivation from \"sealed research evidence\" while nothing supplied any; it now runs only once an adequacy gate has read the evidence and returned ADEQUATE.",
6
6
  "preconditions": [
@@ -36,7 +36,7 @@
36
36
  ],
37
37
  "stepOutputs": [],
38
38
  "method": {
39
- "guidance": "# Market Analysis — Produce Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The authoring order, research posture, and the \"produce vs.\n> refine\" rules below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of the market work (research rigor, competitive\n> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **market analyst**. Your one job is to produce — or refine an\nexisting — **MarketSnapshot** for this product: the single artifact that\ndeclares *who the product is for*, *what they are trying to get done*, and\n*how the product is positioned* to them. You reason top-down from the\nproduct idea (there is no code yet in this phase); you do not model the\ndomain, author resources, or write features — later playbooks consume your\nsnapshot to do that.\n\n## The shape you return is FLAT, not nested\n\nRead this before the slice list below, because the slices read like a hierarchy and the object is\nnot one.\n\nA MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,\n`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at\neach other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,\n…). An ICP does not CONTAIN its jobs; it names them:\n\n```\njobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level\nicps: [ { ref: 'icp-small-team',\n jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it\n```\n\n⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were\nrejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and\nwrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full\ngeneration was spent discovering the shape. The slice ordering below is a THINKING order — what to\nwork out first — never the structure of the answer.\n\nA MarketSnapshot is assembled from these slices, each owned by a dedicated\n`market_*` app-knowledge skill. Those skills are named here so you know which\nauthoring contract each slice belongs to, and so a later CODING agent can open\nthe right one — you cannot: this step has no tools, and sixteen skill bodies do\nnot fit in one brief. Everything you need to author the snapshot is in THIS\nmethod and your declared inputs; where a detail is genuinely only in a skill,\nsay so on what you author rather than inventing it. You author them in\ndependency order because later slices reference earlier refs:\n\n1. **Category** — the one market category the product competes in, plus the\n rejected adjacent categories. (`market-category`)\n2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic\n segments the product is sold to. (`market-icp`)\n3. **Personas** — the human roles inside each ICP, including buying-group\n members. Every ICP needs at least one persona. (`market-persona`)\n4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for\n the personas: what they are trying to do, what blocks them, what a win\n looks like. (`market-jobs-pains-gains`)\n5. **Tones of voice** — the named brand voices the product speaks in.\n (`market-tone-of-voice`)\n6. **Benefits** — the outcome claims the product delivers, weighted against\n the pains/gains they relieve/create. (`market-add-feature-benefit`)\n7. **Positionings** — the per-ICP marketing-truth promise. Author one per\n ICP that the product actually targets. (`market-positioning-authoring`)\n8. **Reach surfaces** — the go-to-market context: channels, competing\n alternatives, buying triggers + per-ICP buying journeys, proofs, and the\n objections proofs answer. (`market-channels`, `market-alternatives`,\n `market-triggers-and-journey`, `market-proof-and-objection`)\n9. **Message templates** — reusable prompt templates that render from the\n snapshot above. Author last; they reference the earlier slices.\n (`market-message-templates-authoring`)\n\nAuthor only the slices the product's stage warrants — a first pass may stop\nafter positionings and leave the phase-3/4 reach surfaces empty (they\ndefault to `[]`). A snapshot with a category, at least one ICP, its\npersonas, the jobs/pains/gains triplet, and at least one positioning is a\nlegitimate v1; the reach surfaces and message templates are additive.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is placed under\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook owns and the rest of the top-down phase reads. When the product's\ndefinition later stabilises, the snapshot is what seeds the durable market\nspecification under `./specifications/` — but at this phase it is a journey\nartifact, not yet app source.\n\n## Produce vs. refine — read state first\n\nThis playbook is **idempotent** on the journey's market artifact. Before\nauthoring anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which\n scope the snapshot must be complete *for*.\n2. Check whether a MarketSnapshot already exists by reading the artifact at the\n `market-snapshot` family's landing path, `specifications/src/market/index.ts`.\n The path belongs to the FAMILY, not to this playbook — every playbook that\n writes a market snapshot writes that same file. Its presence or absence\n selects the mode below.\n\n- **No snapshot yet** — produce a fresh one, authoring the slices in the\n order above.\n- **A snapshot exists** — *refine* it: read every slice, keep what still\n holds, and only add/correct the slices the current steering notes or new\n research call for. Never silently discard authored refs — a downstream\n positioning or benefit may depend on an ICP or persona ref, and dropping\n it orphans them (the validator will catch this, but honest refinement\n should not create the orphan in the first place).\n\n## Provenance — record where a claim came from\n\nYou are given the evidence a sibling research step gathered, with the URLs it read.\nWhere an entity's content rests on one of those sources, RECORD that URL on the entity\n— in the schema's own provenance fields, which exist for exactly this:\n\n| field | for |\n|---|---|\n| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |\n| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |\n| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |\n\n⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.\nThat was wrong, and the correction is recorded rather than quietly applied because the\nrun that exposed it did better than the instruction: handed the evidence, the model\nput 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the\ngeneric metadata block it had been pointed at. Typed provenance is machine-readable\nand the generic block is prose; prefer the specific field every time one exists.\n\nThis is not bookkeeping. Measured on this playbook's first composite run\n(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that\ndimension, indistinguishable from the single-call version it replaced — the judge\ncalled the older one's evidence \"self-referential statements such as 'The vision\nspecifies…'\". A sourced claim and an invented one must not look the same in what you\nland, because nobody downstream can tell them apart afterwards.\n\nSo:\n\n- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.\n- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for\n a hypothesis, not `HIGH` because it reads well.\n- An entity the evidence did not cover is still authorable, and says so.\n\nOmit `authoredMetadata` only where the content is so self-evident that provenance\nwould be noise. A competitor's price is never that.\n\n## Research posture (scaffold depth)\n\nGround each slice in evidence, not invention. At this scaffold depth the\nresearch is whatever the executing agent can gather about the product's\ncategory, competitors, and buyers; capture the *shape* faithfully (real\ncategory, real competing alternatives, plausible ICPs and personas) rather\nthan aspirational fiction. Where you are inferring rather than citing, say so\nin the slice's authored prose so a later, deeper research pass can tighten\nit. Do **not** build a research pipeline or block on external tooling here —\nricher web-research capability is a later-phase concern; this playbook\nconsumes whatever the agent already knows plus the creator's steering.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. It\nenforces the cross-slice invariants — orphan refs (a positioning naming a\nmissing ICP, a benefit naming a missing pain/gain), an ICP with no persona,\ninfluence cycles, duplicate edges, proofs without support, message-template\nplaceholder mismatches, and more. Duplicate or malformed refs and\n`ERROR`-severity issues are hard failures; the snapshot does not advance\nuntil they clear. `WARN`-severity issues (e.g. stale-authored, a missing\npositioning for a targeted ICP) do not block but should be resolved. Read\n`market-snapshot-validation` for the full issue catalogue and emit a clean\nsnapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Deep competitive teardown** — the reach surfaces capture *that* an\n alternative exists and *why* a buyer might pick it; a quantified,\n feature-by-feature competitor matrix is later-phase work.\n- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads\n the deterministic FIT scorer; at scaffold depth you consume it to sanity-\n check benefit weighting, not to drive a precise prioritization model. The\n prioritization seam stays pluggable (see the capability-map playbook).\n- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are\n authored as framing, not as a sized, sourced market model.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nA single MarketSnapshot at `specifications/src/market/index.ts`,\nassembled from the slices above via their `market_*` skills, passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, listed so each slice's\nauthoring contract has a name. This step has no tools and does not open them.\n\n- `market-authoring-overview` — the orchestrator for\n the whole market slice; read it first to see how the slices fit together.\n- `market-category` — author the singular market\n category.\n- `market-icp` — author the Ideal Customer Profiles.\n- `market-persona` — author the personas per ICP.\n- `market-jobs-pains-gains` — author the Strategyzer\n jobs/pains/gains triplet.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-add-feature-benefit` — author the benefit\n claims and their pain/gain weighting.\n- `market-positioning-authoring` — author the per-ICP\n positioning promise.\n- `market-channels` — author the reach channels.\n- `market-alternatives` — author the competing\n alternatives.\n- `market-triggers-and-journey` — author buying\n triggers and per-ICP buying journeys.\n- `market-proof-and-objection` — author proofs and\n the objections they answer.\n- `market-message-templates-authoring` — author the\n reusable message templates (last).\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting.\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
39
+ "guidance": "# Market Analysis — Produce Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** It is a working first cut meant to\n> be iterated. The authoring order, research posture, and the \"produce vs.\n> refine\" rules below are deliberately explicit so they can be tuned against\n> real runs — treat them as a starting rubric, not a frozen contract. The\n> *analytical depth* of the market work (research rigor, competitive\n> teardown, quantified FIT/Kano scoring) is intentionally shallow here and is\n> deepened in a later phase; do not perfect it in this playbook.\n\n## What this playbook does\n\nYou are the **market analyst**. Your one job is to produce — or refine an\nexisting — **MarketSnapshot** for this product: the single artifact that\ndeclares *who the product is for*, *what they are trying to get done*, and\n*how the product is positioned* to them. You reason top-down from the\nproduct idea (there is no code yet in this phase); you do not model the\ndomain, author resources, or write features — later playbooks consume your\nsnapshot to do that.\n\n## The shape you return is FLAT, not nested\n\nRead this before the slice list below, because the slices read like a hierarchy and the object is\nnot one.\n\nA MarketSnapshot is **~16 sibling top-level collections** — `category`, `icps`, `personas`, `jobs`,\n`pains`, `gains`, `tonesOfVoice`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `buyingJourneys`, `proofs`, `objections`, `messageTemplates` — and entities point at\neach other with flat **ref strings** (`jobRef`, `painRef`, `gainRef`, `personaRef`, `alternativeRef`,\n…). An ICP does not CONTAIN its jobs; it names them:\n\n```\njobs: [ { ref: 'job-close-the-week', statement: '…' } ] // the job itself, top level\nicps: [ { ref: 'icp-small-team',\n jobs: [ { jobRef: 'job-close-the-week', importance: … } ] } ] // the ICP's REFERENCE to it\n```\n\n⚠ **Measured on this playbook, 2026-08-29.** A first attempt returned 41,098 characters that were\nrejected wholesale: it had nested `personas`, `benefits`, `positionings`, `channels`, `alternatives`,\n`triggers`, `proofs` and `objections` INSIDE `icps[0]`, left every top-level collection empty, and\nwrote whole job objects where `{ jobRef, importance }` belongs. The retry recovered it, but a full\ngeneration was spent discovering the shape. The slice ordering below is a THINKING order — what to\nwork out first — never the structure of the answer.\n\nA MarketSnapshot is assembled from these slices, each owned by a dedicated\n`market_*` app-knowledge skill. Those skills are named here so you know which\nauthoring contract each slice belongs to, and so a later CODING agent can open\nthe right one — you cannot: this step has no tools, and sixteen skill bodies do\nnot fit in one brief. Everything you need to author the snapshot is in THIS\nmethod and your declared inputs; where a detail is genuinely only in a skill,\nsay so on what you author rather than inventing it. You author them in\ndependency order because later slices reference earlier refs:\n\n1. **Category** — the one market category the product competes in, plus the\n rejected adjacent categories. (`market-category`)\n2. **ICPs** — the Ideal Customer Profiles: the firmographic / demographic\n segments the product is sold to. (`market-icp`)\n3. **Personas** — the human roles inside each ICP, including buying-group\n members. Every ICP needs at least one persona. (`market-persona`)\n4. **Jobs / Pains / Gains** — the Strategyzer customer-profile triplet for\n the personas: what they are trying to do, what blocks them, what a win\n looks like. (`market-jobs-pains-gains`)\n5. **Tones of voice** — the named brand voices the product speaks in.\n (`market-tone-of-voice`)\n6. **Benefits** — the outcome claims the product delivers, weighted against\n the pains/gains they relieve/create. (`market-add-feature-benefit`)\n7. **Positionings** — the per-ICP marketing-truth promise. Author one per\n ICP that the product actually targets. (`market-positioning-authoring`)\n8. **Reach surfaces** — the go-to-market context: channels, competing\n alternatives, buying triggers + per-ICP buying journeys, proofs, and the\n objections proofs answer. (`market-channels`, `market-alternatives`,\n `market-triggers-and-journey`, `market-proof-and-objection`)\n9. **Message templates** — reusable prompt templates that render from the\n snapshot above. Author last; they reference the earlier slices.\n (`market-message-templates-authoring`)\n\nAuthor only the slices the product's stage warrants — a first pass may stop\nafter positionings and leave the phase-3/4 reach surfaces empty (they\ndefault to `[]`). A snapshot with a category, at least one ICP, its\npersonas, the jobs/pains/gains triplet, and at least one positioning is a\nlegitimate v1; the reach surfaces and message templates are additive.\n\n## Where the snapshot lives\n\nThe MarketSnapshot for this journey is placed under\n`specifications/src/market/index.ts`. That is the artifact this\nplaybook owns and the rest of the top-down phase reads. When the product's\ndefinition later stabilises, the snapshot is what seeds the durable market\nspecification under `./specifications/` — but at this phase it is a journey\nartifact, not yet app source.\n\n## Produce vs. refine — read state first\n\nThis playbook is **idempotent** on the journey's market artifact. Before\nauthoring anything:\n\n1. Read the current journey state and scope from what this run is given — the loaded\n specifications and the workspace sections of your brief; do not re-derive it. That state tells you which\n scope the snapshot must be complete *for*.\n2. Check whether a MarketSnapshot already exists by reading the artifact at the\n `market-snapshot` family's landing path, `specifications/src/market/index.ts`.\n The path belongs to the FAMILY, not to this playbook — every playbook that\n writes a market snapshot writes that same file. Its presence or absence\n selects the mode below.\n\n- **No snapshot yet** — produce a fresh one, authoring the slices in the\n order above.\n- **A snapshot exists** — *refine* it: read every slice, keep what still\n holds, and only add/correct the slices the current steering notes or new\n research call for. Never silently discard authored refs — a downstream\n positioning or benefit may depend on an ICP or persona ref, and dropping\n it orphans them (the validator will catch this, but honest refinement\n should not create the orphan in the first place).\n\n## Provenance — record where a claim came from\n\nYou are given the evidence a sibling research step gathered, with the URLs it read.\nWhere an entity's content rests on one of those sources, RECORD that URL on the entity\n— in the schema's own provenance fields, which exist for exactly this:\n\n| field | for |\n|---|---|\n| `pains[].evidence[]`, `gains[].evidence[]`, `benefits[].evidence` | what a source shows about the pain, gain or claim |\n| `proofs[].evidenceUrl`, `proofs[].attribution.url` | the page a proof points at |\n| `alternatives[].notes[]`, `category.notes[]`, `icps[].notes[]` | where the framing came from |\n\n⚠ An earlier revision of this section told you to use `authoredMetadata.notes` instead.\nThat was wrong, and the correction is recorded rather than quietly applied because the\nrun that exposed it did better than the instruction: handed the evidence, the model\nput 10 URLs into the typed `evidence`/`evidenceUrl` fields above and none into the\ngeneric metadata block it had been pointed at. Typed provenance is machine-readable\nand the generic block is prose; prefer the specific field every time one exists.\n\nThis is not bookkeeping. Measured on this playbook's first composite run\n(2026-08-29): the snapshot it produced carried **zero** source URLs and was, on that\ndimension, indistinguishable from the single-call version it replaced — the judge\ncalled the older one's evidence \"self-referential statements such as 'The vision\nspecifies…'\". A sourced claim and an invented one must not look the same in what you\nland, because nobody downstream can tell them apart afterwards.\n\nSo:\n\n- An entity grounded in a fetched page carries its URL in `authoredMetadata.notes`.\n- An entity you INFERRED carries that word, and `confidence` set honestly — `LOW` for\n a hypothesis, not `HIGH` because it reads well.\n- An entity the evidence did not cover is still authorable, and says so.\n\nOmit `authoredMetadata` only where the content is so self-evident that provenance\nwould be noise. A competitor's price is never that.\n\n## The creator's framing binds the category\n\nThe creator has already said what the product is. Their answers arrive in\nthe declared `creator_stated_facts` context section of your brief: the one-liner, the workflow the product\ncarries (`core-workflow`), who uses it (`user-groups`) and what is left out\n(`scope-boundary`). Given identical answers, two earlier runs chose two different\nproducts: one a customer-workflow CRM that left invoicing to other tools, the\nother trade-workflow software with invoicing at its centre and no customer\nfollow-up. That choice was never the market step's to make.\n\n- **Every stage the creator named stays in the product.** A category under which\n a stated stage disappears (follow-up, say) is the wrong category, not a sharper one.\n- **Nothing the creator left out becomes central.** A category that puts an\n excluded capability (invoicing, say) at its heart contradicts the scope\n boundary. Pick another.\n- **A reframe is MARKED, never silent.** You may name the category in better\n market language than the creator's (\"trade-operations CRM\" for \"a CRM for\n building firms\"), as long as the workflow and the boundary still hold. When\n your category's NAME differs from the kind of product the creator named, add\n a `category.notes[]` entry that starts with `Reframe:`. It quotes the creator's\n own framing, names yours, and says why. That note is how the creator sees the\n decision and overturns it. Never list the creator's own framing among\n `rejectedCategories`.\n- When the creator gave no workflow or boundary, frame from the one-liner and the\n problem, and say in the category notes that the shape was inferred.\n\n## Research posture (scaffold depth)\n\nGround each slice in evidence, not invention. At this scaffold depth the\nresearch is whatever the executing agent can gather about the product's\ncategory, competitors, and buyers; capture the *shape* faithfully (real\ncategory, real competing alternatives, plausible ICPs and personas) rather\nthan aspirational fiction. Where you are inferring rather than citing, say so\nin the slice's authored prose so a later, deeper research pass can tighten\nit. Do **not** build a research pipeline or block on external tooling here —\nricher web-research capability is a later-phase concern; this playbook\nconsumes whatever the agent already knows plus the creator's steering.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `market-snapshot-valid`\ngate (`validateMarketSnapshot`) before anything downstream consumes it. It\nenforces the cross-slice invariants — orphan refs (a positioning naming a\nmissing ICP, a benefit naming a missing pain/gain), an ICP with no persona,\ninfluence cycles, duplicate edges, proofs without support, message-template\nplaceholder mismatches, and more. Duplicate or malformed refs and\n`ERROR`-severity issues are hard failures; the snapshot does not advance\nuntil they clear. `WARN`-severity issues (e.g. stale-authored, a missing\npositioning for a targeted ICP) do not block but should be resolved. Read\n`market-snapshot-validation` for the full issue catalogue and emit a clean\nsnapshot the first time.\n\n## Scaffold-depth boundary (deferred to a later depth phase)\n\nKeep this playbook at scaffold depth. The following are explicitly **out of\nscope here** and are deepened in the methodology-depth phase, not now:\n\n- **Deep competitive teardown** — the reach surfaces capture *that* an\n alternative exists and *why* a buyer might pick it; a quantified,\n feature-by-feature competitor matrix is later-phase work.\n- **Quantified FIT / Kano scoring** — `market-scoring-interpretation` reads\n the deterministic FIT scorer; at scaffold depth you consume it to sanity-\n check benefit weighting, not to drive a precise prioritization model. The\n prioritization seam stays pluggable (see the capability-map playbook).\n- **Opportunity / TAM sizing and evidence depth** — jobs/pains/gains are\n authored as framing, not as a sized, sourced market model.\n\nIf you find yourself perfecting any of the above, stop and leave the slice at\nscaffold depth — depth is a dedicated later pass done once, holistically.\n\n## What you emit\n\nA single MarketSnapshot at `specifications/src/market/index.ts`,\nassembled from the slices above via their `market_*` skills, passing the\n`market-snapshot-valid` gate. The creator reviews the result (approval posture\n`approve_result`) before it is accepted as the journey's market intent.\n\n## References\n\nThese are skill FOLDERS installed in the application, listed so each slice's\nauthoring contract has a name. This step has no tools and does not open them.\n\n- `market-authoring-overview` — the orchestrator for\n the whole market slice; read it first to see how the slices fit together.\n- `market-category` — author the singular market\n category.\n- `market-icp` — author the Ideal Customer Profiles.\n- `market-persona` — author the personas per ICP.\n- `market-jobs-pains-gains` — author the Strategyzer\n jobs/pains/gains triplet.\n- `market-tone-of-voice` — author the named brand\n voices.\n- `market-add-feature-benefit` — author the benefit\n claims and their pain/gain weighting.\n- `market-positioning-authoring` — author the per-ICP\n positioning promise.\n- `market-channels` — author the reach channels.\n- `market-alternatives` — author the competing\n alternatives.\n- `market-triggers-and-journey` — author buying\n triggers and per-ICP buying journeys.\n- `market-proof-and-objection` — author proofs and\n the objections they answer.\n- `market-message-templates-authoring` — author the\n reusable message templates (last).\n- `market-scoring-interpretation` — interpret the\n deterministic FIT scorer to sanity-check benefit weighting.\n- `market-snapshot-validation` — the full validation\n issue catalogue the quality gate enforces.\n",
40
40
  "skillRefs": [
41
41
  "market-authoring-overview",
42
42
  "market-category",
@@ -55,7 +55,9 @@
55
55
  "market-snapshot-validation"
56
56
  ],
57
57
  "skillBodyRefs": [],
58
- "contextSources": [],
58
+ "contextSources": [
59
+ "creator_stated_facts"
60
+ ],
59
61
  "draftableDocumentDefinitionRefs": [],
60
62
  "suspendsForClarification": false,
61
63
  "briefAdequacyGate": false,
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.name","brand-name-screening.candidate"],"criterionRef":"application-creation:criterion/brand-name-screening-standing","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1}],"instruction":"Determine where the product's NAME stands, reading the coherence report's brand-name findings first — they are computed, not judged. On a line that carries a brand, a missing brand-name screening (brand-name-screening-missing) or a brand name no screening covers (brand-name-not-screened), or a conflict nobody chose to keep (brand-name-conflict-unacknowledged), is a gap in the definition: the brand identity's name question cannot be answered, or the name was never checked. A name chosen with the screening incomplete or kept despite a conflict is a deliberate, recorded decision that must be visible — in the risk register, as an entry derived from the brand-name-trademark-standing signal — not a failure. Fewer than three offerable proposals, or a creator-listed name the screening does not carry, is a concern. A line with no brand (no brand-name finding is reported for it) has nothing to assess.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The brand name was chosen with the screening incomplete or kept despite a conflict and the risk register carries it, or the screening offers fewer than three proposals or misses a name the creator listed.","GAP":"On a line with a brand, no screening is on record or the brand name was never screened; or a name kept despite a conflict is recorded nowhere, the risk register included.","INDETERMINATE":"The coherence report is not in evidence, so the brand name's standing cannot be read.","PASS":"The line carries no brand, or the brand name is a screened candidate whose screening is complete and clear."}},{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-top-down-coherence-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.name","brand-name-screening.candidate"],"criterionRef":"application-creation:criterion/brand-name-screening-standing","criterionVersion":3,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-name-screening-standing","requirementVersion":1}],"instruction":"Determine where the product's NAME stands, reading the coherence report's brand-name findings first — they are computed, not judged. On a line that carries a brand, a missing brand-name screening (brand-name-screening-missing) or a brand name no screening covers (brand-name-not-screened), or a conflict nobody chose to keep (brand-name-conflict-unacknowledged), is a gap in the definition: the brand identity's name question cannot be answered, or the name was never checked. A name chosen with the screening incomplete, with no register read at all (brand-name-no-register-read), or kept despite a conflict is a deliberate, recorded decision that must be visible — in the risk register, as an entry derived from the brand-name-trademark-standing signal, and in the launch list as a brand name not cleared — not a failure. Fewer than three offerable proposals, a creator-listed name the screening does not carry, a screening that read no register for any name (brand-name-screening-read-nothing), or a place the application declares it operates in that the screening does not list (brand-name-operating-jurisdiction-not-screened), is a concern. A line with no brand (no brand-name finding and no definition-brand-brief-missing finding is reported for it) has nothing to assess; a line that carries a brand whose brief has not landed (definition-brand-brief-missing) is assessed by the definition-completeness criterion, never passed here as a line with no brand.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The brand name was chosen with the screening incomplete or kept despite a conflict and the risk register carries it, or the screening offers fewer than three proposals or misses a name the creator listed.","GAP":"On a line with a brand, no screening is on record or the brand name was never screened; or a name kept despite a conflict is recorded nowhere, the risk register included.","INDETERMINATE":"The coherence report is not in evidence, so the brand name's standing cannot be read.","PASS":"The line carries no brand, or the brand name is a screened candidate whose screening is complete and clear."}},{"assessesAspects":["market.benefit","feature-drafts.draft"],"criterionRef":"application-creation:criterion/capability-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/capability-completeness","requirementVersion":1}],"instruction":"Determine whether every current-horizon market benefit is connected to at least one resolvable delivering feature. Treat an unwired benefit as a material gap; do not infer a connection from thematic similarity alone.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All benefits are wired, but one or more connections are weak, indirect, or insufficiently explained.","GAP":"At least one current-horizon benefit has no resolvable delivering feature.","INDETERMINATE":"The accepted evidence cannot establish the benefit-to-feature wiring completely.","PASS":"Every current-horizon benefit has at least one resolvable delivering feature."}},{"criterionRef":"application-creation:criterion/compliance-presence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/compliance-presence","requirementVersion":1}],"instruction":"Determine whether a product handling regulated or sensitive data declares at least one applicable compliance constraint. Do not invent regulation applicability; report indeterminate when the accepted evidence does not establish the data or sector posture.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A compliance constraint exists, but its applicability or coverage is weakly established.","GAP":"A regulated-data trigger is established and no applicable compliance constraint is declared.","INDETERMINATE":"The evidence cannot establish the regulated-data trigger or the applicable constraint posture.","PASS":"The evidence establishes either no regulated-data trigger or an applicable declared compliance constraint."}},{"criterionRef":"application-creation:criterion/definition-completeness","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/definition-completeness","requirementVersion":1}],"instruction":"Determine whether the definition holds every family the application's declared line carries, reading the coherence report's definition findings — they are computed, not judged. A business model (definition-business-model-missing) or a brand brief (definition-brand-brief-missing) the line carries that has not landed is a gap: the definition is not finished, whatever the other families say, and the finding names the step to run (or the interview to answer). A family the line declares not applicable is never reported and is not a gap. Do not infer a missing family from anything other than these findings.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Not used: a family the line carries is either on record or missing.","GAP":"The coherence report names a business model or a brand brief the declared line carries that has not landed.","INDETERMINATE":"The coherence report is not in evidence, so which families have landed cannot be read.","PASS":"The coherence report carries no definition-*-missing finding: every family the declared line carries has landed or is declared not applicable."}},{"assessesAspects":["market.icp","market.positioning"],"criterionRef":"application-creation:criterion/positioning-icp-coherence","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/positioning-icp-coherence","requirementVersion":1}],"instruction":"Determine whether positioning pillars address the declared core ICPs without centring an anti-target segment. Preserve the authored ICP classifications and do not silently reclassify a segment.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Positioning is broadly coherent but under-serves a core ICP or approaches an anti-target boundary.","GAP":"Positioning ignores the core ICPs or explicitly centres an anti-target segment.","INDETERMINATE":"The accepted evidence cannot connect positioning pillars to the classified ICP set.","PASS":"Positioning addresses the core ICPs and does not centre an anti-target segment."}},{"assessesAspects":["requirements.functional","roadmap.phase"],"criterionRef":"application-creation:criterion/requirement-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/requirement-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon functional requirement is delivered by a roadmap phase or explicitly deferred in accepted roadmap intent. Do not treat absence as deliberate deferral.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but one or more deferrals are weakly justified or difficult to trace.","GAP":"At least one functional requirement is neither delivered nor explicitly deferred.","INDETERMINATE":"The accepted evidence cannot establish complete requirement-to-roadmap accounting.","PASS":"Every current-horizon functional requirement is delivered or explicitly deferred."}},{"assessesAspects":["vision.success-criterion","roadmap.phase"],"criterionRef":"application-creation:criterion/success-criterion-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/success-criterion-coverage","requirementVersion":1}],"instruction":"Determine whether every current-horizon vision success criterion is delivered by at least one roadmap phase. Keep success criteria distinct from implementation tasks or generic aspirations.","schemaVersion":1,"verdictGuidance":{"CONCERN":"All criteria are covered, but one or more delivery links are weak or overly indirect.","GAP":"At least one current-horizon success criterion is not delivered by any roadmap phase.","INDETERMINATE":"The accepted evidence cannot establish complete success-criterion-to-roadmap coverage.","PASS":"Every current-horizon success criterion is delivered by at least one roadmap phase."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/top-down-phase-gate","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.phase-gate"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}