@wildo-ai/framework-knowledge 1.1.2 → 1.1.3

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 (287) hide show
  1. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  2. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  3. package/dist/esm/framework-knowledge.definitions.js +228 -6
  4. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  5. package/dist/esm/framework-knowledge.schemas.d.ts +1 -2
  6. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  7. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  8. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +3 -4
  9. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  10. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -4
  11. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  12. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -4
  13. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +4 -4
  15. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -1
  17. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -1
  19. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  20. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -1
  21. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  22. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -1
  23. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +1 -2
  25. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -2
  27. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +2 -3
  29. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +3 -3
  31. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -2
  33. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -2
  35. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +0 -1
  37. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +0 -1
  39. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +0 -1
  41. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +0 -1
  43. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +0 -1
  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 +0 -1
  47. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +0 -1
  49. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  50. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -1
  51. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  52. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +0 -1
  53. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -1
  55. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  56. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +0 -2
  57. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +2 -2
  59. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  60. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +0 -1
  61. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +0 -1
  63. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +0 -1
  65. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +0 -1
  67. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +0 -1
  69. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +0 -1
  71. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +0 -1
  73. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +0 -1
  75. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +0 -2
  77. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -4
  79. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
  81. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
  83. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
  85. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
  87. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -1
  89. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  91. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +0 -1
  93. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -1
  95. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  96. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +0 -1
  97. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -1
  99. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  100. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +0 -1
  101. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +0 -1
  103. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  104. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -1
  105. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  107. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +0 -1
  109. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +0 -1
  111. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  112. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  113. package/dist/knowledge/manifest.json +8 -9
  114. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +13 -70
  115. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +11 -19
  116. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +5 -88
  117. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +15 -8
  118. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +4 -5
  119. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +15 -8
  120. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +4 -0
  121. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -7
  122. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +22 -49
  123. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -17
  124. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -780
  125. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -11
  126. package/dist/knowledge/playbooks/refinement.document-facts/method.md +20 -141
  127. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -10
  128. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +3 -2
  129. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +16 -11
  130. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +14 -6
  131. package/dist/knowledge/playbooks/top_down.capability-map/method.md +4 -2
  132. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +16 -7
  133. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +4 -21
  134. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +65 -16
  135. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
  136. package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
  137. package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
  138. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +43 -23
  139. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +4 -8
  140. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +7 -9
  141. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +7 -9
  142. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +15 -7
  143. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +3 -3
  144. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +16 -11
  145. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +4 -2
  146. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +15 -7
  147. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +2 -2
  148. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +16 -11
  149. package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
  150. package/dist/knowledge/references/companion.technical-doc.service.md +2 -102
  151. package/dist/knowledge/references/example.config.app-shell.full.md +5 -0
  152. package/dist/knowledge/references/example.module.companion-exports.full.md +0 -1
  153. package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
  154. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
  155. package/dist/knowledge/references/platform.config.saas.md +0 -51
  156. package/dist/knowledge/references/presets.models.surface-policy.md +10 -19
  157. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
  158. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +11 -31
  159. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
  160. package/dist/knowledge/references/saas.frontend.composite-view.authoring.md +0 -45
  161. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -198
  162. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -164
  163. package/dist/knowledge/references/saas.models.engine-capabilities.md +6 -26
  164. package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
  165. package/dist/knowledge/references/saas.models.provider-capabilities.md +3 -4
  166. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
  167. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
  168. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
  169. package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +31 -11
  170. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +2 -32
  171. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +6 -29
  172. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -56
  173. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +0 -22
  174. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
  175. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
  176. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -7
  177. package/dist/knowledge/references/zod.decorators.field-spec-params.md +5 -31
  178. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -44
  179. package/dist/knowledge/references/zod.decorators.primitive-ui.md +0 -3
  180. package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
  181. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +0 -15
  182. package/dist/knowledge/registries/assurance-authority-bases.json +2 -3
  183. package/dist/knowledge/registries/framework-topics.json +11 -146
  184. package/dist/knowledge/registries/playbooks.json +18 -154
  185. package/dist/knowledge/registries/source-tags.json +630 -883
  186. package/dist/knowledge/skills/INDEX.md +3 -4
  187. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +1 -2
  188. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
  189. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +9 -31
  190. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
  191. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
  192. package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +53 -97
  193. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +21 -84
  194. package/dist/knowledge/skills/config-app-shell/SKILL.md +9 -31
  195. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +12 -31
  196. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -23
  197. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +10 -19
  198. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -75
  199. package/dist/knowledge/skills/config-saas/SKILL.md +2 -19
  200. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +9 -30
  201. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -51
  202. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
  203. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +1 -2
  204. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +3 -4
  205. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -56
  206. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -56
  207. package/dist/knowledge/skills/module-companion-exports/SKILL.md +0 -1
  208. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -56
  209. package/dist/knowledge/skills/resource-add-field/SKILL.md +3 -3
  210. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -213
  211. package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
  212. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
  213. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -15
  214. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -224
  215. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -198
  216. package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
  217. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
  218. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
  219. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -22
  220. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +8 -28
  221. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
  222. package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
  223. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
  224. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +0 -15
  225. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
  226. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -7
  227. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -198
  228. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -44
  229. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +0 -3
  230. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +0 -1
  231. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -56
  232. package/dist/knowledge/skills/spec-resource-update/references/framework-field-spec-params-api.md +5 -31
  233. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +0 -22
  234. package/dist/knowledge/skills/views-composite-authoring/references/framework-composite-view-contracts-api.md +0 -45
  235. package/dist/knowledge/topic-index.json +220 -725
  236. package/dist/tsconfig.build.tsbuildinfo +1 -1
  237. package/dist/tsconfig.tsbuildinfo +1 -1
  238. package/package.json +4 -4
  239. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +0 -1
  240. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +0 -51
  241. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -43
  242. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
  243. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -64
  244. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +0 -41
  245. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +0 -100
  246. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +0 -117
  247. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +0 -86
  248. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +0 -61
  249. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +0 -41
  250. package/dist/knowledge/playbooks/top_down.compliance-research/method.md +0 -76
  251. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +0 -42
  252. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
  253. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -42
  254. package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
  255. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -44
  256. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
  257. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -67
  258. package/dist/knowledge/references/placement-plan.config.md +0 -330
  259. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +0 -34
  260. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +0 -45
  261. package/dist/knowledge/references/saas.frontend.public-shell.identity-mode.md +0 -65
  262. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
  263. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
  264. package/dist/knowledge/references/saas.models.file-upload-grant.md +0 -179
  265. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +0 -124
  266. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +0 -99
  267. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +0 -127
  268. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +0 -42
  269. package/dist/knowledge/references/saas.specifications.application-authored-document-fact-specification.contract.md +0 -29
  270. package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
  271. package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
  272. package/dist/knowledge/skills/config-app-shell/references/framework-public-shell-identity-api.md +0 -124
  273. package/dist/knowledge/skills/config-design-system/references/loading-placeholder-authoring.md +0 -47
  274. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +0 -98
  275. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +0 -54
  276. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +0 -232
  277. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +0 -149
  278. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +0 -114
  279. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +0 -133
  280. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +0 -111
  281. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
  282. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-file-upload-grant-contract.md +0 -192
  283. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
  284. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
  285. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
  286. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
  287. /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
