@wildo-ai/framework-knowledge 1.1.10 → 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 (1062) 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/derived-artifacts.md +4 -2
  4. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  5. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  6. package/dist/esm/framework-knowledge.definitions.js +459 -76
  7. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  8. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  9. package/dist/esm/framework-knowledge.research-provenance.d.ts +88 -0
  10. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
  11. package/dist/esm/framework-knowledge.research-provenance.js +140 -0
  12. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
  13. package/dist/esm/index.d.ts +2 -0
  14. package/dist/esm/index.d.ts.map +1 -1
  15. package/dist/esm/index.js +2 -0
  16. package/dist/esm/index.js.map +1 -1
  17. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  18. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  19. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  20. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +5 -2
  23. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +11 -6
  25. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  27. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  31. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +1 -1
  32. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +9 -5
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +11 -7
  36. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +4 -1
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +3 -3
  41. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +3 -2
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +2 -2
  45. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +7 -2
  47. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +2 -2
  49. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +2 -2
  51. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +26 -7
  53. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +23 -6
  55. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  56. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  57. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  59. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  60. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  61. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +9 -3
  62. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  63. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  65. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +1 -1
  66. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  67. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +1 -1
  69. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  70. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +1 -1
  72. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +6 -4
  74. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -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.map +1 -1
  79. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
  83. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
  86. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  87. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.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.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  95. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +9 -3
  97. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +8 -2
  99. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +8 -2
  101. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  103. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
  104. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  108. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
  110. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  113. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  115. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  116. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  117. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +95 -0
  118. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
  119. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +111 -0
  120. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
  121. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  123. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +4 -3
  124. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  125. package/dist/esm/source-anchor-grammar.d.ts +70 -0
  126. package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
  127. package/dist/esm/source-anchor-grammar.js +114 -0
  128. package/dist/esm/source-anchor-grammar.js.map +1 -0
  129. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  130. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  131. package/dist/knowledge/manifest.json +8 -8
  132. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
  133. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  134. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  135. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  136. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +350 -23
  137. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +6 -3
  138. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +248 -9
  139. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  140. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
  141. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +2 -2
  142. package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
  143. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +3 -3
  144. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +12 -1
  145. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +5 -2
  146. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +13 -4
  147. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +4 -3
  148. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +5 -0
  149. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +1 -1
  150. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +12 -0
  151. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +4 -3
  152. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +33 -5
  153. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +3 -3
  154. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +176 -22
  155. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +20 -3
  156. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +3 -2
  157. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +6 -2
  158. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +97 -23
  159. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  160. package/dist/knowledge/playbooks/refinement.document-facts/method.md +30 -3
  161. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -2
  162. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  163. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
  164. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
  165. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  166. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  167. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +9 -2
  168. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +2 -2
  169. package/dist/knowledge/playbooks/top_down.business-model/method.md +6 -0
  170. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +2 -2
  171. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  172. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +12 -2
  173. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +1 -1
  174. package/dist/knowledge/playbooks/top_down.definition/method.md +7 -2
  175. package/dist/knowledge/playbooks/top_down.definition/playbook.json +5 -4
  176. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
  177. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +3 -3
  178. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  179. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -1
  180. package/dist/knowledge/playbooks/top_down.risk-register/method.md +1 -1
  181. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -1
  182. package/dist/knowledge/playbooks/top_down.service-method/method.md +198 -0
  183. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +96 -0
  184. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +4 -0
  185. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +5 -4
  186. package/dist/knowledge/references/acp.execution-profile.md +9 -1
  187. package/dist/knowledge/references/application-maturity.config.md +1 -1
  188. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +55 -0
  189. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +13 -2
  190. package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
  191. package/dist/knowledge/references/backend.inbound-handlers.definition.md +426 -5
  192. package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
  193. package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
  194. package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
  195. package/dist/knowledge/references/build-plan.task-graph.config.md +238 -8
  196. package/dist/knowledge/references/business-model.pricing-plan.config.md +7 -0
  197. package/dist/knowledge/references/business-model.snapshot.validation.md +18 -0
  198. package/dist/knowledge/references/capability-composition.config.md +4 -3
  199. package/dist/knowledge/references/cli.market.generate-command.md +2 -1
  200. package/dist/knowledge/references/companion.technical-doc.service.md +166 -32
  201. package/dist/knowledge/references/engine.client-bundle.allow-list.md +14 -0
  202. package/dist/knowledge/references/engine.saas-technical-doc.config.md +1 -1
  203. package/dist/knowledge/references/engine.saas-website.config.md +16 -44
  204. package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
  205. package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
  206. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +4 -3
  207. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +22 -0
  208. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +45 -0
  209. package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
  210. package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
  211. package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
  212. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
  213. package/dist/knowledge/references/example.config.design-system.full.md +40 -116
  214. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
  215. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +70 -14
  216. package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
  217. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
  218. package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
  219. package/dist/knowledge/references/example.infra.environment-config.local.md +24 -0
  220. package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
  221. package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
  222. package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
  223. package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
  224. package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
  225. package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
  226. package/dist/knowledge/references/example.provider.backend-module-shape.md +10 -0
  227. package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
  228. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
  229. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
  230. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -1
  231. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
  232. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +52 -22
  233. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +81 -0
  234. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +19 -20
  235. package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
  236. package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
  237. package/dist/knowledge/references/example.website.blocks.section.md +20 -0
  238. package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
  239. package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
  240. package/dist/knowledge/references/example.website.demo.append.md +57 -0
  241. package/dist/knowledge/references/example.website.demo.approval.md +47 -0
  242. package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
  243. package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
  244. package/dist/knowledge/references/example.website.demo.connect.md +45 -0
  245. package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
  246. package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
  247. package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
  248. package/dist/knowledge/references/example.website.demo.transform.md +43 -0
  249. package/dist/knowledge/references/example.website.page.manifest.md +2 -6
  250. package/dist/knowledge/references/example.website.section.bento.md +27 -0
  251. package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
  252. package/dist/knowledge/references/example.website.section.factories.md +82 -0
  253. package/dist/knowledge/references/example.website.section.faq.md +17 -0
  254. package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
  255. package/dist/knowledge/references/example.website.section.hero.md +16 -0
  256. package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
  257. package/dist/knowledge/references/example.website.section.marquee.md +26 -0
  258. package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
  259. package/dist/knowledge/references/example.website.section.site-block.md +43 -0
  260. package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
  261. package/dist/knowledge/references/example.website.section.stats.md +23 -0
  262. package/dist/knowledge/references/example.website.section.steps.md +15 -0
  263. package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
  264. package/dist/knowledge/references/example.website.theme.composed.md +69 -0
  265. package/dist/knowledge/references/experience-plan.config.md +16 -0
  266. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +6 -0
  267. package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
  268. package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
  269. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +6 -0
  270. package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
  271. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +64 -0
  272. package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
  273. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +61 -2
  274. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +70 -0
  275. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +253 -0
  276. package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
  277. package/dist/knowledge/references/integration-plan.config.md +21 -1
  278. package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
  279. package/dist/knowledge/references/minions.tick-contract.md +2 -2
  280. package/dist/knowledge/references/placement-plan.config.md +75 -13
  281. package/dist/knowledge/references/platform.config.environment.deployment.md +9 -1
  282. package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -0
  283. package/dist/knowledge/references/platform.config.platform-key-management.md +206 -0
  284. package/dist/knowledge/references/platform.config.saas.md +106 -14
  285. package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
  286. package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
  287. package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
  288. package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
  289. package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
  290. package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
  291. package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
  292. package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
  293. package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
  294. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
  295. package/dist/knowledge/references/presets.models.surface-variant.md +10 -0
  296. package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
  297. package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
  298. package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
  299. package/dist/knowledge/references/presets.themes.compose-theme.md +46 -0
  300. package/dist/knowledge/references/roadmap.phase.config.md +2 -16
  301. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +131 -0
  302. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +77 -11
  303. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +158 -0
  304. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
  305. package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
  306. package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
  307. package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
  308. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
  309. package/dist/knowledge/references/saas.backend.domain-module.md +76 -1
  310. package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
  311. package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
  312. package/dist/knowledge/references/saas.backend.email.send.md +7 -0
  313. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +9 -1
  314. package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
  315. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
  316. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
  317. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
  318. package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
  319. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +207 -0
  320. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
  321. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +300 -3
  322. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +13 -2
  323. package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
  324. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
  325. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
  326. package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
  327. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
  328. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +27 -0
  329. package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
  330. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
  331. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
  332. package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
  333. package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
  334. package/dist/knowledge/references/saas.backend.system-access-service.md +242 -107
  335. package/dist/knowledge/references/saas.config.content-security-policy.md +1 -2
  336. package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
  337. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
  338. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
  339. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
  340. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
  341. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
  342. package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
  343. package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
  344. package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
  345. package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
  346. package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
  347. package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
  348. package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
  349. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +18 -16
  350. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
  351. package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
  352. package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
  353. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +17 -3
  354. package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
  355. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
  356. package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
  357. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +10 -2
  358. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +7 -4
  359. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +17 -16
  360. package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
  361. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
  362. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +149 -0
  363. package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
  364. package/dist/knowledge/references/saas.frontend.resource-label-params.md +3 -1
  365. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +17 -11
  366. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +89 -51
  367. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +9 -6
  368. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +141 -32
  369. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +66 -4
  370. package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
  371. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
  372. package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
  373. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
  374. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
  375. package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
  376. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
  377. package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
  378. package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
  379. package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
  380. package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
  381. package/dist/knowledge/references/saas.models.audit.trail-config.md +18 -5
  382. package/dist/knowledge/references/{saas.models.auth.service-provider-client-authentication.md → saas.models.auth.relationship-grantor-authentication.md} +54 -48
  383. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
  384. package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
  385. package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
  386. package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
  387. package/dist/knowledge/references/saas.models.config.organization-types.md +42 -82
  388. package/dist/knowledge/references/saas.models.conversation-threads.md +4 -3
  389. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +22 -0
  390. package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
  391. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +27 -0
  392. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +403 -0
  393. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +84 -0
  394. package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -1
  395. package/dist/knowledge/references/saas.models.engine-capabilities.md +28 -0
  396. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
  397. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
  398. package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
  399. package/dist/knowledge/references/saas.models.external-data-pipeline.md +81 -18
  400. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
  401. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +317 -0
  402. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
  403. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
  404. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +147 -0
  405. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
  406. package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
  407. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
  408. package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
  409. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +62 -0
  410. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +314 -0
  411. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
  412. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +62 -0
  413. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
  414. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +1 -0
  415. package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
  416. package/dist/knowledge/references/saas.models.flows.runnable-model.md +255 -0
  417. package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
  418. package/dist/knowledge/references/saas.models.http-api-binding.md +157 -42
  419. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
  420. package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
  421. package/dist/knowledge/references/saas.models.inbound-channels.md +4 -1
  422. package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
  423. package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
  424. package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
  425. package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
  426. package/dist/knowledge/references/saas.models.notifications.targets.md +25 -2
  427. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +58 -6
  428. package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
  429. package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
  430. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +73 -0
  431. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +48 -0
  432. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
  433. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
  434. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +911 -0
  435. package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
  436. package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
  437. package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
  438. package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
  439. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +224 -0
  440. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +277 -0
  441. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +113 -0
  442. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +68 -5
  443. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +67 -2
  444. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
  445. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +278 -40
  446. package/dist/knowledge/references/saas.models.provider-capabilities.md +33 -0
  447. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
  448. package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
  449. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +8 -0
  450. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +37 -0
  451. package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
  452. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
  453. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
  454. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
  455. package/dist/knowledge/references/saas.models.representative-activity.md +65 -0
  456. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +58 -2
  457. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
  458. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +57 -11
  459. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
  460. package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
  461. package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
  462. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
  463. package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
  464. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +99 -2
  465. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
  466. package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
  467. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
  468. package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
  469. package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
  470. package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
  471. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +9 -0
  472. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
  473. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +25 -0
  474. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
  475. package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
  476. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
  477. package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
  478. package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
  479. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -6
  480. package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -4
  481. package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
  482. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +121 -0
  483. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +3 -2
  484. package/dist/knowledge/references/saas.models.systems-of-record.md +36 -1
  485. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
  486. package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
  487. package/dist/knowledge/references/saas.public-runtime.contract.md +34 -2
  488. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
  489. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
  490. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +275 -13
  491. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
  492. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +9 -0
  493. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +16 -2
  494. package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
  495. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
  496. package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
  497. package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
  498. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +24 -2
  499. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
  500. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +19 -5
  501. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
  502. package/dist/knowledge/references/saas.website.astro.bridge.md +51 -14
  503. package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
  504. package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
  505. package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
  506. package/dist/knowledge/references/saas.website.astro.label-loader.md +38 -9
  507. package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
  508. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +48 -17
  509. package/dist/knowledge/references/saas.website.astro.site-context.md +17 -8
  510. package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
  511. package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
  512. package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
  513. package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
  514. package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
  515. package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
  516. package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
  517. package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
  518. package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
  519. package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
  520. package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
  521. package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
  522. package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
  523. package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
  524. package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
  525. package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
  526. package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
  527. package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
  528. package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
  529. package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
  530. package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
  531. package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
  532. package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
  533. package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
  534. package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
  535. package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
  536. package/dist/knowledge/references/saas.website.blog.bridge.md +98 -53
  537. package/dist/knowledge/references/saas.website.blog.collection-config.md +76 -24
  538. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
  539. package/dist/knowledge/references/saas.website.blog.frontmatter.md +104 -7
  540. package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
  541. package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
  542. package/dist/knowledge/references/saas.website.blog.index.md +43 -0
  543. package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
  544. package/dist/knowledge/references/saas.website.blog.post-renderer.md +113 -85
  545. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +181 -0
  546. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
  547. package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
  548. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +2 -1
  549. package/dist/knowledge/references/saas.website.config.site-context-loader.md +21 -1
  550. package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
  551. package/dist/knowledge/references/saas.website.consent.context.md +1 -1
  552. package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
  553. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
  554. package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
  555. package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
  556. package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
  557. package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
  558. package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
  559. package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
  560. package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
  561. package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
  562. package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
  563. package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
  564. package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
  565. package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
  566. package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
  567. package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
  568. package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
  569. package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
  570. package/dist/knowledge/references/saas.website.label-keys.format.md +2 -2
  571. package/dist/knowledge/references/saas.website.label-pack.validator.md +7 -8
  572. package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
  573. package/dist/knowledge/references/saas.website.legal.public-document-links.md +19 -4
  574. package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
  575. package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
  576. package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
  577. package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
  578. package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
  579. package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
  580. package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
  581. package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
  582. package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
  583. package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
  584. package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
  585. package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
  586. package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
  587. package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
  588. package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
  589. package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
  590. package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
  591. package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
  592. package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
  593. package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
  594. package/dist/knowledge/references/saas.website.page.context.md +9 -2
  595. package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
  596. package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
  597. package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
  598. package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
  599. package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
  600. package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
  601. package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
  602. package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
  603. package/dist/knowledge/references/saas.website.product.figures.md +320 -0
  604. package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
  605. package/dist/knowledge/references/saas.website.product.panels.md +324 -0
  606. package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
  607. package/dist/knowledge/references/saas.website.refs.section.md +2 -2
  608. package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
  609. package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
  610. package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
  611. package/dist/knowledge/references/saas.website.runtime.context.md +44 -17
  612. package/dist/knowledge/references/saas.website.section.component.md +21 -19
  613. package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
  614. package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
  615. package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
  616. package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
  617. package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
  618. package/dist/knowledge/references/saas.website.stacking.md +86 -0
  619. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
  620. package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
  621. package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
  622. package/dist/knowledge/references/service-method.config.md +270 -0
  623. package/dist/knowledge/references/website-plan.config.md +544 -32
  624. package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
  625. package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
  626. package/dist/knowledge/references/website-plan.page-routes.md +39 -0
  627. package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
  628. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +73 -9
  629. package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
  630. package/dist/knowledge/references/zod.decorators.data-categories.md +101 -11
  631. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +75 -6
  632. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +23 -1
  633. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
  634. package/dist/knowledge/references/zod.decorators.file-schema.md +6 -5
  635. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
  636. package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
  637. package/dist/knowledge/references/zod.decorators.schema-metadata.md +4 -0
  638. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +32 -4
  639. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +44 -5
  640. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +130 -9
  641. package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -8
  642. package/dist/knowledge/references/zod.factories.code.md +18 -9
  643. package/dist/knowledge/references/zod.factories.duration.md +23 -14
  644. package/dist/knowledge/references/zod.factories.money.md +24 -15
  645. package/dist/knowledge/references/zod.factories.phone.md +23 -14
  646. package/dist/knowledge/references/zod.factories.range.md +5 -1
  647. package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
  648. package/dist/knowledge/registries/framework-topics.json +2411 -139
  649. package/dist/knowledge/registries/playbooks.json +51 -30
  650. package/dist/knowledge/registries/source-tags.json +8500 -4768
  651. package/dist/knowledge/rules/database-migration-obligation.md +11 -5
  652. package/dist/knowledge/skills/INDEX.md +60 -33
  653. package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
  654. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +203 -0
  655. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
  656. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
  657. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
  658. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
  659. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
  660. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +15 -3
  661. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
  662. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
  663. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
  664. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +341 -0
  665. package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
  666. package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
  667. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
  668. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
  669. package/dist/knowledge/skills/application-database-migrations/SKILL.md +27 -9
  670. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
  671. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +6 -6
  672. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +124 -3
  673. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +90 -0
  674. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +59 -0
  675. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
  676. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +79 -2
  677. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +35 -1
  678. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
  679. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +3 -0
  680. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
  681. package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
  682. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
  683. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +189 -0
  684. package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
  685. package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
  686. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +127 -2
  687. package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
  688. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
  689. package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
  690. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +163 -0
  691. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +295 -0
  692. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
  693. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
  694. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +134 -33
  695. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
  696. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
  697. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +34 -7
  698. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
  699. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +37 -0
  700. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +178 -4
  701. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
  702. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +485 -61
  703. package/dist/knowledge/skills/config-app-shell/SKILL.md +57 -28
  704. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
  705. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
  706. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
  707. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
  708. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +17 -6
  709. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +24 -22
  710. package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
  711. package/dist/knowledge/skills/config-design-system/SKILL.md +245 -162
  712. package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
  713. package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
  714. package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
  715. package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
  716. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +37 -0
  717. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +235 -0
  718. package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
  719. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
  720. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
  721. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +7 -1
  722. package/dist/knowledge/skills/config-saas/SKILL.md +2 -0
  723. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +11 -3
  724. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +18 -5
  725. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +314 -0
  726. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
  727. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +8 -0
  728. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +1 -2
  729. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1182 -0
  730. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +61 -0
  731. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +56 -11
  732. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
  733. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +106 -14
  734. package/dist/knowledge/skills/config-saas-backend/SKILL.md +5 -3
  735. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
  736. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
  737. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +155 -92
  738. package/dist/knowledge/skills/configure-billing/SKILL.md +14 -0
  739. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +10 -0
  740. package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
  741. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
  742. package/dist/knowledge/skills/email-add-template/SKILL.md +46 -5
  743. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +7 -0
  744. package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
  745. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
  746. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +71 -14
  747. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +95 -13
  748. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +9 -1
  749. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
  750. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +44 -16
  751. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
  752. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
  753. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
  754. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +281 -20
  755. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +70 -14
  756. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +451 -0
  757. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +406 -0
  758. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +201 -0
  759. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +172 -0
  760. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
  761. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +7 -0
  762. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +63 -0
  763. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +324 -7
  764. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +95 -6
  765. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +255 -0
  766. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
  767. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
  768. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +112 -16
  769. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
  770. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +264 -0
  771. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +133 -0
  772. package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
  773. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +91 -5
  774. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +45 -0
  775. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +14 -3
  776. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
  777. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +5 -4
  778. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +27 -17
  779. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +136 -14
  780. package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
  781. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
  782. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
  783. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
  784. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
  785. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +4 -1
  786. package/dist/knowledge/skills/inbound-channels/SKILL.md +66 -8
  787. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +34 -1
  788. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +78 -6
  789. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
  790. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +434 -6
  791. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
  792. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +1 -1
  793. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +24 -13
  794. package/dist/knowledge/skills/infra-environment-config/SKILL.md +107 -2
  795. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +9 -1
  796. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -0
  797. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +294 -0
  798. package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
  799. package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
  800. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
  801. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
  802. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
  803. package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
  804. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
  805. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
  806. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
  807. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
  808. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +4 -2
  809. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
  810. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +9 -0
  811. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +9 -0
  812. package/dist/knowledge/skills/market-generation-cli/SKILL.md +2 -1
  813. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +2 -1
  814. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
  815. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
  816. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +40 -10
  817. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +57 -2
  818. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
  819. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
  820. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +150 -4
  821. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +9 -0
  822. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +81 -1
  823. package/dist/knowledge/skills/module-relationships/SKILL.md +50 -27
  824. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
  825. package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
  826. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1233 -0
  827. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
  828. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
  829. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +521 -0
  830. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +162 -0
  831. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +145 -0
  832. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
  833. package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
  834. package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
  835. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +67 -0
  836. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
  837. package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
  838. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +1 -1
  839. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
  840. package/dist/knowledge/skills/provider-backend-package/SKILL.md +138 -4
  841. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +32 -28
  842. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
  843. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +6 -0
  844. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +634 -0
  845. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +70 -0
  846. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +61 -2
  847. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
  848. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +9 -5
  849. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +9 -2
  850. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +47 -5
  851. package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
  852. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
  853. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +26 -14
  854. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
  855. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
  856. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
  857. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
  858. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
  859. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +256 -1
  860. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +71 -35
  861. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
  862. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
  863. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +132 -55
  864. package/dist/knowledge/skills/resource-add-resource/SKILL.md +49 -4
  865. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +58 -2
  866. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +137 -0
  867. package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
  868. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +102 -4
  869. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
  870. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
  871. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +6 -0
  872. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +323 -0
  873. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +18 -0
  874. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +159 -0
  875. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +60 -3
  876. package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
  877. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
  878. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +1 -1
  879. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +3 -2
  880. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +195 -23
  881. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +108 -2
  882. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +242 -107
  883. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +176 -10
  884. package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
  885. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +88 -50
  886. package/dist/knowledge/skills/resource-external-data/SKILL.md +280 -64
  887. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
  888. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
  889. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +71 -12
  890. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
  891. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +81 -18
  892. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +238 -49
  893. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
  894. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +145 -0
  895. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
  896. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
  897. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +61 -14
  898. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
  899. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
  900. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +39 -13
  901. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
  902. package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
  903. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +1 -1
  904. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +17 -4
  905. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
  906. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
  907. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +6 -0
  908. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +31 -1
  909. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +3 -1
  910. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +68 -5
  911. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +25 -0
  912. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +26 -10
  913. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
  914. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +9 -7
  915. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
  916. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +79 -6
  917. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
  918. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +127 -12
  919. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -4
  920. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +32 -4
  921. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +44 -5
  922. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +116 -66
  923. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
  924. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +203 -18
  925. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +6 -0
  926. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +155 -76
  927. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +19 -17
  928. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +120 -1
  929. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
  930. package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
  931. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +168 -58
  932. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
  933. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
  934. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +151 -1
  935. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +144 -57
  936. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +131 -0
  937. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +57 -31
  938. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +56 -0
  939. package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
  940. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
  941. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
  942. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +42 -11
  943. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +141 -32
  944. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +66 -4
  945. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
  946. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
  947. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +9 -0
  948. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +15 -7
  949. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +71 -14
  950. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +19 -5
  951. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +14 -5
  952. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -1
  953. package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
  954. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +5 -0
  955. package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
  956. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +11 -4
  957. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +11 -2
  958. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +17 -3
  959. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +61 -25
  960. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +251 -78
  961. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1064 -192
  962. package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
  963. package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
  964. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
  965. package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
  966. package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
  967. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +39 -18
  968. package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
  969. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +18 -5
  970. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +84 -28
  971. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +67 -64
  972. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +58 -23
  973. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
  974. package/dist/knowledge/skills/website-label-pack/SKILL.md +24 -17
  975. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +112 -77
  976. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +24 -13
  977. package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
  978. package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
  979. package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
  980. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +255 -397
  981. package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
  982. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +28 -6
  983. package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
  984. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -326
  985. package/dist/knowledge/skills/website-page-authoring/SKILL.md +160 -67
  986. package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
  987. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +24 -3
  988. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
  989. package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
  990. package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
  991. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +48 -28
  992. package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
  993. package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
  994. package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
  995. package/dist/knowledge/skills/website-section-contact/SKILL.md +408 -185
  996. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
  997. package/dist/knowledge/skills/website-section-cta/SKILL.md +398 -234
  998. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
  999. package/dist/knowledge/skills/website-section-faq/SKILL.md +561 -302
  1000. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
  1001. package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
  1002. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +647 -274
  1003. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
  1004. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +572 -264
  1005. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
  1006. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +532 -233
  1007. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
  1008. package/dist/knowledge/skills/website-section-hero/SKILL.md +603 -332
  1009. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
  1010. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
  1011. package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
  1012. package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
  1013. package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
  1014. package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
  1015. package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
  1016. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
  1017. package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
  1018. package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
  1019. package/dist/knowledge/skills/website-section-pricing/SKILL.md +549 -378
  1020. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +77 -0
  1021. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
  1022. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +2 -1
  1023. package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
  1024. package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
  1025. package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
  1026. package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
  1027. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
  1028. package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
  1029. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
  1030. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
  1031. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
  1032. package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
  1033. package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
  1034. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +739 -315
  1035. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
  1036. package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
  1037. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
  1038. package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
  1039. package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
  1040. package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
  1041. package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
  1042. package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
  1043. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +183 -67
  1044. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +575 -57
  1045. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +1 -1
  1046. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +6 -94
  1047. package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
  1048. package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
  1049. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
  1050. package/dist/knowledge/topic-index.json +16442 -8572
  1051. package/package.json +4 -4
  1052. package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
  1053. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
  1054. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
  1055. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
  1056. package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
  1057. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
  1058. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
  1059. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
  1060. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
  1061. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
  1062. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "refinement.document-facts",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "phase": "refinement",
