@wildo-ai/framework-knowledge 1.1.8 → 1.1.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (480) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
  5. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
  7. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  8. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
  9. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  10. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
  11. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
  12. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
  14. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
  15. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +20 -4
  17. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  18. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  19. package/dist/esm/framework-knowledge.definitions.js +95 -5
  20. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  21. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  22. package/dist/esm/index.d.ts.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  24. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
  28. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +41 -3
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +175 -14
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  40. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
  43. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
  45. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +4 -2
  47. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +90 -13
  49. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
  51. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
  53. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
  55. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
  57. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  59. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  61. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
  63. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
  65. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  69. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  72. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
  74. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
  78. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +91 -43
  80. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +41 -0
  82. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +43 -0
  84. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
  85. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +200 -0
  86. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
  87. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +203 -0
  88. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
  89. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +81 -0
  90. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
  91. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +93 -0
  92. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
  93. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
  94. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  95. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
  96. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  97. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
  99. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
  101. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
  103. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
  105. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
  113. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  116. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
  117. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  118. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  121. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  123. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  124. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  125. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  126. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
  127. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  128. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
  129. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  130. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +71 -2
  131. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  132. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  133. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  134. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  135. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
  137. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  138. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
  139. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  140. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
  141. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  142. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
  143. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  144. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
  146. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +41 -17
  148. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  149. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  150. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  151. package/dist/knowledge/manifest.json +8 -8
  152. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
  153. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  154. package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
  155. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
  156. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  157. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  158. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +261 -34
  159. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
  160. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -59
  161. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  162. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
  163. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
  164. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
  165. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
  166. package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
  167. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
  168. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  169. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  170. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +129 -17
  171. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
  172. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
  173. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
  174. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
  175. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
  176. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  177. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
  178. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
  179. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
  180. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  181. package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
  182. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
  183. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  184. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  185. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  186. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  187. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +75 -37
  188. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
  189. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
  190. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -0
  191. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
  192. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
  193. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +99 -0
  194. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
  195. package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
  196. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -0
  197. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  198. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  199. package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
  200. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
  201. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  202. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  203. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
  204. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
  205. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
  206. package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
  207. package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
  208. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
  209. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  210. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  211. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  212. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  213. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  214. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
  215. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  216. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  217. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
  218. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  219. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  220. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  221. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  222. package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
  223. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
  224. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
  225. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +29 -0
  226. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
  227. package/dist/knowledge/references/brand.name-choice.config.md +144 -0
  228. package/dist/knowledge/references/brand.name-screening.config.md +308 -0
  229. package/dist/knowledge/references/build-plan.task-graph.config.md +119 -11
  230. package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
  231. package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
  232. package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
  233. package/dist/knowledge/references/capability-composition.config.md +67 -4
  234. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  235. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  236. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  237. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
  238. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  239. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
  240. package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
  241. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  242. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  243. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  244. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  245. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  246. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  247. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  248. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
  249. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  250. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  251. package/dist/knowledge/references/experience-plan.config.md +60 -7
  252. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  253. package/dist/knowledge/references/market.snapshot.validation.md +1 -1
  254. package/dist/knowledge/references/placement-plan.config.md +43 -0
  255. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  256. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  257. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  258. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  259. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  260. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  261. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  262. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  263. package/dist/knowledge/references/saas.backend.email.send.md +77 -0
  264. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  265. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
  266. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  267. package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
  268. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  269. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
  270. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
  271. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
  272. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
  273. package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
  274. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
  275. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
  276. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  277. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
  278. package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
  279. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
  280. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
  281. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
  282. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  283. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  284. package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
  285. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
  286. package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
  287. package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
  288. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  289. package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
  290. package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
  291. package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
  292. package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
  293. package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
  294. package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
  295. package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
  296. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  297. package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
  298. package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
  299. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  300. package/dist/knowledge/references/website-plan.config.md +26 -0
  301. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
  302. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
  303. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  304. package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
  305. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
  306. package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
  307. package/dist/knowledge/references/zod.factories.code.md +1 -0
  308. package/dist/knowledge/references/zod.factories.duration.md +1 -0
  309. package/dist/knowledge/references/zod.factories.money.md +1 -0
  310. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  311. package/dist/knowledge/registries/framework-topics.json +374 -1
  312. package/dist/knowledge/registries/playbooks.json +76 -28
  313. package/dist/knowledge/registries/source-tags.json +1513 -898
  314. package/dist/knowledge/rules/live-context-door.md +5 -2
  315. package/dist/knowledge/skills/INDEX.md +5 -2
  316. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  317. package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
  318. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  319. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  320. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  321. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
  322. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
  323. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  324. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
  325. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
  326. package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
  327. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
  328. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
  329. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
  330. package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
  331. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
  332. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
  333. package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
  334. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  335. package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
  336. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
  337. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
  338. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
  339. package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
  340. package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
  341. package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
  342. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  343. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
  344. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  345. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  346. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  347. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
  348. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
  349. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
  350. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
  351. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
  352. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
  353. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
  354. package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
  355. package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
  356. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
  357. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
  358. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
  359. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
  360. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  361. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  362. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  363. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  364. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  365. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
  366. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
  367. package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
  368. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
  369. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  370. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  371. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  372. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  373. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  374. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  375. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  376. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  377. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
  378. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
  379. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  380. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
  381. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  382. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
  383. package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
  384. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  385. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
  386. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
  387. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
  388. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
  389. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  390. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
  391. package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
  392. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
  393. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
  394. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
  395. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
  396. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
  397. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  398. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
  399. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
  400. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  401. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
  402. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
  403. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
  404. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
  405. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
  406. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  407. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
  408. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
  409. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
  410. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
  411. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  412. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  413. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  414. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
  415. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
  416. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
  417. package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
  418. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  419. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
  420. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  421. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
  422. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
  423. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
  424. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  425. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
  426. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  427. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
  428. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  429. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  430. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  431. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  432. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  433. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  434. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
  435. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  436. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  437. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
  438. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
  439. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
  440. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
  441. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
  442. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
  443. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
  444. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
  445. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
  446. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
  447. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
  448. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
  449. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
  450. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
  451. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
  452. package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
  453. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
  454. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
  455. package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
  456. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
  457. package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
  458. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
  459. package/dist/knowledge/skills/website-section-faq/SKILL.md +21 -1
  460. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
  461. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +21 -1
  462. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
  463. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +25 -2
  464. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
  465. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
  466. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
  467. package/dist/knowledge/skills/website-section-hero/SKILL.md +33 -10
  468. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
  469. package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
  470. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
  471. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +27 -2
  472. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
  473. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +16 -4
  474. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
  475. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
  476. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
  477. package/dist/knowledge/topic-index.json +1590 -292
  478. package/dist/tsconfig.build.tsbuildinfo +1 -1
  479. package/dist/tsconfig.tsbuildinfo +1 -1
  480. package/package.json +4 -4