@@ -29,25 +29,14 @@ document's own limitations: these terms are not ready to be presented for accept
29
29
  **Asserts** — who legally operates the service: entity name, registered address, contact route for
30
30
  data-protection questions, and a representative where one is required.
31
31
 
32
- **Derives from** — `operatorComplianceIdentity` in `wildo.saas.config.ts`: the legal entity, its
33
- registered address, the privacy contact route, and an Art. 27 representative where one is required.
32
+ **Derives from** — nothing, and nothing could. A legal entity is a fact about the world, not a
33
+ property of a codebase, so this is not a framework gap and no engine change would close it.
34
34
 
35
- The VALUE is never derivable — a legal entity is a fact about the world, not a property of a codebase.
36
- What the framework provides is the PLACE to record it, and until 2026-08-30 it did not: this fragment
37
- said "no engine change would close it", which was right about derivation and wrong about the home.
38
- The consequence was concrete. A landing REPLACES the produced document on every run, so an operator
39
- who answered by editing the document lost the answer at the next regeneration — the answer has to live
40
- in the application or it does not survive.
35
+ **Completeness** — `NEEDS_DECISION`, always, until the operator supplies it.
41
36
 
42
- **Completeness** — `DERIVED` when the identity is declared; `NEEDS_DECISION` when it is not.
43
-
44
- ⚠️ `NEEDS_DECISION`, not `NEEDS_FRAMEWORK`, and the distinction is load-bearing now that the surface
45
- exists. `NEEDS_FRAMEWORK` means there is nowhere to record the answer; `NEEDS_DECISION` means there is
46
- and nobody has. They have different remedies — build something, versus fill something in — and a
47
- reader who cannot tell them apart cannot act on either. Say which surface the answer goes to.
48
-
49
- **What closes it** — the operator declaring `operatorComplianceIdentity`. It is cheap and it can be
50
- filled in later without redrafting anything around it, which is the reason it is not a blocker.
37
+ **What closes it** — the operator recording the entity, address and contact route. That is the second
38
+ step, and it is cheap: the reason it is not a blocker is precisely that it can be filled in later
39
+ without redrafting anything around it.
51
40
 
52
41
  **Never infer it.** Not from the application name, not from a domain, not from another application,
53
42
  not from model memory. A published legal document naming the wrong entity is worse than one that says
@@ -109,15 +98,8 @@ CONTROLLER for the data it holds about the customer's users as account holders.
109
98
  roles with different duties over the same database. Say which is which; do not pick one and apply it
110
99
  to everything.
111
100
 
112
- **The attribution has a home now.** `operatorComplianceIdentity.roleAllocations` in
113
- `wildo.saas.config.ts` carries one role per population of data — PROCESSOR for the records a customer
114
- stores about its own people, CONTROLLER for the account data of the people who administer them. It is
115
- a LIST for exactly the reason this fragment gives: those are different roles over the same database,
116
- and a single field would force one of them to be wrong.
117
-
118
- Where the attribution is not established, that is a `NEEDS_DECISION` — never a guess — and the
119
- surface to name is `roleAllocations`. Not `NEEDS_FRAMEWORK`: there is somewhere to write the answer,
120
- so the remedy is to fill it in rather than to build something. See the legal-basis fragment.
101
+ Where a document needs to attribute a duty and the attribution is not established, that is a
102
+ `NEEDS_DECISION` — never a guess. See the legal-basis fragment.
121
103
 
122
104
 
123
105
  ### Concern: data exit
