@wildo-ai/framework-knowledge 1.1.9 → 1.1.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (376) 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/expert-personas-and-deliberations.md +26 -7
  5. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +4 -2
  6. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +9 -3
  8. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  9. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  10. package/dist/esm/framework-knowledge.definitions.js +84 -4
  11. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  12. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  13. package/dist/esm/index.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  17. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +39 -1
  20. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +132 -20
  22. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
  25. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
  27. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  29. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +85 -8
  31. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
  33. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
  35. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  37. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  39. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
  41. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
  43. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  45. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  47. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  49. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  50. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  51. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
  52. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  53. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  55. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +2 -2
  56. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  57. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +10 -4
  58. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +2 -1
  60. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  61. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +5 -3
  62. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  63. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +2 -1
  64. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  65. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +11 -9
  66. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  67. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +17 -3
  68. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  69. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +19 -2
  70. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  71. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  72. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  75. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
  80. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  81. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
  82. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  83. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  88. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  89. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
  90. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +38 -3
  93. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  95. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  97. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  99. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  101. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -0
  103. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  104. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  105. package/dist/knowledge/manifest.json +7 -7
  106. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +1 -1
  107. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  108. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  109. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +149 -11
  110. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +40 -2
  111. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +55 -0
  112. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
  113. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +10 -2
  114. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  115. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  116. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +107 -11
  117. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -2
  118. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
  119. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
  120. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
  121. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  122. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
  123. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
  124. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +2 -1
  125. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  126. package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
  127. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
  128. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  129. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  130. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  131. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  132. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +7 -3
  133. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +3 -3
  134. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +56 -16
  135. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +6 -4
  136. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  137. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  138. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +30 -9
  139. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +5 -3
  140. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +12 -1
  141. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  142. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  143. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
  144. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  145. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  146. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  147. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  148. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  149. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
  150. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  151. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  152. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -1
  153. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  154. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  155. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  156. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  157. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +19 -0
  158. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +19 -1
  159. package/dist/knowledge/references/brand.name-choice.config.md +20 -3
  160. package/dist/knowledge/references/brand.name-screening.config.md +58 -3
  161. package/dist/knowledge/references/build-plan.task-graph.config.md +55 -0
  162. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  163. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  164. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  165. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
  166. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  167. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
  168. package/dist/knowledge/references/example.data-seeding.minimal.md +10 -9
  169. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  170. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  171. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  172. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  173. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  174. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  175. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  176. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
  177. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  178. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  179. package/dist/knowledge/references/experience-plan.config.md +60 -7
  180. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  181. package/dist/knowledge/references/placement-plan.config.md +43 -0
  182. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  183. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  184. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  185. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  186. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  187. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  188. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  189. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  190. package/dist/knowledge/references/saas.backend.email.send.md +77 -0
  191. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  192. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  193. package/dist/knowledge/references/saas.data-seeding.definition-input.md +8 -2
  194. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  195. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
  196. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
  197. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
  198. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
  199. package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
  200. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
  201. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
  202. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  203. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
  204. package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
  205. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
  206. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
  207. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  208. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  209. package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
  210. package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
  211. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  212. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  213. package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
  214. package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
  215. package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
  216. package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
  217. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  218. package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
  219. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  220. package/dist/knowledge/references/website-plan.config.md +26 -0
  221. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
  222. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
  223. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  224. package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
  225. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
  226. package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
  227. package/dist/knowledge/references/zod.factories.code.md +1 -0
  228. package/dist/knowledge/references/zod.factories.duration.md +1 -0
  229. package/dist/knowledge/references/zod.factories.money.md +1 -0
  230. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  231. package/dist/knowledge/registries/framework-topics.json +337 -1
  232. package/dist/knowledge/registries/playbooks.json +18 -18
  233. package/dist/knowledge/registries/source-tags.json +1435 -873
  234. package/dist/knowledge/rules/live-context-door.md +1 -1
  235. package/dist/knowledge/skills/INDEX.md +3 -1
  236. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  237. package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
  238. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  239. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  240. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  241. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
  242. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
  243. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  244. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
  245. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
  246. package/dist/knowledge/skills/brand-name-screening/SKILL.md +33 -9
  247. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +78 -6
  248. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +30 -8
  249. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +2 -1
  250. package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
  251. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
  252. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
  253. package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
  254. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  255. package/dist/knowledge/skills/config-saas/SKILL.md +25 -11
  256. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +51 -1
  257. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
  258. package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
  259. package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
  260. package/dist/knowledge/skills/email-add-template/SKILL.md +27 -5
  261. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  262. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
  263. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  264. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  265. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  266. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
  267. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
  268. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
  269. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
  270. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
  271. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +18 -4
  272. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
  273. package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
  274. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +6 -1
  275. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  276. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  277. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  278. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  279. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  280. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -3
  281. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +1 -1
  282. package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
  283. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
  284. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  285. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  286. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  287. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  288. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  289. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  290. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  291. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +14 -3
  292. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  293. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
  294. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  295. package/dist/knowledge/skills/module-relationships/SKILL.md +31 -4
  296. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  297. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
  298. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
  299. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
  300. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
  301. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  302. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
  303. package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
  304. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
  305. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
  306. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
  307. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
  308. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
  309. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  310. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
  311. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
  312. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  313. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
  314. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
  315. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
  316. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
  317. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
  318. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  319. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
  320. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
  321. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
  322. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
  323. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  324. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  325. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  326. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
  327. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
  328. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
  329. package/dist/knowledge/skills/seeding-authoring/SKILL.md +155 -40
  330. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  331. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +148 -4
  332. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  333. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
  334. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
  335. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  336. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  337. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
  338. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  339. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  340. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  341. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  342. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  343. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  344. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
  345. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  346. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  347. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
  348. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
  349. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
  350. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
  351. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
  352. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
  353. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
  354. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
  355. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +10 -2
  356. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
  357. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
  358. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
  359. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
  360. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
  361. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
  362. package/dist/knowledge/skills/website-page-authoring/SKILL.md +16 -5
  363. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
  364. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
  365. package/dist/knowledge/skills/website-section-faq/SKILL.md +6 -1
  366. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +6 -1
  367. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +10 -2
  368. package/dist/knowledge/skills/website-section-hero/SKILL.md +6 -1
  369. package/dist/knowledge/skills/website-section-pricing/SKILL.md +6 -1
  370. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +12 -2
  371. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +15 -3
  372. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
  373. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
  374. package/dist/knowledge/topic-index.json +1441 -269
  375. package/dist/tsconfig.build.tsbuildinfo +1 -1
  376. package/package.json +4 -4
