@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
@@ -60,6 +60,13 @@ The runtime normalizes your answer and **rejects** it — spending one of three
60
60
  were shown exactly which. There is no partial credit for a plausible objective.
61
61
  - cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`
62
62
  prefix, spelled exactly.
63
+ - answer an obligation under a source its objective was not reviewed under. The authority section
64
+ names, per objective, the sources the basis reviewed it under. You choose one of those; the
65
+ requirements the obligation cites are stamped from the basis, so you do not write them.
66
+ - give a `sourceSlug` for an objective the authority section marks as reviewed under no source by
67
+ design, or omit it for one that was reviewed under a source. Whether an objective answers any
68
+ external source is the basis's decision: such an obligation omits `sourceSlug` and is stamped as
69
+ answering no source.
63
70
  - bind the same objective twice.
64
71
  - bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability
65
72
  it requires is absent, so nothing could ever evidence it.
@@ -79,8 +86,11 @@ For each objective you were shown, ask three questions **in order**, and stop at
79
86
  whose intent describes something the declarations do not show is not bound. Read the computed
80
87
  applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only
81
88
  as `UNDETERMINED`.
82
- 2. **Which external requirement does it answer, and does that source reach this application?** If the
83
- product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.
89
+ 2. **Which source does it answer, and does that source reach this application?** Only a source the
90
+ objective was reviewed under can be answered; which of its requirements apply is the basis's
91
+ review, not yours. If the product serves no EU data subjects, GDPR does not reach it and no
92
+ obligation should cite it. An objective the basis reviews under no source by design answers
93
+ none: skip this question for it, and decide its applicability on the objective alone.
84
94
  3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can
85
95
  defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is
86
96
  the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a
@@ -35,7 +35,7 @@
35
35
  ],
36
36
  "stepOutputs": [],
37
37
  "method": {
38
- "guidance": "# Compliance Conception — Derivation Method (v1)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which external requirement does it answer, and does that source reach this application?** If the\n product serves no EU data subjects, GDPR does not reach it and no obligation should cite it.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is THREE fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated identifier for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. `title` is the role's name as a person reads it (`Application owner`,\n `Control operator`) — what the creator sees wherever the role is named. Two programme roles may map to\n the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
38
+ "guidance": "# Compliance Conception — Derivation Method (v1)\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is the first step in the journey that makes a POSITIVE compliance claim.** Everything before\n> it describes the product. This one says what the product commits to, and a governed document will\n> later quote it. Treat every sentence you write as something an auditor may read back to the\n> operator.\n\n## What this playbook does\n\nThe compliance-posture step decided **which regimes apply**, in prose, as `compliance`-kind\nconstraints on the vision. You turn that into the application's **assurance programme**: which Wildo\ncontrol objectives this product binds, which external requirement each one answers, who is\naccountable, and what is explicitly undetermined.\n\nYou do **not** re-elicit the vision, design the domain, or draft any document. You produce one\nartifact — the `compliance-program` family — and nothing else.\n\n## The one rule that governs everything below\n\n**A vision sentence is not a control mapping.** The posture step recorded \"must be GDPR-compliant for\nEU customer personal data\". That is product intent. It is *not* a decision that this application binds\n`WILDO.PRIVACY.SUBJECT_DATA_EXPORT`, and converting one into the other by reading is exactly what the\nposture step's own method forbids: the transition \"must not reinterpret a vision sentence as a control\nmapping or positive compliance claim.\"\n\nSo every element of the programme comes from one of exactly three places:\n\n| element | comes from |\n|---|---|\n| which objectives exist, what they demand, what proves them | the **engine authority** you were shown — never invented |\n| which sources exist, their edition, authority and rights | the **source registry** — you supply only a slug |\n| what the programme COVERS — the product, its type, its services and modules | the declared `compliance_primary_facts` context section of your brief — DECLARED, never described |\n| which roles this application declares, and which holds the administrative ceiling | the declared `application_role_graph` context section of your brief — a CLOSED SET you select from |\n| WHEN this draft was produced | the HOST's observed instant — stamped, never answered |\n| WHEN it is next reviewed | the application's declared review cadence, applied by the host — a dated commitment, or a stamped limitation saying none is committed |\n| whether an objective CAN apply here | the application's enabled capabilities, computed per objective in the declared `assurance_program_authority` context section of your brief — a lookup, never your finding |\n| whether an objective's intent is TRUE of this product | your reading of the declarations against that intent — a proposal, read back by an advisory judge and accepted by a commit |\n| what is genuinely undetermined | the **creator's answer in this run** — the one thing no declaration records |\n\nIf something comes from none of those, it does not go in the programme. Say it is `UNDETERMINED`, or\nstate it as a limitation.\n\n## What you will be refused for\n\nThe runtime normalizes your answer and **rejects** it — spending one of three runs — if you:\n\n- bind an objective the authority basis states no expectation for. The basis covers a small set; you\n were shown exactly which. There is no partial credit for a plausible objective.\n- cite a source the registry does not carry. `sourceSlug` is the registry ref minus its `source:`\n prefix, spelled exactly.\n- answer an obligation under a source its objective was not reviewed under. The authority section\n names, per objective, the sources the basis reviewed it under. You choose one of those; the\n requirements the obligation cites are stamped from the basis, so you do not write them.\n- give a `sourceSlug` for an objective the authority section marks as reviewed under no source by\n design, or omit it for one that was reviewed under a source. Whether an objective answers any\n external source is the basis's decision: such an obligation omits `sourceSlug` and is stamped as\n answering no source.\n- bind the same objective twice.\n- bind an objective the authority section marks `NOT_APPLICABLE` for this application. Every capability\n it requires is absent, so nothing could ever evidence it.\n- state `APPLICABLE` for an objective the authority section marks `UNDETERMINED`. A capability that would\n attest it is absent here, so the evidence `APPLICABLE` promises cannot be produced; state it\n `UNDETERMINED` and say what is open.\n\nThese are not style checks. Each one is a claim the framework cannot stand behind, and the rejection\nmessage names what you got wrong — read it and fix that, rather than restructuring the answer.\n\n## Deciding an obligation\n\nFor each objective you were shown, ask three questions **in order**, and stop at the first \"no\".\n\n1. **Does this application actually do what the intent describes?** You have its resource declarations\n — erasure treatment, data-subject kinds, whether subject export is declared. Use them. An objective\n whose intent describes something the declarations do not show is not bound. Read the computed\n applicability first: a `NOT_APPLICABLE` objective is refused, and an `UNDETERMINED` one is bound only\n as `UNDETERMINED`.\n2. **Which source does it answer, and does that source reach this application?** Only a source the\n objective was reviewed under can be answered; which of its requirements apply is the basis's\n review, not yours. If the product serves no EU data subjects, GDPR does not reach it and no\n obligation should cite it. An objective the basis reviews under no source by design answers\n none: skip this question for it, and decide its applicability on the objective alone.\n3. **Can you justify binding it from the evidence you were shown?** Write the disposition you can\n defend, with the reason. `APPROVED` is not you asserting that a review happened — the review is\n the human's COMMIT, and until then this is a proposal on disk. What is forbidden is a\n disposition you cannot point at evidence for; \"the objective sounded right\" is the failure this\n whole step exists to prevent.\n\nAn objective that fails (1) or (2) is simply absent from the programme. **Absence is a legitimate,\nreadable answer** — a programme binding one objective honestly is worth more than one binding four\nhopefully.\n\n### Applicability: `APPLICABLE` or `UNDETERMINED`, never a guess\n\n`UNDETERMINED` with a reason is the right answer whenever the run cannot settle it, and the posture\nstep asks for exactly that. It is visible, it is actionable, and a later pass can close it. A confident\n`APPLICABLE` that nobody could justify is invisible and reads as a decision somebody made.\n\n`NOT_APPLICABLE` is not offered to you. That branch requires evidence that the obligation does not\napply, and evidence is not something a derivation can produce.\n\n## Limitations are required, and they are the honest part\n\nYou must state at least one. The programme you produce binds a handful of objectives out of everything\na regime demands, and a reader who is not told that will read it as a complete posture. Say plainly\nwhat it does not cover: which objectives are unbound, that no operating effectiveness is claimed, and\nthat the programme is not a conformity assertion for any named regime.\n\nThis is not a disclaimer bolted on. It is what makes the rest of the document quotable.\n\n## What reads your programme back\n\nAn advisory judge reads the landed programme against the same declarations and the same computed\napplicability you were given. For each obligation it asks whether the objective's intent is true of this\nproduct, whether an `UNDETERMINED` says what is open, and whether anything claims operating effectiveness, regime conformity or a wider scope. It refuses\nnothing — its verdict travels with the result — but it is why \"the objective sounded right\" does not\nsurvive to the commit.\n\nIt replaced a question that asked the creator, per objective, whether the application met it. That answer\nis either in the declarations, where you can read it, or it is a judgement — which is a judge's job, not a\nform's.\n\n## What you never do\n\n- **Never author a rights record, an edition, or an authority name.** Those come from the registry\n because they govern what may be reproduced from a source. Inventing one is a licensing claim nobody\n reviewed.\n- **Never invent a reviewer, and never author a review instant.** You are not asked for one: the host\n stamps the instant it observed this draft. What makes the dispositions a REVIEW is the human's\n COMMIT — a landed programme is a working edit until then — so write the disposition you can\n justify from the evidence and let acceptance happen where acceptance happens.\n- **Never author a next-review date, and never write a review-schedule limitation.** You are not asked\n for either. The host applies the application's declared review cadence; where none is declared the\n programme is still produced and carries a stamped limitation saying no schedule is committed. A\n limitation of your own on the same point would say it twice, in words nothing checks.\n- **Never invent a ROLE KEY, and do not ask for one either.** The accountable and operating roles are\n SELECTED from the declared `application_role_graph` context section of your brief, which lists every role this application\n declares and marks the administrative ceiling at each scope. A role key that resolves to nothing is\n worse than an absent one — it reads as a named accountable party. If no declared role genuinely holds\n a responsibility, record an explicit gap.\n\n **A programme role is THREE fields, and the key goes in only one of them.** `applicationRoleRef` is the\n application's role key, spelled exactly as that section shows it (`APP_ADMIN_SUPER_ADMIN`). `slug` is\n the programme's OWN lowercase, hyphenated identifier for the responsibility (`application-owner`,\n `control-operator`), and it is the slug — never the key — that `responsibility`'s role lists and\n `reviewerRoleSlug` refer to. `title` is the role's name as a person reads it (`Application owner`,\n `Control operator`) — what the creator sees wherever the role is named. Two programme roles may map to\n the same key; a slug never carries one.\n- **Never name an organization-scope role as accountable for the PROGRAMME.** An organization role\n answers for one tenant; the programme is about the product. The two scopes are rendered separately\n and labelled for exactly this reason.\n- **Never state operating effectiveness.** That a control is configured is not that it has worked. The\n programme has no way to say the latter, and a document downstream is refused for claiming it.\n- **Never widen the scope you were given, and do not ask for it.** What the programme covers is\n DECLARED: the product, its type and its services are in\n the declared `compliance_primary_facts` context section of your brief, which also separates the contracted service from\n build-time tooling that is deliberately outside it. State the boundary from that, naming the\n services individually — an application, its environments and its services, never the operator's\n whole organisation. A service not listed there is not part of this application.\n\n## The two routing decisions you emit beside the programme\n\nNaming which documents are required and stopping there leaves the next step with nothing to route by.\nSo this playbook also answers where those documents are published, and what must happen before one\nfaces a real reader.\n\n### `document-publication` — which variants exist at all\n\nOne entry per exact **locale x jurisdiction** combination the application publishes in. The two are an\nINSEPARABLE pair: `en-GB` for `jurisdiction:eu` and `en-GB` for `jurisdiction:gb` are two variants\ncarrying different clauses, and neither implies a third assembled from one of each. Nothing\ndownstream may recombine the axes.\n\nTake the jurisdictions from what the application has DECLARED — its operating regions, its posture —\nnever from where you imagine it might expand. A variant nobody publishes in is a routing claim no\ndocument can honour, and every later release must name a variant declared here.\n\n### `document-release-policy` — which approval lane each requirement takes\n\nOne selection per documentation requirement the authority section lists under **Documentation\nrequirements this application owes**, keyed by that `requirementRef` and `requirementVersion` exactly.\nThose are DERIVED from what the application declares — the programme declares exactly them, and you do\nnot write them — so a selection naming any other requirement is refused:\n\n| lane | means |\n|---|---|\n| `DRAFT_ONLY` | the document may be drafted and retained; nothing may serve it as published |\n| `OPERATOR_ATTESTED` | an accountable operator may release an exact draft with explicit limitations, which the selection must list |\n| `QUALIFIED_REVIEW` | the reviewer-authority route is required before it is served |\n\n**Choose the lane the application can honestly satisfy today, and prefer the strictest only where it\nis true.** `DRAFT_ONLY` is the right answer for a document nobody has reviewed, and it is not a\nfailure state: a drafted document and an unapproved release are both legitimate artifacts an\napplication holds for most of its life.\n\n**None of these lanes blocks drafting or composing a release.** They decide what must be true before\na document faces a REAL READER, which is a later question than the one this journey is answering. A\nlane that stopped the build would be a compliance workflow standing in front of the\napplication-creation mechanism.\n\n## Where this leaves the journey\n\nThe programme you land is the accepted answer for which controls this product commits to. It is what\nan obligation register reads, what a governed document cites when it says the operator has a\nprogramme, and what a later mapping pass binds to external framework identifiers.\n\nIt is accepted the way everything is accepted here: by a commit, which this run does not make. Who\nmakes it is the host's autonomy posture, and the programme's dispositions become a REVIEW only when a\nPERSON commits them. A commit the development companion makes under the YOLO posture is authored as\nthe companion: it accepts the working edit and reviews nothing.\n",
39
39
  "skillRefs": [],
40
40
  "skillBodyRefs": [],
41
41
  "elicitation": {
@@ -47,6 +47,11 @@ needed by nothing downstream of this lane:
47
47
  - **`top_down.brand-identity`** — the visual identity, from the creator's answers. Its
48
48
  `brand-name` is a CHOICE among the screened names, so it runs after the naming lane.
49
49
  - **`top_down.risk-register`** — the register the assurance mechanisms read.
50
+ - **`top_down.service-method`** — a service firm's method: the services it sells, how each case
51
+ is worked, decided and delivered. Needs the vision alone, so it usually runs first beside the
52
+ chain; offer it again as a REFRESH as the market snapshot, the requirements and the business
53
+ model land, since each sharpens it (the business model is what settles per-case pricing). It
54
+ is not applicable on a B2B SaaS or an internal tool until a feature line needs it.
50
55
 
51
56
  Nothing above is a sequence. Each child declares what it needs, and the runtime
52
57
  re-computes what may run after every round. That is what makes the lane re-runnable
@@ -62,8 +67,8 @@ vision whole, the others as a map of what exists — and the children that may r
62
67
  since it landed is not offered at all. Every option is marked FIRST RUN, or REFRESH
63
68
  with the input that moved and the run that moved it. Prefer first runs; take a
64
69
  refresh when the change it names matters to that child.
65
- - **Independent children share a round.** The brand identity and the risk register
66
- ride beside the chain; several research lanes with genuinely different objectives
70
+ - **Independent children share a round.** The brand identity, the risk register and a
71
+ firm's method ride beside the chain; several research lanes with genuinely different objectives
67
72
  return more than one asked everything.
68
73
  - **A child whose interview is unanswered is not offered.** The dossier answers the
69
74
  creator's questions per leaf; a leaf the dossier does not cover waits for the creator,
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "top_down.definition",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "phase": "top_down",
5
- "intent": "Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand naming (screened name proposals), the brand identity and the risk register beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves' preconditions and never a list. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. Prefer first runs; take a refresh when its changed input matters to it. Run independent children in the same round (brand naming or the brand identity, and the risk register beside the chain; several research lanes with different objectives). Run the phase gate once the roadmap is on record, and STOP after it has run — its verdict is this lane's closing decision, and it is not re-run in the same run. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the definition.",
5
+ "intent": "Drive the top-down DEFINITION of the application as one lane: from an answered vision through market evidence, the market snapshot, the value proposition, the requirements, the capability map, the business model and the roadmap, to the phase gate — with the brand naming (screened name proposals), the brand identity, the risk register and the firm's method (its services, decisions and signatories; on a service firm, or wherever a feature line needs it) beside the chain. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round, so the order is the leaves' preconditions and never a list. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. Prefer first runs; take a refresh when its changed input matters to it. Run independent children in the same round (brand naming or the brand identity, and the risk register or the firm's method beside the chain; several research lanes with different objectives). Run the phase gate once the roadmap is on record, and STOP after it has run — its verdict is this lane's closing decision, and it is not re-run in the same run. A child whose interview the creator has not answered is not offered; run everything else and stop when nothing eligible advances the definition.",
6
6
  "preconditions": [],
7
7
  "inputs": [
8
8
  {
@@ -44,7 +44,7 @@
44
44
  }
45
45
  ],
46
46
  "method": {
47
- "guidance": "# The Definition Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the leaves that DEFINE the\napplication — what it is, for whom, against which market, delivering which\nrequirements, in which order, sold how — and it ends on the phase gate's verdict,\nwhich is the lane's closing decision.\n\n## The children, and why the order is not written here\n\nThe chain, each leaf gated by the families the ones before it land:\n\n- **`top_down.vision-elicitation`** — the vision brief, from the creator's own\n answers. No precondition: the lane starts here on a fresh application.\n- **`top_down.market-analysis`** — a NESTED LANE, not a leaf: it gathers web evidence,\n judges whether it is enough, and lands the `market-snapshot` only once the verdict is\n `adequate`, re-searching against the gaps the gate named for as long as it needs. Its\n evidence loop is its own business; this lane sees only that a market snapshot landed.\n- **`top_down.value-proposition`** — refines the same snapshot: benefits, tones of\n voice, one positioning pillar per targeted ICP.\n- **`top_down.requirements-definition`** — the requirements, from vision and market.\n- **`top_down.capability-map`** — benefit → feature edges on the snapshot, and the\n feature drafts.\n- **`top_down.business-model`** — revenue model and pricing plans, from the creator's\n pricing intent.\n- **`top_down.scope-roadmap`** — the phases that deliver or defer the requirements and\n the success criteria.\n- **`top_down.phase-gate`** — five criteria over the coherence report. Lands nothing;\n its verdict is what this lane ends on.\n\nBeside the chain, needing the vision (and the business model, for the register) and\nneeded by nothing downstream of this lane:\n\n- **`top_down.brand-naming`** — a nested lane: proposes names and runs a minimal trademark\n screening of each, landing the `brand-name-screening`. Needs the market snapshot.\n- **`top_down.brand-identity`** — the visual identity, from the creator's answers. Its\n `brand-name` is a CHOICE among the screened names, so it runs after the naming lane.\n- **`top_down.risk-register`** — the register the assurance mechanisms read.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. That is what makes the lane re-runnable\non an application where most of it exists: whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next children\n\nThe selector is shown the accepted truth for the families this lane declares — the\nvision whole, the others as a map of what exists — and the children that may run.\n\n- **Missing beats present.** A child already on record whose inputs have not changed\n since it landed is not offered at all. Every option is marked FIRST RUN, or REFRESH\n with the input that moved and the run that moved it. Prefer first runs; take a\n refresh when the change it names matters to that child.\n- **Independent children share a round.** The brand identity and the risk register\n ride beside the chain; several research lanes with genuinely different objectives\n return more than one asked everything.\n- **A child whose interview is unanswered is not offered.** The dossier answers the\n creator's questions per leaf; a leaf the dossier does not cover waits for the creator,\n and the lane runs everything else it can.\n- **The phase gate runs once, last, then the lane stops.** It lands nothing and returns\n nothing the runtime can mark delivered, so the round history is the record that it\n ran.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. For a research child the\nmarket umbrella's rule holds: the first round broad, a later round naming the gap the\ngate named. For a chain leaf the objective names what changed upstream since its output\nlast landed — a re-derived market snapshot, a revised vision — so the leaf refines\nrather than restarts.\n\n## When to stop\n\nStop when the phase gate has run: its verdict is the decision. Stop also when nothing\neligible advances the definition — every remaining child is waiting for the creator, or\nthe evidence gate has named the same gap twice and a further round could not close it.\nSay which, in the rationale.\n\n## What the phase gate's verdict re-opens\n\nThe lane declares this table, and the runtime applies it: a GAP on one of the first four\ncriteria offers the mapped leaf again, even though it already landed in this run. When a\nleaf you have already seen land is eligible again after the gate, that is this loop-back,\nnot churn. Re-run that leaf against the gate's rationale for the faulted criterion, then run\nthe gate again. A PASS re-opens nothing, and CONCERN or INDETERMINATE re-open nothing\neither: re-deriving a leaf does not answer advice, and it does not produce evidence.\n\n| criterion | re-opens |\n|---|---|\n| requirement coverage | `top_down.scope-roadmap` |\n| success-criterion coverage | `top_down.scope-roadmap` |\n| capability completeness | `top_down.capability-map` |\n| positioning / ICP coherence | `top_down.value-proposition` |\n| compliance presence | the compliance lane, which this lane does not admit — the root re-opens it, from this lane's exported verdict |\n\n## What the creator reviews\n\nThe definition set, family by family, exactly as each leaf's own review guide says —\nand the phase gate's verdict, which is the one decision this lane ends on: accept the\ndefinition, or send it back to the leaf the verdict names.\n",
47
+ "guidance": "# The Definition Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the leaves that DEFINE the\napplication — what it is, for whom, against which market, delivering which\nrequirements, in which order, sold how — and it ends on the phase gate's verdict,\nwhich is the lane's closing decision.\n\n## The children, and why the order is not written here\n\nThe chain, each leaf gated by the families the ones before it land:\n\n- **`top_down.vision-elicitation`** — the vision brief, from the creator's own\n answers. No precondition: the lane starts here on a fresh application.\n- **`top_down.market-analysis`** — a NESTED LANE, not a leaf: it gathers web evidence,\n judges whether it is enough, and lands the `market-snapshot` only once the verdict is\n `adequate`, re-searching against the gaps the gate named for as long as it needs. Its\n evidence loop is its own business; this lane sees only that a market snapshot landed.\n- **`top_down.value-proposition`** — refines the same snapshot: benefits, tones of\n voice, one positioning pillar per targeted ICP.\n- **`top_down.requirements-definition`** — the requirements, from vision and market.\n- **`top_down.capability-map`** — benefit → feature edges on the snapshot, and the\n feature drafts.\n- **`top_down.business-model`** — revenue model and pricing plans, from the creator's\n pricing intent.\n- **`top_down.scope-roadmap`** — the phases that deliver or defer the requirements and\n the success criteria.\n- **`top_down.phase-gate`** — five criteria over the coherence report. Lands nothing;\n its verdict is what this lane ends on.\n\nBeside the chain, needing the vision (and the business model, for the register) and\nneeded by nothing downstream of this lane:\n\n- **`top_down.brand-naming`** — a nested lane: proposes names and runs a minimal trademark\n screening of each, landing the `brand-name-screening`. Needs the market snapshot.\n- **`top_down.brand-identity`** — the visual identity, from the creator's answers. Its\n `brand-name` is a CHOICE among the screened names, so it runs after the naming lane.\n- **`top_down.risk-register`** — the register the assurance mechanisms read.\n- **`top_down.service-method`** — a service firm's method: the services it sells, how each case\n is worked, decided and delivered. Needs the vision alone, so it usually runs first beside the\n chain; offer it again as a REFRESH as the market snapshot, the requirements and the business\n model land, since each sharpens it (the business model is what settles per-case pricing). It\n is not applicable on a B2B SaaS or an internal tool until a feature line needs it.\n\nNothing above is a sequence. Each child declares what it needs, and the runtime\nre-computes what may run after every round. That is what makes the lane re-runnable\non an application where most of it exists: whatever is on record satisfies the gates of\nwhatever is not.\n\n## Selecting the next children\n\nThe selector is shown the accepted truth for the families this lane declares — the\nvision whole, the others as a map of what exists — and the children that may run.\n\n- **Missing beats present.** A child already on record whose inputs have not changed\n since it landed is not offered at all. Every option is marked FIRST RUN, or REFRESH\n with the input that moved and the run that moved it. Prefer first runs; take a\n refresh when the change it names matters to that child.\n- **Independent children share a round.** The brand identity, the risk register and a\n firm's method ride beside the chain; several research lanes with genuinely different objectives\n return more than one asked everything.\n- **A child whose interview is unanswered is not offered.** The dossier answers the\n creator's questions per leaf; a leaf the dossier does not cover waits for the creator,\n and the lane runs everything else it can.\n- **The phase gate runs once, last, then the lane stops.** It lands nothing and returns\n nothing the runtime can mark delivered, so the round history is the record that it\n ran.\n\n## Composing an objective for a child\n\nEach dispatch carries an objective composed for that round. For a research child the\nmarket umbrella's rule holds: the first round broad, a later round naming the gap the\ngate named. For a chain leaf the objective names what changed upstream since its output\nlast landed — a re-derived market snapshot, a revised vision — so the leaf refines\nrather than restarts.\n\n## When to stop\n\nStop when the phase gate has run: its verdict is the decision. Stop also when nothing\neligible advances the definition — every remaining child is waiting for the creator, or\nthe evidence gate has named the same gap twice and a further round could not close it.\nSay which, in the rationale.\n\n## What the phase gate's verdict re-opens\n\nThe lane declares this table, and the runtime applies it: a GAP on one of the first four\ncriteria offers the mapped leaf again, even though it already landed in this run. When a\nleaf you have already seen land is eligible again after the gate, that is this loop-back,\nnot churn. Re-run that leaf against the gate's rationale for the faulted criterion, then run\nthe gate again. A PASS re-opens nothing, and CONCERN or INDETERMINATE re-open nothing\neither: re-deriving a leaf does not answer advice, and it does not produce evidence.\n\n| criterion | re-opens |\n|---|---|\n| requirement coverage | `top_down.scope-roadmap` |\n| success-criterion coverage | `top_down.scope-roadmap` |\n| capability completeness | `top_down.capability-map` |\n| positioning / ICP coherence | `top_down.value-proposition` |\n| compliance presence | the compliance lane, which this lane does not admit — the root re-opens it, from this lane's exported verdict |\n\n## What the creator reviews\n\nThe definition set, family by family, exactly as each leaf's own review guide says —\nand the phase gate's verdict, which is the one decision this lane ends on: accept the\ndefinition, or send it back to the leaf the verdict names.\n",
48
48
  "skillRefs": [],
49
49
  "skillBodyRefs": [],
50
50
  "contextSources": [],
@@ -62,7 +62,8 @@
62
62
  "top_down.vision-elicitation",
63
63
  "top_down.brand-naming",
64
64
  "top_down.brand-identity",
65
- "top_down.risk-register"
65
+ "top_down.risk-register",
66
+ "top_down.service-method"
66
67
  ],
67
68
  "maximumIterations": 20,
68
69
  "maximumLanesPerIteration": 3,
@@ -32,9 +32,14 @@ critic, and a FINALIZE pass when the critique asks for one — then promotes the
32
32
 
33
33
  - **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never
34
34
  replaced; the accept step refuses and the run reports it.
35
- - **Re-derive a committed charter.** A role that already has a committed charter is left alone; ask for a
36
- re-derivation explicitly through the companion's `expert-personas/derive` route if the application's
37
- definition moved enough to warrant one.
35
+ - **Re-derive a current charter.** A committed charter is derived again only when one of its shaping inputs
36
+ changed AFTER it (written by a later run, edited, or committed later): the brand's visual tone, the market, the vision, the requirements, the business
37
+ model, the brand's promoted assets or the design-system configuration, whichever that role reads. The
38
+ board then offers this step as a refresh naming the inputs that moved, and the run reports those roles
39
+ as derived again. Each input is dated from the file the persona reads, so promoting a logo moves only
40
+ the roles that read the promoted assets.
41
+ - **Re-derive a drifted charter a person edited.** It is named in the run's report with the inputs that
42
+ moved, for the person to update by hand.
38
43
  - **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with
39
44
  no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.
40
45
 
@@ -54,3 +59,5 @@ therefore which roles are derivable now.
54
59
  and `index.ts` lists every one of them.
55
60
  - `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.