5
5
  "intent": "Derive the application's governed-document FACTS from truth it has already accepted — its vision (including the compliance regimes the posture pass recorded), its domain and its requirements — and land them as the `document-facts` family. A fact is a plain statement about how this application actually behaves: what data it holds, how long it keeps it, who it discloses to, what rights it honours. This produces the raw material a privacy notice or service terms is drafted FROM; it never drafts the document, never decides a legal question, and never states a fact the application's own code and accepted specifications do not support. Mechanism facts — retention treatment, data-subject kind, subject export — are read from the resource configurations, which declare what the application will actually do to a row; specifications supply purpose, not mechanism.",
6
6
  "preconditions": [
@@ -37,7 +37,7 @@
37
37
  ],
38
38
  "stepOutputs": [],
39
39
  "method": {
40
- "guidance": "# Governed-document facts — derivation 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 you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource declarations**, which are already in this brief, under *\"The application's\n compliance-relevant resource declarations (read from its CODE)\"*. Per resource:\n `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session\n an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer\n for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already\n written down and enforced at runtime. They are the best evidence a governed document can rest on,\n and they need no interpretation — only phrasing.\n\n **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that\n does not correspond to a declaration in that section is not derived, it is recalled, and this\n playbook's whole reason for existing is the difference.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nThat section reports engine-declared and application-declared coverage **separately**, and you should\nkeep them apart in your facts too: the two have different owners, so they have different remedies. An\napplication's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.\n\nDo not assume the engine half is the settled half. Read the counts. On the first real application to\nbe measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user\naccount and its self-view — and nothing on credentials, profiles, audit logs, files or membership.\nWhatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with\ndeclarations it has not made is exactly as false as one crediting the application.\n\n## COVER THE WHOLE SET — this is the half a first attempt gets wrong\n\nThe facts you declare here are the only thing a later document can state as established. A concern you\nsay nothing about does not become a cautious sentence in the notice; it becomes a clause reading *\"this\nhas not yet been established\"*, in a document about somebody's personal data, when the application had\nalready established it.\n\nMeasured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and\nthe notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,\nwhich every one of that application's resources declares, and analytics, which it does not enable. Both\nwere answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:\na notice that understates what an application does is as wrong as one that overstates it.\n\nWork through this list and declare a fact for each one you can answer:\n\n| what a document will need | where the answer is |\n|---|---|\n| what personal data is held, and in which records | the resource declarations + the domain plan |\n| what erasure does to each record | `retentionPolicy.mode` per resource |\n| how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |\n| whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |\n| whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |\n| who else can see the data inside the application | the domain model — roles, membership, sharing |\n| which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |\n| whether the application makes automated decisions or uses AI | the AI POSTURE section — per enabled capability, a declared consequence or OUTSTANDING |\n| what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |\n| what consent the application asks for | the declared capabilities + the domain plan |\n| how organizations are separated from each other | the domain model and the tenancy declarations |\n\n## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief\n\nThe sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE\nand nothing else — it never sees the resource declarations, the retention schedule, the processor\nregister, the AI posture or the client-storage inventory. **A gap you notice and do not write down is a\ngap that disappears**, and the document then states the half that was answered as though it were the\nwhole.\n\nSo when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,\ndeclare a fact recording it, naming what is missing:\n\n- *\"No retention period is declared for any of the four data classes; all four require an operator\n decision.\"*\n- *\"The `app` frontend surface's own client storage has not been catalogued.\"*\n\nThis is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated\nbrowser storage is configured — true — and said nothing about the frontend surface nobody had\ninventoried. A reader of the notice would take the first as the whole answer.\n\nA gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`\nfor it — that says the question does not arise, and it does.\n\n**An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can\ndeclare a period for each of the four data classes and has not for some of them. State which classes\nare declared, with their periods and the reasons given, and state plainly which are still undecided —\nthe remedy is an operator deciding, not the framework growing a mechanism. Never write a period the\napplication has not declared, and never soften an absent one into \"as long as necessary\": that is a\ncommitment nobody made and nothing enforces.\n\n**An absent capability is a fact, not a silence.** If no analytics provider is configured, that is\n`KNOWN`: *\"no external analytics provider is configured\"*. If no AI capability is declared, say so. These\nare the answers that let a notice state something true instead of confessing ignorance about a decision\nthe application already made — and the composition section in your brief lists them exactly.\n\n**Not built yet is not \"none\".** When your brief says NOT BUILT YET, the build has not yet produced the\napplication's own resources, and their absence is a stage of the build, not a decision. Write that the\napplication's own data is not yet established. Never write \"zero resources\", \"holds no personal data\" or\n\"declares nothing\" for data that does not exist yet. These facts are dated by the code they were read\nfrom: once the build commits its resources, configuration or roles, they go stale and are derived again.\nAn earlier run wrote \"zero personal-data resources\" and \"no billing\" an hour before the build declared\nboth, and those sentences stayed in the file.\n\n**Declare mechanism facts per RESOURCE where the resources differ.** \"All eight application resources\ndeclare a subject-export mode\" is a usable fact; \"the application supports exports\" is not, because a\nreader cannot tell which records it covers.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## The shape of a declaration — get this right or the whole file is rejected\n\nEach declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),\nand **every one of them must be UNIQUE across the file**:\n\n- `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the\n single most common way a good fact set fails: a drafter answering several facts about retention\n gives them all `slug: \"retention\"`. Make each one describe its own fact.\n- `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two\n declarations may not share a `factSlug` either. If you want to say two things about retention, they\n are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.\n- `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY\n repeat; it is a classification, not an identity.\n\nA rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:\nre-read your list for two entries sharing a name.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE\n accepts. A declaration carrying any other authority is refused before it reaches a file.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch\n\nYour output replaces `document-facts` entirely on every run. That is why the facts only a human may\nestablish — a creator decision, a qualified review — live in a SEPARATE family,\n`document-facts-authored`, which you neither read nor write. Before the two were split they shared one\nfile, and a producer run silently deleted the human half.\n\nSo an absent fact is never something for you to fill in \"because nobody else will\". The brief already\nnames which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent\nis the correct outcome rather than a gap you are working around.\n\n## Some facts are COMPUTED, and you do not declare them\n\nA few facts are not written by anyone. The runtime computes them from the application's own typed\ndeclarations every time the facts are read:\n\n- `controller-and-contact` is computed from `operatorComplianceIdentity`;\n- `recipients-and-processors` is computed from the processor register and the providers' deployment\n choices;\n- `lawful-bases` is computed from `operatorComplianceIdentity.lawfulBases`;\n- `retention-rules` is computed from the `dataRetention` schedule and each resource's erasure treatment;\n- `international-transfers` is computed from each register entry's `transferDetermination`;\n- `rights-and-complaint-route` is computed from the operating jurisdictions, the lawful bases, the\n privacy contact, the identity-verification procedure and the role allocations;\n- `retention-enforcement` is computed from the retention-enforcement records the evidence plane\n collected;\n- `system-of-record-sources` is computed from the resources bound to, or copied from, a declared\n system of record, and the purposes their bindings link.\n\nThis list is a convenience. The brief's \"do not declare\" heading is the authority.\n\nThe brief lists them under a separate \"do not declare\" heading. Declaring one is refused at\ngeneration, and a copy in the file is refused by the family's validator.\n\nThe reason is drift. Your answer would be a paraphrase of a declaration that already exists, and it\nwould go stale the day that declaration changes. If the declaration a computed fact reads is missing,\nthe fact stays absent, and the documents mark it as owed. Leave that gap alone. Do not state a\ncontroller, a recipient, a basis, a period, a transfer or a right in prose to fill it: say what is missing in a fact you do own, or leave it to\nthe document's gap marking.\n\n## A judge reads your facts against what you were given\n\nAfter the file lands, an advisory judge reads every declaration beside the same evidence you had: the\ninput families, the application's compliance-relevant declarations and the computed facts. It reports\ntwo kinds of finding. A **gap** is a claim a governed document would publish as true that nothing\nestablishes: a recipient, a transfer, a retention period, a lawful basis or an AI use that no\ndeclaration names, or an undeclared matter stated as settled. A **concern** is wording drift a reader\nwould not act on differently.\n\nThe judge refuses nothing, and a finding does not undo your file. It is written so that an unsupported\nclaim is named before a document cites it. Write each fact so that its source is obvious from the\nwords.\n\n## Refs are stamped for you\n\nSupply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and\nauthority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;\na contract that asked you to would be asking you to fail on form rather than on substance.\n\n(This paragraph listed `retention-rules`, `data-categories-and-sources` and\n`recipients-and-processors` as examples. All three are required fact names, and naming three of eight\nas \"examples\" invited a drafter to treat them as a style to imitate rather than a set to use. The\nauthoritative list now arrives in the brief.)\n\n**For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were\ngiven lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.\n\nThis is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a\nfact answering the right question under a different name is a fact the document cannot cite — it reads\nas missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of\nthe eight a privacy notice requires, because the names were semantically adjacent and lexically\ndisjoint (`retention-period-schedule-status` for `retention-rules`).\n\nFor anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as\nthe question it answers. An application legitimately declares facts no document requires.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\nEverything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as\ninput sections under \"# Accepted application truth\", and the application's live resource\nDECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as\nthe declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to\nrun in this mode.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n\n## External sign-in assurance\n\nDerive `document-fact:external-sign-in-assurance` from the brief's declared authentication policy, including organization restrictions. Do not infer an active enterprise connection from an enabled method. Describe enterprise OAuth2/OIDC responsibility delegation separately from observed MFA. For social login, name the configured warning/strict treatment and provider evidence limitations. An unreadable configuration remains unresolved, never “no external login”. Feed this fact into the service-terms account-duties clause; liability conclusions still require qualified review.\n",
40
+ "guidance": "# Governed-document facts — derivation 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 you produce\n\nOne `document-facts` file for the application: a list of **facts**, each a plain statement about how\nthis application actually behaves. Not prose for a notice — the raw material a notice is later drafted\nfrom, and the thing a drafted clause is checked against.\n\nA fact is the answer to a question a reader of a legal document would want settled:\n\n- what categories of personal data does the application hold, and where do they come from;\n- what does it do with them, and for how long does it keep them;\n- who else sees them — providers, processors, other tenants;\n- what rights does it actually honour, and through which mechanism;\n- who operates the service, and how is it contacted.\n\n## The rule that governs everything here\n\n**Every fact you write must be supported by something the application has already accepted** — and the\nstrongest support is not prose about the application, it is **the application's own code**.\n\nRead in this order:\n\n1. **The resource declarations**, which are already in this brief, under *\"The application's\n compliance-relevant resource declarations (read from its CODE)\"*. Per resource:\n `retentionPolicy.mode` (what erasure does to a row), `dataSubjectPolicy.kind` (whose login session\n an erasure ends), `systemAccessPolicy.exportSubject` (whether an Art. 15 / Art. 20 export can answer\n for them) and `seeRetained` (the audited path to retained data). These are DECLARATIONS, already\n written down and enforced at runtime. They are the best evidence a governed document can rest on,\n and they need no interpretation — only phrasing.\n\n **Use them.** A fact about a mechanism — what is kept, what is scrubbed, what can be exported — that\n does not correspond to a declaration in that section is not derived, it is recalled, and this\n playbook's whole reason for existing is the difference.\n2. **The compliance constraints on the vision**, which tell you which facts a reader will need.\n3. **The domain plan and requirements**, for what the product is FOR — purpose, not mechanism.\n\nThe split between 1 and 3 is the point. A specification says what the application is meant to do; a\nresource configuration says what it will actually do to a row tomorrow morning. Where they disagree,\nthe configuration is the fact.\n\nThat section reports engine-declared and application-declared coverage **separately**, and you should\nkeep them apart in your facts too: the two have different owners, so they have different remedies. An\napplication's authors cannot close an engine gap, and the engine's maintainers cannot close theirs.\n\nDo not assume the engine half is the settled half. Read the counts. On the first real application to\nbe measured, the engine declared an erasure treatment on **two of eighty-five** resources — the user\naccount and its self-view — and nothing on credentials, profiles, audit logs, files or membership.\nWhatever the numbers say in your own brief, they are the fact; a sentence crediting the framework with\ndeclarations it has not made is exactly as false as one crediting the application.\n\n## COVER THE WHOLE SET — this is the half a first attempt gets wrong\n\nThe facts you declare here are the only thing a later document can state as established. A concern you\nsay nothing about does not become a cautious sentence in the notice; it becomes a clause reading *\"this\nhas not yet been established\"*, in a document about somebody's personal data, when the application had\nalready established it.\n\nMeasured on the first real application (wonder-crm, 2026-08-29): this pass produced **three** facts, and\nthe notice drafted from them marked **ten of thirteen** concerns incomplete — including subject rights,\nwhich every one of that application's resources declares, and analytics, which it does not enable. Both\nwere answerable from the brief in front of it. That is the failure mode to avoid, and it is not caution:\na notice that understates what an application does is as wrong as one that overstates it.\n\nWork through this list and declare a fact for each one you can answer:\n\n| what a document will need | where the answer is |\n|---|---|\n| what personal data is held, and in which records | the resource declarations + the domain plan |\n| what erasure does to each record | `retentionPolicy.mode` per resource |\n| how long records are kept | the RETENTION SCHEDULE in your brief — four classes, each declared or UNDECIDED |\n| whether a subject-access or portability export can answer for a record | `systemAccessPolicy.exportSubject` per resource |\n| whether retained data stays reachable, and audited | `systemAccessPolicy.seeRetained` per resource |\n| who else can see the data inside the application | the domain model — roles, membership, sharing |\n| which third parties receive data, WHO they are and WHERE they process | the PROCESSOR REGISTER section — declared entries, plus the providers it lists UNDECLARED |\n| whether the application makes automated decisions or uses AI | the `## Automated decisions and AI` section — per AI capability of the contracted service, then `Agents declaring their use`, `OUTSTANDING agents` (or `Agents: NOT READ`) and the regulatory reading: the declared use, its domain and class, its human review (derived from approval gates where every write is gated) |\n| what each agent's model provider receives, and what is screened or moderated | the same section's `Content guardrails each agent DECLARES` list — the personal-data treatment, prompt-injection screening and output moderation each agent declares |\n| what analytics or tracking runs, and what is stored in a browser | the declared capabilities + the CLIENT STORAGE section (framework entries, then per surface) |\n| what consent the application asks for | the declared capabilities + the domain plan |\n| how organizations are separated from each other | the domain model and the tenancy declarations |\n\n## RECORD THE GAPS AS FACTS TOO — nothing downstream can see this brief\n\nThe sections above are yours alone. The pass that drafts the document reads the `document-facts` FILE\nand nothing else — it never sees the resource declarations, the retention schedule, the processor\nregister, the AI uses and agents or the client-storage inventory. **A gap you notice and do not write down is a\ngap that disappears**, and the document then states the half that was answered as though it were the\nwhole.\n\nSo when a section names something as `UNDECIDED`, `UNDECLARED`, `OUTSTANDING` or `UNINVENTORIED`,\ndeclare a fact recording it, naming what is missing:\n\n- *\"No retention period is declared for any of the four data classes; all four require an operator\n decision.\"*\n- *\"The `app` frontend surface's own client storage has not been catalogued.\"*\n\nThis is the failure mode to avoid, measured on a real run: the facts stated that no consent-gated\nbrowser storage is configured — true — and said nothing about the frontend surface nobody had\ninventoried. A reader of the notice would take the first as the whole answer.\n\nA gap recorded as a fact is `KNOWN`: the thing that is known IS the gap. Do not use `NOT_APPLICABLE`\nfor it — that says the question does not arise, and it does.\n\n**An UNDECIDED retention period is an OPERATOR's decision, not a framework gap.** The application can\ndeclare a period for each of the four data classes and has not for some of them. State which classes\nare declared, with their periods and the reasons given, and state plainly which are still undecided —\nthe remedy is an operator deciding, not the framework growing a mechanism. Never write a period the\napplication has not declared, and never soften an absent one into \"as long as necessary\": that is a\ncommitment nobody made and nothing enforces.\n\n**Agents are AI uses one by one.** Declare a fact per agent of the contracted service — or one fact listing\nthem, each by ref — stating its declared use, whether it decides anything about a person and who reviews it,\nand what its model is sent in place of personal data. An agent listed OUTSTANDING, a guardrail \"not declared\"\nand a field NOT READ are gaps: record each as such, never as \"the agent decides nothing\" or \"nothing is\nsent\". State a guardrail as what the agent DECLARES: an organization can tighten it at run time, and a fact\nmust not claim the tightening happened.\n\n**An absent capability is a fact, not a silence.** If no analytics provider is configured, that is\n`KNOWN`: *\"no external analytics provider is configured\"*. If no AI capability is declared, say so. These\nare the answers that let a notice state something true instead of confessing ignorance about a decision\nthe application already made — and the composition section in your brief lists them exactly.\n\n**Not built yet is not \"none\".** When your brief says NOT BUILT YET, the build has not yet produced the\napplication's own resources, and their absence is a stage of the build, not a decision. Write that the\napplication's own data is not yet established. Never write \"zero resources\", \"holds no personal data\" or\n\"declares nothing\" for data that does not exist yet. These facts are dated by the code they were read\nfrom: once the build commits its resources, configuration or roles, they go stale and are derived again.\nAn earlier run wrote \"zero personal-data resources\" and \"no billing\" an hour before the build declared\nboth, and those sentences stayed in the file.\n\n**Declare mechanism facts per RESOURCE where the resources differ.** \"All eight application resources\ndeclare a subject-export mode\" is a usable fact; \"the application supports exports\" is not, because a\nreader cannot tell which records it covers.\n\nYou are **not** deciding anything. A legal basis, a controller-versus-processor role, a governing law,\na liability position and a retention *duration the product has not chosen* are all decisions, and none\nof them is yours. If a fact needs a human to decide it, **leave it out**. Do not write a plausible\nplaceholder, and do not soften a decision into a fact by hedging the wording.\n\nLeaving it out is not a failure — it is the designed behaviour, and it does **not** block anything\ndownstream. A document clause that would have rested on a fact you did not declare is still written:\nit is marked as not yet established, names what it needs and who can supply it, and the document is\nproduced. So an absence costs the reader a precise statement of a gap, which is useful. A guessed fact\ncosts them a published false statement about somebody's data, which is not.\n\n## The shape of a declaration — get this right or the whole file is rejected\n\nEach declaration carries three slugs, all lowercase kebab-case (`retention-treatment-per-resource`),\nand **every one of them must be UNIQUE across the file**:\n\n- `slug` — names THIS declaration. Two declarations sharing a `slug` are rejected, and this is the\n single most common way a good fact set fails: a drafter answering several facts about retention\n gives them all `slug: \"retention\"`. Make each one describe its own fact.\n- `factSlug` — names the FACT being answered. One governance scope carries one answer per fact, so two\n declarations may not share a `factSlug` either. If you want to say two things about retention, they\n are two facts (`retention-treatment-per-resource`, `retention-duration`), not one fact twice.\n- `sensitivitySlug` — how sensitive the fact itself is (`public`, `internal-governance`). This one MAY\n repeat; it is a classification, not an identity.\n\nA rejection naming `declarations.N.slug` is almost always a COLLISION rather than a bad character:\nre-read your list for two entries sharing a name.\n\n## KNOWN and NOT_APPLICABLE are different answers — and both are different from absence\n\nThree states, and confusing them is the most common way this pass goes wrong.\n\n| state | means | how you write it |\n|---|---|---|\n| `KNOWN` | the application does this, and here is what it does | `resolution: KNOWN` with `value` |\n| `NOT_APPLICABLE` | this was considered and it genuinely does not apply | `resolution: NOT_APPLICABLE` with `reason` |\n| absent | nobody has established this yet | omit the declaration entirely |\n\n`NOT_APPLICABLE` is a real, useful answer — \"this application performs no international transfers\"\ntells a reviewer something. It is **not** a way to dispose of a fact you could not find. If you do not\nknow, the honest output is absence.\n\nA `KNOWN` fact must carry an actual value. An empty string, a blank one or an empty object is rejected\nby the validator: a fact that exists and says nothing is worse than a missing one, because a document\ncan cite it and learn nothing.\n\n## Read the compliance constraints first\n\n`top_down.compliance-posture` records each applicable regime as a `compliance`-kind constraint on the\nvision. Those constraints tell you which facts matter. A GDPR constraint means a reader will need data\ncategories, purposes, retention, recipients, transfers and rights mechanisms. A data-residency\nconstraint means where data lives is a fact worth stating.\n\nDerive the fact SET from the regimes, then answer each one from the application's own truth — the\nconfigurations first. Where the regime implies a fact the application has not settled, that is an\nabsence: record nothing, and let the document state the gap in place.\n\n## Who the privacy notice addresses\n\nThe facts brief says so when it matters. On an application one organization owns (an internal tool),\nthe privacy notice is addressed to that organization's STAFF, not to the public, and the brief carries\na paragraph saying so. Word the facts you declare for that reader: processing purposes and data\ncategories in terms of what the application records about staff as they work in it. The lawful bases\nand the recipients stay computed from the operator's declarations, as below; the audience never makes\nthem yours to declare. Where the brief says nothing about the audience, the notice is the public one.\n\n## Scope: one operator, deliberately\n\nEvery fact you write is attributed to one application-operator governance scope. The family can carry\nfacts for a tenant organization or a shared-responsibility boundary too, but choosing a different\nsubject per fact is deciding **shared-responsibility attribution**, which is exactly the thing that\nmust never be guessed or flattened. One operator scope is the honest output of a derivation; a second\nsubject is a human's edit.\n\nThe `operatorSlug` you supply is an operator identity, **not** a legal-entity assertion. It names who\nruns the service, not which company is on the contract — that is a decision, and it is absent until a\nhuman makes it.\n\n## What you never write\n\n- A legal basis, a lawful-processing justification, or a controller/processor role.\n- A retention period the product has not chosen, or one you inferred from a default.\n- A named human, a reviewer, a qualification or an independence statement. Every fact you produce\n carries `APPLICATION_SPECIFICATION` authority — the accepted specification is the authority, and it\n is the only one a derivation can honestly claim, and since 2026-09-03 the only one the family's TYPE\n accepts. A declaration carrying any other authority is refused before it reaches a file.\n- A decision instant. You have no clock, and the honest instant for a human decision is the commit that\n records it.\n- A security claim beyond what the application's configuration actually shows.\n- A fact about a provider, region or capability the application has not configured.\n\n## The file you write is REGENERATED WHOLE, and a second family holds what you must not touch\n\nYour output replaces `document-facts` entirely on every run. That is why the facts only a human may\nestablish — a creator decision, a qualified review — live in a SEPARATE family,\n`document-facts-authored`, which you neither read nor write. Before the two were split they shared one\nfile, and a producer run silently deleted the human half.\n\nSo an absent fact is never something for you to fill in \"because nobody else will\". The brief already\nnames which facts are yours; anything it withholds has a home you cannot reach, and leaving it absent\nis the correct outcome rather than a gap you are working around.\n\n## Some facts are COMPUTED, and you do not declare them\n\nA few facts are not written by anyone. The runtime computes them from the application's own typed\ndeclarations every time the facts are read:\n\n- `controller-and-contact` is computed from `operatorComplianceIdentity`;\n- `recipients-and-processors` is computed from the processor register and the providers' deployment\n choices;\n- `lawful-bases` is computed from `operatorComplianceIdentity.lawfulBases`;\n- `retention-rules` is computed from the `dataRetention` schedule and each resource's erasure treatment;\n- `international-transfers` is computed from each register entry's `transferDetermination`;\n- `rights-and-complaint-route` is computed from the operating jurisdictions, the lawful bases, the\n privacy contact, the identity-verification procedure and the role allocations;\n- `retention-enforcement` is computed from the retention-enforcement records the evidence plane\n collected;\n- `system-of-record-sources` is computed from the resources bound to, or copied from, a declared\n system of record, and the purposes their bindings link;\n- `ai-use-inventory` is computed from the AI-use declarations — each capability's `aiUsePosture` and\n each agent's own `aiUse` — scoped to the contracted service and joined to the providers serving each\n use and the processor register;\n- `ai-content-guardrails` is computed from the agent-operation records and guardrail audit events the\n evidence plane collected: per agent, the guardrails it declares, the recorded calls each was active\n on and what each judged.\n\nThe AI facts replace the AI half of the service terms' AI question. What is left of\n`ai-features-and-content-use` (whether customer content trains or improves a model) is a decision a\nperson records, so it is not yours to declare either.\n\nThis list is a convenience. The brief's \"do not declare\" heading is the authority.\n\nThe brief lists them under a separate \"do not declare\" heading. Declaring one is refused at\ngeneration, and a copy in the file is refused by the family's validator.\n\nThe reason is drift. Your answer would be a paraphrase of a declaration that already exists, and it\nwould go stale the day that declaration changes. If the declaration a computed fact reads is missing,\nthe fact stays absent, and the documents mark it as owed. Leave that gap alone. Do not state a\ncontroller, a recipient, a basis, a period, a transfer or a right in prose to fill it: say what is missing in a fact you do own, or leave it to\nthe document's gap marking.\n\n## A judge reads your facts against what you were given\n\nAfter the file lands, an advisory judge reads every declaration beside the same evidence you had: the\ninput families, the application's compliance-relevant declarations and the computed facts. It reports\ntwo kinds of finding. A **gap** is a claim a governed document would publish as true that nothing\nestablishes: a recipient, a transfer, a retention period, a lawful basis or an AI use that no\ndeclaration names, or an undeclared matter stated as settled. A **concern** is wording drift a reader\nwould not act on differently.\n\nThe judge refuses nothing, and a finding does not undo your file. It is written so that an unsupported\nclaim is named before a document cites it. Write each fact so that its source is obvious from the\nwords.\n\n## Refs are stamped for you\n\nSupply slugs. The runtime turns each into its namespaced ref, attaches the governance scope and\nauthority, assigns versions and sorts the declarations. Do not author a ref, a version or an ordering;\na contract that asked you to would be asking you to fail on form rather than on substance.\n\n(This paragraph listed `retention-rules`, `data-categories-and-sources` and\n`recipients-and-processors` as examples. All three are required fact names, and naming three of eight\nas \"examples\" invited a drafter to treat them as a style to imitate rather than a set to use. The\nauthoritative list now arrives in the brief.)\n\n**For a concern a governed document requires, the slug is NOT yours to choose.** The brief you were\ngiven lists the exact `factSlug` for each one, taken from the engine catalog. Use it verbatim.\n\nThis is not a style preference. A clause cites a fact BY REF, the ref is stamped from your slug, and a\nfact answering the right question under a different name is a fact the document cannot cite — it reads\nas missing while your answer sits in the file. Measured on a real run: twenty facts declared, zero of\nthe eight a privacy notice requires, because the names were semantically adjacent and lexically\ndisjoint (`retention-period-schedule-status` for `retention-rules`).\n\nFor anything the catalog does NOT name, the slug is yours: use a stable, descriptive one that reads as\nthe question it answers. An application legitimately declares facts no document requires.\n\n## Verification\n\nBefore you finish, check each declaration against these:\n\n- [ ] every `KNOWN` value states something a reader could act on, and is traceable to accepted truth;\n- [ ] no declaration encodes a decision (legal basis, role, governing law, liability, chosen retention);\n- [ ] every `NOT_APPLICABLE` reason says why it does not apply, not that it could not be found;\n- [ ] a fact you could not establish is ABSENT, not guessed and not marked not-applicable;\n- [ ] the fact set is derived from the vision's compliance constraints, not from a generic SaaS template;\n- [ ] no `factSlug` is declared twice.\n\n## Approval\n\nThe derived fact set is presented to the creator before it becomes the committed `document-facts`\nfamily. Show it back as plain statements grouped by the question each answers, and name what you left\nout and why — the absences are the part a human most needs to see, because each one is a decision\nsomebody still owes.\n\n## Runtime context\n\nEverything above is already in your brief: `vision-brief` / `domain-plan` / `requirements` render as\ninput sections under \"# Accepted application truth\", and the application's live resource\nDECLARATIONS (retention mode, data-subject kind, subject export, retained see-through) arrive as\nthe declared `compliance_primary_facts` context section of your brief. Derive facts from those sections; there is no command to\nrun in this mode.\n\n## References\n\nThese are skill FOLDERS installed in the application, named so each piece of work has an\nauthoring contract a later coding agent can open. This step has no tools and does not open them;\nwhat reaches you is this method, your declared inputs, and the brief's own sections.\n\n\n## External sign-in assurance\n\nDerive `document-fact:external-sign-in-assurance` from the brief's declared authentication policy, including organization restrictions. Do not infer an active enterprise connection from an enabled method. Describe enterprise OAuth2/OIDC responsibility delegation separately from observed MFA. For social login, name the configured warning/strict treatment and provider evidence limitations. An unreadable configuration remains unresolved, never “no external login”. Feed this fact into the service-terms account-duties clause; liability conclusions still require qualified review.\n",
41
41
  "skillRefs": [],
42
42
  "skillBodyRefs": [],
43
43
  "contextSources": [
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "refinement.feature-contribution",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "refinement",
5
5
  "intent": "Add ONE feature to the product model, as the feature-development line it runs for describes it: the functional requirements the feature adds, and one spec-first, ref-less feature draft per capability it needs, each tracing to those requirements. Return only what the feature adds; everything the application already holds stays as it is.",
6
6
  "preconditions": [
@@ -239,9 +239,10 @@ table; the administrative-continuity floors (a tenant cannot be left with no usa
239
239
  application cannot be left with no super-administrator); and the platform-access-grant mechanism,
240
240
  under which a platform operator crossing the per-record tenant boundary requires a granted,
241
241
  time-bounded authorization. Application-wide directory reads retain independent approval. The
242
- application audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to
243
- `AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the
244
- read-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in
242
+ application audit viewer has a distinct policy: `auditTrail.applicationReadAccess`, when undeclared,
243
+ follows the application's shape in every environment — `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`
244
+ where the parties of one of its relationship kinds are independent of its operator, `ROLE_BASED` otherwise. `ROLE_BASED` admits the
245
+ super-administrator or the read-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in
245
246
  addition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to
246
247
  its own credential and signed by a second administrator — a grant bound to a machine never admits the
247
248
  administrator who requested it. Access admission, audit observation and retained
@@ -291,9 +292,10 @@ operator's responsibilities and the customer's lies.
291
292
  **Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every
292
293
  tenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be
293
294
  declared and carry a usable access grant. The application audit viewer is a separate policy surface:
294
- it defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with
295
- `auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under
296
- which a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
295
+ it follows `auditTrail.applicationReadAccess`, which defaults by the application's shape:
296
+ `AuditApplicationReadAccess.INDEPENDENT_APPROVAL` where the parties of one of its relationship kinds are independent of its operator, role-based
297
+ access (the super-administrator or the read-only audit-evidence reader) otherwise. Under independent approval a
298
+ machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;
297
299
  role-based access neither implies anonymized records nor supplies an approval that never occurred.
298
300
 
299
301
  **Completeness** — `DERIVED`.
@@ -25,7 +25,7 @@
25
25
  ],
26
26
  "stepOutputs": [],
27
27
  "method": {
28
- "guidance": "# Governance document candidate method\n\nYou are drafting ONE internal governance document for this application, from what the application has\nalready declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,\ncompleteness, what a clause may say. This method says which document, what its concerns are, and the two\nthings a governance document meets that a public notice does not.\n\n## Choose the document, from the four this lane may draft\n\nThe candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones\n(`document:public.privacy-notice`, `document:public.service-terms`) belong to\n`refinement.compliance-document-candidate` and are not yours to draft here.\n\n| `documentRef` | what it is | its concerns |\n|---|---|---|\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |\n| `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |\n| `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |\n\n**Draft a document this application does not already hold.** The brief opens with what it has already\ndrafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by\n`documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a\nwasted run when it is not.\n\n**A held draft marked ALREADY DRAFTED, and WRONG comes before everything below.** The brief marks a held\ndraft that cites facts this application no longer declares, and names them. Nothing else corrects it: the\nlanding checks only the document a run writes, so a draft written before the facts were regenerated keeps\nits dead citations until a run redrafts that document. Redraft it against the facts that exist, and cite\nnone of the named ones.\n\nWhere several remain, **scope and system description** comes first: it is the one an assurance reader\nopens first, the one the other three refer back to, and the only one of the four carrying facts the\nframework derives rather than a person establishes.\n\n`document:governance.document-record-control` composes **no application-fact concern**, and that is\ndeclared rather than missing: it describes how documents are identified, reviewed, released and retired —\na process the operator defines, not anything derivable from the product. Every section you write for it\ncarries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.\n\n## Expect to MARK, and never invent your way past a mark\n\nMost of what a governance document asserts is established by a PERSON, not derived from the application.\nMeasured on the blueprints: `roles-responsibilities` and `document-record-control` carry no\nspecification-derived fact at all — every one of their facts needs a creator decision or a qualified\nreview — and the other two carry a handful.\n\nSo a governance draft that is largely marked incomplete is the expected outcome. Draft every section,\nstate precisely what is missing in `incompleteness.needs` and what would close it in\n`incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read\nexactly which governance decisions it owes is further ahead than one holding no document at all.\n\n**Two inventions are worse than any gap, and both are specific to these documents.**\n\n- **A record of review that did not happen.** These are the documents where a reviewer, an approver, an\n approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the\n application has not declared and you have not written a weak sentence — you have fabricated the record\n of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.\n- **A control asserted to OPERATE, with nothing behind it.** \"Access is reviewed quarterly\", \"we\n monitor\", \"the trail is checked\" are claims about operating effectiveness. In THIS lane one of them\n may be legitimate — and only when a judged run in your brief's evidence section supports it, the\n clause cites that run, and the clause says what was measured and over what period. Without all three,\n say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section\nthat genuinely answers no concern — a preamble, a scope statement, and every section of\n`document-record-control`. Draft one section per concern in the order the table above gives, and produce\n**every** one: a concern nothing can answer becomes a section with a marked clause, never a missing\nheading.\n\nThe value must be the concern's exact name. A near miss (`access-control` for\n`access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the\ndocument addresses it.\n\nEach section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,\n`satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the\ncatalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it\nmust not claim, automatically. A clause that says nothing is checked against nothing.\n\nA section that supplies no required part of the document answers **`null`**, never `[]` — an empty array\nis refused, because it would be a second spelling of the same state. On a governance document the sections\nthat answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is\nmostly made of them.\n\n## The three ref arrays on every clause\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —\ntwo of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a\npolicy area is sourced by nothing.\n\n- `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is\n normal here: a marked clause usually establishes nothing.\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must\n be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,\n `policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy\n ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A\n clause resting on declared facts already cites them through `factRefs`, which resolves them; restating\n one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a\n fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that\n apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard\n for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before\nthis draft is worth anything. On a governance document that list is long, and it is where \"who reviewed\nthis, and when\" belongs — as something a person must supply, never as a name you write into a clause.\n\n`limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this\ndocument does NOT cover.\n\n## What the blueprint gives you\n\nthe declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its\nclauses and which of them are required. Read the one matching your `documentRef` and treat its required\nclauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.\n\n## Citing this application's own measured evidence\n\nA governance document is the one place an operator may say what its controls DO, and this lane is the\nonly one that may cite the measurements behind such a statement.\n\nthe declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has\ncommitted: what was measured, under which demand, with what verdict, at which framework revision, and\nwhether the judge was calibrated. Read it before writing any sentence about what a control does.\n\n- **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the\n clause what was measured and over what period. A citation a reader cannot scope is one they cannot\n check.\n- **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A\n clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the\n question, which is worse than saying nothing.\n- **Say what it is.** The operator judged its own product with its own harness. A clause may say that\n and what it found; it may not say the result was verified, certified, audited or independently\n assured, and the claim guards refuse the sentence that blurs the two.\n- **Where no run supports the statement, MARK it** — the same answer this lane gives every\n unestablished statement, and the right one.\n\nA ref that resolves to no committed run is refused before the draft becomes a file, as is any citation\nat all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.\n\n## You do not approve, release or publish\n\nYou draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is\nnot approval. You do not author the release — almost everything a release carries is derived from the\naccepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`\nrather than withheld.\n\n**Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and\ndescribing a draft as approved to get past a gate, are the two symmetric failures; the first is a\ncompliance workflow standing in front of the mechanism that builds the application.\n\n## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit, beside any\npublic candidates the application already holds.\n\n---\n\n# The compositions\n\nEach entry below is one concern: what it asserts, what in the application it derives from, what state it\nusually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the\nrest.\n\n### Concern: service scope\n\n**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the\nsurfaces it exposes.\n\n**Derives from** — the application's declared modules and their resources, and the surfaces it builds\n(application, API, public website, technical documentation).\n\n**Completeness** — `DERIVED`.\n\n**Derive it; do not describe the product from its marketing.** Scope in a governed document is the\nboundary of what the statements around it apply to, so an aspirational description silently widens\nevery other clause. The declared modules are the honest boundary, and a capability the application\ndoes not run does not belong here even if it is on the roadmap.\n\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned\n(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA\ncapability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was\nwithdrawn because no provider could fill it, and a derived control statement must never rest on a\nslot that cannot be configured.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the application's own audit store, which every application writes; the\n`COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator crossing the per-record tenant boundary requires a granted,\ntime-bounded authorization. Application-wide directory reads retain independent approval. The\napplication audit viewer has a distinct policy: `auditTrail.applicationReadAccess` defaults to\n`AuditApplicationReadAccess.ROLE_BASED` in every environment, admitting the super-administrator or the\nread-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in\naddition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to\nits own credential and signed by a second administrator — a grant bound to a machine never admits the\nadministrator who requested it. Access admission, audit observation and retained\nevidence are separate claims: the access decision does not depend on a successful audit write.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access is governed by the resource and its declared policy.** Ordinary tenant\ncrossings require a usable grant. The application audit viewer is role-based by default, with\nindependent approval available as an explicit policy. Its cross-tenant observations still identify\nthe operator and tenants reached; role-based access does not imply anonymized logs or fabricate an\napproval record. Actual application-wide grants always retain their independent-approval requirement.\n\n**Observation coverage** — the per-record organization gate observes access to an identifiable\ntenant's record when the caller does not already hold organization-wide entry there. Separately,\ndeclared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe\nthe identifiable tenants in their returned records that the caller does not already belong to,\ngrouped into one observation per tenant reached. This collection observer excludes context-free\ninternal requests and webhook callbacks; COUNT\nreturns no records and is not covered by that observer. Do not turn these scoped mechanisms into a\nclaim that every operation or every returned record produces an audit entry.\n\n**Delivery and evidence** — these observations are best-effort and do not fail the observed request.\nAn unavailable audit service, a synchronous emission error or a rejected emission can leave an\nauthorized request without a retained crossing entry. Observer-side drops have an\n`audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store\nwrite have the separate `audit_store_failure_total` signal. Metrics export and log retention must\nactually be configured and operating for those signals to provide evidence beyond the process.\nNeither a loss counter nor an attempted emission substitutes for the missing audit entry.\n\n**Document-authoring consequence** — derive the roles, operation declarations and usable-grant\nrequirements and the audit viewer's access policy from the application's configuration. Do not\nclaim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported\ncoverage, then substantiate any statement about recorded access with retained audit records and\nevidence that the collection pipeline and loss monitoring were operating over the period claimed.\nAn empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`\nabove identifies the source of the access-control description; it does not certify complete audit\ndelivery or the application's operational compliance.\n\n\n### Concern: tenancy model\n\n**Asserts** — that customer data is separated per organization, and where the boundary between the\noperator's responsibilities and the customer's lies.\n\n**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every\ntenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be\ndeclared and carry a usable access grant. The application audit viewer is a separate policy surface:\nit defaults to role-based access (the super-administrator or the read-only audit-evidence reader), with\n`auditTrail.applicationReadAccess` optionally set to `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`, under\nwhich a machine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;\nrole-based access neither implies anonymized records nor supplies an approval that never occurred.\n\n**Completeness** — `DERIVED`.\n\n**This fragment is where shared responsibility is described, and it must never be flattened.** In a\nB2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a\nCONTROLLER for the data it holds about the customer's users as account holders. Those are different\nroles with different duties over the same database. Say which is which; do not pick one and apply it\nto everything.\n\n**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in\n`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer\nstores about its own people, CONTROLLER for the account data of the people who administer them. It is\na LIST for exactly the reason this fragment gives: those are different roles over the same database,\nand a single field would force one of them to be wrong.\n\nWhere the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the\nsurface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,\nso the remedy is to fill it in rather than to build something. See the legal-basis fragment.\n\n\n### Concern: operator identity\n\n**Asserts** — who legally operates the service: entity name, registered address, contact route for\ndata-protection questions, and a representative where one is required.\n\n**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its\nregistered address, the privacy contact route, and an Art. 27 representative where one is required.\n\nThe VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.\nWhat the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment\nsaid \"no engine change would close it\", which was right about derivation and wrong about the home.\nThe consequence was concrete. A landing REPLACES the produced document on every run, so an operator\nwho answered by editing the document lost the answer at the next regeneration — the answer has to live\nin the application or it does not survive.\n\n**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.\n\n⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface\nexists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is\nand nobody has. They have different remedies — build something, versus fill something in — and a\nreader who cannot tell them apart cannot act on either. Say which surface the answer goes to.\n\n**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be\nfilled in later without redrafting anything around it, which is the reason it is not a blocker.\n\n**Never infer it.** Not from the application name, not from a domain, not from another application,\nnot from model memory. A published legal document naming the wrong entity is worse than one that says\nthe entity is not yet recorded — the first misdirects a person exercising a right, the second tells\nthem the document is incomplete.\n\n**Every document needs this fragment**, which makes it the clearest demonstration of why producing\nwith gaps beats blocking: the whole document set would be unproducible until one form is filled in.\n",
28
+ "guidance": "# Governance document candidate method\n\nYou are drafting ONE internal governance document for this application, from what the application has\nalready declared. Follow the `compliance-document-authoring` skill for the rules — refs, clause shape,\ncompleteness, what a clause may say. This method says which document, what its concerns are, and the two\nthings a governance document meets that a public notice does not.\n\n## Choose the document, from the four this lane may draft\n\nThe candidate contract admits six `documentRef` values. Four of them are this lane's; the two public ones\n(`document:public.privacy-notice`, `document:public.service-terms`) belong to\n`refinement.compliance-document-candidate` and are not yours to draft here.\n\n| `documentRef` | what it is | its concerns |\n|---|---|---|\n| `document:governance.scope-system-description` | what the system IS, for an assurance reader | service scope, security controls, audit and accountability, access control and roles, tenancy model |\n| `document:governance.roles-responsibilities` | who is accountable for what | access control and roles, operator identity |\n| `document:governance.program-handbook` | how the governance programme runs | security controls, audit and accountability, access control and roles |\n| `document:governance.document-record-control` | how governed documents are themselves controlled | **none** — see below |\n\n**Draft a document this application does not already hold.** The brief opens with what it has already\ndrafted, listing each document this lane may produce as ALREADY DRAFTED or not yet. Drafts are keyed by\n`documentRef`, so drafting one that is already there REPLACES it — right when that draft is wrong, a\nwasted run when it is not.\n\n**A held draft marked ALREADY DRAFTED, and WRONG comes before everything below.** The brief marks a held\ndraft that cites facts this application no longer declares, and names them. Nothing else corrects it: the\nlanding checks only the document a run writes, so a draft written before the facts were regenerated keeps\nits dead citations until a run redrafts that document. Redraft it against the facts that exist, and cite\nnone of the named ones.\n\nWhere several remain, **scope and system description** comes first: it is the one an assurance reader\nopens first, the one the other three refer back to, and the only one of the four carrying facts the\nframework derives rather than a person establishes.\n\n`document:governance.document-record-control` composes **no application-fact concern**, and that is\ndeclared rather than missing: it describes how documents are identified, reviewed, released and retired —\na process the operator defines, not anything derivable from the product. Every section you write for it\ncarries `concernRef: null`, and almost every clause is marked. That is the document working, not failing.\n\n## Expect to MARK, and never invent your way past a mark\n\nMost of what a governance document asserts is established by a PERSON, not derived from the application.\nMeasured on the blueprints: `roles-responsibilities` and `document-record-control` carry no\nspecification-derived fact at all — every one of their facts needs a creator decision or a qualified\nreview — and the other two carry a handful.\n\nSo a governance draft that is largely marked incomplete is the expected outcome. Draft every section,\nstate precisely what is missing in `incompleteness.needs` and what would close it in\n`incompleteness.closedBy`, and let the marks be the document's contribution. An application that can read\nexactly which governance decisions it owes is further ahead than one holding no document at all.\n\n**Two inventions are worse than any gap, and both are specific to these documents.**\n\n- **A record of review that did not happen.** These are the documents where a reviewer, an approver, an\n approval, an independence disclosure, a qualification and a decision instant are NAMED. Write one the\n application has not declared and you have not written a weak sentence — you have fabricated the record\n of a review nobody performed. Mark it instead: the fact is owed, and saying so is the answer.\n- **A control asserted to OPERATE, with nothing behind it.** \"Access is reviewed quarterly\", \"we\n monitor\", \"the trail is checked\" are claims about operating effectiveness. In THIS lane one of them\n may be legitimate — and only when a judged run in your brief's evidence section supports it, the\n clause cites that run, and the clause says what was measured and over what period. Without all three,\n say what is CONFIGURED or DECLARED, which is what the facts give you, and mark the rest.\n\n## One section per concern, and SAY which concern\n\nEvery section carries `concernRef` from the closed compliance-concern vocabulary, or `null` for a section\nthat genuinely answers no concern — a preamble, a scope statement, and every section of\n`document-record-control`. Draft one section per concern in the order the table above gives, and produce\n**every** one: a concern nothing can answer becomes a section with a marked clause, never a missing\nheading.\n\nThe value must be the concern's exact name. A near miss (`access-control` for\n`access-control-and-roles`) is worse than a null: it reports the concern as unaddressed while the\ndocument addresses it.\n\nEach section also names what it satisfies in the catalog — `satisfiesSectionRefs` on the section,\n`satisfiesClauseRefs` on each clause, from the blueprint in your brief. Those are what attach the\ncatalog's claim guards to your clauses, so a clause that says what it satisfies is checked against what it\nmust not claim, automatically. A clause that says nothing is checked against nothing.\n\nA section that supplies no required part of the document answers **`null`**, never `[]` — an empty array\nis refused, because it would be a second spelling of the same state. On a governance document the sections\nthat answer `null` are the ones with `concernRef: null` beside them, and `document-record-control` is\nmostly made of them.\n\n## The three ref arrays on every clause\n\nEvery `…Ref` field is a **namespaced ref**: `namespace:slug`, both halves lowercase, words joined by\nhyphens. One malformed ref rejects the whole draft, and all three arrays are required on every clause —\ntwo of them may be empty, but **not the first two at once**, because a clause naming neither a fact nor a\npolicy area is sourced by nothing.\n\n- `factRefs` — the facts this clause rests on, spelled exactly as the facts file declares them. EMPTY is\n normal here: a marked clause usually establishes nothing.\n- `sourcePolicyRefs` — the application POLICY AREA the statement is sourced from, and **every entry must\n be in the `policy:` namespace**: `policy:security-controls`, `policy:access-control`,\n `policy:document-control`. Any other namespace is rejected outright — `policy-area:…` is not a policy\n ref, and neither is a fact ref repeated here. **Do NOT put a fact or its authority in this array.** A\n clause resting on declared facts already cites them through `factRefs`, which resolves them; restating\n one here duplicates the citation beside it and resolves to nothing. So this array is EMPTY for a\n fact-backed clause, and carries a policy area for a clause sourced from a policy rather than a fact.\n- `claimGuardRefs` — at least one: what this clause must NOT be read as claiming. Name the ones that\n apply; do not repeat the same guard on every clause out of habit. You do not name the CATALOG's guard\n for the material — that is added for you from the blueprint clauses this clause `satisfiesClauseRefs`.\n\n`reviewChecklistRefs` needs at least one (`review-checklist:<slug>`): what a human must confirm before\nthis draft is worth anything. On a governance document that list is long, and it is where \"who reviewed\nthis, and when\" belongs — as something a person must supply, never as a name you write into a clause.\n\n`limitationRefs` may be empty and rarely should be: it is where you say, in your own words, what this\ndocument does NOT cover.\n\n## What the blueprint gives you\n\nthe declared `document_blueprint` context section of your brief carries, for each document this lane may draft, its sections, its\nclauses and which of them are required. Read the one matching your `documentRef` and treat its required\nclauses as the floor: a required clause you cannot establish is a clause you MARK, never one you omit.\n\n## Citing this application's own measured evidence\n\nA governance document is the one place an operator may say what its controls DO, and this lane is the\nonly one that may cite the measurements behind such a statement.\n\nthe declared `assurance_evidence` context section of your brief carries the judged runs this application's own assurance cycle has\ncommitted: what was measured, under which demand, with what verdict, at which framework revision, and\nwhether the judge was calibrated. Read it before writing any sentence about what a control does.\n\n- **Cite by putting the run's `assurance-run:` ref in the clause's `evidenceRefs`**, and say in the\n clause what was measured and over what period. A citation a reader cannot scope is one they cannot\n check.\n- **Only a run whose verdict CONCLUDED may support such a statement.** The section marks each one. A\n clause resting on an `INSUFFICIENT_EVIDENCE` run asserts a measurement that did not settle the\n question, which is worse than saying nothing.\n- **Say what it is.** The operator judged its own product with its own harness. A clause may say that\n and what it found; it may not say the result was verified, certified, audited or independently\n assured, and the claim guards refuse the sentence that blurs the two.\n- **Where no run supports the statement, MARK it** — the same answer this lane gives every\n unestablished statement, and the right one.\n\nA ref that resolves to no committed run is refused before the draft becomes a file, as is any citation\nat all in a PUBLIC document. Neither is your judgement to make here: cite only what the section lists.\n\n## You do not approve, release or publish\n\nYou draft the candidate. A human accepts it by committing it; nothing else is acceptance, and landing is\nnot approval. You do not author the release — almost everything a release carries is derived from the\naccepted document definition, and a release nobody has approved is composed and marked `UNAPPROVED`\nrather than withheld.\n\n**Which is why a missing approval never changes what you do here.** Waiting for one before drafting, and\ndescribing a draft as approved to get past a gate, are the two symmetric failures; the first is a\ncompliance workflow standing in front of the mechanism that builds the application.\n\n## Where the draft goes\n\nIt lands as a FILE in the application's specifications package, as an ordinary working edit, beside any\npublic candidates the application already holds.\n\n---\n\n# The compositions\n\nEach entry below is one concern: what it asserts, what in the application it derives from, what state it\nusually reaches, and what closes it when it cannot. Use the ones your document's row names and ignore the\nrest.\n\n### Concern: service scope\n\n**Asserts** — what the service actually is: the modules it runs, the resources it manages, and the\nsurfaces it exposes.\n\n**Derives from** — the application's declared modules and their resources, and the surfaces it builds\n(application, API, public website, technical documentation).\n\n**Completeness** — `DERIVED`.\n\n**Derive it; do not describe the product from its marketing.** Scope in a governed document is the\nboundary of what the statements around it apply to, so an aspirational description silently widens\nevery other clause. The declared modules are the honest boundary, and a capability the application\ndoes not run does not belong here even if it is on the roadmap.\n\n\n### Concern: security controls\n\n**Asserts** — the security measures the application actually runs, at the level of detail a notice\nneeds and no further.\n\n**Derives from** — the application's authored authentication configuration (methods enabled, MFA,\npassword policy, lockout, step-up, session lifetimes), its access floors, its encryption of stored\nsecrets, and its antivirus posture where the `ANTIVIRUS_SCANNING` INFRA capability is provisioned\n(ClamAV, consumed by the engine's file-scanning service on upload). Note this reads the INFRA\ncapability, not an engine provider slot: the equally-named `EngineCapability.ANTIVIRUS_SCANNING` was\nwithdrawn because no provider could fill it, and a derived control statement must never rest on a\nslot that cannot be configured.\n\n**Completeness** — `DERIVED`, bounded.\n\n**Bounded is the operative word.** A public notice states that measures exist and their general\nnature. **It must not enumerate the control set**: a published list of exactly which protections are\nin place, and by implication which are not, is a map for somebody attacking the service. Detail\nbelongs in a security addendum shared under agreement, not on a public page — so this fragment reads\nvery differently in `public.privacy-notice` than in a security schedule, and that difference is\ndeliberate rather than an omission.\n\n**Never state a certification.** \"Compliant\", \"certified\", \"audited\" and \"ISO/SOC\" claims are not\nderivable from configuration and are not this document's to make.\n\n\n### Concern: audit and accountability\n\n**Asserts** — that security-relevant actions are recorded, what kinds are recorded, and where those\nrecords can be sent.\n\n**Derives from** — the application's own audit store, which every application writes; the\n`COMPLIANCE_AUDIT_TRAIL` engine capability, which additionally sends each event to external providers\n(`saas-models` → `external-providers/engine-capabilities.shared.schemas.ts`); the auditable-event\ncatalog the engine emits (authentication, authorization grants, consent decisions, token lifecycle,\nconfiguration and permission changes, cross-tenant administrative access), and per-organization SIEM\nrouting where a tenant has configured it.\n\n**Completeness** — `DERIVED`.\n\nThis is one of the fragments where the ENGINE answers for the application. Every generated\napplication inherits the event catalog and the emitters; a document may state it without the\napplication having configured anything. Where a tenant has additionally routed events to its own\nSIEM, that is the tenant's configuration and belongs in a shared-responsibility statement rather than\nin the operator's own notice.\n\n\n### Concern: access control and roles\n\n**Asserts** — who inside the operator and inside a customer tenant can reach personal data, and what\nconstrains them.\n\n**Derives from** — `CORE_APP_ROLES` and `CORE_ORG_ROLES`\n(`saas-models` → `security/authorizations/roles.shared.schemas.ts`) plus the application's own role\ntable; the administrative-continuity floors (a tenant cannot be left with no usable owner, the\napplication cannot be left with no super-administrator); and the platform-access-grant mechanism,\nunder which a platform operator crossing the per-record tenant boundary requires a granted,\ntime-bounded authorization. Application-wide directory reads retain independent approval. The\napplication audit viewer has a distinct policy: `auditTrail.applicationReadAccess`, when undeclared,\nfollows the application's shape in every environment — `AuditApplicationReadAccess.INDEPENDENT_APPROVAL`\nwhere the parties of one of its relationship kinds are independent of its operator, `ROLE_BASED` otherwise. `ROLE_BASED` admits the\nsuper-administrator or the read-only audit-evidence reader role; `INDEPENDENT_APPROVAL` requires a usable application-wide grant in\naddition to the role, and a machine reader (such as an assurance collector) holds one only when it is bound to\nits own credential and signed by a second administrator — a grant bound to a machine never admits the\nadministrator who requested it. Access admission, audit observation and retained\nevidence are separate claims: the access decision does not depend on a successful audit write.\n\n**Completeness** — `DERIVED`.\n\nWorth stating plainly in a B2B notice, because it is the question a customer's own reviewer asks\nfirst: **operator access is governed by the resource and its declared policy.** Ordinary tenant\ncrossings require a usable grant. The application audit viewer is role-based by default, with\nindependent approval available as an explicit policy. Its cross-tenant observations still identify\nthe operator and tenants reached; role-based access does not imply anonymized logs or fabricate an\napproval record. Actual application-wide grants always retain their independent-approval requirement.\n\n**Observation coverage** — the per-record organization gate observes access to an identifiable\ntenant's record when the caller does not already hold organization-wide entry there. Separately,\ndeclared cross-tenant READ, LIST and SEARCH operations outside the organization-scoped gate observe\nthe identifiable tenants in their returned records that the caller does not already belong to,\ngrouped into one observation per tenant reached. This collection observer excludes context-free\ninternal requests and webhook callbacks; COUNT\nreturns no records and is not covered by that observer. Do not turn these scoped mechanisms into a\nclaim that every operation or every returned record produces an audit entry.\n\n**Delivery and evidence** — these observations are best-effort and do not fail the observed request.\nAn unavailable audit service, a synchronous emission error or a rejected emission can leave an\nauthorized request without a retained crossing entry. Observer-side drops have an\n`audit_observation_dropped_total` signal and throttled error logs; failures at the primary audit-store\nwrite have the separate `audit_store_failure_total` signal. Metrics export and log retention must\nactually be configured and operating for those signals to provide evidence beyond the process.\nNeither a loss counter nor an attempted emission substitutes for the missing audit entry.\n\n**Document-authoring consequence** — derive the roles, operation declarations and usable-grant\nrequirements and the audit viewer's access policy from the application's configuration. Do not\nclaim that every audit read required independent approval when the viewer is role-based. Describe the observation mechanisms as supported\ncoverage, then substantiate any statement about recorded access with retained audit records and\nevidence that the collection pipeline and loss monitoring were operating over the period claimed.\nAn empty crossing search alone does not prove that no operator accessed tenant data. `DERIVED`\nabove identifies the source of the access-control description; it does not certify complete audit\ndelivery or the application's operational compliance.\n\n\n### Concern: tenancy model\n\n**Asserts** — that customer data is separated per organization, and where the boundary between the\noperator's responsibilities and the customer's lies.\n\n**Derives from** — the `ORGANIZATIONS` engine capability, the organization scoping applied to every\ntenant-scoped resource, and the cross-tenant admission rules. Ordinary tenant crossings must be\ndeclared and carry a usable access grant. The application audit viewer is a separate policy surface:\nit follows `auditTrail.applicationReadAccess`, which defaults by the application's shape:\n`AuditApplicationReadAccess.INDEPENDENT_APPROVAL` where the parties of one of its relationship kinds are independent of its operator, role-based\naccess (the super-administrator or the read-only audit-evidence reader) otherwise. Under independent approval a\nmachine reader needs a second-signed grant bound to its own credential. Both modes retain cross-tenant read observations;\nrole-based access neither implies anonymized records nor supplies an approval that never occurred.\n\n**Completeness** — `DERIVED`.\n\n**This fragment is where shared responsibility is described, and it must never be flattened.** In a\nB2B SaaS the operator is a PROCESSOR for the data a customer stores about its own people, and a\nCONTROLLER for the data it holds about the customer's users as account holders. Those are different\nroles with different duties over the same database. Say which is which; do not pick one and apply it\nto everything.\n\n**The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in\n`wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer\nstores about its own people, CONTROLLER for the account data of the people who administer them. It is\na LIST for exactly the reason this fragment gives: those are different roles over the same database,\nand a single field would force one of them to be wrong.\n\nWhere the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the\nsurface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,\nso the remedy is to fill it in rather than to build something. See the legal-basis fragment.\n\n\n### Concern: operator identity\n\n**Asserts** — who legally operates the service: entity name, registered address, contact route for\ndata-protection questions, and a representative where one is required.\n\n**Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its\nregistered address, the privacy contact route, and an Art. 27 representative where one is required.\n\nThe VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.\nWhat the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment\nsaid \"no engine change would close it\", which was right about derivation and wrong about the home.\nThe consequence was concrete. A landing REPLACES the produced document on every run, so an operator\nwho answered by editing the document lost the answer at the next regeneration — the answer has to live\nin the application or it does not survive.\n\n**Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.\n\n⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface\nexists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is\nand nobody has. They have different remedies — build something, versus fill something in — and a\nreader who cannot tell them apart cannot act on either. Say which surface the answer goes to.\n\n**What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be\nfilled in later without redrafting anything around it, which is the reason it is not a blocker.\n\n**Never infer it.** Not from the application name, not from a domain, not from another application,\nnot from model memory. A published legal document naming the wrong entity is worse than one that says\nthe entity is not yet recorded — the first misdirects a person exercising a right, the second tells\nthem the document is incomplete.\n\n**Every document needs this fragment**, which makes it the clearest demonstration of why producing\nwith gaps beats blocking: the whole document set would be unproducible until one form is filled in.\n",
29
29
  "skillRefs": [
30
30
  "compliance-document-authoring"
31
31
  ],
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the creator's answers; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the creator's visual-direction answer, when it is not \"none\", is honoured and outranks the derivation. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the creator's answers; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the creator's visual-direction answer, when it is not \"none\", is honoured and outranks the derivation — in the WORDS and in the LOOK they derive: the derived context gives the theme point the drafted style keywords and mood select (shape, motion, density, elevation, letter case…), computed by the framework, and a point that contradicts the direction (a rounded direction and a sharp shape, a lively one and still motion) is not honoured, however faithful the words read. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores or whose derived look contradicts it, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"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-brand-brief","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/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-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/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-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/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the creator's answers; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the creator's visual-direction answer, when it is not \"none\", is honoured and outranks the derivation. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"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/brand-identity","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-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-name-screening-and-brand-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-brand-brief","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/brand-identity-grounding-in-creator-and-vision"],"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1,"riskClassRef":"application-creation:risk/brand-brief-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/brand-identity","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/brand-identity-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/brand-identity","policyVersion":1},"decisionPointRef":"application-creation:decision-point/brand-identity-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/brand-identity-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/brand-identity","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/brand-brief-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/current-horizon-brand-brief-change","triggerRefs":["application-creation:trigger/brand-brief-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-brand-identity-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision"],"hardFloorRef":"application-creation:hard-floor/brand-brief-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/brand-identity-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/brand-identity","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-brand-identity-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"assessesAspects":["brand.audience","brand.asset","market.icp"],"criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1}],"instruction":"Determine whether the brief hands off correctly: every targetIcpRef in the audience names an ICP the market snapshot holds and none is an anti-target; the audience rationale follows from the brief's own tone and mission; and resolvedAssets is EMPTY, because assets are the companion logo step's output and a hand-authored asset reference would be overwritten or flagged.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The audience is absent although the market snapshot names ICPs the tone was chosen for, or the rationale is generic.","GAP":"An audience ref naming an ICP the market does not hold or an anti-target, or a resolvedAssets entry authored by hand.","INDETERMINATE":"The market snapshot's ICPs are not in evidence, so the audience cannot be checked.","PASS":"Every audience ref resolves to a market ICP that is not an anti-target, and resolvedAssets is empty."}},{"assessesAspects":["brand.name","brand.logo-direction","brand.visual-tone","vision.idea","vision.mission"],"criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1}],"instruction":"Determine whether the brand brief is GROUNDED: the brand name is exactly the name the creator chose in the interview (an option may carry a bracketed qualifier such as [not-screened], [screening-incomplete] or [keep-despite-conflict] — the name is the text before it, and the qualifier never appears in the brand name); the mark type, background and colour seeds are the creator's answers; the symbolism, motifs and imagery to avoid DERIVE from the vision's idea and mission; the visual tone translates the market's verbal voice where a market snapshot exists and is noted as provisional where it does not; and the creator's visual-direction answer, when it is not \"none\", is honoured and outranks the derivation — in the WORDS and in the LOOK they derive: the derived context gives the theme point the drafted style keywords and mood select (shape, motion, density, elevation, letter case…), computed by the framework, and a point that contradicts the direction (a rounded direction and a sharp shape, a lively one and still motion) is not honoured, however faithful the words read. Derived direction is expected — the interview no longer asks for it — but it must trace to the vision or the market voice, never be a decorative choice of the model's own. A partially-directed brief (name only, direction still open) is a legitimate state, not a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Grounded overall, with a thin symbolism rationale, a tone that only loosely follows the market voice, or a background treatment the pipeline must compensate for.","GAP":"A name or mark choice that differs from the interview, a visual direction the creator gave that the brief ignores or whose derived look contradicts it, or symbolism and tone that trace to neither the vision nor the market voice.","INDETERMINATE":"The interview answers or the vision are not in evidence, so grounding cannot be established.","PASS":"The name and the mark choices are the creator's, the symbolism and imagery trace to the vision, the tone follows the market voice or is honestly provisional, and the creator's visual direction is honoured."}},{"assessesAspects":["brand.name","brand-name-screening.candidate","brand-name-screening.jurisdiction","brand-name-screening.nice-class"],"criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1}],"instruction":"Determine whether the chosen NAME stands honestly against its screening: the brand name is a candidate of the brand-name screening, whose queries cover every jurisdiction and Nice class the screening declares; where the screening could not check a register, nothing in the brief presents the name as cleared; where the creator kept a name despite a conflict, the brief does not hide or soften it; and nothing in the brief asserts that the name is available, free to use, registered by this product or legally cleared — a minimal trademark screening is never a clearance opinion.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The name was chosen as not screened, screening-incomplete or kept despite a conflict, and the brief says so plainly.","GAP":"The name is not among the screened candidates, an unchecked or conflicting name is presented as clear, or the brief asserts availability or legal clearance.","INDETERMINATE":"The brand-name screening is not in evidence, so the name's standing cannot be checked.","PASS":"The name is a screened candidate covered in every declared jurisdiction and class, and the brief claims no availability or clearance."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/brand-identity","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:top_down.brand-identity"},"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/brand-identity","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-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-audience-and-handoff","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-audience-and-handoff","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-grounding-in-creator-and-vision","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":4,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-grounding-in-creator-and-vision","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/vision-market-and-brand-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-brand-inputs-and-candidate","criterionRef":"application-creation:criterion/brand-identity-name-screened-and-unclaimed","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":3,"minCount":2,"requirementRef":"application-creation:evidence-requirement/brand-identity-name-screened-and-unclaimed","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/brand-name-screening-and-brand-candidate"}],"schemaVersion":1}
@@ -120,9 +120,16 @@ and you say where it came from.
120
120
  - **Visual tone** (optional, WARNed when absent). The aesthetic register — the
121
121
  VISUAL counterpart to the market voice, DERIVED from it (and shaped by the
122
122
  creator's `visual-direction`): 3–7 concrete `styleKeywords`
123
- ("geometric", "minimal", "warm"), a one-line `mood`, a prose `colorIntent`
123
+ ("friendly", "fluid", "confident"), a one-line `mood`, a prose `colorIntent`
124
124
  (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in
125
- `visual-color-seeds`, only when they named any.
125
+ `visual-color-seeds`, only when they named any. Keep the creator's MAIN colour
126
+ first: the build derives the application's palette from these seeds, the first
127
+ as its primary and the second as its accent.
128
+ The style words and the mood ALSO choose the theme of the application and its
129
+ website (corners, depth, spacing, motion, letter case): pick them for the look
130
+ the creator's `visual-direction` describes, not only for the logo. "Minimal"
131
+ flattens every shadow, "precise" makes corners sharp and motion still, "warm"
132
+ and "soft" add depth; the `brand-logo-authoring` skill lists every word.
126
133
  - **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of
127
134
  the market ICPs its name and tone are chosen to speak to, copied exactly from
128
135
  the market's `icps`, plus a one-line `rationale`. Derive it from what the brief
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.brand-identity",
3
- "version": "0.4.0",
3
+ "version": "0.5.0",
4
4
  "phase": "top_down",
5
5
  "intent": "Brand-identity elicitation: draw the product's VISUAL identity out of the creator — the brand name (CHOSEN by the creator from the screened candidates `top_down.brand-naming` landed), the logo creative direction (mark type, motifs, symbolism, imagery don'ts, background), and the visual tone (style keywords, mood, color story) — and capture it as a single validated BrandSnapshot (the `brand-brief` artifact family). The visual counterpart to the vision (intent) and market (verbal voice) briefs: it derives symbolism from the VisionSnapshot's idea/mission and, when a MarketSnapshot exists, translates its verbal `tonesOfVoice` into a visual register. The emitted brand-brief is the INPUT the companion logo step generates the master logo + derived assets from, and via `BrandSnapshot.resolvedAssets` the single source of truth every logo/favicon/brand-image consumer resolves against. Progressive: may persist a partially-directed brand (logoDirection/visualTone optional) and resume. v1 scaffold methodology — iterate the interview.",
6
6
  "preconditions": [
@@ -46,7 +46,7 @@
46
46
  ],
47
47
  "stepOutputs": [],
48
48
  "method": {
49
- "guidance": "# Brand Identity — 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 question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity author**. Your job is to capture the product's VISUAL\nidentity, from the creator's few decisions plus what the vision and the market already\nsay, as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## What the creator decided, and what you derive\n\nThe interview asks only what the creator alone can decide. Everything else you derive,\nand you say where it came from.\n\n| Decided by the creator (interview answer) | Derived by you |\n|---|---|\n| `brand-name`: chosen from the screened names | `symbolism`, from the vision's idea and mission |\n| `brand-tagline`, or \"none\" | `motifs`: concrete elements that carry that symbolism |\n| `logo-mark-type` | `avoid`: the guardrails that keep the mark usable (no gradients, no literal clip-art, no text inside a symbol meant to stand alone) |\n| `logo-background` | `visualTone` (style keywords, mood, colour story), translated from the market's verbal voice |\n| `visual-color-seeds`, or \"none\" | |\n| `visual-direction`, or \"none\" | |\n\n- **`visual-direction` outranks the derivation.** When it is not \"none\", whatever it asks\n the mark to evoke, include or avoid is honoured, and the derived parts are shaped around it.\n- **Derived is not invented.** Every symbol, motif and tone keyword must trace to the\n vision or the market voice. A decorative choice of your own is the one thing to avoid.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**. If the vision or\n the market is too thin to derive a direction honestly, leave `logoDirection` or\n `visualTone` out and say what is missing. The snapshot persists partially directed, and\n this playbook can resume.\n- **One product, one brand.** The snapshot is a single aggregate: one name, one logo\n direction, one visual tone.\n\n## What the brief holds — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next.\n\n **You do not invent the name, and you do not choose it.** `top_down.brand-naming`\n proposed names and ran a minimal trademark screening of each; the creator CHOSE\n one in this playbook's `brand-name` question, from options computed from that\n screening. The `brandName` is exactly the chosen option's name. An option may end\n with a bracketed qualifier — `[not-screened]`, `[screening-incomplete]` or\n `[keep-despite-conflict]` — which records how the creator chose; it is NEVER part of\n the name, so drop it. The interview answer also records the line the creator was\n shown beside that option (the product already using the name, the registers nobody\n could read): carry its substance into the brief rather than paraphrasing it away.\n\n The brand-name screening is in your brief. Never describe the name as\n \"available\", \"registered\", \"protected\" or \"cleared\": a screening is not a legal\n clearance opinion. Where the creator kept a name despite a conflict, or chose one\n whose screening is incomplete or read no register at all, do not hide or soften that\n anywhere in the brief.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — the creator's `logo-mark-type` answer. The question suggests\n `COMBINATION_MARK` (symbol + wordmark) because it is the only archetype that\n natively yields BOTH a header lockup and a square symbol for favicons and app\n icons. When the creator chose `WORDMARK` (text only), note in the brief that a\n wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases), DERIVED\n from the symbolism and the creator's `visual-direction`.\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea** (and the creator's `visual-direction`, when they gave one).\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable), DERIVED, plus anything the creator's `visual-direction` rules out.\n - `backgroundTreatment` — the creator's `logo-background` answer.\n `TRANSPARENT_ISOLATED` is the default and the only treatment that rasterizes\n losslessly into every derived asset. A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice, DERIVED from it (and shaped by the\n creator's `visual-direction`): 3–7 concrete `styleKeywords`\n (\"geometric\", \"minimal\", \"warm\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in\n `visual-color-seeds`, only when they named any.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## Answers the creator did not give\n\nIn a quick interview the creator is asked only for `brand-name`. Every other answer may\nreach your brief marked ASSUMED: the companion proposed it from the vision and the market,\nand it was kept without the creator deciding it — on their review, or by an unattended round. Use an assumed answer as a working\ndefault, not as the creator's choice. Where the brief explains a choice that rests on one\n(a tagline, a mark type, a background, a colour seed), say it was proposed rather than\nchosen, and never let an assumed answer outrank what the vision and the market voice imply\nthe way the creator's own answer would. `brand-name` is never assumed: the creator chooses it.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present when they could be decided or honestly derived.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-deriving it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
49
+ "guidance": "# Brand Identity — 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 question set, the interviewing depth, and the \"when is it\n> done enough\" bar below are deliberately explicit so they can be tuned\n> against real elicitation runs — treat them as a starting rubric, not a\n> frozen contract.\n\n## What this playbook does\n\nYou are the **brand-identity author**. Your job is to capture the product's VISUAL\nidentity, from the creator's few decisions plus what the vision and the market already\nsay, as a single typed\n**`BrandSnapshot`** — the `brand-brief` artifact. This is the visual\ncounterpart to the vision brief (which captured *intent*) and the market brief\n(which captured the *verbal* voice): here you capture what the product should\n**look like** and, specifically, the brief a logo is generated from.\n\nThe brand-brief you emit is not the logo itself — it is the *direction*. The\ncompanion logo step reads it to generate the master logo and every derived\nasset (favicon, apple-touch, maskable, OG, email, monochrome, dark/light), and\nthose become the single source of truth every surface resolves against. So an\nhonest, well-framed brief is the whole task. You do **not** generate pixels,\nset design-system color tokens, or restate the verbal brand voice — each is a\ndistinct concern with its own home.\n\n## Where the brief comes from\n\nYou do not invent a brand from nothing. Ground it in what the journey already\nknows:\n\n- **The vision brief is your source of meaning.** Read the `VisionSnapshot` and\n derive the mark's **symbolism** from the product's idea and mission — the\n mark should evoke what the product is *for*, not a decorative motif you liked.\n- **The market brief sharpens the register, when present.** If a\n `MarketSnapshot` exists, translate its verbal `tonesOfVoice` (the Nielsen\n Norman 4-axis voice) into a **visual** tone: a serious / formal voice reads as\n restrained geometry and a muted palette; a funny / casual voice reads as\n rounder forms and a warmer accent. The market brief is an *input*, not a\n precondition — if there is no market snapshot yet, derive the visual tone from\n the vision alone and note it as provisional.\n\n## What the creator decided, and what you derive\n\nThe interview asks only what the creator alone can decide. Everything else you derive,\nand you say where it came from.\n\n| Decided by the creator (interview answer) | Derived by you |\n|---|---|\n| `brand-name`: chosen from the screened names | `symbolism`, from the vision's idea and mission |\n| `brand-tagline`, or \"none\" | `motifs`: concrete elements that carry that symbolism |\n| `logo-mark-type` | `avoid`: the guardrails that keep the mark usable (no gradients, no literal clip-art, no text inside a symbol meant to stand alone) |\n| `logo-background` | `visualTone` (style keywords, mood, colour story), translated from the market's verbal voice |\n| `visual-color-seeds`, or \"none\" | |\n| `visual-direction`, or \"none\" | |\n\n- **`visual-direction` outranks the derivation.** When it is not \"none\", whatever it asks\n the mark to evoke, include or avoid is honoured, and the derived parts are shaped around it.\n- **Derived is not invented.** Every symbol, motif and tone keyword must trace to the\n vision or the market voice. A decorative choice of your own is the one thing to avoid.\n- **Progressive is fine.** A `BrandSnapshot` requires only the **name**. If the vision or\n the market is too thin to derive a direction honestly, leave `logoDirection` or\n `visualTone` out and say what is missing. The snapshot persists partially directed, and\n this playbook can resume.\n- **One product, one brand.** The snapshot is a single aggregate: one name, one logo\n direction, one visual tone.\n\n## What the brief holds — one aggregate\n\n- **Name** (REQUIRED). The anchor lexical identity: the exact, case-sensitive\n `brandName` the logo renders and every surface prints, plus an optional\n `tagline` to lock up with combination marks / OG imagery. Nothing visual\n here — the mark and the palette come next.\n\n **You do not invent the name, and you do not choose it.** `top_down.brand-naming`\n proposed names and ran a minimal trademark screening of each; the creator CHOSE\n one in this playbook's `brand-name` question, from options computed from that\n screening. The `brandName` is exactly the chosen option's name. An option may end\n with a bracketed qualifier — `[not-screened]`, `[screening-incomplete]` or\n `[keep-despite-conflict]` — which records how the creator chose; it is NEVER part of\n the name, so drop it. The interview answer also records the line the creator was\n shown beside that option (the product already using the name, the registers nobody\n could read): carry its substance into the brief rather than paraphrasing it away.\n\n The brand-name screening is in your brief. Never describe the name as\n \"available\", \"registered\", \"protected\" or \"cleared\": a screening is not a legal\n clearance opinion. Where the creator kept a name despite a conflict, or chose one\n whose screening is incomplete or read no register at all, do not hide or soften that\n anywhere in the brief.\n- **Logo direction** (optional, WARNed when absent). The creative brief the\n image model turns into the master logo:\n - `markType` — the creator's `logo-mark-type` answer. The question suggests\n `COMBINATION_MARK` (symbol + wordmark) because it is the only archetype that\n natively yields BOTH a header lockup and a square symbol for favicons and app\n icons. When the creator chose `WORDMARK` (text only), note in the brief that a\n wordmark cannot produce a clean square app icon.\n - `motifs` — concrete visual elements to include (short noun phrases), DERIVED\n from the symbolism and the creator's `visual-direction`.\n - `symbolism` — the meaning the mark should evoke, **derived from the vision\n mission/idea** (and the creator's `visual-direction`, when they gave one).\n - `avoid` — imagery don'ts (the negative-prompt guardrails that keep output\n usable), DERIVED, plus anything the creator's `visual-direction` rules out.\n - `backgroundTreatment` — the creator's `logo-background` answer.\n `TRANSPARENT_ISOLATED` is the default and the only treatment that rasterizes\n losslessly into every derived asset. A\n solid field or contextual scene is an explicit opt-in the pipeline must\n compensate for — the validator WARNs on it.\n- **Visual tone** (optional, WARNed when absent). The aesthetic register — the\n VISUAL counterpart to the market voice, DERIVED from it (and shaped by the\n creator's `visual-direction`): 3–7 concrete `styleKeywords`\n (\"friendly\", \"fluid\", \"confident\"), a one-line `mood`, a prose `colorIntent`\n (the color STORY, not hex values), and the hex `colorSeeds` the creator gave in\n `visual-color-seeds`, only when they named any. Keep the creator's MAIN colour\n first: the build derives the application's palette from these seeds, the first\n as its primary and the second as its accent.\n The style words and the mood ALSO choose the theme of the application and its\n website (corners, depth, spacing, motion, letter case): pick them for the look\n the creator's `visual-direction` describes, not only for the logo. \"Minimal\"\n flattens every shadow, \"precise\" makes corners sharp and motion still, \"warm\"\n and \"soft\" add depth; the `brand-logo-authoring` skill lists every word.\n- **Audience** (optional). WHO the brand is for: `targetIcpRefs`, the refs of\n the market ICPs its name and tone are chosen to speak to, copied exactly from\n the market's `icps`, plus a one-line `rationale`. Derive it from what the brief\n already says: the ICP whose preferred voice the visual tone translates, the\n segment the mission and tagline address. Never name a segment the market does\n not hold, and never list an anti-target. Downstream agents are given the\n brand's ICPs, and through them their personas and positionings, from this one\n declaration.\n\n## Answers the creator did not give\n\nIn a quick interview the creator is asked only for `brand-name`. Every other answer may\nreach your brief marked ASSUMED: the companion proposed it from the vision and the market,\nand it was kept without the creator deciding it — on their review, or by an unattended round. Use an assumed answer as a working\ndefault, not as the creator's choice. Where the brief explains a choice that rests on one\n(a tagline, a mark type, a background, a colour seed), say it was proposed rather than\nchosen, and never let an assumed answer outrank what the vision and the market voice imply\nthe way the creator's own answer would. `brand-name` is never assumed: the creator chooses it.\n\n## What you emit\n\nA single `BrandSnapshot`:\n\n- `version` — the snapshot format version (leave at its default unless told otherwise).\n- `name` — the required anchor (`brandName`, optional `tagline`).\n- `logoDirection` / `visualTone` / `audience` — the optional singletons, present when they could be decided or honestly derived.\n- `resolvedAssets` — **leave empty.** This is the companion logo step's output,\n not something you author. Hand-authoring it fabricates asset references the\n pipeline will overwrite or the validator will flag.\n\nAuthor every entity in English. Follow the `brand-logo-authoring` skill for the\nexact field contracts and the mark-type / background / visual-tone decision\naids — its full text is in your brief, under \"The skills this method tells you\nto FOLLOW\". Read it there; you cannot open files.\n\n## Quality gate\n\nYour emitted snapshot is checked by the deterministic `brand-snapshot-valid`\ngate (`validateBrandSnapshot`) before it commits. A directed-but-ungenerated\nbrand (a `logoDirection` present, `resolvedAssets` still empty) is expected and\nonly WARNs — it is exactly the state you hand off to the companion logo step. A\nmissing logo direction and a missing visual tone are also warnings, reflecting a\nnot-yet-complete brief. Emit a clean brief and let the warnings stand honestly\nwhen the brand genuinely is not fully directed yet, rather than inventing a\nmark to silence them.\n\nAfter landing, the advisory judge reads the brief against two criteria — grounding in\nthe interview and the vision, and the audience-and-assets hand-off — and its verdicts\nreach the creator's review as notes. A verdict never refuses a landing.\n\n## Approval\n\nThe drafted `BrandSnapshot` is presented to the creator for approval before it\nbecomes the committed `brand-brief`. Show the brief back in plain prose — the\nname, the mark direction, the visual tone — and let the creator confirm or\ncorrect it. The brand-brief is what the logo is generated from and what\npropagates everywhere; it is worth one explicit human sign-off before the mark\nis made.\n\n## Runtime context\n\nBefore you start, read the current journey state, the vision brief that grounds\nthe brand's meaning, and any brand brief that already exists so you refine it\nrather than re-deriving it from scratch.\n\n(The vision and any previously landed brand brief arrive in your brief as the `vision-brief` and\n`brand-brief` input sections.)\n\n## References\n\nThese are skill FOLDERS installed in the application, and this step has no tools,\nso it does not open them. What reaches you is stated per skill below.\n\n- `brand-logo-authoring` — the field contracts for the `BrandSnapshot` (name /\n logoDirection / visualTone), the mark-type selection table, background\n derivation-safety, and deriving the visual tone from the market voice. Its\n FULL TEXT is in your brief; follow it exactly.\n",
50
50
  "skillRefs": [
51
51
  "brand-logo-authoring"
52
52
  ],
@@ -51,6 +51,11 @@ Concretely:
51
51
  exactly why it is a trap. If they described one, produce one.
52
52
  - **Never invent a scaling axis.** If they did not say what the price scales
53
53
  with, omit `pricingModel` rather than guessing `per_seat`.
54
+ - **A price per usage names its unit.** When a plan's `pricingModel` is
55
+ `per_usage`, `usageUnit` is what ONE unit counts, singular and in the
56
+ creator's words: "API call", "export", "close". A firm that bills each case
57
+ ("we charge per monthly close", "a fixed fee per audit") is pricing per usage,
58
+ and its unit is the case. Every other plan has `usageUnit: null`.
54
59
  - **"Not decided yet" is an answer.** Record what they *did* decide and leave
55
60
  the rest absent. Absence is legible; an invention is not.
56
61
 
@@ -167,6 +172,7 @@ One output, the `business-model` family. The contract is strict:
167
172
  - [ ] `pricingTiers` is the reading of the tiers answer from the table above.
168
173
  - [ ] Every `pricePoint` and `pricingModel` traces to something the creator
169
174
  actually wrote — on a proposed plan too.
175
+ - [ ] Every `per_usage` plan names its `usageUnit`, and no other plan names one.
170
176
  - [ ] Every `creator_stated` plan traces to a tier they described. No tier count
171
177
  was rounded up.
172
178
  - [ ] Every `proposed` plan carries a `proposalBasis` naming an ICP and the
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.business-model",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "phase": "top_down",
5
5
  "intent": "Turn the accepted market and requirements truth, plus the creator's own pricing intent, into a non-vacuous BusinessModelLiteSnapshot: the product-level revenue model, where its pricing tiers came from (stated by the creator, proposed at the creator's request, or not decided yet), and a sketch of pricing plans, each cross-linked to the market ICPs it is sold to and the requirements it unlocks. A PLANNING artifact carrying commercial INTENT — never the billing runtime, and never a price the creator did not state.",
6
6
  "preconditions": [
@@ -44,7 +44,7 @@
44
44
  ],
45
45
  "stepOutputs": [],
46
46
  "method": {
47
- "guidance": "# Business Model — Commercial Intent Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## Where the tiers came from: `pricingTiers`\n\nThe tiers answer has exactly three honest readings, and you record which one it\nwas. This status is what lets an empty sketch be an answer instead of a gap.\n\n| The creator said | `pricingTiers` | `plans` |\n|---|---|---|\n| named one or more tiers (\"one tier\" counts) | `creator_stated` | exactly the tiers they named, `proposalBasis: null` on each |\n| asked for tiers to be proposed (\"propose them\", \"derive them from the market research\") | `proposed` | your proposal, each plan with a `proposalBasis` |\n| the tiers are not decided, and asked for no proposal | `undecided` | **empty** |\n\nA creator who says \"not decided — let the plan propose them\" has asked for a\nproposal: that is `proposed`, not `undecided`. Read the whole answer, not its\nfirst words.\n\n### An undecided sketch is complete\n\n`undecided` with no plans, plus the `revenueModel` they chose, IS the artifact.\nDo not add a placeholder tier to make it look fuller. The revenue model still\ntells every reader how the product makes money, so an empty `plans` never means\n\"free\" or \"no billing\".\n\n### A proposal is work the creator delegated, and it stays marked as one\n\nWhen the creator asks for a proposal, deriving tiers is the job, not an\ninvention. Derive them from what the inputs hold:\n\n- **one tier per ICP that would pay differently.** The market snapshot's ICPs\n are the segments; a tier exists because a segment needs a different package,\n never because three tiers is customary. An anti-target the vision excludes\n gets no tier.\n- **what separates each tier is a set of requirements.** Put the requirement\n refs it unlocks in `includesRequirementRefs`, and say in `includes` what it\n holds back relative to the tier beside it.\n- **`proposalBasis` names the evidence**: the ICP ref it serves and the\n requirements that distinguish it (\"serves icp-indie-maker; holds back the\n team-planning requirements the Team tier unlocks\"). A proposal with no basis\n is a tier nobody can check.\n- **A proposal still never sets a price or a scaling axis.** Unless the creator\n stated one, `pricePoint`, `billingPeriod` and `pricingModel` are `null` on a\n proposed plan exactly as on a stated one. The creator delegated the tiers, not\n the prices.\n\nThe creator accepts or revises the proposal at the approval step; you do not\nneed to be cautious on their behalf by proposing nothing.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **`pricingTiers` is required**, and it decides how many plans there are (see\n the table above). `creator_stated` and `proposed` carry at least one plan;\n `undecided` carries none. If the creator sells exactly one thing, that is one\n `creator_stated` plan, fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] `pricingTiers` is the reading of the tiers answer from the table above.\n- [ ] Every `pricePoint` and `pricingModel` traces to something the creator\n actually wrote — on a proposed plan too.\n- [ ] Every `creator_stated` plan traces to a tier they described. No tier count\n was rounded up.\n- [ ] Every `proposed` plan carries a `proposalBasis` naming an ICP and the\n requirements that separate it; every `creator_stated` plan carries none.\n- [ ] An `undecided` sketch has no plans, and no placeholder was added.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent. An `undecided` sketch with no plans is coherent\n with any revenue model.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
47
+ "guidance": "# Business Model — Commercial Intent Method (v1 scaffold)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 scaffold methodology.** Pricing sketch depth only — no unit\n> economics, no cohort modelling, no competitive price positioning. Those are a\n> later phase; do not perfect them here.\n\n## What this playbook does\n\nYou are recording the product's **commercial intent**: how it makes money, and\nwhat it sells. The output is one `BusinessModelLiteSnapshot` — a revenue-model\nclassification plus a sketch of pricing plans, each cross-linked to the market\nsegments it is sold to and the requirements it unlocks.\n\nIt is a **PLANNING artifact**, in exactly the sense the vision and the roadmap\nare. It is not the billing runtime, not a Stripe catalogue, and not a price list\nanyone is held to. Nothing reads it to charge a customer.\n\n## The one rule that governs everything below\n\n**You do not decide how this product charges. The creator does.**\n\nEvery other top-down family is DERIVED — the market snapshot follows from the\nvision, requirements follow from both, the roadmap follows from the capability\nmap. This one is not, and the difference is not a matter of degree. The same\nproduct is a fair freemium tool, a per-seat B2B subscription, or a\nusage-metered API, and **nothing in the vision, the market or the requirements\ndecides which**. It is a business decision, and only the creator holds it.\n\nSo this playbook interviews. Your job is to take what the creator said and make\nit *structured and cross-linked* — never to fill a gap they left.\n\nConcretely:\n\n- **Never invent a price.** If the creator said \"not decided yet\", omit\n `pricePoint`. A tier with no price is a real, useful plan; a tier with a price\n nobody chose is a fabrication that then propagates — the foundation playbook\n derives the billing capability from this artifact.\n- **Never invent a tier.** Three tiers is the industry default and that is\n exactly why it is a trap. If they described one, produce one.\n- **Never invent a scaling axis.** If they did not say what the price scales\n with, omit `pricingModel` rather than guessing `per_seat`.\n- **A price per usage names its unit.** When a plan's `pricingModel` is\n `per_usage`, `usageUnit` is what ONE unit counts, singular and in the\n creator's words: \"API call\", \"export\", \"close\". A firm that bills each case\n (\"we charge per monthly close\", \"a fixed fee per audit\") is pricing per usage,\n and its unit is the case. Every other plan has `usageUnit: null`.\n- **\"Not decided yet\" is an answer.** Record what they *did* decide and leave\n the rest absent. Absence is legible; an invention is not.\n\n## Where the tiers came from: `pricingTiers`\n\nThe tiers answer has exactly three honest readings, and you record which one it\nwas. This status is what lets an empty sketch be an answer instead of a gap.\n\n| The creator said | `pricingTiers` | `plans` |\n|---|---|---|\n| named one or more tiers (\"one tier\" counts) | `creator_stated` | exactly the tiers they named, `proposalBasis: null` on each |\n| asked for tiers to be proposed (\"propose them\", \"derive them from the market research\") | `proposed` | your proposal, each plan with a `proposalBasis` |\n| the tiers are not decided, and asked for no proposal | `undecided` | **empty** |\n\nA creator who says \"not decided — let the plan propose them\" has asked for a\nproposal: that is `proposed`, not `undecided`. Read the whole answer, not its\nfirst words.\n\n### An undecided sketch is complete\n\n`undecided` with no plans, plus the `revenueModel` they chose, IS the artifact.\nDo not add a placeholder tier to make it look fuller. The revenue model still\ntells every reader how the product makes money, so an empty `plans` never means\n\"free\" or \"no billing\".\n\n### A proposal is work the creator delegated, and it stays marked as one\n\nWhen the creator asks for a proposal, deriving tiers is the job, not an\ninvention. Derive them from what the inputs hold:\n\n- **one tier per ICP that would pay differently.** The market snapshot's ICPs\n are the segments; a tier exists because a segment needs a different package,\n never because three tiers is customary. An anti-target the vision excludes\n gets no tier.\n- **what separates each tier is a set of requirements.** Put the requirement\n refs it unlocks in `includesRequirementRefs`, and say in `includes` what it\n holds back relative to the tier beside it.\n- **`proposalBasis` names the evidence**: the ICP ref it serves and the\n requirements that distinguish it (\"serves icp-indie-maker; holds back the\n team-planning requirements the Team tier unlocks\"). A proposal with no basis\n is a tier nobody can check.\n- **A proposal still never sets a price or a scaling axis.** Unless the creator\n stated one, `pricePoint`, `billingPeriod` and `pricingModel` are `null` on a\n proposed plan exactly as on a stated one. The creator delegated the tiers, not\n the prices.\n\nThe creator accepts or revises the proposal at the approval step; you do not\nneed to be cautious on their behalf by proposing nothing.\n\n## What you DO derive\n\nTwo things, and both are cross-links rather than content:\n\n### `targetIcpRefs` — who each plan is sold to\n\nThe creator described tiers in prose (\"a free one for solo people, a paid one\nfor teams\"). The market snapshot holds the ICP refs. Your job is to resolve one\nagainst the other: match each described audience to the ICP that means it, and\nput its ref on the plan.\n\nEvery ref you write must EXIST in the market snapshot. A dangling ICP ref is a\nvalidator ERROR, and it is also the more interesting failure — it usually means\nthe creator described an audience the market analysis never identified, which is\nworth surfacing rather than papering over. If a described audience matches no\nICP, omit the ref and say so in `targetSummary` prose instead.\n\nWatch for **anti-targets**: a vision constraint may explicitly rule out a\nsegment (an enterprise procurement motion, say). Do not target an ICP the vision\nexcludes, even if a tier looks like it fits.\n\n### `includesRequirementRefs` — what each plan unlocks\n\nThis is the traceability that makes the artifact load-bearing rather than\ndecorative: it is what `bottom_up.foundation` reads to decide whether the\napplication needs a billing capability at all.\n\nResolve the creator's description of what each tier includes against the\n`requirements` family, and list the refs. Every ref must exist there. A paid\ntier that unlocks no nameable requirement is a signal worth leaving visible —\neither the requirement is missing, or the tier is not really differentiated.\n\n## The free tier is the one to get right\n\nIf the creator described a free tier or trial, two things matter and both come\nfrom what they said:\n\n- what it **includes** — the requirements it unlocks;\n- what is **deliberately held back** — which is usually the sharper statement of\n the paid tiers' value, and belongs in the paid plan's `includes` prose.\n\nIf they said there is no free tier, say nothing about one. Freemium is a\n*revenue model*, not a default.\n\n## Producing the artifact\n\nOne output, the `business-model` family. The contract is strict:\n\n- **`revenueModel` is required.** Pick the enum member closest to what the\n creator described. If they described something genuinely outside the set, pick\n the nearest and explain the mismatch in the plans' prose — do not stretch a\n member past its meaning.\n- **`pricingTiers` is required**, and it decides how many plans there are (see\n the table above). `creator_stated` and `proposed` carry at least one plan;\n `undecided` carries none. If the creator sells exactly one thing, that is one\n `creator_stated` plan, fully described.\n- **`slug`, not `ref`.** You author a kebab-case slug per plan; the trusted\n runtime stamps the `pricing-plan-` prefix. Never write a ref yourself.\n- **Every optional field is nullable and required.** Send `null` where the\n creator gave you nothing. An omitted key and a considered \"there is none\" must\n not look the same.\n\n## Verification before you answer\n\n- [ ] `pricingTiers` is the reading of the tiers answer from the table above.\n- [ ] Every `pricePoint` and `pricingModel` traces to something the creator\n actually wrote — on a proposed plan too.\n- [ ] Every `per_usage` plan names its `usageUnit`, and no other plan names one.\n- [ ] Every `creator_stated` plan traces to a tier they described. No tier count\n was rounded up.\n- [ ] Every `proposed` plan carries a `proposalBasis` naming an ICP and the\n requirements that separate it; every `creator_stated` plan carries none.\n- [ ] An `undecided` sketch has no plans, and no placeholder was added.\n- [ ] Every `targetIcpRefs` entry exists in the market snapshot.\n- [ ] Every `includesRequirementRefs` entry exists in the requirements snapshot.\n- [ ] No ICP the vision constraints exclude is targeted.\n- [ ] `revenueModel` is consistent with the plans beneath it — a `freemium`\n classification with no free plan, or a `subscription` with only a one-off\n purchase, is incoherent. An `undecided` sketch with no plans is coherent\n with any revenue model.\n- [ ] Nothing in the artifact answers a question the creator left open.\n",
48
48
  "skillRefs": [],
49
49
  "skillBodyRefs": [],
50
50
  "elicitation": {
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.capability-map",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "top_down",
5
5
  "intent": "Map accepted market benefits and requirements to coherent product capabilities, atomically refining the market benefit-to-feature edges and producing ref-less feature specification drafts. FIT/Kano remains a pluggable fit signal, never an implicit build-order ranking.",
6
6
  "preconditions": [