@@ -97,10 +97,31 @@ When you change `wildo.saas.config.ts` or infrastructure config files, update
97
97
  task instead of silently skipping specification review.
98
98
 
99
99
 
100
- ### Step 4: Verify
101
-
102
- Run CLI status or boot the app; ensure all listed modules / minions /
103
- workers resolve from disk and the requested provider scopes materialize.
100
+ ### Step 4: Apply the declaration, then verify
101
+
102
+ The running application does not read `wildo.saas.config.ts`. It reads the
103
+ copy apps-manager STORED at registration, and that copy covers
104
+ `engineCapabilities`, `providers`, `providerConfigurations`,
105
+ `frontendServices`, `minions`, `workers`, `organizationTypes`,
106
+ `systemsOfRecord` and the app's display identity. An edit to any of them does
107
+ nothing until it is applied:
108
+
109
+ - `wildo local dev` applies it on every start (registration reapplies the
110
+ declaration) and names each slice it applied, so restarting the stack is
111
+ enough. It is the step to use after adding or removing a minion or worker:
112
+ registration is what mints and revokes their credentials.
113
+ - `wildo config reapply-declaration` applies it to a stack that is already
114
+ running. Add `--dry-run` to see what it would change. It changes no
115
+ infrastructure, and no credential except one: a changed `minions` set
116
+ reconciles the minions' backing-service credentials, so restart the minions
117
+ afterwards. It does not mint a new worker's credential.
118
+ - `wildo config sync` also applies it, but it also regenerates env and
119
+ provider artifacts, so do not reach for it just to apply a declaration edit.
120
+
121
+ `wildo config validate` (or `--domain declaration`) and `wildo local doctor`
122
+ both report a stored config that is behind the file, naming the slices.
123
+ Then ensure all listed modules / minions / workers resolve from disk and the
124
+ requested provider scopes materialize.
104
125
 
105
126
  ## Worked Example
106
127
 