56
61
  - The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.
62
+ - After the run, the board offers this step as current: no charter is older than an input it reads, apart
63
+ from those a person edited, which the run named, and those still waiting on a family.
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "top_down.expert-personas",
3
- "version": "0.2.0",
3
+ "version": "0.3.0",
4
4
  "phase": "top_down",
5
- "intent": "Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed is left alone (a human-edited charter is never overwritten), and a role whose shaping inputs have not landed yet is REPORTED as waiting rather than failing the run. Before this step existed the panel's staffing was not a journey step at all — every deliberated playbook failed closed at bind time on an application whose charters nobody had curled in by hand (#572).",
5
+ "intent": "Staff every expert panel the catalog convenes: derive and accept an application-specific charter for each framework expert role that a deliberated playbook (`method.deliberation`) or a companion generation step (the logo panel) seats, grounded in the application's own vision, market, requirements, business model and brand. Idempotent: a role whose charter is committed and current is left alone, a committed charter older than one of its shaping inputs is derived again (a human-edited one is never overwritten and is named for the person to update, #2819), and a role whose shaping inputs have not landed yet is REPORTED as waiting rather than failing the run. Before this step existed the panel's staffing was not a journey step at all — every deliberated playbook failed closed at bind time on an application whose charters nobody had curled in by hand (#572).",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -42,7 +42,7 @@
42
42
  ],
