@wildo-ai/framework-knowledge 1.1.9 → 1.1.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (1163) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +4 -2
  5. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  6. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +4 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  8. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +9 -3
  9. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  10. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  11. package/dist/esm/framework-knowledge.definitions.js +543 -80
  12. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  13. package/dist/esm/framework-knowledge.research-provenance.d.ts +88 -0
  14. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
  15. package/dist/esm/framework-knowledge.research-provenance.js +140 -0
  16. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
  17. package/dist/esm/index.d.ts +2 -0
  18. package/dist/esm/index.d.ts.map +1 -1
  19. package/dist/esm/index.js +2 -0
  20. package/dist/esm/index.js.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  22. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +43 -2
  25. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +138 -21
  27. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -1
  30. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  32. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +1 -1
  33. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +17 -9
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +22 -11
  37. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +89 -9
  41. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +6 -5
  43. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +6 -4
  45. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +2 -2
  47. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +7 -2
  49. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  51. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  53. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +28 -6
  55. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +23 -5
  57. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  59. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +9 -3
  61. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  63. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +14 -2
  65. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +1 -1
  67. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +2 -2
  69. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +14 -6
  71. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +2 -1
  73. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +5 -3
  75. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +2 -1
  77. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +11 -9
  79. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +17 -3
  81. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +19 -2
  83. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
  85. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  86. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
  87. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -1
  89. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +2 -1
  91. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  93. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +9 -3
  94. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  95. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +34 -7
  96. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +39 -13
  98. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  99. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
  100. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  101. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  102. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  103. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +14 -6
  104. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +38 -3
  107. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  109. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  111. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +95 -0
  113. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
  114. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +111 -0
  115. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
  116. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  117. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +15 -3
  118. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  119. package/dist/esm/source-anchor-grammar.d.ts +70 -0
  120. package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
  121. package/dist/esm/source-anchor-grammar.js +114 -0
  122. package/dist/esm/source-anchor-grammar.js.map +1 -0
  123. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  124. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  125. package/dist/knowledge/manifest.json +8 -8
  126. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
  127. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  128. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  129. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  130. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +497 -32
  131. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +44 -3
  132. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +302 -8
  133. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  134. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
  135. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +2 -2
  136. package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
  137. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
  138. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  139. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  140. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +118 -11
  141. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -3
  142. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +41 -10
  143. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +7 -5
  144. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +5 -0
  145. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +1 -1
  146. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +12 -0
  147. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +4 -3
  148. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +79 -1
  149. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  150. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +187 -14
  151. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +23 -3
  152. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +3 -2
  153. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +6 -2
  154. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +99 -24
  155. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  156. package/dist/knowledge/playbooks/refinement.document-facts/method.md +38 -3
  157. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +4 -3
  158. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  159. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +2 -2
  160. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
  161. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
  162. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  163. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  164. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +16 -5
  165. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +3 -3
  166. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +56 -16
  167. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +6 -4
  168. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  169. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  170. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +30 -9
  171. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +5 -3
  172. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +12 -1
  173. package/dist/knowledge/playbooks/top_down.business-model/method.md +6 -0
  174. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +2 -2
  175. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  176. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +2 -2
  177. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +12 -2
  178. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +1 -1
  179. package/dist/knowledge/playbooks/top_down.definition/method.md +7 -2
  180. package/dist/knowledge/playbooks/top_down.definition/playbook.json +5 -4
  181. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
  182. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +18 -4
  183. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  184. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +2 -2
  185. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  186. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  187. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  188. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +5 -3
  189. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  190. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  191. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -1
  192. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  193. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  194. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  195. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  196. package/dist/knowledge/playbooks/top_down.risk-register/method.md +1 -1
  197. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -1
  198. package/dist/knowledge/playbooks/top_down.service-method/method.md +198 -0
  199. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +96 -0
  200. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +23 -0
  201. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +23 -4
  202. package/dist/knowledge/references/acp.execution-profile.md +9 -1
  203. package/dist/knowledge/references/application-maturity.config.md +1 -1
  204. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +55 -0
  205. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +13 -2
  206. package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
  207. package/dist/knowledge/references/backend.inbound-handlers.definition.md +426 -5
  208. package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
  209. package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
  210. package/dist/knowledge/references/brand.name-choice.config.md +20 -3
  211. package/dist/knowledge/references/brand.name-screening.config.md +58 -3
  212. package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
  213. package/dist/knowledge/references/build-plan.task-graph.config.md +292 -7
  214. package/dist/knowledge/references/business-model.pricing-plan.config.md +7 -0
  215. package/dist/knowledge/references/business-model.snapshot.validation.md +18 -0
  216. package/dist/knowledge/references/capability-composition.config.md +4 -3
  217. package/dist/knowledge/references/cli.market.generate-command.md +2 -1
  218. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  219. package/dist/knowledge/references/companion.technical-doc.service.md +166 -32
  220. package/dist/knowledge/references/engine.client-bundle.allow-list.md +14 -0
  221. package/dist/knowledge/references/engine.saas-technical-doc.config.md +1 -1
  222. package/dist/knowledge/references/engine.saas-website.config.md +16 -44
  223. package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
  224. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  225. package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
  226. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  227. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +259 -0
  228. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  229. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +129 -0
  230. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +45 -0
  231. package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
  232. package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
  233. package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
  234. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
  235. package/dist/knowledge/references/example.config.design-system.full.md +40 -116
  236. package/dist/knowledge/references/example.data-seeding.minimal.md +10 -9
  237. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  238. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  239. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
  240. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +70 -14
  241. package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
  242. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
  243. package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
  244. package/dist/knowledge/references/example.infra.environment-config.local.md +24 -0
  245. package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
  246. package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
  247. package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
  248. package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
  249. package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
  250. package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
  251. package/dist/knowledge/references/example.provider.backend-module-shape.md +10 -0
  252. package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
  253. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
  254. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
  255. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -1
  256. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  257. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  258. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  259. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  260. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
  261. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  262. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +60 -22
  263. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +81 -0
  264. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +19 -20
  265. package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
  266. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  267. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  268. package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
  269. package/dist/knowledge/references/example.website.blocks.section.md +20 -0
  270. package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
  271. package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
  272. package/dist/knowledge/references/example.website.demo.append.md +57 -0
  273. package/dist/knowledge/references/example.website.demo.approval.md +47 -0
  274. package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
  275. package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
  276. package/dist/knowledge/references/example.website.demo.connect.md +45 -0
  277. package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
  278. package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
  279. package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
  280. package/dist/knowledge/references/example.website.demo.transform.md +43 -0
  281. package/dist/knowledge/references/example.website.page.manifest.md +2 -6
  282. package/dist/knowledge/references/example.website.section.bento.md +27 -0
  283. package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
  284. package/dist/knowledge/references/example.website.section.factories.md +82 -0
  285. package/dist/knowledge/references/example.website.section.faq.md +17 -0
  286. package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
  287. package/dist/knowledge/references/example.website.section.hero.md +16 -0
  288. package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
  289. package/dist/knowledge/references/example.website.section.marquee.md +26 -0
  290. package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
  291. package/dist/knowledge/references/example.website.section.site-block.md +43 -0
  292. package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
  293. package/dist/knowledge/references/example.website.section.stats.md +23 -0
  294. package/dist/knowledge/references/example.website.section.steps.md +15 -0
  295. package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
  296. package/dist/knowledge/references/example.website.theme.composed.md +69 -0
  297. package/dist/knowledge/references/experience-plan.config.md +76 -7
  298. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +6 -0
  299. package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
  300. package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
  301. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +6 -0
  302. package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
  303. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +64 -0
  304. package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
  305. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +61 -2
  306. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +70 -0
  307. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +253 -0
  308. package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
  309. package/dist/knowledge/references/integration-plan.config.md +21 -1
  310. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  311. package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
  312. package/dist/knowledge/references/minions.tick-contract.md +2 -2
  313. package/dist/knowledge/references/placement-plan.config.md +107 -2
  314. package/dist/knowledge/references/platform.config.environment.deployment.md +9 -1
  315. package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -0
  316. package/dist/knowledge/references/platform.config.platform-key-management.md +206 -0
  317. package/dist/knowledge/references/platform.config.saas.md +106 -14
  318. package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
  319. package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
  320. package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
  321. package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
  322. package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
  323. package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
  324. package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
  325. package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
  326. package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
  327. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
  328. package/dist/knowledge/references/presets.models.surface-variant.md +10 -0
  329. package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
  330. package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
  331. package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
  332. package/dist/knowledge/references/presets.themes.compose-theme.md +46 -0
  333. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  334. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  335. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  336. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  337. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  338. package/dist/knowledge/references/roadmap.phase.config.md +2 -16
  339. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +131 -0
  340. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +77 -11
  341. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +158 -0
  342. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
  343. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  344. package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
  345. package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
  346. package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
  347. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
  348. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  349. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  350. package/dist/knowledge/references/saas.backend.domain-module.md +76 -1
  351. package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
  352. package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
  353. package/dist/knowledge/references/saas.backend.email.send.md +84 -0
  354. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +9 -1
  355. package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
  356. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
  357. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
  358. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
  359. package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
  360. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +207 -0
  361. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
  362. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +300 -3
  363. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +13 -2
  364. package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
  365. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
  366. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
  367. package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
  368. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
  369. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +27 -0
  370. package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
  371. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  372. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
  373. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
  374. package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
  375. package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
  376. package/dist/knowledge/references/saas.backend.system-access-service.md +242 -107
  377. package/dist/knowledge/references/saas.config.content-security-policy.md +1 -2
  378. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  379. package/dist/knowledge/references/saas.data-seeding.definition-input.md +8 -2
  380. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  381. package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
  382. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
  383. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
  384. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
  385. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
  386. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
  387. package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
  388. package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
  389. package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
  390. package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
  391. package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
  392. package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
  393. package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
  394. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +126 -0
  395. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
  396. package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
  397. package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
  398. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +17 -3
  399. package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
  400. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
  401. package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
  402. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +324 -0
  403. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +109 -0
  404. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +61 -0
  405. package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
  406. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
  407. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +149 -0
  408. package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
  409. package/dist/knowledge/references/saas.frontend.resource-label-params.md +54 -0
  410. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +17 -11
  411. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +125 -58
  412. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +13 -7
  413. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  414. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +141 -32
  415. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +64 -2
  416. package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
  417. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
  418. package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
  419. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
  420. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
  421. package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
  422. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
  423. package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
  424. package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
  425. package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
  426. package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
  427. package/dist/knowledge/references/saas.models.audit.trail-config.md +63 -5
  428. package/dist/knowledge/references/{saas.models.auth.service-provider-client-authentication.md → saas.models.auth.relationship-grantor-authentication.md} +54 -48
  429. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
  430. package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
  431. package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
  432. package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
  433. package/dist/knowledge/references/saas.models.config.organization-types.md +42 -82
  434. package/dist/knowledge/references/saas.models.conversation-threads.md +4 -3
  435. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +22 -0
  436. package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
  437. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +27 -0
  438. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +403 -0
  439. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +84 -0
  440. package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -1
  441. package/dist/knowledge/references/saas.models.engine-capabilities.md +28 -0
  442. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
  443. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
  444. package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
  445. package/dist/knowledge/references/saas.models.external-data-pipeline.md +81 -18
  446. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
  447. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +317 -0
  448. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
  449. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
  450. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +147 -0
  451. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
  452. package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
  453. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
  454. package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
  455. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +62 -0
  456. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +314 -0
  457. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
  458. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +62 -0
  459. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
  460. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +1 -0
  461. package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
  462. package/dist/knowledge/references/saas.models.flows.runnable-model.md +255 -0
  463. package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
  464. package/dist/knowledge/references/saas.models.http-api-binding.md +157 -42
  465. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
  466. package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
  467. package/dist/knowledge/references/saas.models.inbound-channels.md +4 -1
  468. package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
  469. package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
  470. package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
  471. package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
  472. package/dist/knowledge/references/saas.models.notifications.targets.md +25 -2
  473. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +63 -9
  474. package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
  475. package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
  476. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +73 -0
  477. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +48 -0
  478. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
  479. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
  480. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +911 -0
  481. package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
  482. package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
  483. package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
  484. package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
  485. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +224 -0
  486. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +277 -0
  487. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +113 -0
  488. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +68 -5
  489. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +67 -2
  490. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
  491. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +278 -40
  492. package/dist/knowledge/references/saas.models.provider-capabilities.md +33 -0
  493. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
  494. package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
  495. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +8 -0
  496. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +37 -0
  497. package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
  498. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
  499. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
  500. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
  501. package/dist/knowledge/references/saas.models.representative-activity.md +65 -0
  502. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +84 -2
  503. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
  504. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +57 -11
  505. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
  506. package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
  507. package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
  508. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
  509. package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
  510. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +99 -2
  511. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
  512. package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
  513. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
  514. package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
  515. package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
  516. package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
  517. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +9 -0
  518. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
  519. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +25 -0
  520. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
  521. package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
  522. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
  523. package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
  524. package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
  525. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  526. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  527. package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -4
  528. package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
  529. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +121 -0
  530. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +3 -2
  531. package/dist/knowledge/references/saas.models.systems-of-record.md +36 -1
  532. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
  533. package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
  534. package/dist/knowledge/references/saas.public-runtime.contract.md +60 -2
  535. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
  536. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
  537. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +275 -13
  538. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
  539. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +9 -0
  540. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +16 -2
  541. package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
  542. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
  543. package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
  544. package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
  545. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +24 -2
  546. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
  547. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +19 -5
  548. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
  549. package/dist/knowledge/references/saas.website.astro.bridge.md +61 -14
  550. package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
  551. package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
  552. package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
  553. package/dist/knowledge/references/saas.website.astro.label-loader.md +41 -9
  554. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  555. package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
  556. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +48 -17
  557. package/dist/knowledge/references/saas.website.astro.site-context.md +30 -8
  558. package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
  559. package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
  560. package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
  561. package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
  562. package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
  563. package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
  564. package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
  565. package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
  566. package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
  567. package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
  568. package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
  569. package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
  570. package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
  571. package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
  572. package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
  573. package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
  574. package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
  575. package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
  576. package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
  577. package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
  578. package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
  579. package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
  580. package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
  581. package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
  582. package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
  583. package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
  584. package/dist/knowledge/references/saas.website.blog.bridge.md +102 -53
  585. package/dist/knowledge/references/saas.website.blog.collection-config.md +76 -24
  586. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
  587. package/dist/knowledge/references/saas.website.blog.frontmatter.md +104 -7
  588. package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
  589. package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
  590. package/dist/knowledge/references/saas.website.blog.index.md +43 -0
  591. package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
  592. package/dist/knowledge/references/saas.website.blog.post-renderer.md +113 -85
  593. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +181 -0
  594. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
  595. package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
  596. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +2 -1
  597. package/dist/knowledge/references/saas.website.config.site-context-loader.md +24 -1
  598. package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
  599. package/dist/knowledge/references/saas.website.consent.context.md +1 -1
  600. package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
  601. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
  602. package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
  603. package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
  604. package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
  605. package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
  606. package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
  607. package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
  608. package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
  609. package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
  610. package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
  611. package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
  612. package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
  613. package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
  614. package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
  615. package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
  616. package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
  617. package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
  618. package/dist/knowledge/references/saas.website.label-keys.format.md +2 -2
  619. package/dist/knowledge/references/saas.website.label-pack.validator.md +7 -8
  620. package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
  621. package/dist/knowledge/references/saas.website.legal.public-document-links.md +91 -0
  622. package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
  623. package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
  624. package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
  625. package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
  626. package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
  627. package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
  628. package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
  629. package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
  630. package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
  631. package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
  632. package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
  633. package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
  634. package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
  635. package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
  636. package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
  637. package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
  638. package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
  639. package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
  640. package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
  641. package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
  642. package/dist/knowledge/references/saas.website.page.context.md +9 -2
  643. package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
  644. package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
  645. package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
  646. package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
  647. package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
  648. package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
  649. package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
  650. package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
  651. package/dist/knowledge/references/saas.website.product.figures.md +320 -0
  652. package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
  653. package/dist/knowledge/references/saas.website.product.panels.md +324 -0
  654. package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
  655. package/dist/knowledge/references/saas.website.refs.section.md +2 -2
  656. package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
  657. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  658. package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
  659. package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
  660. package/dist/knowledge/references/saas.website.runtime.context.md +51 -17
  661. package/dist/knowledge/references/saas.website.section.component.md +21 -19
  662. package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
  663. package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
  664. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  665. package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
  666. package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
  667. package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
  668. package/dist/knowledge/references/saas.website.stacking.md +86 -0
  669. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
  670. package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
  671. package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
  672. package/dist/knowledge/references/service-method.config.md +270 -0
  673. package/dist/knowledge/references/website-plan.config.md +561 -23
  674. package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
  675. package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
  676. package/dist/knowledge/references/website-plan.page-routes.md +39 -0
  677. package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
  678. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +86 -9
  679. package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
  680. package/dist/knowledge/references/zod.decorators.data-categories.md +101 -11
  681. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +82 -6
  682. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +23 -1
  683. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  684. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
  685. package/dist/knowledge/references/zod.decorators.file-schema.md +6 -5
  686. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
  687. package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
  688. package/dist/knowledge/references/zod.decorators.schema-metadata.md +5 -0
  689. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +50 -1
  690. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +44 -5
  691. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +130 -9
  692. package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -7
  693. package/dist/knowledge/references/zod.factories.code.md +18 -8
  694. package/dist/knowledge/references/zod.factories.duration.md +23 -13
  695. package/dist/knowledge/references/zod.factories.money.md +24 -14
  696. package/dist/knowledge/references/zod.factories.phone.md +23 -14
  697. package/dist/knowledge/references/zod.factories.range.md +5 -1
  698. package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
  699. package/dist/knowledge/registries/framework-topics.json +2854 -246
  700. package/dist/knowledge/registries/playbooks.json +57 -36
  701. package/dist/knowledge/registries/source-tags.json +8863 -4569
  702. package/dist/knowledge/rules/database-migration-obligation.md +11 -5
  703. package/dist/knowledge/rules/live-context-door.md +1 -1
  704. package/dist/knowledge/skills/INDEX.md +63 -34
  705. package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
  706. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +203 -0
  707. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
  708. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
  709. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
  710. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
  711. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
  712. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +15 -3
  713. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
  714. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
  715. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
  716. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +341 -0
  717. package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
  718. package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
  719. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
  720. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
  721. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  722. package/dist/knowledge/skills/application-database-migrations/SKILL.md +41 -12
  723. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +34 -0
  724. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  725. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  726. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  727. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +130 -4
  728. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +90 -0
  729. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +59 -0
  730. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
  731. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +79 -2
  732. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +291 -10
  733. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  734. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
  735. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +223 -0
  736. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
  737. package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
  738. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
  739. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +189 -0
  740. package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
  741. package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
  742. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +132 -2
  743. package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
  744. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
  745. package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
  746. package/dist/knowledge/skills/brand-name-screening/SKILL.md +33 -9
  747. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +78 -6
  748. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +30 -8
  749. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +163 -0
  750. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +295 -0
  751. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
  752. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
  753. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +136 -34
  754. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
  755. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
  756. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +34 -7
  757. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
  758. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +37 -0
  759. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +178 -4
  760. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
  761. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +485 -61
  762. package/dist/knowledge/skills/config-app-shell/SKILL.md +101 -19
  763. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
  764. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
  765. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
  766. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
  767. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +472 -0
  768. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +82 -0
  769. package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
  770. package/dist/knowledge/skills/config-design-system/SKILL.md +271 -166
  771. package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
  772. package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
  773. package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
  774. package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
  775. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +37 -0
  776. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +235 -0
  777. package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
  778. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  779. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
  780. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
  781. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +7 -1
  782. package/dist/knowledge/skills/config-saas/SKILL.md +27 -11
  783. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +62 -4
  784. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +80 -7
  785. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +314 -0
  786. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
  787. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +8 -0
  788. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +1 -2
  789. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1182 -0
  790. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +61 -0
  791. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +56 -11
  792. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
  793. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +106 -14
  794. package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -4
  795. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
  796. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
  797. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +155 -92
  798. package/dist/knowledge/skills/configure-billing/SKILL.md +32 -4
  799. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +10 -0
  800. package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
  801. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
  802. package/dist/knowledge/skills/email-add-template/SKILL.md +72 -9
  803. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  804. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +135 -0
  805. package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
  806. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  807. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  808. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  809. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
  810. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +71 -14
  811. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +95 -13
  812. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +9 -1
  813. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
  814. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +44 -16
  815. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
  816. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
  817. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
  818. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +291 -22
  819. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +70 -14
  820. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +451 -0
  821. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +406 -0
  822. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +201 -0
  823. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +172 -0
  824. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
  825. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +7 -0
  826. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +63 -0
  827. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +324 -7
  828. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +95 -6
  829. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +255 -0
  830. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
  831. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
  832. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +112 -16
  833. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
  834. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +264 -0
  835. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +133 -0
  836. package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
  837. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +109 -9
  838. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +45 -0
  839. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +14 -3
  840. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
  841. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +16 -7
  842. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +29 -18
  843. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +144 -14
  844. package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
  845. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
  846. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
  847. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
  848. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
  849. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +14 -3
  850. package/dist/knowledge/skills/inbound-channels/SKILL.md +66 -8
  851. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +34 -1
  852. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +78 -6
  853. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
  854. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +434 -6
  855. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
  856. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +1 -1
  857. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +24 -13
  858. package/dist/knowledge/skills/infra-environment-config/SKILL.md +113 -3
  859. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +9 -1
  860. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -0
  861. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +294 -0
  862. package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
  863. package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
  864. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
  865. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
  866. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
  867. package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
  868. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
  869. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
  870. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
  871. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
  872. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +6 -1
  873. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +4 -2
  874. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  875. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  876. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  877. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
  878. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  879. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  880. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +20 -3
  881. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +10 -1
  882. package/dist/knowledge/skills/market-generation-cli/SKILL.md +23 -12
  883. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +13 -7
  884. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  885. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  886. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  887. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  888. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  889. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  890. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  891. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +14 -3
  892. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  893. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
  894. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
  895. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +40 -10
  896. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +57 -2
  897. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
  898. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
  899. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +176 -4
  900. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  901. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +9 -0
  902. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +81 -1
  903. package/dist/knowledge/skills/module-relationships/SKILL.md +81 -31
  904. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
  905. package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
  906. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1233 -0
  907. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
  908. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
  909. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +521 -0
  910. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +162 -0
  911. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +145 -0
  912. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  913. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
  914. package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
  915. package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
  916. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +67 -0
  917. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
  918. package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
  919. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +15 -4
  920. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
  921. package/dist/knowledge/skills/provider-backend-package/SKILL.md +138 -4
  922. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +32 -28
  923. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
  924. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +6 -0
  925. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +634 -0
  926. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +70 -0
  927. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +61 -2
  928. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
  929. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +15 -6
  930. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +9 -2
  931. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +47 -5
  932. package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
  933. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
  934. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +37 -14
  935. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
  936. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
  937. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
  938. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
  939. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
  940. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +256 -1
  941. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +81 -37
  942. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
  943. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  944. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
  945. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +167 -61
  946. package/dist/knowledge/skills/resource-add-resource/SKILL.md +63 -6
  947. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +84 -2
  948. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +137 -0
  949. package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
  950. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +131 -7
  951. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
  952. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
  953. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +25 -4
  954. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +323 -0
  955. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +23 -2
  956. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +159 -0
  957. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +162 -2
  958. package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
  959. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
  960. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  961. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +3 -2
  962. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +221 -23
  963. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +108 -2
  964. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +242 -107
  965. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +202 -17
  966. package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
  967. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  968. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +123 -56
  969. package/dist/knowledge/skills/resource-external-data/SKILL.md +280 -64
  970. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
  971. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
  972. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +73 -14
  973. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
  974. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +81 -18
  975. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +238 -49
  976. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
  977. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +145 -0
  978. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
  979. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
  980. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +61 -14
  981. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
  982. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
  983. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +39 -13
  984. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
  985. package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
  986. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +1 -1
  987. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +17 -4
  988. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
  989. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
  990. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +6 -0
  991. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +31 -1
  992. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +8 -2
  993. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +68 -5
  994. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +25 -0
  995. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +39 -9
  996. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
  997. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +571 -0
  998. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  999. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
  1000. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +87 -6
  1001. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
  1002. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +127 -12
  1003. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -4
  1004. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +50 -1
  1005. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +44 -5
  1006. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +119 -64
  1007. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
  1008. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +216 -18
  1009. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +6 -0
  1010. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  1011. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  1012. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  1013. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +185 -80
  1014. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +159 -0
  1015. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +120 -1
  1016. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
  1017. package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
  1018. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +257 -65
  1019. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
  1020. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
  1021. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +151 -1
  1022. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +144 -57
  1023. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +131 -0
  1024. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +57 -31
  1025. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +56 -0
  1026. package/dist/knowledge/skills/seeding-authoring/SKILL.md +155 -40
  1027. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  1028. package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
  1029. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +148 -4
  1030. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  1031. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
  1032. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
  1033. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +42 -11
  1034. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +183 -31
  1035. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +64 -2
  1036. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
  1037. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
  1038. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  1039. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +9 -0
  1040. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  1041. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +17 -9
  1042. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  1043. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  1044. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  1045. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +71 -14
  1046. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  1047. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  1048. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +19 -5
  1049. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +20 -6
  1050. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +20 -3
  1051. package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
  1052. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  1053. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  1054. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +226 -37
  1055. package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
  1056. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +33 -9
  1057. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +12 -3
  1058. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +17 -3
  1059. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +93 -27
  1060. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +264 -78
  1061. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1068 -192
  1062. package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
  1063. package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
  1064. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
  1065. package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
  1066. package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
  1067. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +46 -19
  1068. package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
  1069. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +18 -5
  1070. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +97 -29
  1071. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +77 -66
  1072. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +71 -24
  1073. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
  1074. package/dist/knowledge/skills/website-label-pack/SKILL.md +24 -17
  1075. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +116 -76
  1076. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +43 -14
  1077. package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
  1078. package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
  1079. package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
  1080. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +266 -371
  1081. package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
  1082. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +120 -0
  1083. package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
  1084. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -329
  1085. package/dist/knowledge/skills/website-page-authoring/SKILL.md +170 -66
  1086. package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
  1087. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +27 -3
  1088. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
  1089. package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
  1090. package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
  1091. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +54 -29
  1092. package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
  1093. package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
  1094. package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
  1095. package/dist/knowledge/skills/website-section-contact/SKILL.md +408 -185
  1096. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
  1097. package/dist/knowledge/skills/website-section-cta/SKILL.md +398 -234
  1098. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
  1099. package/dist/knowledge/skills/website-section-faq/SKILL.md +564 -300
  1100. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
  1101. package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
  1102. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +650 -272
  1103. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
  1104. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +577 -261
  1105. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
  1106. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +532 -233
  1107. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
  1108. package/dist/knowledge/skills/website-section-hero/SKILL.md +606 -330
  1109. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
  1110. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
  1111. package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
  1112. package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
  1113. package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
  1114. package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
  1115. package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
  1116. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
  1117. package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
  1118. package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
  1119. package/dist/knowledge/skills/website-section-pricing/SKILL.md +552 -376
  1120. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +77 -0
  1121. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
  1122. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +2 -1
  1123. package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
  1124. package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
  1125. package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
  1126. package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
  1127. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
  1128. package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
  1129. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
  1130. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
  1131. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
  1132. package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
  1133. package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
  1134. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +743 -309
  1135. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
  1136. package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
  1137. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
  1138. package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
  1139. package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
  1140. package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
  1141. package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
  1142. package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
  1143. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +198 -70
  1144. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +575 -57
  1145. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +17 -2
  1146. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +8 -95
  1147. package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
  1148. package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
  1149. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
  1150. package/dist/knowledge/topic-index.json +17305 -8263
  1151. package/dist/tsconfig.build.tsbuildinfo +1 -1
  1152. package/package.json +4 -4
  1153. package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
  1154. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
  1155. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
  1156. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
  1157. package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
  1158. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
  1159. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
  1160. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
  1161. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
  1162. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
  1163. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "bottom_up.placement-plan",