@@ -1,61 +1,25 @@
1
- # Declared application document-fact contract
2
-
3
- Read this before declaring a fact a governed document relies on, or before changing a creator or
4
- qualified-review decision one uses.
5
-
6
- **Every fact a document cites is declared here.** Nothing derives them for you. This page opened with
7
- "read this before adding a fact that the standard application/infrastructure projectors cannot
8
- derive" until 2026-08-30, which described a host-computed projection layer that no longer exists — so
9
- what read as an exception route is the only route, and a drafter who believed otherwise would wait
10
- for values nothing was going to produce.
11
-
12
- ## There are TWO fact families, and which one you write to is decided for you
13
-
14
- The two carry the same shape and differ in one thing: who may assert the fact. The type refuses the
15
- other family's authorities, so choosing wrong is a compile-and-parse error rather than a silent
16
- mistake.
17
-
18
- | family | companion-exports slot | authority it accepts | who writes it |
19
- |---|---|---|---|
20
- | `document-facts` | `documentFactSpecification` | `APPLICATION_SPECIFICATION` only | the `refinement.document-facts` producer, which **regenerates the file whole** |
21
- | `document-facts-authored` | `authoredDocumentFactSpecification` | `CREATOR_DECISION` or `QUALIFIED_REVIEW` | a person, or a host acting on a person's answers. No producer writes it |
22
-
23
- **Never put a human decision in `document-facts`.** The producer rewrites that file on its next run,
24
- so the decision is deleted and nothing notices — there is no compare-and-swap here, deliberately.
25
- That is why the two are separate families rather than one file with a rule somebody has to remember.
26
-
27
- **Never put a specification-answerable fact in `document-facts-authored`** either. A fact the accepted
28
- specification can answer belongs in the derived family, where it is re-derived when the specification
29
- moves; pinned under a human's name it freezes yesterday's answer.
30
-
31
- A document reads BOTH. A fact declared in either satisfies a clause that cites it.
32
-
33
- - `specificationRef` must use the `document-fact-specification:` namespace in both. Validated
34
- fail-closed.
35
- - Use the authority kind the blueprint question requires; the family then has to match it. A declared
36
- TypeScript module never upgrades a creator decision into qualified review, and never turns a human
37
- decision into runtime evidence.
38
- - Author fact value or explicit not-applicable rationale, governance scope, sensitivity and human
39
- decision metadata — and nothing else.
40
- - **Declarations must be unique AND lexically sorted by `declarationRef@declarationVersion`.** The
41
- sort is enforced, not cosmetic: an otherwise valid specification is rejected for ordering alone,
42
- which is a confusing failure if you do not know to expect it.
43
- - One current value for each fact version and governance scope. Replace it with a new
44
- declaration/specification version; do not retain two current values and hide the conflict.
45
- - Keep candidate reviews, approvals and releases out of the specification.
46
- - Omitting either family, or a declaration a document needs, leaves a visible blocking fact gap. Never
47
- create an empty family or a placeholder value to make a candidate look configured — an invented
48
- value in a governed document is the one failure this whole lane exists to prevent.
49
-
50
- ## Acceptance is a commit, and there is nothing to copy
51
-
52
- An earlier version said to author through "normal family acceptance" and warned against copying
53
- "contribution, accepted-head, semantic-member or validation-receipt digests", alongside reviewer
54
- authority grants.
55
-
56
- None of those exist. Accepted means committed: a declared fact is a file, a human commits it, and
57
- `git log` is the record of who accepted what and when. A warning against copying a digest is worse
58
- than silent — it tells a reader the digest exists somewhere and that finding it is part of the job.
1
+ # Accepted application document-fact declaration contract
2
+
3
+ Read this before adding a fact that the standard application/infrastructure
4
+ projectors cannot derive, or before changing a creator or qualified-review
5
+ decision used by a governed document.
6
+
7
+ - Declare raw current facts in the dedicated accepted `document-facts`
8
+ specification family and expose it as `documentFactSpecification`.
9
+ - Use the authority kind required by the exact blueprint question. An accepted
10
+ TypeScript module never upgrades a creator decision into qualified review or
11
+ turns a human decision into runtime evidence.
12
+ - Author fact value or explicit not-applicable rationale, governance scope,
13
+ sensitivity and human decision metadata only. Never copy contribution,
14
+ accepted-head, semantic-member or validation-receipt digests.
15
+ - One current declaration is allowed for each fact version and governance
16
+ scope. Replace it through a new declaration/specification version and normal
17
+ family acceptance; do not retain two current values and hide the conflict.
18
+ - Keep reviewer grants, candidate reviews, approvals and releases out of the
19
+ specification. They are separate private runtime records.
20
+ - Omitting this optional family or a required declaration leaves a visible
21
+ blocking fact gap. Do not create an empty family or placeholder value to make
22
+ a candidate appear configured.
59
23
 
60
24
  ## Import Origins
61
25
 
@@ -67,8 +31,9 @@ than silent — it tells a reader the digest exists somewhere and that finding i
67
31
 
68
32
  ```typescript
69
33
  *
70
- * Accepted application declaration of governed-document facts THE ACCEPTED SPECIFICATION ANSWERS.
71
- * Import from `@wildo-ai/saas-specifications/application-creation`.
34
+ * Accepted application declaration of governed-document facts that cannot be
35
+ * inferred from framework code. Import from
36
+ * `@wildo-ai/saas-specifications/application-creation`.
72
37
  *
73
38
  * This family carries raw decisions only. It never authors contribution
74
39
  * digests, accepted-head identities, validation receipts, reviewer grants,
@@ -82,43 +47,34 @@ than silent — it tells a reader the digest exists somewhere and that finding i
82
47
  * scope. Replacing a decision requires a new declaration/specification version
83
48
  * and normal specification-family acceptance; conflicting current values are
84
49
  * rejected at the authoring boundary instead of being hidden downstream.
85
- *
86
- * ## This file is REGENERATED, and that is why it accepts one authority kind
87
- *
88
- * `refinement.document-facts` rewrites it whole. Before #192 the same file also held the facts only a
89
- * human may establish, so the next producer run silently deleted them — and there was no compare-and-
90
- * swap to notice, by design (`.claude/rules/one-source-of-truth.md` Rule 0). The facts a human owns
91
- * live in {@link ApplicationAuthoredDocumentFactSpecificationSchema}, in their own file, which no
92
- * producer writes.
93
50
  */
94
- export const ApplicationDocumentFactSpecificationSchema = buildDocumentFactSpecificationSchema(ApplicationDerivedDocumentFactDeclarationSchema);
51
+ export const ApplicationDocumentFactSpecificationSchema = z
52
+ .strictObject({
53
+ schemaVersion: z.literal(1),
54
+ specificationRef: AssuranceNamespacedRefSchema,
55
+ specificationVersion: GovernedDocumentPositiveSafeIntegerSchema,
56
+ declarations: z.array(ApplicationDocumentFactDeclarationSchema).min(1),
57
+ })
58
+ .superRefine((specification, context) => {
59
+ if (!specification.specificationRef.startsWith("document-fact-specification:")) {
60
+ context.addIssue({
61
+ code: "custom",
62
+ message: "specificationRef must use the document-fact-specification: namespace",
63
+ path: ["specificationRef"],
64
+ });
65
+ }
66
+ const declarationIdentities = specification.declarations.map((declaration) => `${declaration.declarationRef}@${declaration.declarationVersion}`);
67
+ if (!valuesAreUnique(declarationIdentities) || !valuesAreLexicallySorted(declarationIdentities)) {
68
+ context.addIssue({ code: "custom", message: "declarations must be unique and lexically sorted by identity", path: ["declarations"] });
69
+ }
70
+ const factScopeKeys = specification.declarations.map(applicationDocumentFactDeclarationScopeKey);
71
+ if (!valuesAreUnique(factScopeKeys)) {
72
+ context.addIssue({
73
+ code: "custom",
74
+ message: "a specification may declare only one current value for each fact version and governance scope",
75
+ path: ["declarations"],
76
+ });
77
+ }
78
+ });
95
79
  export type ApplicationDocumentFactSpecification = z.infer<typeof ApplicationDocumentFactSpecificationSchema>;
96
80
  ```