@@ -91,6 +91,56 @@ from forgetting the audit log existed.
91
91
  So: if a destination should not appear anywhere in this application, say so, and say
92
92
  why.
93
93
 
94
+ ## First: does this application need it at all? (the fit test)
95
+
96
+ Before WHERE comes WHETHER. Every engine settings destination exists in the framework; that is not
97
+ a reason to show it. A destination is placed only when something this application declared calls
98
+ for it:
99
+
100
+ - **a requirement** that needs it (single sign-on because a requirement says customers sign in with
101
+ their company identity);
102
+ - **an attribute of the customer profile** in your `market-snapshot` input (the ICPs and personas:
103
+ company size, the tools they already run, their technical staff); or
104
+ - **a capability the application enables** (billing settings because billing is on). What is on is
105
+ not yours to guess: the declared `application_enabled_surface` context section of your brief lists the enabled engine
106
+ capabilities, the billing declaration and each user type's sign-in methods, read from the
107
+ configuration. A capability it does not list is off; one it marks UNREADABLE is unknown, and you
108
+ say so rather than treating it as off. A destination whose capability is off serves nothing yet:
109
+ offer it only when the customer evidence asks for it, and say its capability must be switched on.
110
+
111
+ Otherwise it is DECLINED, with the profile reason. One earlier run, for a 1–20 person trade firm,
112
+ declined single sign-on because such a firm "is not assumed to operate an enterprise identity
113
+ provider". Another, from the same inputs, placed SSO, SCIM, SIEM export, webhooks and legal holds
114
+ because "an admin would look here". Only the first answered the question that comes first.
115
+
116
+ The test cuts both ways. For a 2,000-person insurer whose personas name an identity team and whose
117
+ requirements say staff sign in with their company account, declining single sign-on would be the
118
+ error: there the profile and a requirement both call for it, and it is placed, with both cited. Fit
119
+ is read from THIS application's evidence, never from a habit of declining enterprise features.
120
+
121
+ **Enterprise destinations cite their evidence in the rationale.** Single sign-on, directory sync
122
+ (SCIM), security-event export (SIEM), webhooks, legal holds, API clients and data residency are
123
+ placed only with the requirement, profile attribute or capability named in the rationale. "An admin
124
+ would look here" is findability, not fit; it answers a question you have not earned yet.
125
+
126
+ Read who uses the product from what the creator stated (the declared `creator_stated_facts` context section of your brief):
127
+ the user groups and the devices they use. A field worker on a phone and an office manager at a desk
128
+ want different things first, and the sidebar's order should serve the group that opens it most.
129
+
130
+ **When a section or an entry is for one audience only, say so with `visibleToRoles`.** A sidebar group and
131
+ a sidebar or command-menu decision may carry `visibleToRoles`: the role keys that see it (a field
132
+ technician does not see the office's "Invoices" section). Use it only when the creator's user groups
133
+ really differ in what they open, and name the application's own roles, or core ones like `ORG_ADMIN`.
134
+ A custom role counts only as itself, so list every role that should see it. Absent means everyone,
135
+ and that is the right answer for most groups. It is refused on the settings rail and the user menu,
136
+ whose destinations carry their own role gating.
137
+
138
+ Hiding is not access control: the person who cannot see "Invoices" can still be allowed to open it.
139
+ If the field technician must not read invoices, that is a role decision on the operation, not a
140
+ placement, and an entry for an operation a viewer cannot perform is hidden from them already. So
141
+ `visibleToRoles` is only for narrowing further: an operation everyone may use that only one group
142
+ needs in its navigation.
143
+
94
144
  ## The criteria, in the order you apply them
95
145
 
96
146
  1. **Scope correctness.** A thing that acts on the whole organization does not sit
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "ref": "bottom_up.placement-plan",
3
- "version": "0.1.0",
3
+ "version": "0.1.4",
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 (`visibleToRoles`), 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 `visibleToRoles`.** A sidebar group and\na sidebar or command-menu decision may carry `visibleToRoles`: 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`.\nA custom role counts only as itself, so list every role that should see 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`visibleToRoles` 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## 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",
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,
@@ -73,6 +73,23 @@ objection, job, pain, ICP or tone refs, exactly as the snapshot authored them. T
73
73
  claim checkable: a reader opens the snapshot and finds the entry. A section that draws on nothing is
74
74
  a section somebody invented, and the validator reports a page where no section names anything.
75
75
 
76
+ **A section that says what the product DOES names the requirement behind it** (`backedByRequirementRefs`).
77
+ A market benefit says what a buyer wants; it does not say the product delivers it. An earlier site
78
+ promised "country workflow guidance with its limits stated", drawn from a benefit, while the product
79
+ shipped an empty page for an administrator to write guidance into.
80
+
81
+ - Every `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section cites the requirements (functional, or
82
+ non-functional such as working on a phone in the field), by their refs in your `requirements` input,
83
+ that commit the product to what it describes. The validator reports one that cites none.
84
+ - Any other section (a hero, an FAQ, a pricing table) may cite requirements too, and should when its
85
+ copy will say what the product does. A section that cites none describes no capability as available.
86
+ - A citation is necessary, not sufficient. When the section is built, its author is told where each
87
+ cited requirement stands: delivered, still being built, reported unmet by the run that built it, or
88
+ only on a later roadmap phase. Only what is delivered is written as available; the rest is written as
89
+ planned. So cite what the section is ABOUT, and do not drop a requirement because it is not built yet.
90
+ - A benefit no requirement backs is not presented as a capability: leave it out, or give it a section
91
+ whose purpose says it is planned.
92
+
76
93
  Lead with fit. The brief carries the computed fit matrix beside each benefit's authored Kano
77
94
  category; a page for an ICP argues the benefits that score for THAT ICP first, rather than the ones
78
95
  the model finds most interesting.
@@ -92,6 +109,8 @@ do not renumber.
92
109
  ## Verification
93
110
 
94
111
  - Every `drawsOnRefs` entry names an entry that exists in the market snapshot.
112
+ - Every `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section names at least one `backedByRequirementRefs`
113
+ entry, and each names a requirement in the requirements.
95
114
  - Every page opens on a `HERO`, and exactly one page reads as the landing page.
96
115
  - `rg -n "sectionRef" specifications/src/website-plan/index.ts | wc -l` — the number of website
97
116
  section tasks the build lane will emit.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "ref": "bottom_up.website-plan",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "phase": "bottom_up",
5
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.",
6
6
  "preconditions": [
@@ -42,6 +42,9 @@
42
42
  {
43
43
  "family": "vision-brief"
44
44
  },
45
+ {
46
+ "family": "requirements"
47
+ },
45
48
  {
46
49
  "family": "website-plan"
47
50
  }
@@ -55,7 +58,7 @@
55
58
  ],
56
59
  "stepOutputs": [],
57
60
  "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",
61
+ "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\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 `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section 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.\n- Any other section (a hero, an FAQ, a pricing table) may cite requirements too, and should when its\n copy will say what the product does. A section that cites none describes no capability 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## 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 `FEATURE_DETAIL` and `FEATURE_BENEFIT_SUMMARY` section names at least one `backedByRequirementRefs`\n entry, and each names a requirement in the requirements.\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",
59
62
  "skillRefs": [
60
63
  "website-page-authoring",
61
64
  "website-navigation-authoring",
@@ -390,7 +390,8 @@ cannot say what an erasure does to them. Where the facts also report a category
390
390
  origin, say what IS established alongside it.
391
391
  `NEEDS_CONFIGURATION` for every resource that does not.
392
392
 
393
- **What closes it** — the application's own authors declaring `retentionPolicy` on the resource. Name
393
+ **What closes it** — the application's own authors declaring `retentionPolicy`, with the `dataSubjectPolicy` the
394
+ factory requires beside it, on the resource. Name
394
395
  the resources individually: the remedy is per-resource, and a count is not actionable.
395
396
 
396
397