@@ -195,13 +216,13 @@ What is **not** in this block (and shouldn't be):
195
216
  - `references/framework-connection-target-credentials.md` — which third-party identity a provider call acts as, how a tenant supplies its OWN credential, and why nothing is ever substituted for a missing one
196
217
  - `references/framework-content-security-policy-api.md` — the `csp` block on any frontend: opt-in by absence, the generated artifact is the only one read, and why report-only without a collector does nothing
197
218
  - `references/framework-value-moments-api.md` — `analytics.valueMoments`: why `role` changes three things at once, and why a declared moment with analytics off is evaluated by nothing
198
- - `references/framework-audit-trail-config-api.md` — the `auditTrail` block: why `archiveAfterDays` is the opt-in and why setting it never shrinks the primary store
219
+ - `references/framework-audit-trail-config-api.md` — the `auditTrail` block: why `archiveAfterDays` is the opt-in and why setting it never shrinks the primary store, and how `applicationEventTypes` classifies and words the application's own audit event types
199
220
  - `references/framework-systems-of-record-api.md` — `systemsOfRecord`: declaring a deployment your application reads its OWN rows out of, why it is not a provider, and the three files its name, address and credential live in; an instance's `facetAugmentations` opts it into packages that ADD a partition or a credential kind to its vendor's facet — see `resource-external-data`'s `references/facet-augmentations.md`
200
221
  - `providers.packages` — the provider packages discovery does not walk by name (another scope's, or an own-scope one not named `provider-*`) that the application admits to discovery; listing activates nothing, and `wildo config sync` refuses a listing that admits nothing — see `provider-backend-package`'s `references/framework-provider-package-allow-list-api.md`
201
222
  - `references/saas-config-scope.md` — what belongs in root SaaS config
202
223
  - `references/framework-wildo-saas-config-api.md` — `WildoSaasConfigSchema` / inferred types
203
224
  - `references/framework-provider-capabilities-api.md` — engine slots and provider capability vocabulary, including durable email selection
204
- - `references/compliance-declarations.md` — the six compliance declarations, and why an ABSENT one is never a negative answer
225
+ - `references/compliance-declarations.md` — the six compliance declarations, why an ABSENT one is never a negative answer, and the legal notice (imprint) projected from the operator's identity
205
226
 
206
227
  ## Verification
207
228
 
@@ -215,6 +236,8 @@ What is **not** in this block (and shouldn't be):
215
236
  and each minion and worker that should be traceable
216
237
  - [ ] `services` keys referenced by `modules[*].services` actually exist in `services`
217
238
  - [ ] Companion sees the updated module list (re-run companion introspection)
239
+ - [ ] The stored config matches the file: `wildo config validate --domain declaration`
240
+ reports no stale slice (or the stack was restarted with `wildo local dev`)
218
241
  - [ ] No compliance declaration carries an invented value — every one is either the operator's
219
242
  own answer or absent (absent is reported as an open gap; invented is published as fact)
220
243
 
@@ -224,18 +247,33 @@ Run from the app root:
224
247
 
225
248
  | Invariant | Command |
226
249
  |--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
227
- | Modules listed in config | `rg -oN "^\s+'([a-z-]+)':\s*\{\s*$" wildo.saas.config.ts` |
228
- | Module folders on disk | `ls -1 shared-lib/src/modules/` |
229
- | **Module entries ↔ module folders agree** (must return empty) | `comm -3 <(rg -oN "^\s+'\K[a-z-]+(?='\s*:\s*\{)" wildo.saas.config.ts \| sort -u) <(ls -1 shared-lib/src/modules/ \| sort -u)` |
230
- | Minion / worker paths exist | `rg -oN "path:\s+'\K[^']+" wildo.saas.config.ts \| while read p; do test -d "$p" \|\| echo "MISSING: $p"; done` |
231
- | Each engine capability declares `enabled:` | `rg -n "EngineCapability\.[A-Z_]+\]:\s*\{" wildo.saas.config.ts \| wc -l` then `rg -c "enabled:" wildo.saas.config.ts` |
232
- | **No placeholder in a compliance declaration** (must return empty) | `rg -n "TODO\|TBD\|PLACEHOLDER\|example\.com\|Acme" wildo.saas.config.ts` |
250
+ | **Module entries ↔ module folders agree** (must return empty) | see the commands below the table |
251
+ | Minion / worker paths exist | see the commands below the table |
252
+ | Each engine capability declares `enabled:` | run the commands below the table, then `rg -c "enabled:" wildo.saas.config.ts` |
253
+ | **No placeholder in a compliance declaration** (must return empty) | see the commands below the table |
233
254
  | Which provider is selected for telemetry | `rg -n "OBSERVABILITY_TELEMETRY\]:\s*\{" -A2 wildo.saas.config.ts` |
234
255
  | **Which runtimes declare it** (compare against the runtimes that should be traceable) | `rg -n "^\s+<telemetryProviderRef>:\s*\{" wildo.saas.config.ts` |
256
+ | **Stored config matches the file** (no stale slice reported) | `wildo config validate --domain declaration` |
257
+
258
+ ```bash
259
+ # Module entries ↔ module folders agree (must return empty) — reads only the modules block (inline, or the
260
+ # `applicationModules` constant in the same file); a module's folder lives under each service it declares, so a
261
+ # frontend-only module has no shared-lib folder
262
+ comm -3 <(awk '/^ *(modules: |export const applicationModules = )\{/{f=1;d=0} f{if(d==1&&match($0,/^ *\047?[a-z][a-z0-9-]*\047? *: *\{/)){k=$0;sub(/^ *\047?/,"",k);sub(/\047? *:.*/,"",k);print k} d+=gsub(/\{/,"{")-gsub(/\}/,"}"); if(d<=0)exit}' wildo.saas.config.ts | sort -u) <(ls -1 shared-lib/src/modules frontend/src/modules backend-api/src/modules 2>/dev/null | grep -E '^[a-z][a-z0-9-]*$' | sort -u)
263
+
264
+ # Minion / worker paths exist
265
+ rg -P -oN "path:\s+'\K[^']+" wildo.saas.config.ts | while read p; do test -d "$p" || echo "MISSING: $p"; done
266
+
267
+ # Each engine capability declares `enabled:`
268
+ rg -n "EngineCapability\.[A-Z_]+\]:\s*\{" wildo.saas.config.ts | wc -l
269
+
270
+ # No placeholder in a compliance declaration (must return empty)
271
+ rg -n "TODO|TBD|PLACEHOLDER|example\.com|Acme" wildo.saas.config.ts
272
+ ```
235
273
 
236
- The third invariant (modules ↔ folders) is the high-signal one — a
237
- module declared in config without a matching folder breaks `pnpm dev`
238
- silently in some pipelines and blocks others on startup.
274
+ The modules ↔ folders invariant is the high-signal one: it names a module
275
+ the config declares with no code under any service, and a module folder no
276
+ declaration names.
239
277
 
240
278
  The last two are a READ, not a pass/fail: substitute the ref the first
241
279
  returns into the second, then compare the runtimes it lists against the
@@ -251,6 +289,7 @@ missing it does not appear until a token is provisioned.
251
289
  | "Comment out a module temporarily" | Dead entries confuse tooling and the spec layer; remove the entry or gate the module through an explicit module-owned product feature. |
252
290
  | "Inline the AI provider key here" | Provider secrets MUST stay in secrets/env. Config only declares **policy** (which providers are allowed); the credentials sit in `wildo-secrets` or env. |
253
291
  | "Skip `dataServices.*` prefixes — defaults work" | Defaults collide across apps in shared infra; the prefix declaration is what isolates state per app/environment. |
292
+ | "`wildo config validate` passed, so the capability is on" | Validation checks the file. The runtime reads the declaration apps-manager stored, which only changes when it is applied (`wildo local dev`, or `wildo config reapply-declaration`). The `declaration` domain of `validate` says whether it has been. |
254
293
  | "I'll add a new key not in the schema, the framework will pick it up" | The schema is the contract — unknown keys are dropped or error. Add the field through the framework first if a new dimension is needed. |
255
294
  | "Put a placeholder entity name in now and fix it later" | A produced document quotes it as fact. An absent declaration is reported as an open gap a reader can see; an invented one is published. Leave it out. |
256
295
  | "The identity needs every field, so I'll wait until I have them all" | Every part is independently declarable — record the half you know. Waiting is how the answer ends up edited into a document that a regeneration then replaces. |
@@ -264,6 +303,8 @@ missing it does not appear until a token is provisioned.
264
303
  - Module name in config with no folder on disk (catch with the **modules ↔ folders agree** comm invariant — must return empty).
265
304
  - Minion / worker entry pointing at a non-existent `path` (catch with the **Minion / worker paths exist** check — must return no `MISSING:` lines).
266
305
  - Engine capability block lacking `enabled:` (catch with the **Each engine capability declares `enabled:`** check — counts must match).
306
+ - An `engineCapabilities` (or provider, minion, worker) edit that "does nothing" at runtime: the
307
+ stored declaration was not applied (catch with the **Stored config matches the file** check above).
267
308
  - Frontend service with no `frontendType` (implicit defaults are framework-version-dependent; declare it explicitly).
268
309
  - A minion or worker expected to be traceable whose scope omits the selected
269
310
  `OBSERVABILITY_TELEMETRY` provider (catch with the **which runtimes declare it** read above —
@@ -2,7 +2,8 @@
2
2
 
3
3
  Six optional declarations sit in the root SaaS config alongside the composition keys. They answer a
4
4
  different question from the rest of the file — not *"what am I made of"* but *"what is legally true of
5
- this application"* — and a produced privacy notice or terms document quotes them.
5
+ this application"* — and a produced privacy notice or terms document quotes them. The application's legal
6
+ notice (imprint) is projected from `operatorComplianceIdentity` too; see the section on it below.
6
7
 
7
8
  Read this before adding or editing any of them.
8
9
 
@@ -42,10 +43,23 @@ blocked.
42
43
  operatorComplianceIdentity: {
43
44
  legalEntityName: 'Wonder Software SAS',
44
45
  registeredAddress: '1 rue de la Paix, 75002 Paris, France',
45
- // privacyContact, roleAllocations and lawfulBases may all follow later.
46
+ // privacyContact, roleAllocations, lawfulBases and hostingRegions may all follow later.
46
47
  },
47
48
  ```
48
49
 
50
+ `hostingRegions` says where the operator's OWN infrastructure hosts the data (`['France (eu-west-3)']`).
51
+ It is the operator's region, not a vendor's: a provider's region is `providerComplianceChoices.<ref>.processingRegion`,
52
+ and a hosting company that processes on your behalf also belongs in the processor register.
53
+
54
+ To see every part still owed, with the rest of what stands between the application and launch:
55
+
56
+ ```bash
57
+ wildo context launch-blockers # each open decision, where it is decided, what settles it
58
+ wildo context launch-blockers --json # the same list as a document
59
+ ```
60
+
61
+ It reports and never fails: a missing part is marked, and declaring it removes it on the next read.
62
+
49
63
  What the schema still refuses, and why it is not a contradiction: it refuses an **incoherent** answer,
50
64
  never an **absent** one.
51
65
 
@@ -73,6 +87,55 @@ obligations for one of the two populations.
73
87
  Art. 6(1) basis the processing rests on, are different questions. Declaring a gate does not make
74
88
  consent the basis for anything.
75
89
 
90
+ ## The legal notice (imprint) — owed where the operator is ESTABLISHED
91
+
92
+ A service provider established in the EU, the EEA, the UK or Switzerland must publish its identity where anyone can
93
+ reach it in one step (Directive 2000/31/EC Art. 5(1); in Germany § 5 DDG, the Impressum; in the UK the E-Commerce
94
+ Regulations 2002, reg. 6; in Switzerland UWG Art. 3 Abs. 1 Bst. s). Other countries' rules are not modelled, so for an
95
+ establishment elsewhere the framework publishes no notice: check your own law. The markets you sell into do not decide it:
96
+ an operator established in France owes one, an operator established only in the United States does not, whichever
97
+ countries either serves. So the application reads one field:
98
+
99
+ ```ts
100
+ operatorComplianceIdentity: {
101
+ establishmentJurisdiction: 'fr', // a jurisdiction code, the place the operator is established
102
+ legalEntityName: 'Wonder Software SAS',
103
+ registeredAddress: '1 rue de la Paix, 75002 Paris, France',
104
+ generalContact: { email: 'contact@wonder.example' }, // phone optional; NOT the privacy contact
105
+ // Declare these only where they apply to the operator:
106
+ legalForm: 'SAS',
107
+ authorizedRepresentatives: ['Jeanne Martin, Présidente'],
108
+ tradeRegister: { register: 'RCS Paris', registrationNumber: '123 456 789' },
109
+ vatIdentificationNumber: 'FR12123456789',
110
+ // supervisoryAuthority, regulatedProfession: only for an activity that needs them
111
+ // Germany (§ 5 DDG) also: shareCapital { amount, outstandingContributions? } only if you state your capital,
112
+ // economicIdentificationNumber if you have one, and inLiquidation: true while the company is being wound up.
113
+ },
114
+ ```
115
+
116
+ Then project it into the running application and keep it current:
117
+
118
+ ```bash
119
+ wildo config legal-notice # writes backend-api/src/legal-notice.generated.ts
120
+ wildo config legal-notice --check # fails when the module is out of date
121
+ wildo config validate # the legal-notice domain: current, and composed as compliance.legalNotice
122
+ ```
123
+
124
+ `saas-config.backend.ts` composes the generated constant as `compliance.legalNotice`. The application then serves
125
+ the notice at `/legal-notice`, and a marketing website built from the same config links it from its footer.
126
+ The website decides from `wildo.saas.config.ts` at build time, while the page reads the generated module. Re-run
127
+ `wildo config legal-notice` after every change to the identity, or the footer can link to a page that is out of date.
128
+ `wildo config validate` fails until you do.
129
+
130
+ - Owed: the operator's name, its geographic address and a direct contact. Each one left undeclared appears on the
131
+ page as **not yet declared** and in `wildo context launch-blockers`. Never type a placeholder in its place: the page
132
+ publishes it as fact.
133
+ - Conditional: legal form, representatives, share capital, trade register, VAT number, economic identification number,
134
+ supervisory authority, regulated profession, liquidation.
135
+ Only you know whether each applies, so the page shows the ones you declare and nothing marks the others.
136
+ - `establishmentJurisdiction` undeclared means **unknown**, never "not owed". The page says no notice is published, and
137
+ the launch list names the field until you declare it.
138
+
76
139
  ## `operatingJurisdictions` — and the warning you must not silence
77
140
 
78
141
  ```ts
@@ -1,7 +1,8 @@
1
1
  # Framework Audit-Trail Config API
2
2
 
3
- The `auditTrail` block on the shared application configuration — one operator-tunable field, and two
4
- ways to misread it.
3
+ The `auditTrail` block on the application configuration (authored in the backend configuration). Its fields
4
+ are listed in the contract at the end. This page covers the two that are easiest to misread: the archival horizon
5
+ and the application's own audit event types.
5
6
 
6
7
  ## `archiveAfterDays` is the opt-in, and it deletes nothing
7
8
 
@@ -26,6 +27,20 @@ is a smaller primary store, this is not the mechanism.
26
27
  - An application turning this on after it already has aged data seeds the archive with a one-off run
27
28
  at a wider look-back.
28
29
 
30
+ ## `applicationEventTypes` classifies YOUR event types, never the framework's
31
+
32
+ Every event type an operation records with `logEvent` that is not a framework type is the application's own. Declare
33
+ each one here, keyed by its exact `eventType` string, with a `category` and a `severity`. Rows of that type are then
34
+ recorded and routed to the SIEM with that classification, and the labelling pipeline plans its word
35
+ (`system_enums.CoreAuditableEventType.<eventType>`). An undeclared type is recorded as `data_access` / `info` and shown
36
+ by its raw value.
37
+
38
+ - Type the declaration as total over your event-type enum (`satisfies Record<Your_AuditEventType, …>`), so an event
39
+ type added without a classification fails to compile. The worked example in
40
+ `backend-custom-operation/references/framework-audit-log-event-api.md` does this.
41
+ - Naming a framework event type is refused at startup: the engine's classification of its own events is authoritative.
42
+ - The key must use only letters, digits, `_` and `-`, because it becomes the last segment of a label key.
43
+
29
44
  ## Audit-Trail Config
30
45
 
31
46
  ## Import Origins
@@ -117,6 +132,19 @@ export enum AuditApplicationReadAccess {
117
132
  INDEPENDENT_APPROVAL = 'independent-approval',
118
133
  }
119
134
 
135
+ /**
136
+ * How one of the application's OWN audit event types is classified: the activity it records and the attention it
137
+ * deserves. The same two vocabularies the engine uses for its event types.
138
+ */
139
+ export const ApplicationAuditEventTypeDeclarationSchema = z.strictObject({
140
+ /** What kind of activity the event records. A business event (an invoice issued, a quote sent) is `data_access`. */
141
+ category: z.enum(AuditEventCategory),
142
+ /** How much attention it deserves: `info` is evidence, `warning` is worth review, `critical` is meant for whoever handles security incidents. A SIEM destination's event filter is what routes on it. */
143
+ severity: z.enum(AuditEventSeverity),
144
+ });
145
+
146
+ export type ApplicationAuditEventTypeDeclaration = z.infer<typeof ApplicationAuditEventTypeDeclarationSchema>;
147
+
120
148
  export const AuditTrailConfigSchema = z.object({
121
149
  /**
122
150
  * Application audit viewer admission. Omitted means ROLE_BASED in every environment.
@@ -183,7 +211,39 @@ export const AuditTrailConfigSchema = z.object({
183
211
  * addresses are admitted, never whether the admitted address is the one connected to.
184
212
  */
185
213
  allowPrivateNetworkSiemCollectors: z.boolean().optional(),
214
+
215
+ /**
216
+ * The application's OWN audit event types — the `eventType` values it passes to `AuditLogsBackendService.logEvent`
217
+ * — each with its classification. Keyed by the exact `eventType` string.
218
+ *
219
+ * ── What declaring one changes ─────────────────────────────────────────────
220
+ * - Every row of that type is recorded with the declared `eventCategory` and `severity`, and the SIEM export
221
+ * routes and filters by them. An UNDECLARED application type is recorded as `data_access` / `info`, whatever
222
+ * the event is — a business-critical event is then indistinguishable from routine reads.
223
+ * - The labelling pipeline plans a word for it (`system_enums.CoreAuditableEventType.<eventType>`, the open
224
+ * vocabulary the audit row's `eventType` field names), so the audit views show "Quote issued" instead of
225
+ * `SALES_QUOTE_ISSUED`. Run label generation after adding one.
226
+ *
227
+ * ── What it cannot do ──────────────────────────────────────────────────────
228
+ * It cannot reclassify a FRAMEWORK event type: the engine's own classification is authoritative, and naming one of
229
+ * its event types here is refused at startup. The key must be usable as the last segment of a label key (letters,
230
+ * digits, `_`, `-`).
231
+ *
232
+ * Severity is a property of the event TYPE. A row's `riskLevel` (supplied per emission) is a separate signal and
233
+ * does not change it.
234
+ *
235
+ * @example
236
+ * auditTrail: {
237
+ * applicationEventTypes: {
238
+ * SALES_QUOTE_ISSUED: { category: AuditEventCategory.DATA_ACCESS, severity: AuditEventSeverity.WARNING },
239
+ * },
240
+ * }
241
+ */
242
+ applicationEventTypes: z.record(z.string().regex(LABEL_KEY_SEGMENT_PATTERN), ApplicationAuditEventTypeDeclarationSchema).optional(),
186
243
  });
187
244
 
245
+ /** The application's declared audit event types, keyed by `eventType` — see `AuditTrailConfig.applicationEventTypes`. */
246
+ export type ApplicationAuditEventTypes = NonNullable<AuditTrailConfig['applicationEventTypes']>;
247
+
188
248
  export type AuditTrailConfig = z.infer<typeof AuditTrailConfigSchema>;
189
249
  ```
@@ -247,6 +247,56 @@ The report separates retained occurrence coverage from invocation success, selec
247
247
  export const SCHEDULED_INITIAL_ADMISSION_MAX_AGE_MS = 5 * 60 * 1000;
248
248
  export const SCHEDULED_INITIAL_ADMISSION_FUTURE_SKEW_MS = 30 * 1000;
249
249
 
250
+ /**
251
+ * How long after its token expired a delivery may still be RECORDED as a missed occurrence (#2212).
252
+ *
253
+ * An expired token stays cryptographically valid forever, so without a horizon anyone able to
254
+ * publish onto the application's queue could replay a captured token of any age and plant a
255
+ * "missed while absent" record. The horizon is APPROXIMATELY the job-row retention: within it, a
256
+ * replayed token almost always meets the occurrence's existing row and is recognised as already
257
+ * held; beyond it, no genuine backlog is plausible and the delivery is rejected as a trust failure.
258
+ * "Approximately" because a row that ran on time expires measured from its completion while the
259
+ * horizon is measured from the token's expiry, which leaves a window of a few minutes in which a
260
+ * replay is recorded as a fresh miss. It never runs anything, and archived run evidence still wins
261
+ * the occurrence in coverage.
262
+ *
263
+ * Equal to `JOB_EXECUTION_TTL_SECONDS` (declared further down, outside this shared block, so it
264
+ * cannot be referenced here without a temporal-dead-zone hazard); a test pins the two together, so
265
+ * changing one without the other fails.
266
+ */
267
+ export const SCHEDULED_LATE_DELIVERY_HORIZON_MS = 30 * 24 * 60 * 60 * 1000;
268
+
269
+ /**
270
+ * Why an AUTHENTIC scheduled delivery reached the application too late to be admitted (#2212).
271
+ *
272
+ * Either way the occurrence was MISSED: it is recorded as such and not run, and the schedule
273
+ * continues with its next occurrence. The two gates differ in WHO was late, which is why they are
274
+ * kept apart:
275
+ *
276
+ * - `TOKEN_EXPIRED` — the delivery sat in the queue for longer than its token lives, so nothing
277
+ * consumed the application's scheduled queue for that long: the backend (or minion) was stopped,
278
+ * restarting or crash-looping. This is the common case after a restart.
279
+ * - `OUTSIDE_ADMISSION_WINDOW` — the token is still current, but the occurrence it names is older
280
+ * than the window. The scheduler may sign up to the window's length AFTER the occurrence, so the
281
+ * delay is shared between the scheduler's publication and the application's consumption, and
282
+ * cannot be attributed to the application alone.
283
+ *
284
+ * A late delivery is never an authentication failure: its signature, issuer and audience were
285
+ * proven before it was classified late. A token that cannot be proven authentic, that names an
286
+ * occurrence in the future, or that expired longer ago than `SCHEDULED_LATE_DELIVERY_HORIZON_MS`
287
+ * is a trust failure instead and is reported loudly.
288
+ *
289
+ * Missed occurrences are SKIPPED, never caught up: that is the established cron behaviour (a
290
+ * Kubernetes `CronJob` past its `startingDeadlineSeconds`, a Quartz trigger with the do-nothing
291
+ * misfire instruction), and it keeps the short signed window a replay bound rather than a credential.
292
+ */
293
+ export enum ScheduledDeliveryLateness {
294
+ /** The signed delivery token's `exp` passed before the delivery was consumed. */
295
+ TOKEN_EXPIRED = 'token_expired',
296
+ /** The token is current, but the occurrence it names is older than `SCHEDULED_INITIAL_ADMISSION_MAX_AGE_MS`; scheduler and consumer share the delay. */
297
+ OUTSIDE_ADMISSION_WINDOW = 'outside_admission_window',
298
+ }
299
+
250
300
  /** How the handler's complete effects tolerate execution after an uncertain outcome. */
251
301
  export enum ScheduledReplaySafety {
252
302
  /** No automatic repetition; a failed call can already have committed effects. */
@@ -320,11 +370,41 @@ export const ScheduledEvidencePolicySchema = z.object({
320
370
  });
321
371
  export type ScheduledEvidencePolicy = z.infer<typeof ScheduledEvidencePolicySchema>;
322
372
 
373
+ /** How a scheduled occurrence's archived evidence came to exist. */
323
374
  export enum ScheduledEvidenceSource {
375
+ /** The handler ran and reported completion. */
324
376
  EXECUTION = 'execution',
377
+ /** The handler's reconciler established that an interrupted run completed. */
325
378
  RECONCILIATION = 'reconciliation',
379
+ /** An operator confirmed completion of an occurrence held for review. */
326
380
  OPERATOR_CONFIRMATION = 'operator_confirmation',
381
+ /** An operator decided an occurrence held for review will not run. */
327
382
  ABANDONMENT = 'abandonment',
383
+ /**
384
+ * The occurrence was never run: its authentic delivery reached the application after the
385
+ * admission deadline (see `ScheduledDeliveryLateness` for who was late). Coverage reads it as an
386
+ * EXPLAINED gap: the slot stays missing, because the occurrence did not run, and the record says
387
+ * why — rather than an unexplained one.
388
+ */
389
+ LATE_DELIVERY = 'late_delivery',
390
+ }
391
+
392
+ /**
393
+ * The terminal invocation status each evidence source records — the one place that pairing is stated.
394
+ *
395
+ * A source whose occurrence never reached a successful invocation records `FAILED`; this follows the
396
+ * precedent `ABANDONMENT` set, and the SOURCE (never the status) is what says why it did not run.
397
+ */
398
+ export function scheduledEvidenceInvocationStatus(source: ScheduledEvidenceSource): JobExecutionStatus {
399
+ switch (source) {
400
+ case ScheduledEvidenceSource.EXECUTION:
401
+ case ScheduledEvidenceSource.RECONCILIATION:
402
+ case ScheduledEvidenceSource.OPERATOR_CONFIRMATION:
403
+ return JobExecutionStatus.COMPLETED;
404
+ case ScheduledEvidenceSource.ABANDONMENT:
405
+ case ScheduledEvidenceSource.LATE_DELIVERY:
406
+ return JobExecutionStatus.FAILED;
407
+ }
328
408
  }
329
409
  export enum ScheduledEvidenceResultStatus {
330
410
  CAPTURED = 'captured',
@@ -354,8 +434,7 @@ export const ScheduledRunEvidenceSchema = ScheduledRunEvidenceFieldsSchema.super
354
434
  : evidence.jobType !== JobType.SCHEDULED_CRON || !(evidence.batchRef || evidence.operationPathKey))) {
355
435
  ctx.addIssue({ code: 'custom', message: 'Evidence requires exactly one scheduled batch, operation or minion target' });
356
436
  }
357
- const expectedStatus = evidence.source === ScheduledEvidenceSource.ABANDONMENT ? JobExecutionStatus.FAILED : JobExecutionStatus.COMPLETED;
358
- if (evidence.invocationStatus !== expectedStatus) {
437
+ if (evidence.invocationStatus !== scheduledEvidenceInvocationStatus(evidence.source)) {
359
438
  ctx.addIssue({ code: 'custom', path: ['invocationStatus'], message: 'Terminal outcome must agree with evidence source' });
360
439
  }
361
440
 
@@ -215,7 +215,12 @@ it names the failure you get without the block:
215
215
  | The transactional From address is declared | `rg -n "from:" backend-api/src/saas-config.backend.ts` |
216
216
  | The document-acceptance posture is declared | `rg -n "governedDocumentAcceptanceMode" backend-api/src/saas-config.backend.ts` |
217
217
  | Declared identity-provider ranges are CIDR, never host names (inspect each entry) | `rg -n -A3 "federatedIdentityProviderPrivateNetworks" backend-api/src/saas-config.backend.ts` |
218
- | No platform-managed branch leaked in (MUST return zero) | `rg -n "jwt:\|endPoints\|mongodb\|publicKey" backend-api/src/saas-config.backend.ts` |
218
+ | No platform-managed branch leaked in (MUST return zero) | see the commands below the table |
219
+
220
+ ```bash
221
+ # No platform-managed branch leaked in (MUST return zero)
222
+ rg -n "jwt:|endPoints|mongodb|publicKey" backend-api/src/saas-config.backend.ts
223
+ ```
219
224
 
220
225
  ## Common Rationalizations
221
226
 
@@ -247,13 +247,27 @@ Run from the app root (substitute `<ref>` / `<env>`):
247
247
  |-----------|---------|
248
248
  | **Provider SDK installed** (must return a hit) | `rg -n '"stripe"' backend-api/package.json` |
249
249
  | Engine capability enabled | `rg -n "EngineCapability.BILLING.*enabled:\s*true" wildo.saas.config.ts` |
250
- | Billing block declares provider ref | `rg -n "billing:\s*\{" -A3 backend-api/src/saas-config.backend.ts \| rg "providerRef:"` |
251
- | **Ref authored in BACKEND scope** (must return a hit) | `rg -n "backend:\s*\{" -A80 wildo.saas.config.ts \| rg "<ref>:"` |
250
+ | Billing block declares provider ref | see the commands below the table |
251
+ | **Ref authored in BACKEND scope** (must return a hit) | see the commands below the table |
252
252
  | **No second declaration** (must return NOTHING for an engine-shipped or package-shipped provider) | `rg -n "<ref>" backend-api/src/provider-contributions.ts` |
253
- | Billing scope declares both protocols | `rg -n "'BILLING_PROVIDER'.*'WEBHOOK_ORIGINATOR'\|'WEBHOOK_ORIGINATOR'.*'BILLING_PROVIDER'" wildo.saas.config.ts` |
253
+ | Billing scope declares both protocols | see the commands below the table |
254
254
  | Secrets populated (both listed under `SET`, none under `NEEDED`) | `wildo secrets list --env <env>` |
255
255
  | **Ref materialized in the artifact** (must return a hit after sync) | `rg -n "<ref>" backend-api/src/generated/wildo-provider-runtime.generated.ts` |
256
- | **No frontend-scope billing entry** (must return NOTHING — billing has no browser part) | `rg -n "frontendServices:" -A60 wildo.saas.config.ts \| rg "<ref>:"` |
256
+ | **No frontend-scope billing entry** (must return NOTHING — billing has no browser part) | see the commands below the table |
257
+
258
+ ```bash
259
+ # Billing block declares provider ref
260
+ rg -n "billing:\s*\{" -A3 backend-api/src/saas-config.backend.ts | rg "providerRef:"
261
+
262
+ # Ref authored in BACKEND scope (must return a hit)
263
+ rg -n "backend:\s*\{" -A80 wildo.saas.config.ts | rg "<ref>:"
264
+
265
+ # Billing scope declares both protocols
266
+ rg -n "'BILLING_PROVIDER'.*'WEBHOOK_ORIGINATOR'|'WEBHOOK_ORIGINATOR'.*'BILLING_PROVIDER'" wildo.saas.config.ts
267
+
268
+ # No frontend-scope billing entry (must return NOTHING — billing has no browser part)
269
+ rg -n "frontendServices:" -A60 wildo.saas.config.ts | rg "<ref>:"
270
+ ```
257
271
 
258
272
  The high-signal pair: **"ref authored in BACKEND scope"** returning empty while
259
273
  **"no frontend-scope billing entry"** returns a hit is the exact billing crash-loop
@@ -184,7 +184,9 @@ co-location conventions.
184
184
  Inspect the existing backend module's `emailTemplateDefinitions` slot before choosing a layout. The current skeleton scans compiled email directories; an older application may maintain an explicit map. Preserve the actual ownership and registration path rather than adding a parallel map with a prescribed filename.
185
185
 
186
186
  - The scanner loads `template.js` default exports and co-located `labels.<locale>.js` named `labels` exports. Author their TypeScript sources and let the normal compiler publish them; a new `.tsx` file alone is not a loaded runtime template.
187
- - The scanner's `keyFromPath` owns the template ref. The skeleton maps `system/<name>` to `system.<name_with_underscores>` and `resources/<resource>/<operation>` to `email.<resource>.<operation>`. Module-specific scanners may choose other mappings. Match the existing sender's typed ref to that mapping; creating an enum with a different value does not rename the scanned ref.
187
+ - The scanner's `keyFromPath` owns the template ref. The skeleton maps `system/<name>` to `system.<name_with_underscores>`, and under `resources/` turns the path into the ref by replacing `/` with `.`. Module-specific scanners may choose other mappings. Match the existing sender's typed ref to that mapping; creating an enum with a different value does not rename the scanned ref.
188
+ - **An operation's email (a `userNotifications` EMAIL entry) has a derived ref:** `email.<resource>.<operation>[.<variantKey>].<target>[_<customNotificationRef>]`, so its directory is `resources/<resource>/<operation>[.<variantKey>].<target>[_<customNotificationRef>]/` — for example `resources/todos/change_status.admin.users-custom_notify-creator/`. The target segment is always there, and an operation with a keyed variant needs one template per variant. A missing one only WARNS at startup (it refuses only for a token-bearing operation), and the email is silently never sent. Read `references/framework-operation-email-template-ref-api.md` before naming the directory.
189
+ - **Declare before you code.** A non-user recipient at an address on the record is `recipientEmailField`; an email owed whatever the preferences is `alwaysDeliver: true`. Send from custom code with `EmailBackendService.send` only for an attachment, several or nested addresses, cc / bcc / threading, or a non-user's own language. Read `references/framework-email-send-api.md`.
188
190
  - Contribute the resulting map through the existing owning backend module. For an explicit map, add the imported definition and locale labels there; for a scanner, put the correctly exported files under the scanned directory. Do not manually edit generated definitions or add duplicate registrations.
189
191
  - Sender services resolve the typed ref through the framework email service; they do not import and render the template directly. Identity emails remain with their identity/engine owner; business-module emails remain with the owning business module.
190
192
 
@@ -249,7 +251,7 @@ import { EmailTemplateType } from '@wildo-ai/saas-models';
249
251
  import type {
250
252
  EmailTemplateDefinition,
251
253
  EmailTemplateProps,
252
- } from '~wildo-backend-lib/notifications/email/models/email-template-definition';
254
+ } from '@wildo-ai/saas-backend-lib';
253
255
 
254
256
  export interface MinimalExampleLabels {
255
257
  subject: string;
@@ -352,6 +354,8 @@ single self-contained reference shape for app developers.
352
354
  - `references/framework-email-attachments-and-limits.md` — `attachmentFileIds`, the framework's own size cap, and why a declared vendor list is not failover
353
355
  - `references/email-artifact-paths.md` — where files live (template, labels, registry, type enum)
354
356
  - `references/framework-email-template-api.md` — `EmailTemplateDefinition<TLabels>` + `EmailTemplateDefinitionsMap` types
357
+ - `references/framework-operation-email-template-ref-api.md` — the ref an operation's `userNotifications` email renders, and the directory it lives in, with worked cases (source-backed)
358
+ - `references/framework-email-send-api.md` — when a declaration cannot express the email, and `EmailBackendService.send`'s request, outcomes and retry rule (source-backed)
355
359
  - `i18n-rerun-pipeline/SKILL.md` — translation pipeline orchestrator (Step 6 trigger)
356
360
  - `backend-addon-wiring/SKILL.md` — the module-level `emailTemplateDefinitions` slot consumer (the registry feeds into this)
357
361
 
@@ -361,6 +365,7 @@ single self-contained reference shape for app developers.
361
365
  - [ ] Labels exist for **every** user-visible string (one key per string), satisfying the typed `TLabels` interface key-for-key
362
366
  - [ ] Labels files exist for every supported locale (parallel key sets across locales)
363
367
  - [ ] Compiled template and labels resolve under the owning module’s scanner/map, and its ref matches the sender’s typed id
368
+ - [ ] An operation email's directory carries the full derived ref (`<operation>[.<variantKey>].<target>[_<customNotificationRef>]`), one per keyed variant, and startup logs no unresolved operation email
364
369
  - [ ] Definition explicitly selects `EmailTemplateType.*` and the corresponding provider capability is configured
365
370
  - [ ] Definition is typed `EmailTemplateDefinition<TLabels>` (not `any`, not bare `EmailTemplateDefinition`)
366
371
  - [ ] `subject` / `body` JSX contains **no inline strings** (every string flows through `labels`)
@@ -381,13 +386,27 @@ Run from the app root. Replace `<email-root>` with the actual owning scanner dir
381
386
  | Definition declares `type:` | `rg -n "type:\s+EmailTemplateType\." <email-root>/<template>/template.tsx` |
382
387
  | Subject / body read from `labels.` | `rg -n "labels\.[a-zA-Z]+" <email-root>/<template>/template.tsx` |
383
388
  | Locale files exist for every supported locale | `ls <email-root>/<template>/labels.*.ts` |
384
- | Other-locale files are the generated ones (must return empty) | `rg -L "DO NOT EDIT THIS FILE MANUALLY" <email-root>/<template>/labels.<locale>.ts` (run for each non-primary locale) |
385
- | Owning registry/scanner and ref mapping are present | `rg -n "scanEmailTemplateDirectory\|keyFromPath\|emailTemplateDefinitions" <registry-file>` (inspect the mapping; scanned templates need no per-template map entry) |
386
- | Per-locale label files share the same key set | `comm -23 <(rg -o '\\w+:' <email-root>/<template>/labels.<primary-locale>.ts \| sort -u) <(rg -o '\\w+:' <email-root>/<template>/labels.<locale>.ts \| sort -u)` (output should be empty) |
389
+ | Other-locale files are the generated ones (must return empty) | `rg --files-without-match "DO NOT EDIT THIS FILE MANUALLY" <email-root>/<template>/labels.<locale>.ts` (run for each non-primary locale) |
390
+ | Owning registry/scanner and ref mapping are present | see the commands below the table (inspect the mapping; scanned templates need no per-template map entry) |
391
+ | Per-locale label files share the same key set | see the commands below the table (output should be empty) |
387
392
  | Sender resolves template by typed id | `rg -n "EmailTemplateType\.[A-Z_]+" backend-api/src/modules/<module>/` |
388
393
  | **No inline JSX text in subject / body** (must return empty) | `rg -n ">[A-Za-z][^<{}]{2,}<" <email-root>/<template>/template.tsx` |
389
- | **No app SPA imports** in the template (must return empty) | `rg -n "from\s+['\"](app|frontend)/" <email-root>/<template>/template.tsx` |
394
+ | **No app SPA imports** in the template (must return empty) | see the commands below the table |
390
395
  | **No direct template import** in sender services (must return empty) | `rg -n "from\s+['\"].*notifications/email/<template>/template['\"]" backend-api/src/modules/<module>/` |
396
+ | **Every operation email resolves** (must return empty after a backend start) | `rg -n "does not resolve through the configured primary/fallback locale chain" <backend startup log>` |
397
+
398
+ ```bash
399
+ # No app SPA imports in the template (must return empty)
400
+ rg -n "from\s+['\"](app|frontend)/" <email-root>/<template>/template.tsx
401
+ ```
402
+
403
+ ```bash
404
+ # Owning registry/scanner and ref mapping are present
405
+ rg -n "scanEmailTemplateDirectory|keyFromPath|emailTemplateDefinitions" <registry-file>
406
+
407
+ # Per-locale label files share the same key set
408
+ comm -23 <(rg -o '\w+:' <email-root>/<template>/labels.<primary-locale>.ts | sort -u) <(rg -o '\w+:' <email-root>/<template>/labels.<locale>.ts | sort -u)
409
+ ```
391
410
 
392
411
  The high-signal invariants are **"No inline JSX text in subject /
393
412
  body"** combined with **"No direct template import in sender
@@ -428,6 +447,9 @@ second guarantees the registry is the integration seam.
428
447
  import in sender services** grep — must return empty)
429
448
  - Template imports from `frontend/` (catch with the **No app SPA
430
449
  imports** grep — must return empty)
450
+ - An operation email's template whose folder does not carry the full ref (no target segment, a missing variant) —
451
+ nothing renders it, startup only warns, and the email is silently never sent (catch with the **Every operation
452
+ email resolves** check)
431
453
  - Brand color / domain hard-coded in the body (template no longer
432
454
  renders correctly across environments)
433
455
  - New label keys committed without a translation rerun (Step 6
@@ -12,6 +12,6 @@ Locate the owning backend module's `emailTemplateDefinitions` contribution first
12
12
 
13
13
  The scanner starts beside its caller's `import.meta.url`, scans its configured `subdir` recursively and uses `keyFromPath` to derive refs. Its default extension is `.js`. It imports the template's default export and the labels module's named `labels` export (also accepts `default.labels`). It does not infer refs from a new enum or inspect an arbitrary TypeScript source folder.
14
14
 
15
- In the current skeleton, `backend-api/src/engine/email/email-template-definitions.ts` scans `system/` and `resources/`. `system/password-reset` becomes `system.password_reset`; `resources/tasks/create` becomes `email.tasks.create`. The engine backend module contributes the map. Business-module email definitions should follow their existing module-owned contribution rather than being moved into the engine merely to match this example.
15
+ In the current skeleton, `backend-api/src/engine/email/email-template-definitions.ts` scans `system/` and `resources/`. `system/password-reset` becomes `system.password_reset`; under `resources/`, `/` becomes `.`, so an operation email for `tasks` / `assign` / target `USER_SELF` lives in `resources/tasks/assign.user-self` and registers `email.tasks.assign.user-self` (the full rule: `references/framework-operation-email-template-ref-api.md`). The engine backend module contributes the map. Business-module email definitions should follow their existing module-owned contribution rather than being moved into the engine merely to match this example.
16
16
 
17
17
  For an explicit map, follow its existing `EmailTemplateDefinitionsMap` shape and preserve its labels wiring. For a scanner, adding a correctly named/default-exported template and named locale exports under its root is the registration input; no per-template manual entry is required. In either case, normal compilation/publication and module loading must make the ref visible. Match the sender's typed identifier to the derived ref and verify through preview. Never hand-edit compiled artifacts to make a missing source registration appear fixed.