97
-
98
- ## Import Origins
99
-
100
- - `@wildo-ai/saas-specifications`
101
-
102
- ## Source Excerpts
103
-
104
- ### Origin Package: `@wildo-ai/saas-specifications`
105
-
106
- ```typescript
107
- *
108
- * Accepted application declaration of governed-document facts ONLY A HUMAN MAY ESTABLISH — a creator's
109
- * decision, or a qualified review. Import from
110
- * `@wildo-ai/saas-specifications/application-creation`.
111
- *
112
- * Structurally identical to {@link ApplicationDocumentFactSpecificationSchema}: a declaration is a
113
- * declaration whoever wrote it, and a document reading facts does not care which file one came from.
114
- * The two are separate FAMILIES so that neither writer can destroy the other's half — the derived file
115
- * is regenerated by a producer, this one is only ever edited by a person or by a host acting on a
116
- * person's answers.
117
- *
118
- * Nothing in here may carry `APPLICATION_SPECIFICATION` authority. A fact the specification can answer
119
- * belongs in the derived family, where it is re-derived when the specification moves; pinning it here
120
- * would freeze yesterday's answer under a human's name.
121
- */
122
- export const ApplicationAuthoredDocumentFactSpecificationSchema = buildDocumentFactSpecificationSchema(ApplicationAuthoredDocumentFactDeclarationSchema);
123
- export type ApplicationAuthoredDocumentFactSpecification = z.infer<typeof ApplicationAuthoredDocumentFactSpecificationSchema>;
124
- ```
@@ -1,57 +1,24 @@
1
1
  # Assurance document-blueprint contract
2
2
 
3
- The engine owns the source-neutral document catalog and its blueprints. Applications contribute
4
- declared facts and explicit decisions; they do not copy blueprint definitions into application
5
- specifications. A blueprint says what a document must **address** — it is not legal prose, and
6
- rendering its clause purposes verbatim ships framework text as your operator's legal position.
7
-
8
- **You do not author a catalog, and the one you read is `schemaVersion: 2` / `catalogVersion: 5`.**
9
- Measured 2026-08-30 from the engine's only catalog, and re-confirmed 2026-08-31. That is the current
10
- and correct shape — not a lagging one. A v3 / `catalogVersion` 6 shape also exists in the schema, and
11
- it is deliberately unadopted: nothing yet consumes what v3 adds, so moving the shipped catalog to it
12
- would author content no reader reads. If you have seen v3 described elsewhere as "current", this
13
- paragraph is the newer statement.
14
-
15
- What this page said until 2026-08-30 was "new authoring uses `schemaVersion: 2`", stated as YOUR
16
- instruction. That was wrong twice over: it named a version the schema had already retired, and it
17
- addressed an authoring act an application never performs.
18
-
19
- A catalog declares at least one blueprint, and there is **exactly one blueprint for every
20
- definition** — the pairing is refined fail-closed, in both directions. The shipped catalog carries six
21
- of each: four governance documents (document-record control, programme handbook, roles and
22
- responsibilities, scope and system description) and two public ones (privacy notice, service terms).
23
-
24
- From `catalogVersion` 5 onward each qualified-review policy binds reviewer qualifications to the exact
25
- review kind rather than carrying one flat policy; the retained versions must keep the historical flat
26
- shape, so the two are not interchangeable. `catalogVersion` 6 additionally requires
27
- `structuredValueContracts`, each selected by exactly one annex binding — which is why moving the
28
- shipped catalog forward is authoring work rather than a version bump, and part of why it has not been
29
- done. None of this changes what you author: an application contributes declared facts and decisions,
30
- never a catalog.
31
-
32
- Questions declare answer type, fact authority, sensitivity, not-applicable posture and semantic
33
- options. Sections own visible order. Clauses own drafting purpose, fact variables, monitored source
34
- policies, claim guards and optional declarative inclusion conditions. Conditions inside a group are
35
- ANDed and groups are ORed; no executable expression is accepted. A REQUIRED clause carries no
36
- condition groups. Review checklists cover every review kind the definition's review policies select.
37
-
38
- The contract contains drafting structure, not jurisdiction-specific legal prose, an application fact,
39
- an approval decision, a publication release or an interaction receipt.
40
-
41
- ## Nothing here is sealed, and nothing needs verifying before you author
42
-
43
- An earlier version of this page said the engine owned "sealed blueprints", that a blueprint and its
44
- catalog carried "independent canonical digests", and that "both must verify before authoring."
45
-
46
- No such digests exist. They went with the rest of the digest machinery, and the engine source records
47
- why beside the identities that used to carry them: a digest chain cannot merge, so two branches that
48
- change different blueprints produce a merged catalog whose digests belong to neither — while git
49
- already carries exactly the history the digests were imitating.
50
-
51
- The instruction mattered more than the mechanism did. It told a drafting agent to perform a
52
- verification step that has no implementation, before doing the work it was actually asked for. There
53
- is nothing to verify: read the catalog, answer its questions from declared facts, and let the diff be
54
- the evidence.
3
+ The engine owns the source-neutral document catalog and its sealed blueprints.
4
+ Applications contribute accepted facts and explicit decisions; they do not
5
+ copy blueprint definitions or engine digests into application specifications.
6
+
7
+ Catalog `schemaVersion: 1` is retained only for historical parsing. New
8
+ authoring uses `schemaVersion: 2`, where every document definition has exactly
9
+ one blueprint. Each blueprint and the enclosing catalog have independent
10
+ canonical digests. Both must verify before authoring.
11
+
12
+ Questions declare answer type, fact authority, sensitivity, not-applicable
13
+ posture and semantic options. Sections own visible order. Clauses own drafting
14
+ purpose, fact variables, monitored source policies, claim guards and optional
15
+ declarative inclusion conditions. Conditions inside a group are ANDed and
16
+ groups are ORed. Review checklists cover every review kind selected by the
17
+ definition's review policies.
18
+
19
+ The contract contains drafting structure, not jurisdiction-specific legal
20
+ prose, an application fact, an approval decision, a publication release or an
21
+ interaction receipt.
55
22
 
56
23
  The complete source-neutral contract is:
57
24
 
@@ -1094,28 +1061,7 @@ const AssuranceDocumentAuthorityCatalogV2BaseSchema = AssuranceDocumentAuthority
1094
1061
  });