43
43
  "stepOutputs": [],
44
44
  "method": {
45
- "guidance": "# Expert personas — staff the panels the catalog convenes\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nSeveral steps of the creation journey are DECIDED BY A PANEL rather than by a single generation:\n`bottom_up.placement-plan` convenes an information architect and a design-system guardian, the logo\ngeneration step convenes an art director, a brand strategist and a design-system guardian. A panel is\nbuilt from **expert-persona charters** — one committed charter per framework expert role, derived from\nthis application's own vision, market, requirements, business model and brand, so a reviewer speaks\nfor THIS product rather than for a generic one.\n\nThis step derives and accepts those charters. It is runner-owned: no prompt is composed here. For every\nrole the catalog convenes (read off every playbook's `method.deliberation` and off the generation\nsteps' own panels), it runs the companion's derive → accept flow — a DRAFT, a CRITIQUE by a dedicated\ncritic, and a FINALIZE pass when the critique asks for one — then promotes the proposal into\n`specifications/src/personas/<role>.charter.generated.ts`, regenerates the aggregator and wires the\n`expertPersonaCharters` companion-exports slot.\n\n## What it will not do\n\n- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never\n replaced; the accept step refuses and the run reports it.\n- **Re-derive a committed charter.** A role that already has a committed charter is left alone; ask for a\n re-derivation explicitly through the companion's `expert-personas/derive` route if the application's\n definition moved enough to warrant one.\n- **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with\n no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.\n\n## Cost, so it is scheduled knowingly\n\nA derivation is an agentic three-pass protocol over the application's own artifacts: measured at about\n200 seconds per role on a real application. Five roles is a quarter of an hour. Submit the run detached.\n\n## What you read\n\nThe current journey state this run is given, to see which families have landed and\ntherefore which roles are derivable now.\n\n## Verification\n\n- `specifications/src/personas/` holds one `*.charter.generated.ts` per role the run reports as derived,\n and `index.ts` lists every one of them.\n- `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.\n- The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.\n",
45
+ "guidance": "# Expert personas — staff the panels the catalog convenes\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n## What this step does\n\nSeveral steps of the creation journey are DECIDED BY A PANEL rather than by a single generation:\n`bottom_up.placement-plan` convenes an information architect and a design-system guardian, the logo\ngeneration step convenes an art director, a brand strategist and a design-system guardian. A panel is\nbuilt from **expert-persona charters** — one committed charter per framework expert role, derived from\nthis application's own vision, market, requirements, business model and brand, so a reviewer speaks\nfor THIS product rather than for a generic one.\n\nThis step derives and accepts those charters. It is runner-owned: no prompt is composed here. For every\nrole the catalog convenes (read off every playbook's `method.deliberation` and off the generation\nsteps' own panels), it runs the companion's derive → accept flow — a DRAFT, a CRITIQUE by a dedicated\ncritic, and a FINALIZE pass when the critique asks for one — then promotes the proposal into\n`specifications/src/personas/<role>.charter.generated.ts`, regenerates the aggregator and wires the\n`expertPersonaCharters` companion-exports slot.\n\n## What it will not do\n\n- **Overwrite a human-edited charter.** A committed charter carrying an `authored` block is never\n replaced; the accept step refuses and the run reports it.\n- **Re-derive a current charter.** A committed charter is derived again only when one of its shaping inputs\n changed AFTER it (written by a later run, edited, or committed later): the brand's visual tone, the market, the vision, the requirements, the business\n model, the brand's promoted assets or the design-system configuration, whichever that role reads. The\n board then offers this step as a refresh naming the inputs that moved, and the run reports those roles\n as derived again. Each input is dated from the file the persona reads, so promoting a logo moves only\n the roles that read the promoted assets.\n- **Re-derive a drifted charter a person edited.** It is named in the run's report with the inputs that\n moved, for the person to update by hand.\n- **Fail on a role whose inputs are not landed.** A role needing the brand brief on an application with\n no brand yet is REPORTED as waiting, with the families it waits on. The step re-runs when they land.\n\n## Cost, so it is scheduled knowingly\n\nA derivation is an agentic three-pass protocol over the application's own artifacts: measured at about\n200 seconds per role on a real application. Five roles is a quarter of an hour. Submit the run detached.\n\n## What you read\n\nThe current journey state this run is given, to see which families have landed and\ntherefore which roles are derivable now.\n\n## Verification\n\n- `specifications/src/personas/` holds one `*.charter.generated.ts` per role the run reports as derived,\n and `index.ts` lists every one of them.\n- `companion-exports.ts` wires `expertPersonaCharters` onto the aggregator.\n- The eligibility board no longer reports `PANEL_UNSTAFFED` for `bottom_up.placement-plan`.\n- After the run, the board offers this step as current: no charter is older than an input it reads, apart\n from those a person edited, which the run named, and those still waiting on a family.\n",
46
46
  "skillRefs": [],
47
47
  "skillBodyRefs": [],
48
48
  "contextSources": [],
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.feature-drafts",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "top_down",
5
5
  "intent": "Draft the product capabilities an application needs from its accepted requirements and vision, for an application whose line has no market: one spec-first, ref-less feature specification draft per capability the requirements call for, each tracing to the requirements it serves.",
6
6
  "preconditions": [
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "top_down.market-snapshot-produce",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "phase": "top_down",
5
5
  "intent": "Derive a validated market snapshot from the vision and from the EVIDENCE a sibling research step gathered — the artifact-producing child of the `top_down.market-analysis` composite. The provider proposes the market graph; the trusted runtime stamps entity refs/version and keeps provenance, authority and accepted-family mutation outside model output. Its intent used to claim derivation from \"sealed research evidence\" while nothing supplied any; it now runs only once an adequacy gate has read the evidence and returned ADEQUATE.",
6
6
  "preconditions": [
@@ -53,7 +53,7 @@ Where the application has declared a posture for the signal, record it on the en
53
53
 
54
54
  The derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.
55
55
 
56
- Four of them are read from the application's configuration and always arrive. The two that need every resource materialized — the personal-data inventory and the MCP exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.
56
+ Four of them always arrive: three are read from the application's configuration (its capabilities, retention and provider hosting) and one from its specifications (the brand name's trademark standing). The ones that need every resource materialized — the personal-data inventory and its declaration gap, the MCP exposure and the chat-command exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.
57
57
 
58
58
  The register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.
59
59
 
@@ -43,7 +43,7 @@
43
43
  ],
44
44
  "stepOutputs": [],
45
45
  "method": {
46
- "guidance": "# Complete the risk register\n\nThe derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.\n\nThis step writes what they mean for this product and these users, and proposes the risks no derivation reaches.\n\n## You are drafting, not deciding\n\nA model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:\n\n- Write statements a reader can argue with. \"Personal data is processed by third parties\" is unarguable and says nothing; \"two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely\" is a claim someone can check and correct.\n- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.\n- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.\n\nAfter landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.\n\n## Two kinds of entry, and the difference is what may be believed\n\n**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.\n\n**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.\n\n### The brand name is a derived signal\n\n`application:brand-name-trademark-standing` says where the brand's chosen name stands\nagainst its minimal trademark screening. It is computed by matching the brand name to its\nscreened candidate. When the signal reports the exposure as PRESENT, complete it into a\n**SIGNAL_DERIVED** entry with that `signalRef`. Do not write a PROPOSED one: the standing is\nmeasured, and a later run re-derives it.\n\n- **kept despite a conflict**: name the conflicting marks and registers from the signal's\n detail and the screening in your brief. Say what the exposure means for THIS product: an\n opposition, a cease-and-desist, a forced rebrand after launch.\n- **screening incomplete**: name the jurisdictions or registers not covered, and say the\n name is not cleared there.\n- **conflict unacknowledged**: the screening now finds a conflict that nobody chose to keep\n (the brand was named before a re-screen found it). Say so. Do not describe it as the\n creator's decision, because it was not one.\n- **never screened**: say so plainly.\n\nA cleared name, or a line with no brand, needs no entry. Never weigh a present exposure as\n\"low\" on the grounds that a screening ran: a screening is not a clearance.\n\n## Weighting is two qualitative bands and NOTHING is multiplied\n\nLikelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.\n\nGround the bands in what is IMPLEMENTED, not in how the risk sounds. \"Impact HIGH because the erasure path is manual\" is grounded. \"Impact HIGH because data breaches are serious\" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.\n\nWhere the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.\n\n## The signals, and what to do when they are not all there\n\nThe derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.\n\nFour of them are read from the application's configuration and always arrive. The two that need every resource materialized — the personal-data inventory and the MCP exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.\n\nThe register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.\n\nDo not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.\n\n## What belongs to other mechanisms\n\n- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.\n- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.\n- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.\n- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.\n",
46
+ "guidance": "# Complete the risk register\n\nThe derivation layer says what is PRESENT in this application — how many providers are vendor-hosted, how many operations an external agent can reach, which retention classes have a declared period, which resources have said nothing about personal data. Those are facts, and they are deliberately silent about what they MEAN.\n\nThis step writes what they mean for this product and these users, and proposes the risks no derivation reaches.\n\n## You are drafting, not deciding\n\nA model proposes; a human accepts; the accepted register is the committed file. Nothing you write here takes effect by being written, and the value of the artifact is that a person can disagree with it line by line. So:\n\n- Write statements a reader can argue with. \"Personal data is processed by third parties\" is unarguable and says nothing; \"two vendor-hosted LLM providers receive task titles and user names, which are the fields customers type freely\" is a claim someone can check and correct.\n- Never write a statement you cannot ground. If the evidence for a risk is that it sounds prudent, it is a PROPOSED entry and must be marked as one.\n- Do not soften a derived fact to make the register read better. The register is read by people deciding how deeply to audit something; a reassuring one is worse than none.\n\nAfter landing, the advisory judge reads the register against three criteria — honest entry origins, arguable statements with grounded bands, and the boundary with other mechanisms — and its verdicts reach the person accepting the register as notes. A verdict never refuses a landing.\n\n## Two kinds of entry, and the difference is what may be believed\n\n**SIGNAL_DERIVED** — completed from a derived signal, which the entry names. The measurement can be re-run, so the entry's premise is falsifiable: if the signal stops reporting the exposure, the statement resting on it is stale rather than merely old. One derived entry per signal.\n\n**PROPOSED** — a business risk nothing measures. This is why the step exists rather than the derivation being the whole answer: a register limited to what code can compute would omit most of what a product actually carries. Ground each one in the vision, the business model and the market snapshot, which this application has already authored, and never anchor it to a signal — a proposal pointing at a measurement is a derived entry wearing the wrong label.\n\n### The brand name is a derived signal\n\n`application:brand-name-trademark-standing` says where the brand's chosen name stands\nagainst its minimal trademark screening. It is computed by matching the brand name to its\nscreened candidate. When the signal reports the exposure as PRESENT, complete it into a\n**SIGNAL_DERIVED** entry with that `signalRef`. Do not write a PROPOSED one: the standing is\nmeasured, and a later run re-derives it.\n\n- **kept despite a conflict**: name the conflicting marks and registers from the signal's\n detail and the screening in your brief. Say what the exposure means for THIS product: an\n opposition, a cease-and-desist, a forced rebrand after launch.\n- **screening incomplete**: name the jurisdictions or registers not covered, and say the\n name is not cleared there.\n- **conflict unacknowledged**: the screening now finds a conflict that nobody chose to keep\n (the brand was named before a re-screen found it). Say so. Do not describe it as the\n creator's decision, because it was not one.\n- **never screened**: say so plainly.\n\nA cleared name, or a line with no brand, needs no entry. Never weigh a present exposure as\n\"low\" on the grounds that a screening ran: a screening is not a clearance.\n\n## Weighting is two qualitative bands and NOTHING is multiplied\n\nLikelihood and impact are each one of five bands. There is no score, no rating and no product of the two anywhere in the register, and this is not a stylistic preference: the derivation layer beneath this one asserts structurally that it emits no score, because a number is what a reader trusts without checking. Two judgements multiplied into a third judgement would put exactly that underneath a layer built to refuse it.\n\nGround the bands in what is IMPLEMENTED, not in how the risk sounds. \"Impact HIGH because the erasure path is manual\" is grounded. \"Impact HIGH because data breaches are serious\" is not — it would be equally true of every application ever built, which is the test for a weighting that carries no information.\n\nWhere the application has declared a posture for the signal, record it on the entry. A posture of AVOIDED that the measurement contradicts is not yours to resolve: state the risk as measured, note the contradiction in the weighting grounding, and let the person accepting the register decide whether the declaration or the product is wrong.\n\n## The signals, and what to do when they are not all there\n\nThe derived signals arrive in the declared `risk_signals` context section of your brief — measured facts about this application's own declarations, each with the inputs it came from and none with a score. Ground your weighting in them. Do not restate a signal as a risk, do not treat their order as a priority, and never re-derive or estimate one: they are computed, and a number you produced yourself would be indistinguishable on the page from one that was measured.\n\nFour of them always arrive: three are read from the application's configuration (its capabilities, retention and provider hosting) and one from its specifications (the brand name's trademark standing). The ones that need every resource materialized — the personal-data inventory and its declaration gap, the MCP exposure and the chat-command exposure — can be absent when the application cannot be introspected, and the section simply will not carry them.\n\nThe register does not require the derivation to have run. If signals were not supplied to this run, or only some were, produce the PROPOSED entries you can ground in the authored specification families, state plainly in the register which derived half is absent, and finish.\n\nDo not stop, do not ask for evidence to be collected first, and do not treat an absent measurement as an absent risk. A step that cannot proceed until evidence exists has made a measurement into a precondition, and a compliance workflow may never stand in front of the mechanism it describes.\n\n## What belongs to other mechanisms\n\n- **Which control objectives this application claims** — the compliance programme. A register entry may mention a control; it never binds one.\n- **Whether a control's evidence is adequate** — the evidence-adequacy step. The register says a risk exists, never that it has been discharged.\n- **How deeply to audit a demand** — a consumer of this register, not part of it. Write the risk; do not write the audit plan.\n- **Retention periods, provider deployment choices, jurisdictions** — configuration the application already declares. Read them; do not restate them as risks, and never contradict them here.\n",
47
47
  "skillRefs": [],
48
48
  "skillBodyRefs": [],
49
49
  "contextSources": [
@@ -0,0 +1,198 @@
1
+ # Service Method — How the Firm Works
2
+
3
+ ### Target Application Framing
4
+
5
+ This knowledge is for configuring behavior in the target application.
6
+ Wildo is the framework surface being used, not the product being built.
7
+
8
+ Read and apply these patterns from the application-developer point of view:
9
+
10
+ - how the application should configure the relevant app-level file
11
+ - how the application should use framework-provided factories, enums, and helpers
12
+ - how the application should avoid mixing frontend, backend, and infrastructure concerns
13
+
14
+
15
+ ## What this playbook does
16
+
17
+ You are writing down the firm's **method**: the services it sells to its clients and, for each, how a
18
+ case is worked. The output is one `ServiceMethod`. It is the one place the method is written down; the
19
+ domain plan, the roles and the build plan derive from it, so a method that is vague here is an
20
+ application that is vague everywhere.
21
+
22
+ A firm is not a product its users drive alone. A case is opened for a client, agents and the firm's
23
+ people work it, a qualified person takes the decisions that carry the firm's responsibility, and the
24
+ client receives something at the end. Write that down, case by case.
25
+
26
+ ## What the creator decides, and what you draft
27
+
28
+ The interview has four questions:
29
+
30
+ - **`services`** — what the firm sells, what starts a case and what ends it.
31
+ - **`signatories`** — which decisions only a qualified person may take, and what that person must be.
32
+ - **`agent-work`** — which work in a case the creator wants agents to do.
33
+ - **`working-hours`** — where and when the firm's reviewers work.
34
+
35
+ An answer the creator gave is theirs: build on it, do not second-guess it. An answer recorded as an
36
+ ASSUMPTION (proposed, because the creator did not know or chose a quick interview) is a proposal: use it,
37
+ and keep anything resting on it easy to revise. `agent-work` and `working-hours` are usually assumptions.
38
+
39
+ Everything else you DRAFT from those answers, the vision and the market: the stages, the steps, the
40
+ deliverables, the evidence retention, the correction reasons. Draft them so the creator can accept them
41
+ as they are; they will review them.
42
+
43
+ If an answer says "propose it", the creator delegated that part: propose it from the services. If the
44
+ interview says "none", write none — an empty list is an answer.
45
+
46
+ ## Step 1 — One service per thing the firm sells
47
+
48
+ Each service is one entry in `services`:
49
+
50
+ - `serviceRef` — a kebab-case key (`month-end-close`, `annual-audit`). Later families name it.
51
+ - `label` — what the firm calls it.
52
+ - `purpose` — what the CLIENT gets, in one sentence. Not what the firm does: "the client's books closed
53
+ every month, reconciled and signed off", not "we reconcile bank lines".
54
+
55
+ Two services the creator described as one are one service. Do not split a service to look thorough.
56
+
57
+ ## Step 2 — The case, and its stages
58
+
59
+ `case` is the unit of work a service is delivered in: one close, one audit engagement, one filing.
60
+
61
+ - `caseRef` — the PLANNED RESOURCE whose rows are the cases, in the domain plan's naming (plural,
62
+ kebab-case: `closes`, `audit-engagements`). The domain plan inventories it and the build plan makes it
63
+ the work unit, the record every model call on the case is costed to.
64
+ - `opensWhen` / `closesWhen` — the events, in the creator's words.
65
+
66
+ `stages` are the states a case moves through, in order, first stage first. Each has a `meaning`: what is
67
+ true of a case in that stage. Include the stage a case returns to when something surfaces after it was
68
+ finished ("reopened") when the creator's work has one. Stage refs are kebab-case and unique within the
69
+ service.
70
+
71
+ ## Step 3 — The steps, and who carries each one
72
+
73
+ Each step happens in one stage and is performed by exactly one of:
74
+
75
+ | `performedBy` | means |
76
+ |---|---|
77
+ | `AGENT` | an agent of the application does it. Say how it runs in `agentShape` |
78
+ | `PERSON` | one of the firm's people does it |
79
+ | `CLIENT` | the client does it (sends documents, answers a question) |
80
+
81
+ An agent step names its `agentShape`, and no other step does:
82
+
83
+ - `AUTONOMOUS` — it runs on its own, on a schedule or an event (reconciling every night, reading every
84
+ document that arrives);
85
+ - `CHAT_ASSISTANT` — a person talks to it and it proposes;
86
+ - `INVOKED` — another part of the application calls it;
87
+ - `FLOW_STEP` — it is one step of a declared flow the application runs.
88
+
89
+ Give work to an agent where it relieves the firm's people of reading, matching and drafting. **Never
90
+ give an agent a decision a qualified person must take**: an agent proposes, and the decision point in
91
+ Step 4 is where the person decides.
92
+
93
+ `readsRefs` and `producesRefs` name the planned resources a step reads and writes, in the domain plan's
94
+ naming. They are what lets the domain plan know a step needs a resource. Leave them empty rather than
95
+ inventing a resource no requirement implies.
96
+
97
+ ## Step 4 — The decision points: who decides, on what ground, by when
98
+
99
+ A decision point is where the case waits for a person. Each sits at one step (`stepRef`) and says in
100
+ `decides` what is decided. Then three choices, and they are the heart of this artifact.
101
+
102
+ **Who decides (`route`):**
103
+
104
+ | `route` | when |
105
+ |---|---|
106
+ | `owner` | the person whose own work raised it confirms it (accepting what an assistant proposed to them). Nobody vets the owner, so it takes no qualification |
107
+ | `role` | anyone holding a role may decide (any qualified accountant serving the client) |
108
+ | `assignee` | one named person decides (the client's engagement partner). Say who in `assignee`, in the firm's words |
109
+
110
+ **On what ground (`qualificationRef`):** every `role` and `assignee` decision names a qualification from
111
+ `qualifications`, and an `owner` decision names none. A qualification says:
112
+
113
+ - `role` — the role the person holds for the client, as the role table keys it
114
+ (`ORG_QUALIFIED_ACCOUNTANT`). It says what the client ENTRUSTED the firm with.
115
+ - `heldBy` — whose people hold that role: `FIRM` when the firm's people take the decision for the client
116
+ (almost always: the qualified accountant, the engagement partner), `CLIENT` when the client's own staff
117
+ take it in their organization (the client's finance director approving a deliverable). A firm-held role
118
+ reaches the firm's people through the relationship the firm serves its clients through, so the build
119
+ confers it there; `ORG_REPRESENTATIVE` is conferred by that relationship already. A role is always one
120
+ a member of an organization holds: never an application role (`APP_…`), and a firm-held role is never
121
+ the client's administration (`ORG_OWNER`, `ORG_ADMIN`), which no relationship may confer.
122
+ - `professionalQualificationKind` — set ONLY when the PERSON must also hold a verified professional
123
+ qualification (a chartered accountant, a licensed engineer). It follows the person, and lapses with
124
+ their licence. The value is a kebab-case kind (`chartered-accountant`) the application declares in its
125
+ `professionalQualificationKinds`; name the kind you need, and the build declares it.
126
+
127
+ Use the creator's `signatories` answer to choose. A decision the creator tied to a profession ("a
128
+ chartered accountant") needs both the role and the professional qualification. A decision tied to a
129
+ position ("the engagement partner") is an `assignee` decision with the role. A review any expert serving
130
+ the client may do is a `role` decision whose qualification names the role alone. Most decisions need
131
+ only a role; the professional-qualifications skill shown to you explains the mechanisms and how they
132
+ combine.
133
+
134
+ **By when (`decisionDeadline`):** a review that keeps a client waiting says when it is due, as an
135
+ ISO-8601 duration (`PT9H`, `P2D`) counted on `basis`: `calendar` (the firm's working hours) or `elapsed`
136
+ (around the clock). A business-time deadline needs `reviewCalendar`, built from the `working-hours`
137
+ answer: the `timeZone` (an IANA name), the `workingDays`, the `workingHours` (`HH:MM` from and to) and
138
+ the `holidays` as dates (`YYYY-MM-DD`). When the creator names a calendar ("French public holidays"),
139
+ write out its dates for the current and next year. A decision with no deadline is allowed, and it is marked:
140
+ the engine's default lapse and reminders apply.
141
+
142
+ ## Step 5 — What the client receives, what is kept, and what it costs
143
+
144
+ - `deliverables` — what a case produces for the client, at which stage, from which planned resource
145
+ (`fromResourceRef`). A close report, an audit opinion, a filed return.
146
+ - `evidenceRetention` — how long the case's evidence is kept: a `retentionClass` and its `ground`.
147
+ Records the law requires the firm to keep (accounting documents, working papers) are
148
+ `BUSINESS_RECORDS`; say the ground in plain words and name the jurisdiction the vision gives. You
149
+ state the firm's obligation as you understand it; the compliance lane governs the retention period.
150
+ - `pricing` — `PER_CASE` when each case is billed, `INCLUDED_IN_PLAN` when a subscription covers it,
151
+ `BILLED_OUTSIDE` when the firm bills from its own tools. Read it off the business model when one is on
152
+ record: a plan priced `per_usage` whose `usageUnit` is this service's case ("close") makes the service
153
+ `PER_CASE`; a subscription plan that covers the service makes it `INCLUDED_IN_PLAN`. With no business
154
+ model, `BILLED_OUTSIDE`, which commits the application to nothing. A service `PER_CASE` is billed one
155
+ metered unit when its case closes, once per case however often it is reopened; the build records it.
156
+ An internal tool has no billing at all, whatever a business model or a feature line brings: price
157
+ every service `BILLED_OUTSIDE` there. The coherence report names a price per case on such an
158
+ application as the method's gap, and no build can record it.
159
+
160
+ ## Step 6 — How the client takes part, and why a person corrects an agent
161
+
162
+ - `clientParticipation` — one paragraph: what the client provides, what they answer, what they read.
163
+ - `correctionReasons` — when agents do work a person reviews, the short list of reasons a person gives
164
+ for correcting it (`wrong_account`, `missing_evidence`). Each `reasonCode` is lowercase snake_case.
165
+ They let the firm see why agent work is corrected. Five to eight reasons, specific to the work.
166
+
167
+ ## Refine, don't re-author
168
+
169
+ When a method is already on record, refine it. Keep every ref that still names the same thing, because
170
+ later families name them; change the content, not the identity.
171
+
172
+ ## What you emit
173
+
174
+ One `ServiceMethod`. The schema refuses:
175
+
176
+ - a step in a stage the service does not declare, and a deliverable at one;
177
+ - an agent step without an `agentShape`, and any other step with one;
178
+ - a decision at a step the service does not declare;
179
+ - an `owner` decision naming a qualification, a `role` or `assignee` decision naming none, and a
180
+ qualification the method does not declare;
181
+ - one resource kept in two retention classes, because two services name it as their evidence;
182
+ - an `assignee` decision with no `assignee`, and an `assignee` on any other decision;
183
+ - a business-time deadline with no `reviewCalendar`, and a deadline that is not a positive duration
184
+ in weeks, days, hours, minutes or seconds (`PT8H`, `P2D`; no years or months);
185
+ - a qualification on a role no member of an organization holds (an application role, an inbound
186
+ handler's, a capability lent through a relationship), and a firm-held one on `ORG_OWNER` or `ORG_ADMIN`;
187
+ - any ref declared twice.
188
+
189
+ Fix the cause it names and answer again.
190
+
191
+ ## Verification
192
+
193
+ - Every service's `purpose` says what the client gets.
194
+ - Every decision the `signatories` answer named is a decision point, with the role, and the professional
195
+ qualification when the answer named a profession.
196
+ - No agent step decides anything a decision point decides.
197
+ - Every `role` and `assignee` decision names a declared qualification; every qualification is used.
198
+ - Every reviewer decision that keeps a client waiting has a deadline, or the creator said it has none.