3
- "version": "0.1.0",
3
+ "version": "0.1.5",
4
4
  "phase": "bottom_up",
5
- "intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean) and the requirements (which tasks matter), and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches through the `settings-placement-authoring` skill. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
5
+ "intent": "Decide WHERE every settings destination, resource operation and application view sits in the application shell, and WHY. Reads the domain plan (the modules, their resources and what they mean), the requirements (which tasks matter), the customer profile (who the customers are, which decides whether an enterprise destination belongs at all) and what the creator stated about the user groups, and produces a PLACEMENT PLAN: for each subject, either a PLACED decision naming one surface (the settings hub rail, the sidebar, the user menu, the command palette) and its address on that surface, or an explicit DECLINED decision with a reason. Both carry a rationale. It also declares the GROUPS that should exist on the grouped surfaces (settings rail categories, sidebar sections) with the product purpose behind each, which is what grounds their generated labels in authored intent instead of filler. This playbook DECIDES placement; it does NOT author configuration — turning a decision into `frontend/src/config/settings-hub.config.ts` and `app-shell.config.ts` is a coding task the build lane dispatches, through the `settings-placement-authoring` skill for the settings rail and the `config-app-shell` skill for the sidebar, command palette and user menu. A sidebar group or a sidebar or palette decision may name the roles it is shown to (`requiredRoles`), when one audience only opens it. It runs BEFORE build-decompose, which consumes the plan and emits those tasks — the reverse order would be a cycle, since build-decompose is what produces the build plan. It writes no TypeScript, invents no destination refs, and authors no labels. It exists because the alternative is the framework defaulting placement, which is what made an application's settings rail unauthorable: nothing is placed implicitly, so a subject nobody decided about is a visible coverage gap rather than a silent framework default.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -17,6 +17,16 @@
17
17
  },