1095
1062
  const AssuranceDocumentAuthorityCatalogV2Schema = AssuranceDocumentAuthorityCatalogV2BaseSchema.superRefine(refineAssuranceDocumentAuthorityCatalogBlueprints);
1096
1063
 
1097
- /**
1098
- * Blueprint v2 plus a closed, exactly consumed structured-value-contract registry.
1099
- *
1100
- * ASPIRATIONAL, by decision — 2026-08-31, issue #148. The shape is designed, refined and tested, and
1101
- * it has no instance and no consumer. Measured on that date, `structuredValueContracts` and
1102
- * `annexBindings` appear in exactly two files: this one, and `assurance-document-structured-contract.schemas.test.ts`.
1103
- * There is no producer, no reader, and no implementation behind
1104
- * `AssuranceDocumentStructuredContentProcessorIdentitySchema` — nothing consumes an annex-bound
1105
- * structured value. `AssuranceDocumentAuthorityCatalogV3Schema` itself is referenced twice, both in
1106
- * this file: its declaration and the union member below.
1107
- *
1108
- * So moving the engine's six document definitions to v3 would mean authoring structured value
1109
- * contracts that nothing reads, which `.claude/rules/application-creation-directive.md` forbids in
1110
- * as many words: "If we write a log or record, something or someone actually reads it — otherwise we
1111
- * do not write it." The migration was rejected on that ground, NOT on effort.
1112
- *
1113
- * WHAT WOULD CHANGE THE DECISION: a consumer for annex-bound structured values — something that
1114
- * renders or validates a document annex from a `structuredValueContract` (a processor register or a
1115
- * retention schedule as a machine-readable table rather than prose). Build that first; the catalog
1116
- * migration is then mechanical and worth doing. Until then v2/catalogVersion 5 is the current, correct
1117
- * and fully-refined shape, and v3 stays available for the author who has that consumer.
1118
- */
1064
+ /** Current authoring branch: blueprint v2 plus a closed, exactly consumed structured-value-contract registry. */
1119
1065
  export const AssuranceDocumentAuthorityCatalogV3Schema = AssuranceDocumentAuthorityCatalogCommonSchema.extend({
1120
1066
  schemaVersion: z.literal(3),
1121
1067
  catalogVersion: z.literal(6),
@@ -1179,16 +1125,7 @@ export const AssuranceDocumentAuthorityCatalogV3Schema = AssuranceDocumentAuthor
1179
1125
  }
1180
1126
  });
1181
1127
 
