@wildo-ai/framework-knowledge 1.1.7 → 1.1.9

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 (226) hide show
  1. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
  3. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
  5. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +29 -5
  6. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
  8. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
  9. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
  10. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
  11. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
  12. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +11 -1
  13. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  14. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  15. package/dist/esm/framework-knowledge.definitions.js +11 -1
  16. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  17. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  18. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  19. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
  21. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
  23. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -3
  25. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +59 -10
  27. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  29. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
  30. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  32. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +1 -1
  35. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  37. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +5 -5
  39. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
  41. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
  43. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
  45. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +85 -43
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +40 -0
  49. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
  50. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +41 -0
  51. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
  52. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +199 -0
  53. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
  54. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +201 -0
  55. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
  56. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +67 -0
  57. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
  58. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +76 -0
  59. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
  60. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
  61. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
  63. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
  65. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
  67. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
  69. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
  71. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
  73. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
  75. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
  77. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
  79. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
  81. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +36 -2
  83. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
  85. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
  87. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
  89. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
  91. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
  93. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +30 -17
  95. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  96. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  97. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  98. package/dist/knowledge/manifest.json +8 -8
  99. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
  100. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  101. package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
  102. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
  103. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  104. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  105. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +117 -28
  106. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +4 -4
  107. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +133 -59
  108. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  109. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
  110. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
  111. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
  112. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
  113. package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
  114. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +2 -2
  115. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  116. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  117. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +22 -6
  118. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -3
  119. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
  120. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +5 -2
  121. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  122. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  123. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  124. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +71 -37
  125. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
  126. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +105 -0
  127. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +55 -0
  128. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
  129. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
  130. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +78 -0
  131. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +63 -0
  132. package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
  133. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +65 -0
  134. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  135. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  136. package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
  137. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
  138. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
  139. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
  140. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
  141. package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
  142. package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
  143. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  144. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  145. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
  146. package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
  147. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
  148. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
  149. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +10 -0
  150. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +40 -17
  151. package/dist/knowledge/references/brand.name-choice.config.md +127 -0
  152. package/dist/knowledge/references/brand.name-screening.config.md +253 -0
  153. package/dist/knowledge/references/build-plan.task-graph.config.md +64 -11
  154. package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
  155. package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
  156. package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
  157. package/dist/knowledge/references/capability-composition.config.md +67 -4
  158. package/dist/knowledge/references/example.data-seeding.minimal.md +29 -1
  159. package/dist/knowledge/references/market.snapshot.validation.md +1 -1
  160. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
  161. package/dist/knowledge/references/saas.data-seeding.definition-input.md +6 -0
  162. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
  163. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
  164. package/dist/knowledge/references/saas.website.astro.label-loader.md +9 -0
  165. package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
  166. package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
  167. package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
  168. package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
  169. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  170. package/dist/knowledge/registries/framework-topics.json +38 -1
  171. package/dist/knowledge/registries/playbooks.json +68 -20
  172. package/dist/knowledge/registries/source-tags.json +748 -695
  173. package/dist/knowledge/rules/live-context-door.md +5 -2
  174. package/dist/knowledge/skills/INDEX.md +2 -1
  175. package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -1
  176. package/dist/knowledge/skills/brand-name-screening/SKILL.md +154 -0
  177. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +394 -0
  178. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +65 -0
  179. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +5 -2
  180. package/dist/knowledge/skills/config-saas/SKILL.md +31 -4
  181. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +14 -1
  182. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
  183. package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
  184. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
  185. package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
  186. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +11 -1
  187. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
  188. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
  189. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
  190. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -1
  191. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +11 -1
  192. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  193. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -1
  194. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
  195. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
  196. package/dist/knowledge/skills/module-relationships/SKILL.md +6 -4
  197. package/dist/knowledge/skills/seeding-authoring/SKILL.md +51 -3
  198. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +6 -0
  199. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
  200. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
  201. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -0
  202. package/dist/knowledge/skills/website-page-authoring/SKILL.md +84 -3
  203. package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
  204. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
  205. package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
  206. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
  207. package/dist/knowledge/skills/website-section-faq/SKILL.md +15 -0
  208. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
  209. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +15 -0
  210. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
  211. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +15 -0
  212. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
  213. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
  214. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
  215. package/dist/knowledge/skills/website-section-hero/SKILL.md +27 -9
  216. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
  217. package/dist/knowledge/skills/website-section-pricing/SKILL.md +15 -0
  218. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
  219. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +15 -0
  220. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
  221. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +1 -1
  222. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
  223. package/dist/knowledge/topic-index.json +169 -43
  224. package/dist/tsconfig.build.tsbuildinfo +1 -1
  225. package/dist/tsconfig.tsbuildinfo +1 -1
  226. package/package.json +4 -4