18
18
  {
19
19
  "family": "requirements"
20
+ },
21
+ {
22
+ "family": "market-snapshot",
23
+ "aspects": [
24
+ "market.icp",
25
+ "market.persona"
26
+ ]
27
+ },
28
+ {
29
+ "family": "vision-brief"
20
30
  }
21
31
  ],
22
32
  "outputs": [
@@ -28,7 +38,7 @@
28
38
  ],
29
39
  "stepOutputs": [],
30
40
  "method": {
31
- "guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n**Not every surface can carry every kind of subject**, and the validator refuses a\nplacement that no configuration could realise (`SUBJECT_NOT_EXPRESSIBLE_ON_SURFACE`,\na hard floor):\n\n| surface | engine destination | resource operation | application view |\n|---|---|---|---|\n| `SETTINGS_HUB` | yes | yes — as a settings section the application declares for it | **no** |\n| `USER_MENU` | yes | yes — the same application settings section, opened from the dropdown | **no** |\n| `SIDEBAR` | yes | yes | yes |\n| `COMMAND_MENU` | yes | yes | yes |\n\nThe settings rail and the user dropdown hold settings SECTIONS. A section can show a\nresource operation (a list of the team's members, say), a framework panel, or a\ncomponent the application registers; it cannot show an application view. A view\nthat people reach from settings belongs on the sidebar or the palette.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## Placing an operator surface commits the application to an AUDIENCE — say which\n\nSome subjects exist for whoever OPERATES the product rather than for the people who use it:\napplication-wide single sign-on, the application's own API keys and OAuth clients, the\nentitlement state of every tenant, the plans and prices on sale, the application-wide audit\ntrail. The framework keeps them in a separate preset scope from the end-user surfaces, and it\nkeeps them separate ON PURPOSE — an application may legitimately never render them.\n\n**So placing one is a decision about what this application IS, and the plan must state it.**\nTwo answers, both correct:\n\n- **ONE application.** Operators and users share a frontend and are told apart by their roles.\n Place the operator subjects in their own group — an `administration` category beside the\n account and organization ones — and record that this application composes BOTH preset scopes.\n- **TWO applications.** A separate operator frontend. Decline the operator subjects here, with\n that as the rationale, and they belong to the other application's plan.\n\nState the answer in the plan even when it is the obvious one, because the failure it prevents is\nsilent: an application that places operator subjects while composing only the end-user scope gets\nrail entries that OPEN AND RENDER NOTHING. An operation no composed preset surfaces is\ncallable-from-code with no interface, so the section is not missing and does not error — it is\nblank, and it reads as a slow load or a broken backend rather than as an application that was\nassembled without an audience. Seventeen sections were in exactly that state on the dogfood\napplication before this was written down.\n\nYou are not choosing the composition here — that is a coding task the build lane dispatches\nthrough `settings-placement-authoring`. You are stating WHICH audience the arrangement assumes,\nso the task that follows has something to implement rather than a default to guess.\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** The workspace-truth section lists every engine\n settings destination under **\"Settings destinations the engine ships\"**, with what each\n one shows and its role gating. That list is the whole universe: a ref outside it is an\n `UNKNOWN_SUBJECT` and the validator REFUSES the plan — a hard floor, not a warning. Rule\n on all of them where you can; a destination your plan says nothing about is reported\n undecided.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- No application view placed on the settings rail or the user dropdown.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every group has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n- The plan states which AUDIENCE it assumes — one application or two — whenever it places or\n declines an operator subject.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
41
+ "guidance": "# Placement Plan — Where Each Thing Belongs in the Shell, and Why\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\n> **This is a v1 methodology.** The criteria below are deliberately explicit so\n> they can be tuned against real runs. What is NOT provisional is the shape of the\n> output: a decision per subject, on a named surface, with a rationale.\n\n## Where you are in the journey\n\nYou run in the **bottom-up phase**, after the **domain plan** exists and **before**\nthe build is decomposed. By now the application knows what its modules and resources\nARE; what nobody has decided is **where any of it appears**.\n\nThat order matters and was corrected during authoring. Placing things *after* the\nbuild plan reads natural — you would know every task — but `bottom_up.build-decompose`\nis what PRODUCES the build plan and it consumes this one to emit the placement tasks.\nRequiring its output would be a cycle. It is also the better order on its own merits:\nplacement is a design decision that should INFORM the decomposition, not trail it. You\ndo not need the task graph to know that a `deals` resource will have a list.\n\nThat question used to have no owner. The framework shipped a placed settings rail,\nso an application could not add, remove, reorder or rename a section without the\nframework agreeing — and the application's own config file did not tell you what a\nuser would see. Placement is now the application's, which means somebody has to\ndecide it. That is this playbook.\n\n## What this playbook does\n\nYou produce a **placement plan**: for every subject, one decision per surface.\n\nA **subject** is one of three things:\n\n- an **engine settings destination**, named by its ref from the engine catalog\n (`profile`, `security`, `billing`, `sso`, …) — the engine owns what each MEANS\n (its target, its required roles, its entitlement); it owns nothing about where it\n goes;\n- a **resource operation** — a resource's LIST, its READ, a custom verb;\n- an **application view** — composite, chart, execution, full-custom.\n\nA **surface** is one of four:\n\n| surface | grouped by | authoring home |\n|---|---|---|\n| `SETTINGS_HUB` | a rail **category** | `frontend/src/config/settings-hub.config.ts` |\n| `SIDEBAR` | a sidebar **section** | `appShellConfig[SIDEBAR].contentSections` |\n| `USER_MENU` | flat | the user dropdown's settings entries |\n| `COMMAND_MENU` | flat | the command palette |\n\nA subject may legitimately be placed on **several** surfaces — billing is a settings\nrail section AND answers to the command palette. One decision per (subject, surface);\ntwo placements of one subject on ONE surface is a contradiction and the validator\nrefuses it.\n\n**Not every surface can carry every kind of subject**, and the validator refuses a\nplacement that no configuration could realise (`SUBJECT_NOT_EXPRESSIBLE_ON_SURFACE`,\na hard floor):\n\n| surface | engine destination | resource operation | application view |\n|---|---|---|---|\n| `SETTINGS_HUB` | yes | yes — as a settings section the application declares for it | **no** |\n| `USER_MENU` | yes | yes — the same application settings section, opened from the dropdown | **no** |\n| `SIDEBAR` | yes | yes | yes |\n| `COMMAND_MENU` | yes | yes | yes |\n\nThe settings rail and the user dropdown hold settings SECTIONS. A section can show a\nresource operation (a list of the team's members, say), a framework panel, or a\ncomponent the application registers; it cannot show an application view. A view\nthat people reach from settings belongs on the sidebar or the palette.\n\n## Decline explicitly; never omit\n\nEvery decision is `PLACED` or `DECLINED`, and **both require a rationale**.\n\nThis is the rule most worth getting right. A subject recorded as `DECLINED` is a\ndecision a later reader can disagree with. A subject simply missing from the plan is\na **coverage gap** — nobody looked. If those two were the same thing, \"we considered\nthe audit log and this app has no compliance audience\" would be indistinguishable\nfrom forgetting the audit log existed.\n\nSo: if a destination should not appear anywhere in this application, say so, and say\nwhy.\n\n## First: does this application need it at all? (the fit test)\n\nBefore WHERE comes WHETHER. Every engine settings destination exists in the framework; that is not\na reason to show it. A destination is placed only when something this application declared calls\nfor it:\n\n- **a requirement** that needs it (single sign-on because a requirement says customers sign in with\n their company identity);\n- **an attribute of the customer profile** in your `market-snapshot` input (the ICPs and personas:\n company size, the tools they already run, their technical staff); or\n- **a capability the application enables** (billing settings because billing is on). What is on is\n not yours to guess: the declared `application_enabled_surface` context section of your brief lists the enabled engine\n capabilities, the billing declaration and each user type's sign-in methods, read from the\n configuration. A capability it does not list is off; one it marks UNREADABLE is unknown, and you\n say so rather than treating it as off. A destination whose capability is off serves nothing yet:\n offer it only when the customer evidence asks for it, and say its capability must be switched on.\n\nOtherwise it is DECLINED, with the profile reason. One earlier run, for a 1–20 person trade firm,\ndeclined single sign-on because such a firm \"is not assumed to operate an enterprise identity\nprovider\". Another, from the same inputs, placed SSO, SCIM, SIEM export, webhooks and legal holds\nbecause \"an admin would look here\". Only the first answered the question that comes first.\n\nThe test cuts both ways. For a 2,000-person insurer whose personas name an identity team and whose\nrequirements say staff sign in with their company account, declining single sign-on would be the\nerror: there the profile and a requirement both call for it, and it is placed, with both cited. Fit\nis read from THIS application's evidence, never from a habit of declining enterprise features.\n\n**Enterprise destinations cite their evidence in the rationale.** Single sign-on, directory sync\n(SCIM), security-event export (SIEM), webhooks, legal holds, API clients and data residency are\nplaced only with the requirement, profile attribute or capability named in the rationale. \"An admin\nwould look here\" is findability, not fit; it answers a question you have not earned yet.\n\nRead who uses the product from what the creator stated (the declared `creator_stated_facts` context section of your brief):\nthe user groups and the devices they use. A field worker on a phone and an office manager at a desk\nwant different things first, and the sidebar's order should serve the group that opens it most.\n\n**When a section or an entry is for one audience only, say so with `requiredRoles`.** A sidebar group and\na sidebar or command-menu decision may carry `requiredRoles`: the role keys that see it (a field\ntechnician does not see the office's \"Invoices\" section). Use it only when the creator's user groups\nreally differ in what they open, and name the application's own roles, or core ones like `ORG_ADMIN`.\nRoles count through the role hierarchy, custom roles included: a role that inherits a listed one sees it. Absent means everyone,\nand that is the right answer for most groups. It is refused on the settings rail and the user menu,\nwhose destinations carry their own role gating.\n\nHiding is not access control: the person who cannot see \"Invoices\" can still be allowed to open it.\nIf the field technician must not read invoices, that is a role decision on the operation, not a\nplacement, and an entry for an operation a viewer cannot perform is hidden from them already. So\n`requiredRoles` is only for narrowing further: an operation everyone may use that only one group\nneeds in its navigation.\n\n## The criteria, in the order you apply them\n\n1. **Scope correctness.** A thing that acts on the whole organization does not sit\n among a person's own preferences, and the reverse. This is first because it is\n the only criterion that is objectively *wrong* rather than debatable.\n2. **Findability.** Would the user who wants this look here FIRST — unprompted?\n Not \"would they accept it once shown\". Those are different tests and only the\n first one predicts behaviour.\n3. **Grouping coherence.** Everything in a group answers one question a user\n actually asks. A group that needs \"and other things\" in its name is two groups.\n4. **Convention fit.** Users arrive with expectations already formed by comparable\n products. A novel arrangement must EARN the cost of surprising them.\n5. **Depth discipline.** One more level of nesting must buy more than it costs. A\n section reachable only after three guesses is not placed, it is hidden.\n\nReject placements justified by implementation convenience (\"it renders there\nalready\"), by the shape of the data model rather than the user's task, or by symmetry\nfor its own sake. Surfacing something everywhere is a **cost**, not thoroughness.\n\n## Groups carry a purpose, and the purpose is load-bearing\n\nWhen you declare a group, state its `purpose` in product terms. It is not decoration:\nit is what grounds the generated `settings_hub.categories.<ref>.label` and\n`sidebar_sections.<ref>.title` labels in authored intent. Without it a model invents\nfiller from the ref alone — which is exactly how a sidebar section came to be\ndescribed as \"various tools and utilities\".\n\n## A crowded settings category gets sub-categories\n\nA settings rail category can hold **sub-categories**: headings inside the category that\ngather its sections. Declare them INSIDE the category's group, as its `subGroups` (each with a\n`groupRef`, a `purpose` and an `order`), and place a section under one with `subGroupRef` on the\nsection's address (beside the `groupRef` that names the category). A sub-category's ref is scoped\nto its category, so two categories can each have a `people` sub-category.\n\nWhen to use them:\n\n- **Group a category of more than about eight sections.** Below that, a flat list is found\n faster than a heading and the list under it. Above it, people scan for a heading first.\n- **Start from the engine's proposal.** People · Billing & entitlements · Security & access ·\n Integrations · Compliance · AI is what a new application is scaffolded with, for both the\n organization and the administration categories. Using the same headings in both lets the\n same kind of surface sit under the same heading in each. Depart from it when this\n application's sections answer different questions, and say why in the purpose.\n- **Leave a category's general entries ungrouped.** The entries that name the scope itself\n (its general settings, the directory of its members' organizations) sit directly in the\n category, above the sub-categories: omit `subGroupRef` on them.\n- **One level only.** A sub-category has no sub-categories of its own; the plan cannot express\n one. Depth discipline applies: a heading inside a heading inside a category is a section\n nobody finds.\n- **A sub-category is a group, so it carries a `purpose`** like any other, and it must have\n something placed in it.\n\n## Placing an operator surface commits the application to an AUDIENCE — say which\n\nSome subjects exist for whoever OPERATES the product rather than for the people who use it:\napplication-wide single sign-on, the application's own API keys and OAuth clients, the\nentitlement state of every tenant, the plans and prices on sale, the application-wide audit\ntrail. The framework keeps them in a separate preset scope from the end-user surfaces, and it\nkeeps them separate ON PURPOSE — an application may legitimately never render them.\n\n**So placing one is a decision about what this application IS, and the plan must state it.**\nTwo answers, both correct:\n\n- **ONE application.** Operators and users share a frontend and are told apart by their roles.\n Place the operator subjects in their own group — an `administration` category beside the\n account and organization ones — and record that this application composes BOTH preset scopes.\n- **TWO applications.** A separate operator frontend. Decline the operator subjects here, with\n that as the rationale, and they belong to the other application's plan.\n\nState the answer in the plan even when it is the obvious one, because the failure it prevents is\nsilent: an application that places operator subjects while composing only the end-user scope gets\nrail entries that OPEN AND RENDER NOTHING. An operation no composed preset surfaces is\ncallable-from-code with no interface, so the section is not missing and does not error — it is\nblank, and it reads as a slow load or a broken backend rather than as an application that was\nassembled without an audience. Seventeen sections were in exactly that state on the dogfood\napplication before this was written down.\n\nYou are not choosing the composition here — that is a coding task the build lane dispatches\nthrough `settings-placement-authoring`. You are stating WHICH audience the arrangement assumes,\nso the task that follows has something to implement rather than a default to guess.\n\n## What you do NOT do\n\n- **You do not author configuration.** Turning a decision into\n `settings-hub.config.ts` or `app-shell.config.ts` is a coding task the build lane\n dispatches through the `settings-placement-authoring` skill. If you catch yourself\n writing a config key, a file path or a label string, stop.\n- **You do not invent destination refs.** The workspace-truth section lists every engine\n settings destination under **\"Settings destinations the engine ships\"**, with what each\n one shows and its role gating. That list is the whole universe: a ref outside it is an\n `UNKNOWN_SUBJECT` and the validator REFUSES the plan — a hard floor, not a warning. Rule\n on all of them where you can; a destination your plan says nothing about is reported\n undecided.\n- **You do not decide what a destination MEANS.** Its target, roles and entitlement\n are the engine's. You decide only where it sits.\n- **You do not re-open the build plan.** What is being built is settled.\n\n## Verification\n\n- Every subject the workspace offers is either PLACED or DECLINED — nothing omitted.\n- No subject placed twice on one surface.\n- No application view placed on the settings rail or the user dropdown.\n- Every grouped placement names a group this plan declares, for that same surface.\n- Every `subGroupRef` names a sub-category this plan declares under that placement's category.\n- Sub-categories are declared only on `SETTINGS_HUB` categories, each ref once per category.\n- Every group, sub-categories included, has something in it.\n- Every decision, both arms, carries a rationale that would satisfy a reader who\n disagrees with it.\n- The plan states which AUDIENCE it assumes — one application or two — whenever it places or\n declines an operator subject.\n\n## WHO decides — a panel, not you alone and not the creator\n\n**The creator does not choose placement.** This playbook convenes an expert panel and\ntakes its winner.\n\nConcretely, on every run: three candidate arrangements are generated independently\nagainst this brief, each schema-valid before anyone sees it and each told to take a\ngenuinely different position; the **information-architect** derives the rubric (it\nowns the domain); it and the **design-system-guardian** review every candidate; the\nguardian coordinates, shortlists, and synthesises a winner. What lands is that winner.\n\nTwo consequences for how you write:\n\n- **Take a position and commit to it.** You are one candidate among three, and the\n panel cannot compare three hedged arrangements. State what your arrangement makes\n WORSE — an arrangement with no cost has not been thought about, and the reviewers\n are instructed to notice.\n- **The rationale on each decision is the durable part.** It is what a creator asking\n \"why is Billing under Organization?\" reads, and it is the only trace of the argument\n once the winner has landed.\n\n**Fail-closed on charters.** Every panel role needs a committed charter, and the\ncompanion indexes agents at startup — a charter accepted after boot has no agent until\na restart, and the error says exactly that. The run does NOT quietly degrade to a\nsingle generation: an artifact carrying a panel's authority over a decision no panel\nsaw is the worst outcome available here, so fewer than two usable candidates returns\nto the ordinary retry instead.\n\n## And when the placement is wrong\n\nTwo different things can change, and conflating them is how a plan starts lying.\n\n**The config file** — `settings-hub.config.ts`, `app-shell.config.ts` — is what actually\nrenders. A creator who disagrees edits it directly. That works today, needs no companion,\nand is a git commit, which is the accepted state.\n\n**The plan** is the decision record, and it is what a later reader consults to ask why.\nIt can be changed two ways:\n\n- **Re-run this playbook.** The panel deliberates again and the landing REPLACES the\n existing file. Nothing refuses it; that is the design.\n- **Edit the landed plan.** It is an application-owned source like any other.\n\nEither way, a decision that no longer reflects the panel must say so. Set its `origin`\nto `REVISED` and record what the panel had decided in `supersedes.rationale`. Both are\nrequired together — the schema refuses a `REVISED` decision with nothing superseded, and\nrefuses a `DELIBERATED` one that supersedes something, because no panel run produces\neither shape.\n\n**Why the artifact carries this when git already records the change.** Git knows who\nchanged the line, when, and with what message, and that is not being duplicated here. What\ngit cannot tell someone READING the file — in an editor, asking \"why is Billing under\nAccount?\" — is that this particular decision is no longer the panel's. Without it, the\n`rationale` field goes on asserting panel reasoning for a decision the panel never took,\nand there is no way to notice.\n\nDo not paraphrase the panel's rationale into the new one. A `supersedes.rationale` that\nrepeats the decision's own text word for word satisfies the schema and tells a reader\nnothing; the validator reports it as an authoring warning.\n",
32
42
  "skillRefs": [
33
43
  "settings-placement-authoring",
34
44
  "config-app-shell",
@@ -36,7 +46,9 @@
36
46
  ],
37
47
  "skillBodyRefs": [],
38
48
  "contextSources": [
39
- "workspace_truth"
49
+ "workspace_truth",
50
+ "creator_stated_facts",
51
+ "application_enabled_surface"
40
52
  ],
41
53
  "draftableDocumentDefinitionRefs": [],
42
54
  "suspendsForClarification": false,
@@ -35,21 +35,40 @@ plan landed while it was needed is set aside for every reader if the composition
35
35
  `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not
36
36
  plan a site the application will never compose — the pages would become tasks with nowhere to write.
37
37
 
38
- ## Step 2 — Decide the pages, from what the product actually declares
38
+ ## Step 2 — Decide the pages and their KINDS, from what the product actually declares
39
39
 
40
- A page exists because something the application declared needs a place to be said. Derive first,
41
- and invent nothing:
40
+ Every page has a **kind**, and the kind decides what you no longer have to: its route
41
+ (`/product/<slug>`, `/solutions/<slug>`, `/pricing`, …), its place in the site menu, and the sections
42
+ it cannot do without. You never name a route or a menu position — they are derived.
42
43
 
43
- | page | exists when |
44
- |---|---|
45
- | the landing page | always — it is the origin every canonical URL derives from |
46
- | a pricing page | the business model declares pricing plans |
47
- | a features page | the market snapshot carries benefits worth arguing one at a time |
48
- | a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |
44
+ | kind | exists when | route |
45
+ |---|---|---|
46
+ | `HOME` | always, exactly one; its slug is `landing` (the scaffold's starter page, which the home page grows) | `/` |
47
+ | `PRODUCT` | one per product AREA the application actually ships and the snapshot argues for — a capability a visitor would look up by name | `/product/<slug>` |
48
+ | `PRODUCT_OVERVIEW` | three or more PRODUCT pages (the validator asks for it from three on), or one page for a single-area product | `/product` |
49
+ | `SOLUTION` | one per audience the snapshot positions separately — an ICP, a role, an industry or a use case with its own pains and proofs | `/solutions/<slug>` |
50
+ | `PRICING` | the business model declares pricing plans | `/pricing` |
51
+ | `CONTACT` | the audience buys through a conversation (an inbound channel, a legal-entity ICP) | `/contact` |
52
+ | `COMPANY` | the snapshot or brand carries a story about who builds the product and why | `/about` |
53
+ | `TRUST` | the application has controls a buyer's security review asks about — where data is stored, how people sign in, what is recorded, how long what is kept, the rights a person can exercise | `/security` |
54
+ | `BLOG` | the application publishes posts (the blog adapter: one MDX file per post, per locale) | `/blog` |
55
+
56
+ **Product page or solution page?** A product page answers *what does it do* — one area of the BUILT
57
+ product: what it is, how it works, what it changes. A solution page answers *how does it solve MY
58
+ problem* — the product seen from one audience: their problem first, in their words, then how the
59
+ product answers it, with proof from people like them. A SOLUTION page carries a `solutionAxis` —
60
+ `ROLE`, `INDUSTRY`, `USE_CASE` or `COMPANY_SIZE` — which groups the Solutions menu; name it the way
61
+ the visitor names themselves. Solutions are secondary to the product: never plan solution pages
62
+ instead of product pages.
63
+
64
+ **Ground product pages in the built product.** A PRODUCT page about a capability the application
65
+ does not ship is a promise on the page buyers read most. Plan one per area the application's modules
66
+ deliver; if the market snapshot argues for something the product does not do yet, it is not a page.
49
67
 
50
68
  Each page names the ICPs it is **written for** and the tone of voice it speaks in, both by their
51
69
  market-snapshot refs. A page written for everybody is written for nobody: the positioning the
52
- market pass produced is per ICP, and a page that names none cannot use it.
70
+ market pass produced is per ICP, and a page that names none cannot use it. A SOLUTION page names
71
+ exactly the audience it is for.
53
72
 
54
73
  ## Step 3 — Compose each page's sections, in reading order
55
74
 
@@ -67,16 +86,154 @@ argues from there. The section kinds are closed, and each one names the skill th
67
86
  | `CTA` | a call to action inside the page's flow |
68
87
  | `FOOTER_CTA` | the closing call to action |
69
88
  | `CONTACT` | a way to reach a human |
89
+ | `PROBLEM` | the audience's pain, in their words, before the product appears — a solution page's opening argument |
90
+ | `HOW_IT_WORKS` | three or four steps the built product performs |
91
+ | `PRODUCT_SHOWCASE` | the real product shown: a framed screen, a bento of key screens, tabs across its views |
92
+ | `SOLUTION_PATHS` | one card per solution page, routing each audience to the page written for it |
93
+ | `COMPARISON` | the product against the alternatives the snapshot names, honestly |
94
+ | `STATS` | facts about the product as figures — each one a value the application declares |
95
+ | `INTEGRATIONS` | the systems the product connects to, each one a provider, channel or protocol it declares |
96
+ | `LATEST_POSTS` | the blog's newest posts, read from their own frontmatter |
97
+ | `ROADMAP` | what has shipped, what is next, what comes later — nothing unbuilt shown as available |
98
+
99
+ Each kind has essentials the validator reports when missing: a product page shows how the product
100
+ works (HOW_IT_WORKS / FEATURE_DETAIL / PRODUCT_SHOWCASE) and offers a next step (FOOTER_CTA / CTA); a
101
+ solution page opens on its PROBLEM, then argues (FEATURE_DETAIL / HOW_IT_WORKS /
102
+ FEATURE_BENEFIT_SUMMARY) and offers a next step; the home page shows the product and offers a next
103
+ step; pricing carries PRICING, contact CONTACT; a security page describes its controls (FEATURE_DETAIL /
104
+ FEATURE_BENEFIT_SUMMARY / STATS); the blog page carries LATEST_POSTS. A LATEST_POSTS section anywhere else
105
+ (the home page's "from the blog") needs a BLOG page in the same plan, because the posts live in the blog's
106
+ content collection: a plan that lists posts and has no blog is refused.
107
+
108
+ **The home page reads as modern when the product is on it, early.** Open on the HERO, show the
109
+ product next (a PRODUCT_SHOWCASE, unless the hero itself carries the product visual), name the
110
+ problem when the audience does not yet know it has one, then how it works, the one or two benefits
111
+ that score highest, a SOLUTION_PATHS section once there are two or more solution pages, proof,
112
+ objections, and the closing call to action. Vary the section kinds — five benefit grids in a row read
113
+ as filler — and keep it to about eight sections.
114
+
115
+ **A solution page** reads: HERO ("For <audience>"), PROBLEM, FEATURE_DETAIL × 2–3 (each answering a
116
+ pain) or HOW_IT_WORKS, COMPARISON against what this audience uses today when the snapshot names it,
117
+ SOCIAL_PROOF from people in this audience, FAQ, FOOTER_CTA.
118
+
119
+ **A product page** reads: HERO, HOW_IT_WORKS or PRODUCT_SHOWCASE, FEATURE_DETAIL × 2–3, SOCIAL_PROOF,
120
+ FAQ, FOOTER_CTA.
121
+
122
+ **A security page** reads: HERO, FEATURE_BENEFIT_SUMMARY (the controls at a glance), FEATURE_DETAIL × 2–3 (sign-in,
123
+ data rights, the retention schedule as a table), STATS when the controls have figures, FAQ, FOOTER_CTA. It states
124
+ what the product DOES; a certification the application does not hold is not on it, not even as "in progress".
70
125
 
71
126
  **Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,
72
127
  objection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a
73
128
  claim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is
74
129
  a section somebody invented, and the validator reports a page where no section names anything.
75
130
 
131
+ **A section that says what the product DOES names the requirement behind it** (`backedByRequirementRefs`).
132
+ A market benefit says what a buyer wants; it does not say the product delivers it. An earlier site
133
+ promised "country workflow guidance with its limits stated", drawn from a benefit, while the product
134
+ shipped an empty page for an administrator to write guidance into.
135
+
136
+ - Every section whose kind says what the product does (`FEATURE_DETAIL`, `FEATURE_BENEFIT_SUMMARY`,
137
+ `PRODUCT_SHOWCASE`, `HOW_IT_WORKS`, `COMPARISON` and `INTEGRATIONS`) cites the requirements (functional, or
138
+ non-functional such as working on a phone in the field), by their refs in your `requirements` input,
139
+ that commit the product to what it describes. The validator reports one that cites none. An
140
+ INTEGRATIONS section cites the requirement each connection serves as well as naming the provider the
141
+ integration plan declares: the declaration says the provider is planned, the requirement's standing
142
+ says whether the build delivered it.
143
+ - Any other section (a hero, an FAQ, a pricing table, the solution paths) may cite requirements too, and
144
+ should when its copy will say what the product does. A section that cites none describes no capability
145
+ as available.
146
+ - A citation is necessary, not sufficient. When the section is built, its author is told where each
147
+ cited requirement stands: delivered, still being built, reported unmet by the run that built it, or
148
+ only on a later roadmap phase. Only what is delivered is written as available; the rest is written as
149
+ planned. So cite what the section is ABOUT, and do not drop a requirement because it is not built yet.
150
+ - A benefit no requirement backs is not presented as a capability: leave it out, or give it a section
151
+ whose purpose says it is planned.
152
+
76
153
  Lead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano
77
154
  category; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones
78
155
  the model finds most interesting.
79
156
 
157
+ ## Step 4 — Every claim on the site is something the application already says
158
+
159
+ A site generated from a product's own specifications can do what a hand-written one cannot: make every sentence
160
+ checkable. Hold the plan to it, because the coding agent will write exactly what the section's purpose asks for.
161
+
162
+ The brief carries what the application declares about itself, beside the market material: the roadmap (built now,
163
+ next, later), the requirements, the document facts (what it keeps and for how long, who receives what and where, the
164
+ rights it honours) and the integration plan, each when it has landed. A section's purpose names which of them it
165
+ states. When none of them backs a claim the market snapshot makes, the claim belongs on the roadmap or nowhere; when
166
+ the family a section would state from has not landed yet, plan the section to state less, not to guess.
167
+
168
+ - **A capability** is on a page only when the application PERFORMS it for the people the site is addressed to; a
169
+ declared phase that is not built goes on a ROADMAP section in the horizon the roadmap gives it. Four near-misses
170
+ read like capabilities and are not:
171
+ - a STORED SETTING is not a behaviour: a resource that records a policy (reminder rules, an escalation policy, a
172
+ snooze date) does nothing until something reads it, so the page may not say the product reminds, escalates or
173
+ hides anything;
174
+ - the OPERATOR's integration is not the customer's: a system of record the application reads its own business rows
175
+ from is not something a customer connects;
176
+ - an integration needs its deployment: a provider with no credential in the environment the site describes (a
177
+ sign-in client, an app registration) is not offered there;
178
+ - a gate belongs to one surface: an approval declared on an assistant's tool does not govern the same operation
179
+ reached over MCP or the API. Say which surface asks, never that every surface does.
180
+ - **A figure** (STATS, a hero note, an FAQ answer) is a value the application declares: a retention period, the
181
+ length of an exposed list, a storage region, the number of locales.
182
+ - **Where data lives** is the primary store's region AND every vendor-hosted service the application declares a
183
+ compliance choice for (`providerComplianceChoices`), each with its region. "All customer data in <region>" is
184
+ true only when every one of them is in it; otherwise the page names the services that are not. The same rule holds
185
+ for a security control: state what the configuration REQUIRES (a policy for a user type, a role), never "always"
186
+ for something a person may switch on. Write the section's purpose so it names the
187
+ declaration ("the audit trail's retention period from the retention schedule"). A customer count, a rating, an
188
+ uptime or "x% faster" is not a figure this lane can source, and is never planned.
189
+ - **A name** (INTEGRATIONS, a COMPARISON column) is a provider, channel or protocol the application declares, or an
190
+ alternative the market snapshot names.
191
+ - **A quote** (SOCIAL_PROOF) comes from the snapshot's proofs with its source; a testimonial nobody gave is never
192
+ planned, however natural the page would look with one.
193
+
194
+ ## Step 5 — Show the product, drawn faithfully and moving
195
+
196
+ A modern site is read as a product when the product is on it. Plan PRODUCT_SHOWCASE (and FEATURE_DETAIL sections
197
+ with a visual) as DRAWN demos of the real interface, and say in the section's purpose which screen and which
198
+ moment: the screen the product is used from, and the moment it exists for (an item reaching done, a request being
199
+ approved, a record arriving from outside). The coding agent draws them from the application's own resources (their
200
+ real fields, statuses and enum values) and animates them as a short state timeline in the engine's demo frame
201
+ (`website-section-product-showcase`, `website-motion-design`). The last state is the still frame, which the server,
202
+ reduced motion and a STILL site show; a paused demo holds the moment it is on. Plan breadth, not repetition: across
203
+ the site, show each product area once in motion, not the same list five times.
204
+
205
+ Write that decision into the section's `demo`: its `archetype` (what happens: items APPEND, an APPROVAL, a
206
+ QUERY_ANSWER, a TRANSFORM, a CONNECT, COMPLETE_ITEMS, a STATUS_LIFECYCLE, a DASHBOARD filling in, a CELEBRATE), the
207
+ `resourceRef` it is drawn from (the resource's ref in the domain plan, so the drawing is bound to that resource's real
208
+ fields and values; for a status demo, the states its lifecycle declares), and the `moment` in one sentence. A ref the
209
+ domain plan does not declare is noted, and the build cannot bind the drawing to it. A demo goes only on a section whose block may hold a drawing (a hero, a feature row, a
210
+ product tour, a bento, or a block of the site's own); a product showcase or feature detail drawn with one and planned without a demo is reported.
211
+
212
+ **A drawing is a claim too**, and Step 4 governs it like a sentence. It draws only what the application shows: no
213
+ field the operation cannot change, no "before" value a screen does not render, no count or meter the resource does not
214
+ carry, no screen the application does not have (an operation reachable only through the API or an assistant is drawn
215
+ there, not as a screen of its own).
216
+
217
+ ## Step 6 — Design each section in the engine's blocks
218
+
219
+ The site's design is decided here, once, so every section task builds what the plan names instead of each choosing
220
+ its own. Each section carries:
221
+
222
+ - `component`: the block that builds it, among those its kind allows. A FAQ is a FAQ block, a hero a hero; a
223
+ benefits summary is a card grid or a bento; a product showcase a product tour, a bento or a card grid; social proof
224
+ quotation cards or a marquee. Leave it out to take the kind's usual block. `SITE_BLOCK`, a block of the site's own, is open only to the
225
+ kinds whose skill teaches one (a problem stated once, area cards with moving drawings, a logo band, a contact
226
+ layout), and its purpose says why no engine block fits.
227
+ - `variant`, when the block has named layouts: a hero's STAGE (the product below the copy, for the home page's
228
+ opening), SPLIT (beside it) or COMPACT (no visual); a feature row's side, alternated down the page so rows
229
+ zig-zag; a card grid's columns; steps in a row or a stack; a FAQ's intro beside or above. A variant belongs to one
230
+ block, and the plan refuses one given to another.
231
+ - `tone`, the surface it stands on, where the surface carries meaning: the page's turning points and its numbers on
232
+ INVERSE, its close on INVERSE, at most one BRAND band a page. Leave the rest out; the build alternates them.
233
+
234
+ Each page names its `signatureSectionRef`: the one section a visitor remembers the page by, usually its richest
235
+ drawing. The build gives it the most care. It must be one of the page's own sections.
236
+
80
237
  ## Refine, don't re-author
81
238
 
82
239
  Your own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks
@@ -86,13 +243,28 @@ do not renumber.
86
243
  ## What you emit
87
244
 
88
245
  - The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its
89
- rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered
90
- sections.
246
+ rationale, and the pages, each with its kind (and a SOLUTION page's axis), purpose, audience, tone,
247
+ signature section and ordered sections, each section with its design (block, layout, surface, demo). Routes and
248
+ menu placement are derived from the kinds; do not author them.
91
249
 
92
250
  ## Verification
93
251
 
94
252
  - Every `drawsOnRefs` entry names an entry that exists in the market snapshot.
95
- - Every page opens on a `HERO`, and exactly one page reads as the landing page.
253
+ - Exactly one page is `HOME`, with the slug `landing`; every page opens on a `HERO`.
254
+ - Every PRODUCT page names an area the application ships; every SOLUTION page names its audience and
255
+ its `solutionAxis`, and opens its argument on a `PROBLEM`.
256
+ - Every section that says what the product does (`FEATURE_DETAIL`, `FEATURE_BENEFIT_SUMMARY`, `PRODUCT_SHOWCASE`,
257
+ `HOW_IT_WORKS`, `COMPARISON`, `INTEGRATIONS`) names at least one `backedByRequirementRefs` entry, and each names a
258
+ requirement in the requirements.
259
+ - Every STATS, INTEGRATIONS and ROADMAP section's purpose names the declaration its figures, names or stages come
260
+ from; no section plans a customer count, a rating or a testimonial the snapshot does not carry.
261
+ - No kind's essentials are missing (the validator reports them by page).
262
+ - Every section's `component` is one its kind allows and every `variant` shapes that component (the plan refuses
263
+ either otherwise); every product showcase or feature detail drawn with a picture has a `demo`; no page stands
264
+ more than one section on BRAND; every page's `signatureSectionRef` names one of its own sections.
265
+ - Every section ref is unique across the SITE, not only within its page: the build collects every section by
266
+ its ref, so name each after its page (`landing-hero`, `pricing-hero`). Every page opens on a HERO, so two
267
+ pages always need two names; the plan refuses a ref declared on two pages.
96
268
  - `rg -n "sectionRef" specifications/src/website-plan/index.ts | wc -l` — the number of website
97
269
  section tasks the build lane will emit.
98
270
 
@@ -108,7 +280,8 @@ page the build lane cannot author.
108
280
  The others below are the contracts the CODING AGENT opens when it builds each task, listed so a
109
281
  reader knows the plan's decisions land somewhere:
110
282
 
111
- - `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.
283
+ - `website-navigation-authoring` — the site menu each page joins (Product and Solutions panels, direct links), derived from the kinds you plan. Its top level is at most six entries, in a fixed order: product, solutions, pricing, blog, company, contact.
284
+ - `website-motion-design` — the site's motion vocabulary; the home page's one signature entrance is the hero's.
112
285
  - `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.
113
286
  - `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.
114
287
  - `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "bottom_up.website-plan",
3
- "version": "0.2.0",
3
+ "version": "0.5.1",
4
4
  "phase": "bottom_up",
5
- "intent": "Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has, what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Runs only once the capability composition decides the website is NEEDED (a declined website is never planned, and a plan landed before a later decline is set aside). A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.",
5
+ "intent": "Website plan — decide WHAT THE MARKETING WEBSITE SAYS for this application: which pages it has and the KIND of each (home, product overview, product area, solution by role / industry / use case / company size, pricing, contact, company, security, blog — the kind derives its route, its menu placement and its essential sections), what each page is for and who it is written for, and the sections that carry each page's argument in reading order, each drawing on the market entries the top-down lane authored (benefits, proofs, objections, jobs, pains, ICPs, tones of voice). Runs only once the capability composition decides the website is NEEDED (a declined website is never planned, and a plan landed before a later decline is set aside). A section's KIND (hero, benefits summary, benefit in detail, pricing, proof, objections answered, call to action, closing call to action, contact, the problem, how it works, the product shown, paths by audience, comparison, facts in figures, integrations, latest posts, roadmap) names the shipped `website-section-*` skill that authors it, so the build lane can bind each emitted task to its skill without a model naming folders. Every capability, figure and name the plan asks a section to state must be one the application declares (its roadmap, requirements, document facts and integration plan), never a claim the marketing material makes alone. Produces the plan; `bottom_up.build-decompose` turns it into the page and section tasks a coding agent runs, and the `add-website` composition scenario is what creates the `website/` workspace they write in.",
6
6
  "preconditions": [
7
7
  {
8
8
  "kind": "artifact_exists",
@@ -42,6 +42,25 @@
42
42
  {
43
43
  "family": "vision-brief"
44
44
  },
45
+ {
46
+ "family": "roadmap"
47
+ },
48
+ {
49
+ "family": "requirements"
50
+ },
51
+ {
52
+ "family": "document-facts"
53
+ },
54
+ {
55
+ "family": "domain-plan",
56
+ "aspects": [
57
+ "domain-plan.resource",
58
+ "domain-plan.lifecycle"
59
+ ]
60
+ },
61
+ {
62
+ "family": "integration-plan"
63
+ },
45
64
  {
46
65
  "family": "website-plan"
47
66
  }
@@ -55,10 +74,11 @@
55
74
  ],
56
75
  "stepOutputs": [],
57
76
  "method": {
58
- "guidance": "# Website Plan — What the Marketing Site Says\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## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision. This playbook runs only once the composition decides it is\n**NEEDED**: its eligibility is gated on that decision, so a declined website is never planned, and a\nplan landed while it was needed is set aside for every reader if the composition later declines it.\n\n- **Needed** (the normal case): `disposition: PLANNED`, and continue.\n- **Declined** in the record you are given (it changed after you were started): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not\n plan a site the application will never compose — the pages would become tasks with nowhere to write.\n\n## Step 2 — Decide the pages, from what the product actually declares\n\nA page exists because something the application declared needs a place to be said. Derive first,\nand invent nothing:\n\n| page | exists when |\n|---|---|\n| the landing page | always — it is the origin every canonical URL derives from |\n| a pricing page | the business model declares pricing plans |\n| a features page | the market snapshot carries benefits worth arguing one at a time |\n| a contact page | the product's audience buys through a conversation (an inbound channel, a legal-entity ICP) |\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages in navigation order, each with its purpose, audience, tone and ordered\n sections.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Every page opens on a `HERO`, and exactly one page reads as the landing page.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — how pages reach each other, which bounds how many top-level pages are worth planning.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
77
+ "guidance": "# Website Plan — What the Marketing Site Says\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## Where you are in the journey\n\nThe top-down lane has produced a market snapshot — ICPs, jobs, pains, gains, benefits with their\nweighting, positioning per ICP, tones of voice, proofs and objections — and a brand. The capability\ncomposition has decided whether this application has a marketing website. You decide **what that\nsite says**: its pages, and the sections that carry each page's argument.\n\nYou do not write the site. `bottom_up.build-decompose` turns each page and each section into a\nbuild task, and a coding agent authors it against the shipped `website-*` skills. The `website/`\nworkspace itself is composed by the `add-website` scenario, which the foundation applies from the\nsame capability composition you read here.\n\n## Step 1 — Read the capability composition FIRST\n\nFind the `add-website` decision. This playbook runs only once the composition decides it is\n**NEEDED**: its eligibility is gated on that decision, so a declined website is never planned, and a\nplan landed while it was needed is set aside for every reader if the composition later declines it.\n\n- **Needed** (the normal case): `disposition: PLANNED`, and continue.\n- **Declined** in the record you are given (it changed after you were started): land a plan with\n `disposition: NOT_APPLICABLE`, no pages, and a `rationale` naming what the composition said. Do not\n plan a site the application will never compose — the pages would become tasks with nowhere to write.\n\n## Step 2 — Decide the pages and their KINDS, from what the product actually declares\n\nEvery page has a **kind**, and the kind decides what you no longer have to: its route\n(`/product/<slug>`, `/solutions/<slug>`, `/pricing`, …), its place in the site menu, and the sections\nit cannot do without. You never name a route or a menu position — they are derived.\n\n| kind | exists when | route |\n|---|---|---|\n| `HOME` | always, exactly one; its slug is `landing` (the scaffold's starter page, which the home page grows) | `/` |\n| `PRODUCT` | one per product AREA the application actually ships and the snapshot argues for — a capability a visitor would look up by name | `/product/<slug>` |\n| `PRODUCT_OVERVIEW` | three or more PRODUCT pages (the validator asks for it from three on), or one page for a single-area product | `/product` |\n| `SOLUTION` | one per audience the snapshot positions separately — an ICP, a role, an industry or a use case with its own pains and proofs | `/solutions/<slug>` |\n| `PRICING` | the business model declares pricing plans | `/pricing` |\n| `CONTACT` | the audience buys through a conversation (an inbound channel, a legal-entity ICP) | `/contact` |\n| `COMPANY` | the snapshot or brand carries a story about who builds the product and why | `/about` |\n| `TRUST` | the application has controls a buyer's security review asks about — where data is stored, how people sign in, what is recorded, how long what is kept, the rights a person can exercise | `/security` |\n| `BLOG` | the application publishes posts (the blog adapter: one MDX file per post, per locale) | `/blog` |\n\n**Product page or solution page?** A product page answers *what does it do* — one area of the BUILT\nproduct: what it is, how it works, what it changes. A solution page answers *how does it solve MY\nproblem* — the product seen from one audience: their problem first, in their words, then how the\nproduct answers it, with proof from people like them. A SOLUTION page carries a `solutionAxis` —\n`ROLE`, `INDUSTRY`, `USE_CASE` or `COMPANY_SIZE` — which groups the Solutions menu; name it the way\nthe visitor names themselves. Solutions are secondary to the product: never plan solution pages\ninstead of product pages.\n\n**Ground product pages in the built product.** A PRODUCT page about a capability the application\ndoes not ship is a promise on the page buyers read most. Plan one per area the application's modules\ndeliver; if the market snapshot argues for something the product does not do yet, it is not a page.\n\nEach page names the ICPs it is **written for** and the tone of voice it speaks in, both by their\nmarket-snapshot refs. A page written for everybody is written for nobody: the positioning the\nmarket pass produced is per ICP, and a page that names none cannot use it. A SOLUTION page names\nexactly the audience it is for.\n\n## Step 3 — Compose each page's sections, in reading order\n\nOrder is the plan's substance. A page opens on a **HERO** — the promise, before any detail — and\nargues from there. The section kinds are closed, and each one names the skill that authors it:\n\n| kind | what it does |\n|---|---|\n| `HERO` | the opening promise: headline, sub-headline, primary call to action |\n| `FEATURE_BENEFIT_SUMMARY` | the benefits in one line each, for a reader who will not read the detail |\n| `FEATURE_DETAIL` | one benefit argued: the job it advances, the pain it relieves, what the product does |\n| `PRICING` | the plans, as the business model declares them |\n| `SOCIAL_PROOF` | the proofs the market pass authored |\n| `FAQ` | the objections, answered |\n| `CTA` | a call to action inside the page's flow |\n| `FOOTER_CTA` | the closing call to action |\n| `CONTACT` | a way to reach a human |\n| `PROBLEM` | the audience's pain, in their words, before the product appears — a solution page's opening argument |\n| `HOW_IT_WORKS` | three or four steps the built product performs |\n| `PRODUCT_SHOWCASE` | the real product shown: a framed screen, a bento of key screens, tabs across its views |\n| `SOLUTION_PATHS` | one card per solution page, routing each audience to the page written for it |\n| `COMPARISON` | the product against the alternatives the snapshot names, honestly |\n| `STATS` | facts about the product as figures — each one a value the application declares |\n| `INTEGRATIONS` | the systems the product connects to, each one a provider, channel or protocol it declares |\n| `LATEST_POSTS` | the blog's newest posts, read from their own frontmatter |\n| `ROADMAP` | what has shipped, what is next, what comes later — nothing unbuilt shown as available |\n\nEach kind has essentials the validator reports when missing: a product page shows how the product\nworks (HOW_IT_WORKS / FEATURE_DETAIL / PRODUCT_SHOWCASE) and offers a next step (FOOTER_CTA / CTA); a\nsolution page opens on its PROBLEM, then argues (FEATURE_DETAIL / HOW_IT_WORKS /\nFEATURE_BENEFIT_SUMMARY) and offers a next step; the home page shows the product and offers a next\nstep; pricing carries PRICING, contact CONTACT; a security page describes its controls (FEATURE_DETAIL /\nFEATURE_BENEFIT_SUMMARY / STATS); the blog page carries LATEST_POSTS. A LATEST_POSTS section anywhere else\n(the home page's \"from the blog\") needs a BLOG page in the same plan, because the posts live in the blog's\ncontent collection: a plan that lists posts and has no blog is refused.\n\n**The home page reads as modern when the product is on it, early.** Open on the HERO, show the\nproduct next (a PRODUCT_SHOWCASE, unless the hero itself carries the product visual), name the\nproblem when the audience does not yet know it has one, then how it works, the one or two benefits\nthat score highest, a SOLUTION_PATHS section once there are two or more solution pages, proof,\nobjections, and the closing call to action. Vary the section kinds — five benefit grids in a row read\nas filler — and keep it to about eight sections.\n\n**A solution page** reads: HERO (\"For <audience>\"), PROBLEM, FEATURE_DETAIL × 2–3 (each answering a\npain) or HOW_IT_WORKS, COMPARISON against what this audience uses today when the snapshot names it,\nSOCIAL_PROOF from people in this audience, FAQ, FOOTER_CTA.\n\n**A product page** reads: HERO, HOW_IT_WORKS or PRODUCT_SHOWCASE, FEATURE_DETAIL × 2–3, SOCIAL_PROOF,\nFAQ, FOOTER_CTA.\n\n**A security page** reads: HERO, FEATURE_BENEFIT_SUMMARY (the controls at a glance), FEATURE_DETAIL × 2–3 (sign-in,\ndata rights, the retention schedule as a table), STATS when the controls have figures, FAQ, FOOTER_CTA. It states\nwhat the product DOES; a certification the application does not hold is not on it, not even as \"in progress\".\n\n**Every section names the market entries it draws on** (`drawsOnRefs`) — the benefit, proof,\nobjection, job, pain, ICP or tone refs, exactly as the snapshot authored them. That is what makes a\nclaim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is\na section somebody invented, and the validator reports a page where no section names anything.\n\n**A section that says what the product DOES names the requirement behind it** (`backedByRequirementRefs`).\nA market benefit says what a buyer wants; it does not say the product delivers it. An earlier site\npromised \"country workflow guidance with its limits stated\", drawn from a benefit, while the product\nshipped an empty page for an administrator to write guidance into.\n\n- Every section whose kind says what the product does (`FEATURE_DETAIL`, `FEATURE_BENEFIT_SUMMARY`,\n `PRODUCT_SHOWCASE`, `HOW_IT_WORKS`, `COMPARISON` and `INTEGRATIONS`) cites the requirements (functional, or\n non-functional such as working on a phone in the field), by their refs in your `requirements` input,\n that commit the product to what it describes. The validator reports one that cites none. An\n INTEGRATIONS section cites the requirement each connection serves as well as naming the provider the\n integration plan declares: the declaration says the provider is planned, the requirement's standing\n says whether the build delivered it.\n- Any other section (a hero, an FAQ, a pricing table, the solution paths) may cite requirements too, and\n should when its copy will say what the product does. A section that cites none describes no capability\n as available.\n- A citation is necessary, not sufficient. When the section is built, its author is told where each\n cited requirement stands: delivered, still being built, reported unmet by the run that built it, or\n only on a later roadmap phase. Only what is delivered is written as available; the rest is written as\n planned. So cite what the section is ABOUT, and do not drop a requirement because it is not built yet.\n- A benefit no requirement backs is not presented as a capability: leave it out, or give it a section\n whose purpose says it is planned.\n\nLead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano\ncategory; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones\nthe model finds most interesting.\n\n## Step 4 — Every claim on the site is something the application already says\n\nA site generated from a product's own specifications can do what a hand-written one cannot: make every sentence\ncheckable. Hold the plan to it, because the coding agent will write exactly what the section's purpose asks for.\n\nThe brief carries what the application declares about itself, beside the market material: the roadmap (built now,\nnext, later), the requirements, the document facts (what it keeps and for how long, who receives what and where, the\nrights it honours) and the integration plan, each when it has landed. A section's purpose names which of them it\nstates. When none of them backs a claim the market snapshot makes, the claim belongs on the roadmap or nowhere; when\nthe family a section would state from has not landed yet, plan the section to state less, not to guess.\n\n- **A capability** is on a page only when the application PERFORMS it for the people the site is addressed to; a\n declared phase that is not built goes on a ROADMAP section in the horizon the roadmap gives it. Four near-misses\n read like capabilities and are not:\n - a STORED SETTING is not a behaviour: a resource that records a policy (reminder rules, an escalation policy, a\n snooze date) does nothing until something reads it, so the page may not say the product reminds, escalates or\n hides anything;\n - the OPERATOR's integration is not the customer's: a system of record the application reads its own business rows\n from is not something a customer connects;\n - an integration needs its deployment: a provider with no credential in the environment the site describes (a\n sign-in client, an app registration) is not offered there;\n - a gate belongs to one surface: an approval declared on an assistant's tool does not govern the same operation\n reached over MCP or the API. Say which surface asks, never that every surface does.\n- **A figure** (STATS, a hero note, an FAQ answer) is a value the application declares: a retention period, the\n length of an exposed list, a storage region, the number of locales.\n- **Where data lives** is the primary store's region AND every vendor-hosted service the application declares a\n compliance choice for (`providerComplianceChoices`), each with its region. \"All customer data in <region>\" is\n true only when every one of them is in it; otherwise the page names the services that are not. The same rule holds\n for a security control: state what the configuration REQUIRES (a policy for a user type, a role), never \"always\"\n for something a person may switch on. Write the section's purpose so it names the\n declaration (\"the audit trail's retention period from the retention schedule\"). A customer count, a rating, an\n uptime or \"x% faster\" is not a figure this lane can source, and is never planned.\n- **A name** (INTEGRATIONS, a COMPARISON column) is a provider, channel or protocol the application declares, or an\n alternative the market snapshot names.\n- **A quote** (SOCIAL_PROOF) comes from the snapshot's proofs with its source; a testimonial nobody gave is never\n planned, however natural the page would look with one.\n\n## Step 5 — Show the product, drawn faithfully and moving\n\nA modern site is read as a product when the product is on it. Plan PRODUCT_SHOWCASE (and FEATURE_DETAIL sections\nwith a visual) as DRAWN demos of the real interface, and say in the section's purpose which screen and which\nmoment: the screen the product is used from, and the moment it exists for (an item reaching done, a request being\napproved, a record arriving from outside). The coding agent draws them from the application's own resources (their\nreal fields, statuses and enum values) and animates them as a short state timeline in the engine's demo frame\n(`website-section-product-showcase`, `website-motion-design`). The last state is the still frame, which the server,\nreduced motion and a STILL site show; a paused demo holds the moment it is on. Plan breadth, not repetition: across\nthe site, show each product area once in motion, not the same list five times.\n\nWrite that decision into the section's `demo`: its `archetype` (what happens: items APPEND, an APPROVAL, a\nQUERY_ANSWER, a TRANSFORM, a CONNECT, COMPLETE_ITEMS, a STATUS_LIFECYCLE, a DASHBOARD filling in, a CELEBRATE), the\n`resourceRef` it is drawn from (the resource's ref in the domain plan, so the drawing is bound to that resource's real\nfields and values; for a status demo, the states its lifecycle declares), and the `moment` in one sentence. A ref the\ndomain plan does not declare is noted, and the build cannot bind the drawing to it. A demo goes only on a section whose block may hold a drawing (a hero, a feature row, a\nproduct tour, a bento, or a block of the site's own); a product showcase or feature detail drawn with one and planned without a demo is reported.\n\n**A drawing is a claim too**, and Step 4 governs it like a sentence. It draws only what the application shows: no\nfield the operation cannot change, no \"before\" value a screen does not render, no count or meter the resource does not\ncarry, no screen the application does not have (an operation reachable only through the API or an assistant is drawn\nthere, not as a screen of its own).\n\n## Step 6 — Design each section in the engine's blocks\n\nThe site's design is decided here, once, so every section task builds what the plan names instead of each choosing\nits own. Each section carries:\n\n- `component`: the block that builds it, among those its kind allows. A FAQ is a FAQ block, a hero a hero; a\n benefits summary is a card grid or a bento; a product showcase a product tour, a bento or a card grid; social proof\n quotation cards or a marquee. Leave it out to take the kind's usual block. `SITE_BLOCK`, a block of the site's own, is open only to the\n kinds whose skill teaches one (a problem stated once, area cards with moving drawings, a logo band, a contact\n layout), and its purpose says why no engine block fits.\n- `variant`, when the block has named layouts: a hero's STAGE (the product below the copy, for the home page's\n opening), SPLIT (beside it) or COMPACT (no visual); a feature row's side, alternated down the page so rows\n zig-zag; a card grid's columns; steps in a row or a stack; a FAQ's intro beside or above. A variant belongs to one\n block, and the plan refuses one given to another.\n- `tone`, the surface it stands on, where the surface carries meaning: the page's turning points and its numbers on\n INVERSE, its close on INVERSE, at most one BRAND band a page. Leave the rest out; the build alternates them.\n\nEach page names its `signatureSectionRef`: the one section a visitor remembers the page by, usually its richest\ndrawing. The build gives it the most care. It must be one of the page's own sections.\n\n## Refine, don't re-author\n\nYour own prior plan is an input. Keep every page ref that still has a reason to exist — build tasks\nname them, and a ref that moves orphans the task that produced its page. Add, sharpen and reorder;\ndo not renumber.\n\n## What you emit\n\n- The **website plan** at `specifications/src/website-plan/index.ts` — a disposition with its\n rationale, and the pages, each with its kind (and a SOLUTION page's axis), purpose, audience, tone,\n signature section and ordered sections, each section with its design (block, layout, surface, demo). Routes and\n menu placement are derived from the kinds; do not author them.\n\n## Verification\n\n- Every `drawsOnRefs` entry names an entry that exists in the market snapshot.\n- Exactly one page is `HOME`, with the slug `landing`; every page opens on a `HERO`.\n- Every PRODUCT page names an area the application ships; every SOLUTION page names its audience and\n its `solutionAxis`, and opens its argument on a `PROBLEM`.\n- Every section that says what the product does (`FEATURE_DETAIL`, `FEATURE_BENEFIT_SUMMARY`, `PRODUCT_SHOWCASE`,\n `HOW_IT_WORKS`, `COMPARISON`, `INTEGRATIONS`) names at least one `backedByRequirementRefs` entry, and each names a\n requirement in the requirements.\n- Every STATS, INTEGRATIONS and ROADMAP section's purpose names the declaration its figures, names or stages come\n from; no section plans a customer count, a rating or a testimonial the snapshot does not carry.\n- No kind's essentials are missing (the validator reports them by page).\n- Every section's `component` is one its kind allows and every `variant` shapes that component (the plan refuses\n either otherwise); every product showcase or feature detail drawn with a picture has a `demo`; no page stands\n more than one section on BRAND; every page's `signatureSectionRef` names one of its own sections.\n- Every section ref is unique across the SITE, not only within its page: the build collects every section by\n its ref, so name each after its page (`landing-hero`, `pricing-hero`). Every page opens on a HERO, so two\n pages always need two names; the plan refuses a ref declared on two pages.\n- `rg -n \"sectionRef\" specifications/src/website-plan/index.ts | wc -l` — the number of website\n section tasks the build lane will emit.\n\n## References — named by REF, because this step cannot open a file\n\nA structured generation has no filesystem: naming a path here would be an instruction answered from\nrecollection (#1435). So each skill is named by its REF, and only `website-page-authoring` reaches\nthis step as a BODY (`method.skillBodyRefs`) — it is the one contract the plan must not contradict,\nbecause it says what a page IS in this engine: a manifest, a route adapter, a sections file and a\nlabel pack that fails the build closed on a missing key. A page planned against anything else is a\npage the build lane cannot author.\n\nThe others below are the contracts the CODING AGENT opens when it builds each task, listed so a\nreader knows the plan's decisions land somewhere:\n\n- `website-navigation-authoring` — the site menu each page joins (Product and Solutions panels, direct links), derived from the kinds you plan. Its top level is at most six entries, in a fixed order: product, solutions, pricing, blog, company, contact.\n- `website-motion-design` — the site's motion vocabulary; the home page's one signature entrance is the hero's.\n- `website-seo-aeo-geo` — what a page owes a search engine and an answer engine.\n- `website-label-pack` — every string a section renders is a label key, and the build fails closed on a missing one.\n- `website-marketing-metadata-extension` — the metadata a page carries beyond its sections.\n- `website-section-*` — one per section KIND, bound to the emitted task by `WEBSITE_SECTION_SKILL_REF`.\n- `market-positioning-authoring`, `market-tone-of-voice`, `market-proof-and-objection` — the market\n vocabularies a section draws on, which arrive here as the market snapshot itself rather than as prose.\n",
59
78
  "skillRefs": [
60
79
  "website-page-authoring",
61
80
  "website-navigation-authoring",
81
+ "website-motion-design",
62
82
  "website-seo-aeo-geo",
63
83
  "website-label-pack",
64
84
  "website-marketing-metadata-extension",
@@ -26,8 +26,9 @@ Each child re-derives one whole family for the application. They come in two kin
26
26
  the roadmap, the brand; the domain, experience, integration, website and documentation plans, and the build
27
27
  plan (`bottom_up.build-decompose`).
28
28
  - **What can only be refreshed**, re-derived from its inputs when a refinement made it stale: the placement
29
- plan, the capability composition, the business model, the risk register, the document facts and the
30
- governed documents.
29
+ plan, the capability composition, the business model, the risk register, the document facts, the
30
+ governed documents, and the expert staffing (`top_down.expert-personas`), which staffs a panel role whose
31
+ inputs the refinement has just landed and leaves every committed charter alone.
31
32
  - **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to
32
33
  the coding agent. A long lane with its own rounds.
33
34
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "cross_cutting.refinement",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "phase": "cross_cutting",
5
5
  "intent": "Refine what this line was opened for: re-derive each named family from what it already holds, guided by the purpose, then refresh what that made out of date and build it. An umbrella: it authors nothing itself. The first move is fixed: the producers of the named families. After that, select only children whose outputs are STALE, upstream before downstream, the build last. STOP when nothing is stale any more and the build has run, or when nothing eligible advances the refinement.",
6
6
  "preconditions": [
@@ -39,7 +39,7 @@
39
39
  "outputs": [],
40
40
  "stepOutputs": [],
41
41
  "method": {
42
- "guidance": "# The refinement line — 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 refines what the line was opened for (see \"What this run is for\",\nwhich names the purpose and the families to refine), beside the application's main line. A refinement\nre-derives a family the application ALREADY holds, from what it already says: keep what still holds, change\nwhat the purpose asks, and do not re-author the rest.\n\n## The children\n\nEach child re-derives one whole family for the application. They come in two kinds:\n\n- **What can be refined** (what the line may name), each from its own prior output: the vision, the\n requirements, the feature drafts, the value proposition and the capability map (both refine the market),\n the roadmap, the brand; the domain, experience, integration, website and documentation plans, and the build\n plan (`bottom_up.build-decompose`).\n- **What can only be refreshed**, re-derived from its inputs when a refinement made it stale: the placement\n plan, the capability composition, the business model, the risk register, the document facts and the\n governed documents.\n- **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to\n the coding agent. A long lane with its own rounds.\n\n## Choosing\n\n- **The first rounds are fixed.** While a family this line names has not been re-derived, you are offered\n only its producers, upstream ones first. Pass the purpose on in the child's objective, in the person's\n terms: it is what the refinement must change.\n- **Then refresh what the change made stale, and nothing else.** Each eligible child shows the outputs that\n are stale and the inputs they wait on. Refresh a family only when it is stale, and its own stale inputs\n first: the requirements before the domain plan, the domain plan before the experience plan, a plan before\n the build plan.\n- **Build last**, once the plans the change touched are current.\n- **Stop** when nothing is stale any more and the build has run, or when no eligible child advances the\n refinement. Do not re-run a named family's producer to \"improve\" it further: a further refinement is a new\n run of this line, asked for by the person who opened it.\n",
42
+ "guidance": "# The refinement line — 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 refines what the line was opened for (see \"What this run is for\",\nwhich names the purpose and the families to refine), beside the application's main line. A refinement\nre-derives a family the application ALREADY holds, from what it already says: keep what still holds, change\nwhat the purpose asks, and do not re-author the rest.\n\n## The children\n\nEach child re-derives one whole family for the application. They come in two kinds:\n\n- **What can be refined** (what the line may name), each from its own prior output: the vision, the\n requirements, the feature drafts, the value proposition and the capability map (both refine the market),\n the roadmap, the brand; the domain, experience, integration, website and documentation plans, and the build\n plan (`bottom_up.build-decompose`).\n- **What can only be refreshed**, re-derived from its inputs when a refinement made it stale: the placement\n plan, the capability composition, the business model, the risk register, the document facts, the\n governed documents, and the expert staffing (`top_down.expert-personas`), which staffs a panel role whose\n inputs the refinement has just landed and leaves every committed charter alone.\n- **`bottom_up.build`** — the build lane: it decomposes the changed plan into tasks and dispatches them to\n the coding agent. A long lane with its own rounds.\n\n## Choosing\n\n- **The first rounds are fixed.** While a family this line names has not been re-derived, you are offered\n only its producers, upstream ones first. Pass the purpose on in the child's objective, in the person's\n terms: it is what the refinement must change.\n- **Then refresh what the change made stale, and nothing else.** Each eligible child shows the outputs that\n are stale and the inputs they wait on. Refresh a family only when it is stale, and its own stale inputs\n first: the requirements before the domain plan, the domain plan before the experience plan, a plan before\n the build plan.\n- **Build last**, once the plans the change touched are current.\n- **Stop** when nothing is stale any more and the build has run, or when no eligible child advances the\n refinement. Do not re-run a named family's producer to \"improve\" it further: a further refinement is a new\n run of this line, asked for by the person who opened it.\n",
43
43
  "skillRefs": [],
44
44
  "skillBodyRefs": [],
45
45
  "contextSources": [],
@@ -60,6 +60,8 @@
60
60
  "refinement.document-facts",
61
61
  "top_down.compliance-conception",
62
62
  "top_down.risk-register",
63
+ "top_down.service-method",
64
+ "top_down.expert-personas",
63
65
  "top_down.business-model",
64
66
  "top_down.brand-identity",
65
67
  "top_down.scope-roadmap",
@@ -88,6 +90,8 @@
88
90
  "refinement.document-facts",
89
91
  "top_down.compliance-conception",
90
92
  "top_down.risk-register",
93
+ "top_down.service-method",
94
+ "top_down.expert-personas",
91
95
  "top_down.business-model",
92
96
  "top_down.brand-identity",
93
97
  "top_down.scope-roadmap",