1182
- /**
1183
- * All three versions are ACCEPTED for authoring. v3 is available, not mandated — see the note on
1184
- * `AssuranceDocumentAuthorityCatalogV3Schema`.
1185
- *
1186
- * This comment used to read "Retained v1/v2 catalogs remain parse-only; every newly authored catalog
1187
- * uses v3/catalogVersion 6." That was false in the only way that mattered: the repository's one
1188
- * catalog — `createInitialAssuranceDocumentAuthorityCatalog()` — is v2/catalogVersion 5, so the
1189
- * sentence declared the sole live instance non-authorable. A builder who read it, opened the catalog
1190
- * and found v2 had no way to tell a stale document from a stale catalog (issue #148).
1191
- */
1128
+ /** Retained v1/v2 catalogs remain parse-only; every newly authored catalog uses v3/catalogVersion 6. */
1192
1129
  export const AssuranceDocumentAuthorityCatalogSchema = z.discriminatedUnion("schemaVersion", [
1193
1130
  AssuranceDocumentAuthorityCatalogV1Schema,
1194
1131
  AssuranceDocumentAuthorityCatalogV2Schema,
@@ -37,7 +37,6 @@ them.
37
37
  | Module command items| `frontend/src/modules/<module>/app-shell.module.frontend.ts` (`commandMenuItems` contribution)|
38
38
  | Module scope fields | `frontend/src/modules/<module>/app-shell.module.frontend.ts` (`quickSwitcherFields` contribution)|
39
39
  | Other app config | `frontend/src/config/*.config.ts` (navigation, design-system, global-views) |
40
- | Public-page identity | `frontend/src/modules-registry.frontend.ts` (`publicShellIdentityMode` — NOT `app-shell.config.ts`) |
41
40
  | Translation labels | `frontend/src/i18n/`, `frontend/src/labels/` (depending on app convention) |
42
41
  | Hotkey bindings | Resolved by the engine from `[ApplicationLevelComponentType.HOTKEY]` + per-component `openShortcut` |
43
42
 
@@ -54,7 +53,6 @@ them.
54
53
  - Adjusting user dropdown sections / avatar display
55
54
  - Toggling deferred shell surfaces (activity bar, utility panel, control panel)
56
55
  - Changing responsive policy (sidebar burger threshold, etc.)
57
- - Naming the application on its sign-in / registration pages (`publicShellIdentityMode`)
58
56
 
59
57
  ## When NOT to Use
60
58
 
@@ -137,24 +135,6 @@ dropdown rows, `presentation` for the closed control. Read
137
135
  for what the declaration wires for free (ambient scope, URL promotion,
138
136
  bi-directional mirroring, deselection).
139
137
 
140
- ### Step 3d: Name the application on its public pages
141
-
142
- Sign-in, registration and every other pre-authentication card can carry the
143
- application's mark and name. It is opt-in and off by default.
144
-
145
- It is one property, inside the existing `buildFrontendModuleConfigOverrides({ … })`
146
- call in `frontend/src/modules-registry.frontend.ts`, beside `homeDefinition` and
147
- `errorPageConfig`:
148
-
149
- `publicShellIdentityMode: PublicShellIdentityMode.BRAND_HEADER` (imported from
150
- `@wildo-ai/saas-frontend-lib`).
151
-
152
- Two things to know before you reach for `appShellConfig` instead: this is not an
153
- `ApplicationLevelComponentType` key and putting it there silently configures
154
- nothing, and the mode is a PERMISSION rather than a promise that a logo exists —
155
- an application with no generated brand shows its name alone. Read
156
- `references/framework-public-shell-identity-api.md` for the full render matrix.
157
-
158
138
  ### Step 4: Labels
159
139
 
160
140
  Any new user-visible chrome string (command names, section titles,
@@ -245,6 +225,7 @@ export const appShellConfig : AppConfiguration_Frontend['appComponentsConfigurat
245
225
  responsiveBreakpoint: ViewportBreakpoint.MOBILE,
246
226
  responsivePolicy: SidebarResponsivePolicy.BURGER,
247
227
  defaultSection: 'main',
228
+ showUncategorized: true,
248
229
  // HOME as the app's BRAND HEADER: the generated Your Application symbol + the
249
230
  // application display name, pinned above the search trigger and doubling as
250
231
  // the home button (so no separate "Home" row renders). The alternatives are
@@ -315,8 +296,12 @@ export const appShellConfig : AppConfiguration_Frontend['appComponentsConfigurat
315
296
  ],
316
297
  showOrgSwitcher: true,
317
298
  showLogout: true,
299
+ mergeSettings: false,
318
300
  },
319
301
 
302
+ [ApplicationLevelComponentType.SETTINGS_DROPDOWN]: {
303
+ mergedWith: ApplicationLevelComponentType.USER_DROPDOWN,
304
+ },
320
305
 
321
306
  [ApplicationLevelComponentType.NAVIGATION_CONTROL]: true,
322
307
 
@@ -378,12 +363,10 @@ What earns its place:
378
363
  `[ApplicationLevelComponentType.HOTKEY]: true` to the platform hotkey
379
364
  provider, which is what makes `Cmd+K` reachable.
380
365
  - `USER_DROPDOWN.sections: [UserDropdownSection.*, ...]` orders the
381
- dropdown contents. `settingsEntries: ['profile', 'security']` surfaces
382
- those Settings Hub sections inline in the dropdown, in that order; omit
383
- it (or leave it empty) to render the single "Settings" button that opens
384
- the hub at its default section. The refs name **settings-hub sections**,
385
- the same vocabulary `settings-hub.config.ts` places — never sidebar
386
- section refs. There is no separate enable flag: the list is the intent.
366
+ dropdown contents. `mergeSettings: false` keeps the settings
367
+ dropdown separate; `SETTINGS_DROPDOWN.mergedWith` then lets a
368
+ separate dropdown declare it merges into another — this is the
369
+ framework's idiom for "two surfaces, one popover".
387
370
  - Deferred surfaces (`ACTIVITY_BAR`, `UTILITY_PANEL`,
388
371
  `CONTROL_PANEL`) are explicitly set to `false`. This is **not**
389
372
  optional — explicit disable signals "we know this exists, we chose
@@ -635,7 +618,6 @@ What earns its place:
635
618
  - `references/framework-command-menu-omnibox-api.md` — command-menu policy (`CommandBarPolicy`) + omnibox `searchResources` (`CommandMenuSearchResource`) contract
636
619
  - `references/framework-app-shell-hosted-components-api.md` — menubar/sidebar `hostedComponents` entry shape (`MenubarHostedComponent` / `SidebarHostedComponent`) + per-placement `triggerWidth`
637
620
  - `references/framework-quick-switcher-scope-field-api.md` — `quickSwitcherFields` entry shape (`QuickSwitcherScopeField`), the two independent presentation axes (`optionDisplayMode` / `presentation`), and what a scope declaration wires for free
638
- - `references/framework-public-shell-identity-api.md` — naming the application on its public/auth cards: where the field goes, and what actually renders for each brand state
639
621
 
640
622
  ## Verification
641
623
 
@@ -665,7 +647,6 @@ Run from the app root:
665
647
  | Sidebar section refs are unique | `rg -oN "ref:\s+'\K[a-z-]+" frontend/src/config/app-shell.config.ts \| sort \| uniq -d` (must return empty) |
666
648
  | Command menu has an `openShortcut` | `rg -n "openShortcut:" frontend/src/config/app-shell.config.ts` |
667
649
  | Every `commands: []` entry resolves to a registered `commandId` | `rg -oN "commandId:\s+'\K[A-Z_.]+" frontend/src/config/app-shell.config.ts \| sort -u` then verify each appears in `frontend/src/commands/**/*.ts` (or the engine command registry) |
668
- | `publicShellIdentityMode` is NOT in the shell config | `rg -n "publicShellIdentityMode" frontend/src/config/app-shell.config.ts` (must return empty; it belongs in `frontend/src/modules-registry.frontend.ts`) |
669
650
  | `searchResources` implies `policy: OMNIBOX` | `rg -n "searchResources:" frontend/src/config/app-shell.config.ts` — if it matches, `rg -n "CommandBarPolicy.OMNIBOX" frontend/src/config/app-shell.config.ts` must also match |
670
651
  | Module command items are typed launcher refs | `rg -n "kind:\s+LauncherItemTargetKind\." frontend/src/modules/*/app-shell.module.frontend.ts` (each `commandMenuItems` entry must be a typed `LauncherItemTargetKind`, never a string) |
671
652
  | Hosted-component placement uses the typed enum | `rg -n "placement:\s+(Horizontal\|Vertical)Placement\." frontend/src/config/app-shell.config.ts` (every `hostedComponents` entry that sets `placement` must use `HorizontalPlacement.*` in the menubar / `VerticalPlacement.*` in the sidebar) |
@@ -696,8 +677,6 @@ spec or navigation that targets the section.
696
677
  | "Add a clear button next to the switcher so users can deselect" | The control already renders a clear affordance inside its trigger whenever a value is selected. A sibling button reads as one more chrome icon in the cluster and names no owner. |
697
678
  | "The scope field must exist on the resource schema" | It need not. With no matching schema field the framework falls back to the target resource's primary key — which is why the option-rendering mode is declared on the FIELD and cannot come from a `.foreignKeyUI(...)` decorator. |
698
679
  | "`presentation: LABEL_ABOVE` will break the menubar's alignment" | The bar has no fixed height and centre-aligns its row: it grows to fit the tallest hosted control and shorter siblings re-centre. Pick `LABEL_ABOVE` when you want the label and accept a taller bar; `ICON_LED` when you want identity at one row height. |
699
- | "`publicShellIdentityMode` is shell config, so it goes in `appShellConfig`." | It is not an `ApplicationLevelComponentType` key. Placed there it configures nothing and raises no error — those keys govern the AUTHENTICATED shell, which does not exist on a public page. It belongs in the `buildFrontendModuleConfigOverrides` call. |
700
- | "We have no logo yet, so turning on the public identity would render a broken image." | The mode is a permission, not a promise. With no generated brand the card shows the name alone, and starts showing the mark by itself once one exists — nothing to revisit. |
701
680
 
702
681
  ## Red Flags
703
682
 
@@ -713,7 +692,6 @@ spec or navigation that targets the section.
713
692
  - A scope field's `resourceType` given as a string literal — it bypasses typecheck and silently names no registered resource, so the picker loads no options (catch with the **Scope-field resource types are typed** grep — must return empty).
714
693
  - `optionDisplayMode` / `presentation` given quoted strings instead of their enums (catch with the **Presentation axes use their typed enums** grep — every extracted value must be an enum member).
715
694
  - A hand-rolled "clear scope" button authored beside the switcher — duplicates the affordance the control already renders inside its trigger (catch with the **No hand-rolled clear button** verification item; grep the app for a scope-clear handler).
716
- - `publicShellIdentityMode` appearing inside `frontend/src/config/app-shell.config.ts` — catch with the public-identity grep below
717
695
 
718
696
  ## Related Skills
719
697
 
@@ -35,6 +35,7 @@ export enum ApplicationLevelComponentType {
35
35
  * renders the same preset. Exists to allow separate config entries while reusing
36
36
  * the user dropdown component. For distinct UX, register a dedicated preset.
37
37
  */
38
+ SETTINGS_DROPDOWN = 'settings_dropdown',
38
39
  NAVIGATION_CONTROL = 'navigation_control',
39
40
  /** Mode selector — renders available `AppMode`s as selectable icons. */
40
41
  ACTIVITY_BAR = 'activity_bar',
@@ -223,34 +224,10 @@ export const AppLevelComponentConfigurationSchema = z.object({
223
224
  z.object({
224
225
  placement: z.union([ z.literal(HorizontalPlacement.START), z.literal(HorizontalPlacement.END)]),
225
226
  collapsible: z.boolean().default(true),
226
- /**
227
- * Does the sidebar start COLLAPSED (the icon rail) rather than expanded?
228
- *
229
- * This is the application's STARTING POSITION, not a lock: the rail
230
- * collapse is a per-machine user preference persisted under
231
- * `LOCAL_STORAGE_KEYS.SIDEBAR_COLLAPSED`, and a stored preference always
232
- * wins. So this answers "what does a visitor with no preference yet
233
- * see", which nothing could express before — the hydration fell back to
234
- * `false`, making EXPANDED the only reachable default for every
235
- * application.
236
- *
237
- * Pairs with the theme's `SidebarCompactLabelMode`: `ICON_AND_LABEL`
238
- * renders a wrapping label under each icon in the collapsed rail, so a
239
- * rail-first shell stays readable rather than becoming a column of
240
- * unlabelled glyphs.
241
- *
242
- * OPTIONAL rather than `.default(false)` for the reason `homeDisplayMode`
243
- * gives one line below: a Zod default makes the key REQUIRED in the
244
- * inferred authoring type, forcing every preset and application config to
245
- * restate an opinion it does not have. The framework default (expanded —
246
- * the behavior every app had before this axis existed) is applied in
247
- * `useSidebarBehavior`, which must resolve it there regardless because a
248
- * sidebar authored as plain `true` never reaches this object branch.
249
- */
250
- defaultCollapsed: z.boolean().optional(),
251
227
  responsiveBreakpoint: z.enum(ViewportBreakpoint).default(ViewportBreakpoint.MOBILE),
252
228
  responsivePolicy: z.enum(SidebarResponsivePolicy).default(SidebarResponsivePolicy.BURGER),
253
229
  defaultSection: z.string().default("main"),
230
+ showUncategorized: z.boolean().default(true),
254
231
  /**
255
232
  * How the sidebar surfaces HOME — hidden, the pinned brand header
256
233
  * (app symbol + name above the search trigger), or a "Home" navigation
@@ -396,12 +373,16 @@ export const AppLevelComponentConfigurationSchema = z.object({
396
373
  sections: z.array(z.enum(UserDropdownSection)).optional(),
397
374
  showOrgSwitcher: z.boolean().default(true),
398
375
  showLogout: z.boolean().default(true),
399
- /**
400
- * Settings-hub section refs surfaced inline in the dropdown, in order.
401
- * Empty or omitted renders the single "Settings" button. Names the
402
- * SETTINGS vocabulary directly — never a sidebar section ref.
403
- */
404
- settingsEntries: z.array(z.string()).optional(),
376
+ mergeSettings: z.boolean().default(false),
377
+ /** Sidebar section ref for the single settings block merged into the dropdown when `mergeSettings` is true. */
378
+ settingsSectionRef: z.string().optional(),
379
+ }),
380
+ ]).default(true),
381
+
382
+ [ApplicationLevelComponentType.SETTINGS_DROPDOWN]: z.union([
383
+ z.boolean().default(true),
384
+ z.object({
385
+ mergedWith: z.literal(ApplicationLevelComponentType.USER_DROPDOWN),
405
386
  }),
406
387
  ]).default(true),
407
388
 
@@ -36,7 +36,7 @@ new top-level keys breaks the CSS generator.
36
36
  | Surface | Glob (relative to app root) |
37
37
  |---------------------|------------------------------------------------------------------------------------------|
38
38
  | Design system config | `frontend/src/config/design-system.config.ts` |
39
- | First-paint theme behavior | `frontend/index.html` (head script + style layer), `frontend/src/browser-bootstrap/app-shell-bootstrap.ts` |
39
+ | First-paint theme behavior | `frontend/index.html`, `frontend/src/browser-bootstrap/**/*theme*` |
40
40
  | Generated CSS | App-specific (typically `frontend/src/styles/design-tokens.css` or auto-injected) |
41
41
  | Component theme consumption | `frontend/src/components/**/*.tsx` (via Tailwind / CSS variables) |
42
42
  | Companion design-system snapshot | Re-extracted via `wildo dev design-tokens generate` / app's equivalent CLI |
@@ -104,25 +104,6 @@ own the palette. In `frontend/index.html`, use
104
104
  for the resolved mode. Never copy `oklch`, hex, or RGB token values into HTML
105
105
  or bootstrap TypeScript; duplicated tints drift when the design system changes.
106
106
 
107
- **The resolver is the framework's, not yours.**
108
- `frontend/src/browser-bootstrap/app-shell-bootstrap.ts` calls `initializeTheme()`
109
- from `@wildo-ai/saas-frontend-lib/browser-bootstrap`, which reads the
110
- `theme.preference` browser-storage value (`LIGHT` / `DARK` / `AUTO`, where an
111
- explicit choice beats the operating system and anything else follows
112
- `prefers-color-scheme`) and stamps `data-theme` plus the `dark` class on
113
- `<html>`. Do not re-implement it locally and do not read that key yourself to
114
- decide colors — the CSS already branches on what it stamped.
115
-
116
- **Editing `frontend/index.html` — keep the head script where it is.** It is easy
117
- to move or drop while adding a favicon, meta tags or an analytics snippet, and
118
- the consequence is larger than a flicker: the mounted UI runtime that would
119
- otherwise set the theme lives BELOW the application-config bootstrap, so the
120
- loading screen and the initialization-error screen render above it. Without the
121
- render-blocking head script those two paint LIGHT on a dark desktop — and when
122
- the backend never answers, the error screen is the whole session rather than a
123
- moment on the way to the app. Keep `blocking="render"` on the script tag, keep
124
- it in `<head>`, and keep it ahead of the app entry script.
125
-
126
107
  ### Step 5: Configure material cost at the theme boundary
127
108
 
128
109
  When a theme uses structured materials, read
@@ -376,7 +357,6 @@ What is **not** in this block (and shouldn't be):
376
357
  - `references/framework-material-runtime-policy-api.md` — source-backed priority and aggregate document-budget contract
377
358
  - `references/surface-policy-authoring.md` — app-facing `surfacePolicies`, `SHELL` landmark opt-in/opt-out, active slot and selector-channel status
378
359
  - `references/framework-surface-policy-api.md` — source-backed Surface Policy family and default contracts
379
- - `references/loading-placeholder-authoring.md` — the skeleton fill a theme must not choose freely, and why a collection repeats its silhouette
380
360
 
381
361
  ## Verification
382
362
 
@@ -402,7 +382,6 @@ Run from the app root:
402
382
  | Theme is declared | `rg -n "theme:\s+" frontend/src/config/design-system.config.ts` |
403
383
  | Every background token has a foreground pair (sample) | `rg -oN "'\K[a-z-]+(?=':)" frontend/src/config/design-system.config.ts \| rg -v "foreground" \| sort -u` |
404
384
  | **No string-literal hex / rgb in the config** (must return empty) | `rg -n "'#[0-9a-fA-F]{3,8}'" frontend/src/config/design-system.config.ts` |
405
- | **The head theme bootstrap is present and render-blocking** | `rg -n 'blocking="render"' frontend/index.html` (must match; without it the loading and error screens paint light) |
406
385
  | **No duplicated first-paint palette literals** (must return empty) | `rg -n "oklch\\(|#[0-9a-fA-F]{3,8}|rgba?\\(" frontend/index.html frontend/src/browser-bootstrap` |
407
386
  | Generated CSS exists | `ls -1 frontend/src/styles/design-tokens.css 2>/dev/null \|\| ls -1 frontend/dist/design-tokens.css 2>/dev/null` |
408
387
  | Material profiles and aggregate policy stay theme-owned | `rg -n "materials:|materialRuntimePolicy:|priority:" frontend/src/config/design-system.config.ts` |
@@ -433,7 +412,6 @@ the file and silently loses tokens added in upgrades.
433
412
  - Missing `...DEFAULT_DESIGN_SYSTEM_SOURCE_CONFIG.<bucket>.<mode>` spread (catch with the **Default config is spread at each nested layer** grep — must match every nested `light` / `dark` block).
434
413
  - Hex / RGB color literal where `oklch` is expected (catch with the **No string-literal hex / rgb** grep — must return empty).
435
414
  - Concrete palette literals in `frontend/index.html` or the head bootstrap (catch with the **No duplicated first-paint palette literals** grep — must return empty).
436
- - The head theme bootstrap moved out of `<head>`, stripped of `blocking="render"`, or removed while editing `frontend/index.html` (catch with the **head theme bootstrap is present and render-blocking** grep — must match).
437
415
  - New top-level key (`brand`, `extras`, etc.) outside the schema (catch by typecheck — `defineDesignSystemConfig` will reject).
438
416
  - Optical constants repeated in components instead of `theme.materials` (catch with the **Material profiles and aggregate policy stay theme-owned** grep and inspect any component-local hits).
439
417
  - Glass profiles without a semantic priority or a glass theme without one aggregate runtime policy (catch with the same material-policy grep and schema validation).
@@ -436,29 +436,20 @@ export interface A11yPolicy {
436
436
  * disable). When a finite tier is set the surface is also centered in its
437
437
  * container (`margin-inline: auto`).
438
438
  */
439
- export const RESPONSIVE_MAX_WIDTH_VALUES = [
440
- 'full',
441
- 'sm',
442
- 'md',
443
- 'lg',
444
- 'xl',
439
+ export type ResponsiveMaxWidth =
440
+ | 'full'
441
+ | 'sm'
442
+ | 'md'
443
+ | 'lg'
444
+ | 'xl'
445
445
  // Reading-measure cap (~42rem) for single-column FORM / field stacks (T4c),
446
446
  // so detail/settings forms stop stretching edge-to-edge inside a wide content
447
447
  // zone. Wider than the component tiers (`sm`–`xl`, dialog-scale) but far tighter
448
448
  // than `content`/`centered-readable`. Retune via `--measure-max-width`.
449
- 'measure',
450
- 'centered-readable',
451
- 'content',
452
- 'none',
453
- ] as const;
454
-
455
- /**
456
- * The RUNTIME source for the width vocabulary, so a schema that must validate a declared tier can
457
- * name it instead of re-listing the members. It became necessary the moment width stopped being a
458
- * surface-only concern: the zone content boundary, `DisplayLayout` and `FormLayout` all select a tier
459
- * now, and a second hand-written list of the same nine values is a list that drifts.
460
- */
461
- export type ResponsiveMaxWidth = (typeof RESPONSIVE_MAX_WIDTH_VALUES)[number];
449
+ | 'measure'
450
+ | 'centered-readable'
451
+ | 'content'
452
+ | 'none';
462
453
 
463
454
  export type MobileShape = 'inline' | 'drawer' | 'sheet';
464
455