@@ -114,12 +114,28 @@ export enum CompositionBasis {
114
114
  */
115
115
  INTEGRATION_PLAN_OWNS_WORKERS_AND_MINIONS = 'INTEGRATION_PLAN_OWNS_WORKERS_AND_MINIONS',
116
116
  /**
117
- * The application's configuration declares the languages it serves (`appPreferences.languages`), and
118
- * that decides whether its website is published in more than one locale. A HOST fact rather than a
119
- * family: no specification family declares languages, and the configuration already does, so asking
120
- * anyone would re-state it.
117
+ * The application's configuration declares MORE THAN ONE language (`appPreferences.languages`), so its
118
+ * website is published in a locale for each beyond the primary. A HOST fact rather than a family: no
119
+ * specification family declares languages, and the configuration already does, so asking anyone would
120
+ * re-state it.
121
+ *
122
+ * A NEED basis only. A one-language configuration implies no second locale, and that is
123
+ * {@link CompositionBasis.NO_DECLARATION_IMPLIES_IT} — the configuration was read and implies nothing.
124
+ * Until 2026-10-01 the derivation used this basis for both answers, and the validator refused every
125
+ * one-language application on its first run.
121
126
  */
122
127
  APPLICATION_CONFIG_DECLARES_LANGUAGES = 'APPLICATION_CONFIG_DECLARES_LANGUAGES',
128
+ /**
129
+ * The market snapshot targets countries (a CORE or EXPANSION ICP's geographies) whose languages the
130
+ * application's configuration does not serve, so the website needs a locale for each — named in the
131
+ * decision's detail. Derived by `measureMarketLanguageCoverage`, never asked: both halves are typed
132
+ * declarations (ISO country codes on the ICPs, `appPreferences.languages` in the configuration).
133
+ *
134
+ * Takes precedence over {@link CompositionBasis.APPLICATION_CONFIG_DECLARES_LANGUAGES} when both hold,
135
+ * because it is the one that names a gap: the configuration and the market disagree, and the coherence
136
+ * report says so as well.
137
+ */
138
+ MARKET_TARGETS_UNSERVED_LANGUAGES = 'MARKET_TARGETS_UNSERVED_LANGUAGES',
123
139
  /**
124
140
  * An optional LAYOUT library (the 3D layout, #1827) is the operator's opt-in. Nothing in a product definition
125
141
  * decides a rendering style: most applications are 2D, and one becomes 3D because its operator composes it —
@@ -132,6 +148,44 @@ export enum CompositionBasis {
132
148
  NO_DECLARATION_DECIDES_IT = 'NO_DECLARATION_DECIDES_IT',
133
149
  }
134
150
 
151
+ /**
152
+ * The ONE disposition each basis can justify. Total over {@link CompositionBasis}, so a basis added
153
+ * tomorrow does not compile until somebody says which disposition it supports.
154
+ *
155
+ * A basis is a REASON, and a reason points one way: "the domain plan owns modules" cannot justify
156
+ * NEEDED, "no declaration implies it" cannot justify NEEDED, "the market declares an inbound web
157
+ * channel" cannot justify DECLINED. `validateCapabilityComposition` refuses any decision whose basis
158
+ * this table maps elsewhere, and the derivation's constructors are typed by {@link CompositionBasisFor},
159
+ * so the producer cannot even write the pairing the validator refuses.
160
+ *
161
+ * It exists because the pairing used to live in the validator only, as two hand-kept sets, while the
162
+ * derivation wrote whatever pair it chose. On 2026-10-01 it wrote DECLINED with
163
+ * `APPLICATION_CONFIG_DECLARES_LANGUAGES` for every one-language application; nothing stopped it until
164
+ * the landing refused the record, on a real first run.
165
+ */
166
+ export const COMPOSITION_BASIS_DISPOSITION = {
167
+ [CompositionBasis.MARKET_DECLARES_INBOUND_WEB_CHANNEL]: CompositionDisposition.NEEDED,
168
+ [CompositionBasis.BRAND_BRIEF_LANDED]: CompositionDisposition.NEEDED,
169
+ [CompositionBasis.BUSINESS_MODEL_DECLARES_PRICING_PLANS]: CompositionDisposition.NEEDED,
170
+ [CompositionBasis.MARKET_TARGETS_LEGAL_ENTITIES]: CompositionDisposition.NEEDED,
171
+ [CompositionBasis.REQUIREMENTS_DECLARE_PORTABILITY]: CompositionDisposition.NEEDED,
172
+ [CompositionBasis.APPLICATION_CONFIG_DECLARES_LANGUAGES]: CompositionDisposition.NEEDED,
173
+ [CompositionBasis.MARKET_TARGETS_UNSERVED_LANGUAGES]: CompositionDisposition.NEEDED,
174
+ [CompositionBasis.DOMAIN_PLAN_OWNS_MODULES_AND_RESOURCES]: CompositionDisposition.OWNED_BY_ANOTHER_STEP,
175
+ [CompositionBasis.BUILD_TASKS_OWN_PER_ARTIFACT_SCENARIOS]: CompositionDisposition.OWNED_BY_ANOTHER_STEP,
176
+ [CompositionBasis.PROVIDER_DECISION_OWNS_PROVIDERS]: CompositionDisposition.OWNED_BY_ANOTHER_STEP,
177
+ [CompositionBasis.DEPLOYMENT_OWNS_ENVIRONMENTS]: CompositionDisposition.OWNED_BY_ANOTHER_STEP,
178
+ [CompositionBasis.INTEGRATION_PLAN_OWNS_WORKERS_AND_MINIONS]: CompositionDisposition.OWNED_BY_ANOTHER_STEP,
179
+ [CompositionBasis.OPERATOR_OPTS_INTO_OPTIONAL_LAYOUT]: CompositionDisposition.OWNED_BY_ANOTHER_STEP,
180
+ [CompositionBasis.NO_DECLARATION_IMPLIES_IT]: CompositionDisposition.DECLINED,
181
+ [CompositionBasis.NO_DECLARATION_DECIDES_IT]: CompositionDisposition.DECLINED,
182
+ } as const satisfies Readonly<Record<CompositionBasis, CompositionDisposition>>;
183
+
184
+ /** The bases that can justify disposition `D` — what a typed decision constructor accepts. */
185
+ export type CompositionBasisFor<D extends CompositionDisposition> = {
186
+ [B in CompositionBasis]: (typeof COMPOSITION_BASIS_DISPOSITION)[B] extends D ? B : never;
187
+ }[CompositionBasis];
188
+
135
189
  const NonEmptyStringSchema = z.string().trim().min(1);
136
190
 
137
191
  /** One scenario's decision, with the declaration it was read from. */
@@ -145,6 +199,15 @@ export const CompositionDecisionSchema = z.strictObject({
145
199
  ownedBy: NonEmptyStringSchema.optional(),
146
200
  /** For NO_DECLARATION_DECIDES_IT: the typed declaration that would decide it, so the gap is a named field rather than a question. */
147
201
  missingDeclaration: NonEmptyStringSchema.optional(),
202
+ /**
203
+ * For a NEEDED `add-locale`: the languages the website publishes a locale for, beyond its primary.
204
+ *
205
+ * Carried on the decision so the foundation APPLIES what was decided instead of deciding it again.
206
+ * Before the market could decide a locale, the foundation re-read the configuration's languages and
207
+ * that was the same answer; once a market language the configuration does not serve can make a
208
+ * locale NEEDED, only the decision knows the full set.
209
+ */
210
+ locales: z.array(z.enum(AvailableLanguage).systemEnum('AvailableLanguage')).optional(),
148
211
  });
149
212
  export type CompositionDecision = z.infer<typeof CompositionDecisionSchema>;
150
213
 
@@ -4,8 +4,10 @@
4
4
  ## Usage Example
5
5
 
6
6
  ```typescript
7
+ import { RuntimeEnvironment } from '@wildo-ai/saas-models';
7
8
  import {
8
9
  createDataSeedDefinition,
10
+ DataSeedExistingRowTreatment,
9
11
  DataSeedMode,
10
12
  DataSeedResourceLifecyclePhase,
11
13
  DataSeedScopeKind,
@@ -110,5 +112,31 @@ const organizationDefaultWorkspaceSeed = createDataSeedDefinition({
110
112
  }),
111
113
  });
112
114
 
113
- export { organizationDefaultWorkspaceSeed, systemEmailTemplatesSeed };
115
+ // ─────────────────────────────────────────────────────────────────────
116
+ // Demonstration data — sample rows that make a freshly created application
117
+ // look lived-in, kept OUT of production by `allowedApplicationEnvironments`.
118
+ // Without it these customers would be inserted beside real ones the first
119
+ // time the application starts in production. A restricted seed is withheld
120
+ // at registration, so no trigger, schedule or manual run can reach it there.
121
+ //
122
+ // `FILL_MISSING_DEFAULTS`: a person edits demo rows while trying the app, and
123
+ // the default treatment would re-stamp the declared payload over their edits
124
+ // on every pass.
125
+ // ─────────────────────────────────────────────────────────────────────
126
+ const demoCustomersSeed = createDataSeedDefinition({
127
+ seedKey: 'crm:demo-customers',
128
+ scope: { kind: DataSeedScopeKind.APPLICATION },
129
+ resourceType: 'customer',
130
+ triggers: [{ triggerKind: DataSeedTriggerKind.ON_APP_INIT }],
131
+ mode: DataSeedMode.ADDITIVE,
132
+ version: 1,
133
+ existingRowTreatment: DataSeedExistingRowTreatment.FILL_MISSING_DEFAULTS,
134
+ allowedApplicationEnvironments: [RuntimeEnvironment.DEVELOPMENT, RuntimeEnvironment.STAGING],
135
+ entries: [
136
+ { businessKey: { email: 'ana.martin@example.com' }, data: { name: 'Ana Martin', company: 'Martin Renovations' } },
137
+ { businessKey: { email: 'luc.bernard@example.com' }, data: { name: 'Luc Bernard', company: 'Bernard Plumbing' } },
138
+ ],
139
+ });
140
+
141
+ export { demoCustomersSeed, organizationDefaultWorkspaceSeed, systemEmailTemplatesSeed };
114
142
  ```
@@ -652,7 +652,7 @@ function detectMissingPositioningForIcp(snapshot: MarketSnapshot, issues: Market
652
652
  const positionedIcpRefs = new Set(snapshot.positionings.map(p => p.icpRef));
653
653
 
654
654
  for (const [iIdx, icp] of snapshot.icps.entries()) {
655
- if (icp.priority !== ICPPriority.CORE && icp.priority !== ICPPriority.EXPANSION) continue;
655
+ if (!TARGETED_ICP_PRIORITIES.has(icp.priority)) continue;
656
656
  if (positionedIcpRefs.has(icp.ref)) continue;
657
657
 
658
658
  issues.push({
@@ -160,7 +160,13 @@ export function wireDataSeedingDeclarations(
160
160
  * of the collision a reader can act on.
161
161
  */
162
162
  const engineOwned = registersEngineOwnedSeeds ? ENGINE_OWNED_DATA_SEEDS : [];
163
- const seeds = [...engineOwned, ...(dataSeeds ?? [])];
163
+ /*
164
+ * Admitted over the MERGED list (#2234), so a restricted seed is withheld at registration whoever owns it — the
165
+ * promise `allowedApplicationEnvironments` makes. The application's own seeds were already admitted where
166
+ * `start-application` took them (its seeding gates read that set); re-admitting them here is idempotent, and it is
167
+ * what reaches the engine's.
168
+ */
169
+ const seeds = admitDataSeedsForApplicationEnvironment([...engineOwned, ...(dataSeeds ?? [])], readDeclaredApplicationEnvironment(process.env)).admitted;
164
170
  logDebug('🌱 Registering data-seed definitions...', {
165
171
  count: seeds.length,
166
172
  engineOwned: engineOwned.length,
@@ -51,6 +51,12 @@
51
51
  * - `schedule` — optional cron-driven re-run binding; presence is the
52
52
  * sole opt-in signal for the engine cron batch. FORBIDDEN for
53
53
  * `mode === LAZY`.
54
+ * - `allowedApplicationEnvironments` — optional; omit for reference data the
55
+ * application needs everywhere. DEMONSTRATION data (sample rows that make a
56
+ * fresh application look lived-in) MUST declare it without `production`, e.g.
57
+ * `[RuntimeEnvironment.DEVELOPMENT, RuntimeEnvironment.STAGING]` (import
58
+ * `RuntimeEnvironment` from `@wildo-ai/saas-models`). A restricted seed is never
59
+ * registered elsewhere, and is withheld when the deployment declares no environment.
54
60
  */
55
61
  export interface DataSeedDefinitionInput extends DataSeedDefinitionAuthored, DataSeedDefinitionCallbacks {}
56
62
 
@@ -13,6 +13,56 @@
13
13
  export const SCHEDULED_INITIAL_ADMISSION_MAX_AGE_MS = 5 * 60 * 1000;
14
14
  export const SCHEDULED_INITIAL_ADMISSION_FUTURE_SKEW_MS = 30 * 1000;
15
15
 
16
+ /**
17
+ * How long after its token expired a delivery may still be RECORDED as a missed occurrence (#2212).
18
+ *
19
+ * An expired token stays cryptographically valid forever, so without a horizon anyone able to
20
+ * publish onto the application's queue could replay a captured token of any age and plant a
21
+ * "missed while absent" record. The horizon is APPROXIMATELY the job-row retention: within it, a
22
+ * replayed token almost always meets the occurrence's existing row and is recognised as already
23
+ * held; beyond it, no genuine backlog is plausible and the delivery is rejected as a trust failure.
24
+ * "Approximately" because a row that ran on time expires measured from its completion while the
25
+ * horizon is measured from the token's expiry, which leaves a window of a few minutes in which a
26
+ * replay is recorded as a fresh miss. It never runs anything, and archived run evidence still wins
27
+ * the occurrence in coverage.
28
+ *
29
+ * Equal to `JOB_EXECUTION_TTL_SECONDS` (declared further down, outside this shared block, so it
30
+ * cannot be referenced here without a temporal-dead-zone hazard); a test pins the two together, so
31
+ * changing one without the other fails.
32
+ */
33
+ export const SCHEDULED_LATE_DELIVERY_HORIZON_MS = 30 * 24 * 60 * 60 * 1000;
34
+
35
+ /**
36
+ * Why an AUTHENTIC scheduled delivery reached the application too late to be admitted (#2212).
37
+ *
38
+ * Either way the occurrence was MISSED: it is recorded as such and not run, and the schedule
39
+ * continues with its next occurrence. The two gates differ in WHO was late, which is why they are
40
+ * kept apart:
41
+ *
42
+ * - `TOKEN_EXPIRED` — the delivery sat in the queue for longer than its token lives, so nothing
43
+ * consumed the application's scheduled queue for that long: the backend (or minion) was stopped,
44
+ * restarting or crash-looping. This is the common case after a restart.
45
+ * - `OUTSIDE_ADMISSION_WINDOW` — the token is still current, but the occurrence it names is older
46
+ * than the window. The scheduler may sign up to the window's length AFTER the occurrence, so the
47
+ * delay is shared between the scheduler's publication and the application's consumption, and
48
+ * cannot be attributed to the application alone.
49
+ *
50
+ * A late delivery is never an authentication failure: its signature, issuer and audience were
51
+ * proven before it was classified late. A token that cannot be proven authentic, that names an
52
+ * occurrence in the future, or that expired longer ago than `SCHEDULED_LATE_DELIVERY_HORIZON_MS`
53
+ * is a trust failure instead and is reported loudly.
54
+ *
55
+ * Missed occurrences are SKIPPED, never caught up: that is the established cron behaviour (a
56
+ * Kubernetes `CronJob` past its `startingDeadlineSeconds`, a Quartz trigger with the do-nothing
57
+ * misfire instruction), and it keeps the short signed window a replay bound rather than a credential.
58
+ */
59
+ export enum ScheduledDeliveryLateness {
60
+ /** The signed delivery token's `exp` passed before the delivery was consumed. */
61
+ TOKEN_EXPIRED = 'token_expired',
62
+ /** The token is current, but the occurrence it names is older than `SCHEDULED_INITIAL_ADMISSION_MAX_AGE_MS`; scheduler and consumer share the delay. */
63
+ OUTSIDE_ADMISSION_WINDOW = 'outside_admission_window',
64
+ }
65
+
16
66
  /** How the handler's complete effects tolerate execution after an uncertain outcome. */
17
67
  export enum ScheduledReplaySafety {
18
68
  /** No automatic repetition; a failed call can already have committed effects. */
@@ -86,11 +136,41 @@ export const ScheduledEvidencePolicySchema = z.object({
86
136
  });
87
137
  export type ScheduledEvidencePolicy = z.infer<typeof ScheduledEvidencePolicySchema>;
88
138
 
139
+ /** How a scheduled occurrence's archived evidence came to exist. */
89
140
  export enum ScheduledEvidenceSource {
141
+ /** The handler ran and reported completion. */
90
142
  EXECUTION = 'execution',
143
+ /** The handler's reconciler established that an interrupted run completed. */
91
144
  RECONCILIATION = 'reconciliation',
145
+ /** An operator confirmed completion of an occurrence held for review. */
92
146
  OPERATOR_CONFIRMATION = 'operator_confirmation',
147
+ /** An operator decided an occurrence held for review will not run. */
93
148
  ABANDONMENT = 'abandonment',
149
+ /**
150
+ * The occurrence was never run: its authentic delivery reached the application after the
151
+ * admission deadline (see `ScheduledDeliveryLateness` for who was late). Coverage reads it as an
152
+ * EXPLAINED gap: the slot stays missing, because the occurrence did not run, and the record says
153
+ * why — rather than an unexplained one.
154
+ */
155
+ LATE_DELIVERY = 'late_delivery',
156
+ }
157
+
158
+ /**
159
+ * The terminal invocation status each evidence source records — the one place that pairing is stated.
160
+ *
161
+ * A source whose occurrence never reached a successful invocation records `FAILED`; this follows the
162
+ * precedent `ABANDONMENT` set, and the SOURCE (never the status) is what says why it did not run.
163
+ */
164
+ export function scheduledEvidenceInvocationStatus(source: ScheduledEvidenceSource): JobExecutionStatus {
165
+ switch (source) {
166
+ case ScheduledEvidenceSource.EXECUTION:
167
+ case ScheduledEvidenceSource.RECONCILIATION:
168
+ case ScheduledEvidenceSource.OPERATOR_CONFIRMATION:
169
+ return JobExecutionStatus.COMPLETED;
170
+ case ScheduledEvidenceSource.ABANDONMENT:
171
+ case ScheduledEvidenceSource.LATE_DELIVERY:
172
+ return JobExecutionStatus.FAILED;
173
+ }
94
174
  }
95
175
  export enum ScheduledEvidenceResultStatus {
96
176
  CAPTURED = 'captured',
@@ -120,8 +200,7 @@ export const ScheduledRunEvidenceSchema = ScheduledRunEvidenceFieldsSchema.super
120
200
  : evidence.jobType !== JobType.SCHEDULED_CRON || !(evidence.batchRef || evidence.operationPathKey))) {
121
201
  ctx.addIssue({ code: 'custom', message: 'Evidence requires exactly one scheduled batch, operation or minion target' });
122
202
  }
123
- const expectedStatus = evidence.source === ScheduledEvidenceSource.ABANDONMENT ? JobExecutionStatus.FAILED : JobExecutionStatus.COMPLETED;
124
- if (evidence.invocationStatus !== expectedStatus) {
203
+ if (evidence.invocationStatus !== scheduledEvidenceInvocationStatus(evidence.source)) {
125
204
  ctx.addIssue({ code: 'custom', path: ['invocationStatus'], message: 'Terminal outcome must agree with evidence source' });
126
205
  }
127
206
 
@@ -118,6 +118,8 @@ export interface SpecificationsCompanionExports<
118
118
  TIntegrationPlan = IntegrationPlan,
119
119
  // Appended STRICTLY LAST: where the application stands against its own requirements (#1496).
120
120
  TApplicationMaturity = ApplicationMaturity,
121
+ // Appended STRICTLY LAST: the screened brand-name candidates the brand-identity interview chooses from.
122
+ TBrandNameScreening = BrandNameScreening,
121
123
  > {
122
124
  resourceSpecifications: TResourceSpecifications;
123
125
  applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
@@ -648,6 +650,14 @@ export interface SpecificationsCompanionExports<
648
650
  * never a gate. Read by the coherence report and the workbench.
649
651
  */
650
652
  applicationMaturity?: TApplicationMaturity;
653
+ /**
654
+ * WHICH NAMES were proposed for the brand and what a minimal trademark screening of each found —
655
+ * registers, classes and jurisdictions searched, per-register results with sources and dates, and the
656
+ * competitor collisions beside them. Produced by `top_down.brand-naming`; the brand-identity interview's
657
+ * `brand-name` CHOICE is computed from it, and the coherence report reads it to say where the chosen
658
+ * brand name stands. A screening, never a legal clearance opinion.
659
+ */
660
+ brandNameScreening?: TBrandNameScreening;
651
661
  /**
652
662
  * Accepted application-declared semantic causality between whole
653
663
  * specification-family states. This is not the registry's physical
@@ -231,6 +231,12 @@ function composeEffectiveChromeLabelKeys(
231
231
  * `loadAndValidateAllLabelPacks` is what `wildo website audit` calls
232
232
  * when it wants programmatic access to the per-locale results.
233
233
  *
234
+ * **Empty pages**: it first refuses a page whose `sectionRefs` is empty
235
+ * (`assertWebsitePagesHaveSections`, #2205). That refusal used to live in
236
+ * the manifest schema, where it crashed `astro dev` too; this hook runs
237
+ * only at `astro:build:start`, which is where a page with nothing on it
238
+ * stops being unfinished and starts being wrong.
239
+ *
234
240
  * **Key-origin annotation**: every `missing` key is tagged with the
235
241
  * page (and, if section-scoped, the section) that declared it, so the
236
242
  * author can grep + open the right `defineWebsiteSection` /
@@ -242,6 +248,9 @@ export function assertLabelPacksValid(
242
248
  expectedKeysBySectionRef: ExpectedLabelKeysBySectionRef,
243
249
  ): void {
244
250
  const { rootConfig } = siteContext;
251
+ // The build-start hook every website wires, so the empty-page refusal arms with no config edit
252
+ // (#2205). First, because a page with no section has no label commitments to validate.
253
+ assertWebsitePagesHaveSections(rootConfig);
245
254
  const validations = loadAndValidateAllLabelPacks(
246
255
  packsDir,
247
256
  siteContext,
@@ -27,6 +27,8 @@ export interface DefineWebsiteSectionInput<TProps> {
27
27
  sectionRef: WebsiteSectionRef | string;
28
28
  category: WebsiteSectionCategory;
29
29
  expectedLabelKeys: readonly (WebsiteLabelKey | string)[];
30
+ /** The section's DOM id, so a link can target it (`<a href="#tiers">`). See `WebsiteSectionDefinition.anchorId`. */
31
+ anchorId?: string;
30
32
  Component: ComponentType<TProps>;
31
33
  /**
32
34
  * See `WebsiteSectionDefinition.getStructuredData?` JSDoc for the
@@ -109,6 +111,7 @@ export function defineWebsiteSection<TProps>(
109
111
  sectionRef: input.sectionRef,
110
112
  category: input.category,
111
113
  expectedLabelKeys: input.expectedLabelKeys,
114
+ anchorId: input.anchorId,
112
115
  Component: input.Component,
113
116
  getStructuredData: input.getStructuredData,
114
117
  });
@@ -121,6 +124,7 @@ export function defineWebsiteSection<TProps>(
121
124
  sectionRef: parsed.sectionRef,
122
125
  category: parsed.category,
123
126
  expectedLabelKeys: parsed.expectedLabelKeys,
127
+ ...(parsed.anchorId !== undefined ? { anchorId: parsed.anchorId } : {}),
124
128
  Component: input.Component,
125
129
  ...(input.getStructuredData ? { getStructuredData: input.getStructuredData } : {}),
126
130
  };
@@ -63,6 +63,8 @@
63
63
  * not match the directive in its `.astro` file.
64
64
  *
65
65
  * **Refinements**:
66
+ * - `sectionRefs` MAY be empty — a page whose sections are still being authored. It may be
67
+ * served by a dev server and may not be built: see `assertWebsitePagesHaveSections`.
66
68
  * - `sectionRefs` MUST contain unique values. Duplicates indicate
67
69
  * either a copy-paste bug (two sections pointing at the same
68
70
  * label-key root) or an intent to share a label-key root that
@@ -123,9 +125,16 @@ const _WebsitePageManifestSchema = z
123
125
  ref: WebsitePageRefSchema,
124
126
  routePath: _WebsitePageRoutePathSchema,
125
127
  pageComponent: z.unknown(),
126
- sectionRefs: z.array(WebsiteSectionRefSchema).min(1, {
127
- error: 'A page manifest must declare at least one sectionRef',
128
- }),
128
+ /*
129
+ * EMPTY is a valid manifest (#2205): a page whose sections are not authored YET. The build lane
130
+ * creates that state on purpose (the page task writes the empty list, then each section task
131
+ * appends itself), and refusing it here made `astro dev` crash at module load until every page
132
+ * of the site had a section. An empty page is unfinished, not false, so it is representable and
133
+ * a dev server renders it (`WebsitePageSections` shows the pending state). What is refused is
134
+ * BUILDING one: `assertWebsitePagesHaveSections`, run from the build-start hook, because a
135
+ * published page with nothing on it is a statement to a real reader.
136
+ */
137
+ sectionRefs: z.array(WebsiteSectionRefSchema),
129
138
  metaLabelKeys: _WebsitePageMetaLabelKeysSchema,
130
139
  hydration: WebsitePageHydrationStrategySchema.optional(),
131
140
  seo: _WebsitePageSeoConfigSchema.optional(),
@@ -0,0 +1,72 @@
1
+ # saas.website.page-sections.component
2
+
3
+ ## Import Origins
4
+
5
+ - `@wildo-ai/saas-website`
6
+
7
+ ## Source Excerpts
8
+
9
+ ### Origin Package: `@wildo-ai/saas-website`
10
+
11
+ ```tsx
12
+ *
13
+ * `WebsitePageSections` — renders a page's ordered sections list, each inside its `WebsiteSection`
14
+ * wrapper, and a visible PENDING marker while the list is still empty.
15
+ *
16
+ * A page component should render its sections through this rather than mapping the list by hand:
17
+ *
18
+ * ```tsx
19
+ * export function PricingPage(): ReactNode {
20
+ * return <WebsitePageSections pageRef="pricing" sections={PRICING_SECTIONS} />;
21
+ * }
22
+ * ```
23
+ *
24
+ * **Why the empty state is the point.** A page's sections list starts EMPTY when its page
25
+ * is authored before its sections — the application-creation build lane does exactly that, one task
26
+ * per page and one per section. An empty page is a valid manifest and a dev server serves it; the
27
+ * production build refuses it (`assertWebsitePagesHaveSections`). Mapped by hand, an empty list
28
+ * renders nothing at all, which is indistinguishable from a page that failed. This renders a
29
+ * marked block instead, so the page visibly says its sections are still to come.
30
+ *
31
+ * A section's `anchorId`, declared on its definition, becomes the wrapper's DOM `id`, so in-page links
32
+ * still have a target when no page places its sections by hand.
33
+ *
34
+ * **The marker carries identifiers, not prose.** It shows the page ref and the empty list as code,
35
+ * deliberately: words a person reads come from the label packs, and a label for a state no built
36
+ * page can ever reach (the build refuses an empty page) would be a key every locale must carry for
37
+ * nothing. A missing section must LOOK missing, which a raw identifier does.
38
+ */
39
+ export interface WebsitePageSectionsProps {
40
+ /** The page's ref, as its manifest declares it. Shown in the pending marker. */
41
+ pageRef: string;
42
+ /** The page's ordered sections list — the same array its manifest's `sectionRefs` derive from. */
43
+ sections: readonly WebsiteSectionDefinition[];
44
+ }
45
+
46
+ export function WebsitePageSections({ pageRef, sections }: WebsitePageSectionsProps): ReactNode {
47
+ if (sections.length === 0) {
48
+ return (
49
+ <section
50
+ data-website-pending-page={pageRef}
51
+ aria-busy="true"
52
+ style={{ margin: '2rem auto', maxWidth: '48rem', padding: '2rem', border: '2px dashed currentColor', opacity: 0.6, textAlign: 'center' }}
53
+ >
54
+ <code>{`${pageRef}: sections = []`}</code>
55
+ </section>
56
+ );
57
+ }
58
+ return (
59
+ <>
60
+ {sections.map((section) => {
61
+ const SectionComponent = section.Component as React.ComponentType;
62
+ return (
63
+ <WebsiteSection key={String(section.sectionRef)} sectionRef={section.sectionRef} category={section.category} id={section.anchorId}>
64
+ <SectionComponent />
65
+ </WebsiteSection>
66
+ );
67
+ })}
68
+ </>
69
+ );
70
+ }
71
+ WebsitePageSections.displayName = 'WebsitePageSections';
72
+ ```
@@ -47,6 +47,14 @@
47
47
  * and is caught by nothing until a reviewer reads the page. The
48
48
  * build and `wildo website audit` check the pack against the
49
49
  * DECLARED keys, so declare every slot the component reads.
50
+ * - `anchorId?` — the section's DOM id, so a link (`<a href="#tiers">`)
51
+ * can target it. Belongs to the DEFINITION because a page renders its
52
+ * sections list through `WebsitePageSections`, which places every
53
+ * section itself: an anchor a page author would otherwise write on a
54
+ * hand-placed `<WebsiteSection id=…>` has nowhere else to live. A
55
+ * valid HTML id that is also URL-fragment-safe: a letter, then
56
+ * letters, digits, `-` or `_`. Uniqueness on a page is the author's
57
+ * to keep, like the id attribute it becomes.
50
58
  * - `Component` — the React component that renders the section. Typed
51
59
  * as `ComponentType<unknown>` here because schema-layer cannot lock
52
60
  * the component's prop shape (props vary per section). The factory
@@ -73,6 +81,9 @@ const _WebsiteSectionDefinitionSchema = z.object({
73
81
  sectionRef: WebsiteSectionRefSchema,
74
82
  category: WebsiteSectionCategorySchema,
75
83
  expectedLabelKeys: z.array(WebsiteLabelKeySchema).readonly(),
84
+ anchorId: z.string().regex(/^[A-Za-z][A-Za-z0-9_-]*$/, {
85
+ error: 'A section anchorId must start with a letter and contain only letters, digits, "-" or "_"',
86
+ }).optional(),
76
87
  Component: z.unknown(),
77
88
  getStructuredData: z.unknown().optional(),
78
89
  });
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "assurance-authority-bases",
3
3
  "metadata": {
4
- "generatedAt": "2026-09-30T15:35:32.423Z",
4
+ "generatedAt": "2026-10-03T03:06:36.431Z",
5
5
  "description": "Compiled portable assurance-authority bases."
6
6
  },
7
7
  "entries": {
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "framework-topics",
3
3
  "metadata": {
4
- "generatedAt": "2026-09-30T15:35:32.423Z",
4
+ "generatedAt": "2026-10-03T03:06:36.431Z",
5
5
  "description": "Topic registry derived from extracted framework-knowledge tags."
6
6
  },
7
7
  "entries": {
@@ -188,6 +188,26 @@
188
188
  "referenceFilePath": "references/brand.logo-direction.config.md",
189
189
  "sourceReferenceCount": 1
190
190
  },
191
+ "brand.name-choice.config": {
192
+ "topicId": "brand.name-choice.config",
193
+ "title": "Brand Name Choice Config",
194
+ "categories": [
195
+ "brand",
196
+ "brand.name-choice"
197
+ ],
198
+ "referenceFilePath": "references/brand.name-choice.config.md",
199
+ "sourceReferenceCount": 1
200
+ },
201
+ "brand.name-screening.config": {
202
+ "topicId": "brand.name-screening.config",
203
+ "title": "Brand Name Screening Config",
204
+ "categories": [
205
+ "brand",
206
+ "brand.name-screening"
207
+ ],
208
+ "referenceFilePath": "references/brand.name-screening.config.md",
209
+ "sourceReferenceCount": 1
210
+ },
191
211
  "brand.name.config": {
192
212
  "topicId": "brand.name.config",
193
213
  "title": "Brand Name Config",
@@ -6110,6 +6130,17 @@
6110
6130
  "referenceFilePath": "references/saas.website.page-manifest.seo.md",
6111
6131
  "sourceReferenceCount": 1
6112
6132
  },
6133
+ "saas.website.page-sections.component": {
6134
+ "topicId": "saas.website.page-sections.component",
6135
+ "title": "Saas Website Page Sections Component",
6136
+ "categories": [
6137
+ "saas",
6138
+ "saas.website",
6139
+ "saas.website.page-sections"
6140
+ ],
6141
+ "referenceFilePath": "references/saas.website.page-sections.component.md",
6142
+ "sourceReferenceCount": 1
6143
+ },
6113
6144
  "saas.website.page.context": {
6114
6145
  "topicId": "saas.website.page.context",
6115
6146
  "title": "Saas Website Page Context",
@@ -6903,6 +6934,12 @@
6903
6934
  "categories": [],
6904
6935
  "sourceReferenceCount": 0
6905
6936
  },
6937
+ "brand-name-screening": {
6938
+ "topicId": "brand-name-screening",
6939
+ "title": "Brand Name Screening",
6940
+ "categories": [],
6941
+ "sourceReferenceCount": 0
6942
+ },
6906
6943
  "compliance-document-authoring": {
6907
6944
  "topicId": "compliance-document-authoring",
6908
6945
  "title": "Compliance Document Authoring",