@wildo-ai/framework-knowledge 1.1.10 → 1.1.12

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 (1349) 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 +4 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +25 -3
  5. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +40 -12
  6. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +7 -5
  7. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +12 -0
  8. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +19 -2
  9. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +33 -9
  10. package/dist/esm/framework-knowledge.definitions.d.ts +2 -3
  11. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  12. package/dist/esm/framework-knowledge.definitions.js +628 -107
  13. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  14. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  15. package/dist/esm/framework-knowledge.research-provenance.d.ts +90 -0
  16. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -0
  17. package/dist/esm/framework-knowledge.research-provenance.js +140 -0
  18. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -0
  19. package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
  20. package/dist/esm/framework-knowledge.schemas.js.map +1 -1
  21. package/dist/esm/index.d.ts +2 -0
  22. package/dist/esm/index.d.ts.map +1 -1
  23. package/dist/esm/index.js +2 -0
  24. package/dist/esm/index.js.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -12
  28. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
  31. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +10 -4
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +82 -15
  35. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -5
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +4 -16
  39. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  43. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +1 -1
  45. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +9 -5
  47. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +11 -7
  49. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
  51. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
  53. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  55. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +38 -14
  56. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  57. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +16 -8
  58. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +20 -8
  60. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  61. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +29 -3
  62. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  63. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +80 -16
  64. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  65. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +2 -2
  66. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +7 -2
  68. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  69. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
  70. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
  72. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
  73. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +6 -2
  74. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  75. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +4 -3
  76. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  77. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +26 -7
  78. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +23 -6
  80. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
  82. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  83. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
  84. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
  85. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
  86. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
  88. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
  89. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
  90. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  91. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +7 -3
  93. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
  95. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
  96. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  97. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +9 -7
  99. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  100. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
  101. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +9 -2
  103. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  104. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +5 -2
  106. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +15 -5
  108. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  109. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
  110. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
  113. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  114. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
  115. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  116. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
  117. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  118. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
  119. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  120. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +36 -13
  121. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  122. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +8 -2
  123. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  124. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -1
  125. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  126. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +4 -1
  127. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  128. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +34 -6
  129. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  130. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +7 -3
  131. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  132. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +6 -4
  133. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  134. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
  135. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
  137. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  138. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +39 -29
  139. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  140. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  141. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +8 -3
  142. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  143. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +24 -9
  144. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  145. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +8 -2
  146. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +8 -2
  148. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  149. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +1 -1
  150. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  151. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  152. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +2 -2
  153. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  154. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
  156. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  157. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  158. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
  159. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  160. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -7
  161. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  162. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +12 -14
  163. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  164. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +3 -0
  165. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  166. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
  167. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  168. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
  169. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  170. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +2 -1
  171. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  172. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +98 -0
  173. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -0
  174. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +124 -0
  175. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -0
  176. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
  177. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  178. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +4 -2
  179. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  180. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +34 -1
  181. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  182. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +39 -20
  183. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  184. package/dist/esm/source-anchor-grammar.d.ts +70 -0
  185. package/dist/esm/source-anchor-grammar.d.ts.map +1 -0
  186. package/dist/esm/source-anchor-grammar.js +114 -0
  187. package/dist/esm/source-anchor-grammar.js.map +1 -0
  188. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  189. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  190. package/dist/knowledge/manifest.json +8 -8
  191. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +12 -0
  192. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
  193. package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
  194. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
  195. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  196. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  197. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +788 -49
  198. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +18 -4
  199. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +451 -16
  200. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +3 -6
  201. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
  202. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +2 -2
  203. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +3 -2
  204. package/dist/knowledge/playbooks/bottom_up.conception/method.md +12 -7
  205. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +4 -3
  206. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
  207. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
  208. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  209. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  210. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +115 -2
  211. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +11 -4
  212. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +71 -7
  213. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +19 -6
  214. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +126 -24
  215. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +51 -7
  216. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +28 -9
  217. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +5 -3
  218. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +10 -2
  219. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
  220. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +67 -5
  221. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +10 -3
  222. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +176 -22
  223. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +21 -3
  224. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
  225. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
  226. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
  227. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
  228. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
  229. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -5
  230. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +5 -2
  231. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
  232. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
  233. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +153 -28
  234. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
  235. package/dist/knowledge/playbooks/refinement.document-facts/method.md +36 -7
  236. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +6 -2
  237. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +9 -2
  238. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +8 -6
  239. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +2 -1
  240. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  241. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  242. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +9 -2
  243. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +17 -5
  244. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
  245. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
  246. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  247. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  248. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
  249. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
  250. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
  251. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  252. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  253. package/dist/knowledge/playbooks/top_down.business-model/method.md +49 -11
  254. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
  255. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
  256. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
  257. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
  258. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +15 -5
  259. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
  260. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
  261. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
  262. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
  263. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
  264. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
  265. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
  266. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
  267. package/dist/knowledge/playbooks/top_down.definition/method.md +10 -3
  268. package/dist/knowledge/playbooks/top_down.definition/playbook.json +14 -5
  269. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +10 -3
  270. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +4 -3
  271. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +2 -1
  272. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
  273. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
  274. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
  275. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
  276. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
  277. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
  278. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  279. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  280. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -0
  281. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -6
  282. package/dist/knowledge/playbooks/top_down.risk-register/method.md +8 -1
  283. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
  284. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
  285. package/dist/knowledge/playbooks/top_down.service-method/method.md +216 -0
  286. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +108 -0
  287. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
  288. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
  289. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
  290. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
  291. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +21 -2
  292. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +63 -18
  293. package/dist/knowledge/references/acp.execution-profile.md +9 -1
  294. package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
  295. package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
  296. package/dist/knowledge/references/application-maturity.config.md +28 -2
  297. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +57 -0
  298. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +65 -13
  299. package/dist/knowledge/references/backend.inbound-handlers.agents.md +10 -3
  300. package/dist/knowledge/references/backend.inbound-handlers.definition.md +463 -5
  301. package/dist/knowledge/references/backend.inbound-handlers.pipelines.md +62 -0
  302. package/dist/knowledge/references/blueprint.definition-contract.md +483 -0
  303. package/dist/knowledge/references/brand.name-screening.config.md +30 -3
  304. package/dist/knowledge/references/brand.visual-tone.config.md +26 -8
  305. package/dist/knowledge/references/build-plan.task-graph.config.md +438 -12
  306. package/dist/knowledge/references/business-model.pricing-plan.config.md +19 -9
  307. package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
  308. package/dist/knowledge/references/business-model.snapshot.validation.md +29 -8
  309. package/dist/knowledge/references/capability-composition.config.md +4 -3
  310. package/dist/knowledge/references/cli.market.generate-command.md +2 -1
  311. package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
  312. package/dist/knowledge/references/companion.market.generation-service.md +46 -5
  313. package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
  314. package/dist/knowledge/references/companion.technical-doc.service.md +342 -76
  315. package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
  316. package/dist/knowledge/references/engine.client-bundle.allow-list.md +16 -0
  317. package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
  318. package/dist/knowledge/references/engine.saas-website.config.md +16 -44
  319. package/dist/knowledge/references/example.ai-use-declaration.agent.md +37 -0
  320. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
  321. package/dist/knowledge/references/{example.authorization.service-provider-organization-wide-access.md → example.authorization.relationship-organization-wide-access.md} +2 -2
  322. package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
  323. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +4 -3
  324. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +22 -0
  325. package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
  326. package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
  327. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +47 -0
  328. package/dist/knowledge/references/example.config.app-shell.full.md +6 -3
  329. package/dist/knowledge/references/example.config.app-shell.hosted-components.md +4 -1
  330. package/dist/knowledge/references/example.config.backend.inbound-email.md +4 -2
  331. package/dist/knowledge/references/example.config.backend.required-floors.md +4 -2
  332. package/dist/knowledge/references/example.config.design-system.full.md +40 -116
  333. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +10 -0
  334. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +78 -19
  335. package/dist/knowledge/references/example.flows-actors.declared-flow.md +115 -0
  336. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +12 -0
  337. package/dist/knowledge/references/example.inbound.email-channel-handler.md +10 -1
  338. package/dist/knowledge/references/example.infra.environment-config.local.md +34 -63
  339. package/dist/knowledge/references/example.layout-2d.registration.md +11 -0
  340. package/dist/knowledge/references/example.minion.contained-tick.md +1 -1
  341. package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
  342. package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
  343. package/dist/knowledge/references/example.module.relationships.scope-membership-junction.md +8 -10
  344. package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
  345. package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
  346. package/dist/knowledge/references/example.organizations.relationship-kinds.md +26 -0
  347. package/dist/knowledge/references/example.professional-qualifications.declaration.md +10 -0
  348. package/dist/knowledge/references/example.professional-qualifications.gate.md +25 -0
  349. package/dist/knowledge/references/example.provider.backend-module-shape.md +38 -4
  350. package/dist/knowledge/references/example.provider.frontend-facet.on-demand-sdk.md +41 -0
  351. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +4 -5
  352. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +7 -5
  353. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -5
  354. package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
  355. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
  356. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +23 -7
  357. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +87 -22
  358. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +80 -0
  359. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +20 -21
  360. package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
  361. package/dist/knowledge/references/example.spec.composite-view.workspace.md +10 -2
  362. package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
  363. package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
  364. package/dist/knowledge/references/example.views.composite-view.workspace.md +10 -3
  365. package/dist/knowledge/references/example.website.blocks.section.md +20 -0
  366. package/dist/knowledge/references/example.website.blocks.site-choices.md +78 -0
  367. package/dist/knowledge/references/example.website.blocks.site-configs.md +155 -0
  368. package/dist/knowledge/references/example.website.demo.append.md +57 -0
  369. package/dist/knowledge/references/example.website.demo.approval.md +47 -0
  370. package/dist/knowledge/references/example.website.demo.celebrate.md +39 -0
  371. package/dist/knowledge/references/example.website.demo.complete-items.md +103 -0
  372. package/dist/knowledge/references/example.website.demo.connect.md +45 -0
  373. package/dist/knowledge/references/example.website.demo.dashboard.md +74 -0
  374. package/dist/knowledge/references/example.website.demo.query-answer.md +77 -0
  375. package/dist/knowledge/references/example.website.demo.status-lifecycle.md +71 -0
  376. package/dist/knowledge/references/example.website.demo.transform.md +43 -0
  377. package/dist/knowledge/references/example.website.page.manifest.md +2 -6
  378. package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
  379. package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
  380. package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
  381. package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
  382. package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
  383. package/dist/knowledge/references/example.website.section.bento.md +27 -0
  384. package/dist/knowledge/references/example.website.section.contact-form.md +15 -0
  385. package/dist/knowledge/references/example.website.section.factories.md +82 -0
  386. package/dist/knowledge/references/example.website.section.faq.md +17 -0
  387. package/dist/knowledge/references/example.website.section.footer-cta.md +13 -0
  388. package/dist/knowledge/references/example.website.section.hero.md +16 -0
  389. package/dist/knowledge/references/example.website.section.latest-posts.md +15 -0
  390. package/dist/knowledge/references/example.website.section.marquee.md +26 -0
  391. package/dist/knowledge/references/example.website.section.roadmap.md +25 -0
  392. package/dist/knowledge/references/example.website.section.site-block.md +43 -0
  393. package/dist/knowledge/references/example.website.section.solution-paths.md +17 -0
  394. package/dist/knowledge/references/example.website.section.stats.md +23 -0
  395. package/dist/knowledge/references/example.website.section.steps.md +15 -0
  396. package/dist/knowledge/references/example.website.showcase.tour.md +49 -0
  397. package/dist/knowledge/references/example.website.theme.composed.md +69 -0
  398. package/dist/knowledge/references/experience-plan.config.md +127 -1
  399. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +8 -0
  400. package/dist/knowledge/references/external-connectors.frontend-provider-sdk-activation-mode.md +27 -0
  401. package/dist/knowledge/references/external-connectors.models.connection-target.md +99 -0
  402. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +13 -0
  403. package/dist/knowledge/references/external-connectors.models.hook-inbound-endpoint.md +352 -0
  404. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +168 -0
  405. package/dist/knowledge/references/external-connectors.models.hook-trigger-strategy.md +97 -0
  406. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +72 -8
  407. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +235 -0
  408. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1272 -3
  409. package/dist/knowledge/references/external-connectors.models.subject-erasure-effect.md +105 -0
  410. package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
  411. package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
  412. package/dist/knowledge/references/integration-plan.config.md +28 -8
  413. package/dist/knowledge/references/market.references.weighted-edges.md +14 -1
  414. package/dist/knowledge/references/minions.tick-contract.md +2 -2
  415. package/dist/knowledge/references/placement-plan.config.md +94 -13
  416. package/dist/knowledge/references/platform.config.backing-services.md +9 -11
  417. package/dist/knowledge/references/platform.config.environment.deployment.md +140 -7
  418. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
  419. package/dist/knowledge/references/platform.config.infrastructure-host.md +2 -1
  420. package/dist/knowledge/references/platform.config.platform-key-management.md +282 -0
  421. package/dist/knowledge/references/platform.config.saas.md +126 -32
  422. package/dist/knowledge/references/platform.key-management.vault-custody.md +78 -0
  423. package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
  424. package/dist/knowledge/references/presets.3d.layout-contract.md +4 -30
  425. package/dist/knowledge/references/presets.3d.register-layout.md +14 -36
  426. package/dist/knowledge/references/presets.layouts-2d.authoring.md +157 -0
  427. package/dist/knowledge/references/presets.layouts-2d.register-layout.md +53 -0
  428. package/dist/knowledge/references/presets.layouts-2d.settings.md +53 -0
  429. package/dist/knowledge/references/presets.layouts-2d.vocabulary.md +41 -0
  430. package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
  431. package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
  432. package/dist/knowledge/references/presets.models.palette-contrast.md +183 -0
  433. package/dist/knowledge/references/presets.models.palette-derivation.md +93 -0
  434. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +27 -0
  435. package/dist/knowledge/references/presets.models.surface-variant.md +11 -0
  436. package/dist/knowledge/references/presets.models.theme-contract.md +136 -0
  437. package/dist/knowledge/references/presets.models.theme-personality-lexicon.md +81 -0
  438. package/dist/knowledge/references/presets.models.theme-personality.md +159 -0
  439. package/dist/knowledge/references/presets.themes.compose-theme.md +47 -0
  440. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +4 -4
  441. package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
  442. package/dist/knowledge/references/roadmap.phase.config.md +2 -16
  443. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +158 -0
  444. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +85 -12
  445. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +179 -0
  446. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
  447. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +3 -1
  448. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
  449. package/dist/knowledge/references/saas.backend.crypto-keys.application-keys.md +100 -0
  450. package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
  451. package/dist/knowledge/references/saas.backend.custom-operation.commit-outcome-read-back.md +208 -0
  452. package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
  453. package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
  454. package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
  455. package/dist/knowledge/references/saas.backend.custom-operation.target-authority.md +33 -0
  456. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +131 -1
  457. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
  458. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
  459. package/dist/knowledge/references/saas.backend.domain-module.md +105 -1
  460. package/dist/knowledge/references/saas.backend.email-template.definition.md +34 -0
  461. package/dist/knowledge/references/saas.backend.email-template.words.md +98 -0
  462. package/dist/knowledge/references/saas.backend.email.send.md +7 -0
  463. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +35 -4
  464. package/dist/knowledge/references/saas.backend.flows-actors.ask-person-tool.md +79 -0
  465. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-case-selector.md +71 -0
  466. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +21 -10
  467. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +11 -5
  468. package/dist/knowledge/references/saas.backend.flows-actors.chat-agent-declaration.md +51 -0
  469. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +219 -0
  470. package/dist/knowledge/references/saas.backend.flows-actors.decision-notice-handler.md +239 -0
  471. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +661 -3
  472. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +15 -2
  473. package/dist/knowledge/references/saas.backend.flows-actors.operation-approval-resolvers.md +50 -0
  474. package/dist/knowledge/references/saas.backend.flows-actors.present-records-tool.md +106 -0
  475. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +14 -1
  476. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
  477. package/dist/knowledge/references/saas.backend.flows-actors.retrieval-tool.md +205 -0
  478. package/dist/knowledge/references/saas.backend.flows-actors.tool-dispatch-obligations.md +21 -5
  479. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +28 -0
  480. package/dist/knowledge/references/saas.backend.flows.start-flow.md +47 -0
  481. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +5 -3
  482. package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
  483. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
  484. package/dist/knowledge/references/saas.backend.providers.optional-runtime-peers.md +15 -25
  485. package/dist/knowledge/references/saas.backend.rate-limit-service.check-policy.md +3 -2
  486. package/dist/knowledge/references/saas.backend.submission-challenge.md +4 -0
  487. package/dist/knowledge/references/saas.backend.system-access-service.md +394 -104
  488. package/dist/knowledge/references/saas.config.content-security-policy.md +26 -10
  489. package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
  490. package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
  491. package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
  492. package/dist/knowledge/references/saas.data-seeding.run-ledger.md +3 -0
  493. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +70 -3
  494. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
  495. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
  496. package/dist/knowledge/references/saas.external-providers.llm.model-configuration.md +3 -0
  497. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -2
  498. package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +10 -16
  499. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +7 -3
  500. package/dist/knowledge/references/saas.frontend.app-shell.register-shell-layout.md +97 -0
  501. package/dist/knowledge/references/saas.frontend.app-shell.shell-layout-contract.md +60 -0
  502. package/dist/knowledge/references/saas.frontend.app-shell.shell-motion-contract.md +274 -0
  503. package/dist/knowledge/references/saas.frontend.app-shell.use-shell-motion.md +73 -0
  504. package/dist/knowledge/references/saas.frontend.brand-identity.md +6 -0
  505. package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
  506. package/dist/knowledge/references/saas.frontend.chart-dashboard.md +130 -0
  507. package/dist/knowledge/references/saas.frontend.chart-view.inserted-declaration.md +13 -0
  508. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
  509. package/dist/knowledge/references/saas.frontend.chat-sign-in-completion.md +99 -0
  510. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +92 -23
  511. package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
  512. package/dist/knowledge/references/saas.frontend.display-layout.reading-measure.md +9 -3
  513. package/dist/knowledge/references/saas.frontend.domain-module.md +5 -0
  514. package/dist/knowledge/references/saas.frontend.embedded-resource-descent.md +2 -1
  515. package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
  516. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +57 -3
  517. package/dist/knowledge/references/saas.frontend.field-tiles.md +76 -0
  518. package/dist/knowledge/references/saas.frontend.flows-actors-view.md +10 -2
  519. package/dist/knowledge/references/saas.frontend.focus-indicator.md +119 -0
  520. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +14 -2
  521. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +7 -4
  522. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +17 -16
  523. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
  524. package/dist/knowledge/references/saas.frontend.operation-key-and-resource-config-like.md +68 -1
  525. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +14 -24
  526. package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
  527. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +184 -5
  528. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
  529. package/dist/knowledge/references/saas.frontend.resource-header-title.md +98 -34
  530. package/dist/knowledge/references/saas.frontend.resource-label-params.md +3 -1
  531. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +59 -19
  532. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +344 -62
  533. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +13 -8
  534. package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
  535. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +183 -32
  536. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +72 -13
  537. package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
  538. package/dist/knowledge/references/saas.models.agent-suspension.md +75 -0
  539. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +2 -2
  540. package/dist/knowledge/references/saas.models.agent-work-decision-contents-read.md +69 -0
  541. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +11 -2
  542. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +20 -3
  543. package/dist/knowledge/references/saas.models.agent-work-output-review.md +3 -3
  544. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +6 -5
  545. package/dist/knowledge/references/saas.models.agent-work-review-config.md +22 -4
  546. package/dist/knowledge/references/saas.models.analytics.value-moments.md +22 -0
  547. package/dist/knowledge/references/saas.models.application-agent-policy.md +28 -0
  548. package/dist/knowledge/references/saas.models.application-entry-points.md +45 -0
  549. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
  550. package/dist/knowledge/references/saas.models.audit.trail-config.md +18 -5
  551. package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +175 -0
  552. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +4 -4
  553. package/dist/knowledge/references/saas.models.chat-identity-link-host.md +38 -0
  554. package/dist/knowledge/references/saas.models.compliance.ai-use-classification.md +179 -0
  555. package/dist/knowledge/references/saas.models.compliance.ai-use-posture.md +121 -0
  556. package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
  557. package/dist/knowledge/references/saas.models.config.organization-types.md +54 -74
  558. package/dist/knowledge/references/saas.models.conversation-threads.md +43 -6
  559. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +32 -0
  560. package/dist/knowledge/references/saas.models.crypto-keys.key-management-config.md +130 -0
  561. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +29 -0
  562. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +442 -0
  563. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +91 -0
  564. package/dist/knowledge/references/saas.models.data-mode-read-list.md +24 -79
  565. package/dist/knowledge/references/saas.models.engine-capabilities.md +39 -2
  566. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
  567. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +16 -9
  568. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +23 -6
  569. package/dist/knowledge/references/saas.models.external-data-conflict-vocabulary.md +53 -0
  570. package/dist/knowledge/references/saas.models.external-data-pipeline.md +96 -26
  571. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report-config.md +28 -0
  572. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +321 -0
  573. package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
  574. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails.md +150 -0
  575. package/dist/knowledge/references/saas.models.flows-actors.agent-definition.md +45 -0
  576. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +154 -0
  577. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +49 -7
  578. package/dist/knowledge/references/saas.models.flows-actors.chat-agents-vocabulary.md +26 -0
  579. package/dist/knowledge/references/saas.models.flows-actors.decision-card-wording.md +284 -0
  580. package/dist/knowledge/references/saas.models.flows-actors.decision-notice-recorded-cards.md +93 -0
  581. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +70 -0
  582. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +349 -0
  583. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-pending.md +55 -0
  584. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +93 -0
  585. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +6 -0
  586. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +4 -3
  587. package/dist/knowledge/references/saas.models.flows.run-state.md +49 -0
  588. package/dist/knowledge/references/saas.models.flows.runnable-model.md +274 -0
  589. package/dist/knowledge/references/saas.models.frontend-on-demand-capability-contract.md +54 -0
  590. package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
  591. package/dist/knowledge/references/saas.models.http-api-binding.md +176 -50
  592. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +3 -3
  593. package/dist/knowledge/references/saas.models.http-api-population-filter.md +51 -0
  594. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
  595. package/dist/knowledge/references/saas.models.inbound-channels.md +75 -3
  596. package/dist/knowledge/references/saas.models.inbound-email-domains.md +5 -5
  597. package/dist/knowledge/references/saas.models.inbound-email.md +2 -2
  598. package/dist/knowledge/references/saas.models.m2m-webhook-events.md +73 -0
  599. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
  600. package/dist/knowledge/references/saas.models.model-cost-summary.md +56 -20
  601. package/dist/knowledge/references/saas.models.notifications.targets.md +28 -3
  602. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +259 -21
  603. package/dist/knowledge/references/saas.models.on-demand-provider-capabilities.md +28 -0
  604. package/dist/knowledge/references/saas.models.organization-agent-policy.md +43 -0
  605. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +74 -0
  606. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +51 -0
  607. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +6 -6
  608. package/dist/knowledge/references/saas.models.organizations.application-owner-codes.md +9 -10
  609. package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
  610. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +933 -0
  611. package/dist/knowledge/references/saas.models.organizations.professional-qualification-kinds.md +46 -0
  612. package/dist/knowledge/references/saas.models.organizations.professional-qualifications.md +168 -0
  613. package/dist/knowledge/references/{saas.models.organizations.service-provider-capability-grants.md → saas.models.organizations.relationship-capability-grants.md} +56 -35
  614. package/dist/knowledge/references/saas.models.organizations.relationship-grantor-controls.md +62 -0
  615. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +228 -0
  616. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +291 -0
  617. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +114 -0
  618. package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
  619. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +114 -7
  620. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +73 -2
  621. package/dist/knowledge/references/saas.models.privacy.redaction-treatments.md +13 -14
  622. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
  623. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
  624. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
  625. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +280 -40
  626. package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
  627. package/dist/knowledge/references/saas.models.provider-capabilities.md +38 -0
  628. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +50 -1
  629. package/dist/knowledge/references/saas.models.providers.capability-activation-policy.md +28 -0
  630. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +20 -6
  631. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +52 -0
  632. package/dist/knowledge/references/saas.models.providers.execute-operation-request.md +25 -0
  633. package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
  634. package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
  635. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +1 -1
  636. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +13 -1
  637. package/dist/knowledge/references/saas.models.rate-limit-configuration.md +4 -4
  638. package/dist/knowledge/references/saas.models.representative-activity.md +69 -0
  639. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +165 -44
  640. package/dist/knowledge/references/saas.models.resource-config.metered-usage-recording.md +24 -0
  641. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +92 -11
  642. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
  643. package/dist/knowledge/references/saas.models.resource-config.operation-base.md +20 -3
  644. package/dist/knowledge/references/saas.models.resource-config.operation-bulk.md +37 -0
  645. package/dist/knowledge/references/saas.models.resource-config.operation-chat-command.md +39 -0
  646. package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
  647. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
  648. package/dist/knowledge/references/saas.models.resource-config.operation-mcp-exposure.md +1 -1
  649. package/dist/knowledge/references/saas.models.resource-config.operation-required-qualifications.md +30 -0
  650. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +137 -2
  651. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +1 -1
  652. package/dist/knowledge/references/saas.models.resource-config.operation-union.md +0 -1
  653. package/dist/knowledge/references/saas.models.resource-config.operation-variant-client-timeout.md +1 -1
  654. package/dist/knowledge/references/saas.models.resource-config.record-label-fields.md +23 -0
  655. package/dist/knowledge/references/saas.models.resource-config.request-field-offers.md +104 -0
  656. package/dist/knowledge/references/saas.models.resource-config.required-features.md +20 -0
  657. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +23 -16
  658. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +25 -3
  659. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +46 -0
  660. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
  661. package/dist/knowledge/references/saas.models.resource-config.system-managed-fields.md +2 -1
  662. package/dist/knowledge/references/saas.models.resource-config.token-generation.md +1 -1
  663. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
  664. package/dist/knowledge/references/saas.models.resource-operation-variant-runtime.md +3 -2
  665. package/dist/knowledge/references/saas.models.resource-relationship-builder-parameters.md +6 -2
  666. package/dist/knowledge/references/saas.models.roadmap.phase-horizon.md +31 -0
  667. package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
  668. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +12 -6
  669. package/dist/knowledge/references/saas.models.schema-family-builder.md +32 -4
  670. package/dist/knowledge/references/saas.models.scope-membership.md +2 -2
  671. package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
  672. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +123 -0
  673. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +19 -2
  674. package/dist/knowledge/references/saas.models.systems-of-record.md +110 -14
  675. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +7 -3
  676. package/dist/knowledge/references/saas.models.work-unit-ref.md +17 -2
  677. package/dist/knowledge/references/saas.public-runtime.contract.md +75 -25
  678. package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
  679. package/dist/knowledge/references/saas.specifications.assurance-control-markers.md +3 -2
  680. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +13 -0
  681. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +287 -17
  682. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +5 -4
  683. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +30 -2
  684. package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
  685. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +22 -4
  686. package/dist/knowledge/references/saas.specifications.processor-register.md +10 -1
  687. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +111 -2
  688. package/dist/knowledge/references/saas.specifications.recipient-population.md +46 -0
  689. package/dist/knowledge/references/saas.specifications.resource-frontend-configuration-aspect.md +7 -0
  690. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +44 -5
  691. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +21 -7
  692. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +113 -70
  693. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +136 -6
  694. package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
  695. package/dist/knowledge/references/saas.website.astro.bridge.md +51 -14
  696. package/dist/knowledge/references/saas.website.astro.head-renderer.md +63 -27
  697. package/dist/knowledge/references/saas.website.astro.i18n-helper.md +39 -10
  698. package/dist/knowledge/references/saas.website.astro.label-key-collector.md +12 -11
  699. package/dist/knowledge/references/saas.website.astro.label-loader.md +77 -14
  700. package/dist/knowledge/references/saas.website.astro.pick-labels-for-page.md +1 -2
  701. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +49 -17
  702. package/dist/knowledge/references/saas.website.astro.site-context.md +17 -8
  703. package/dist/knowledge/references/saas.website.astro.structured-data-renderer.md +29 -8
  704. package/dist/knowledge/references/saas.website.blocks.actions.md +91 -0
  705. package/dist/knowledge/references/saas.website.blocks.band.md +41 -0
  706. package/dist/knowledge/references/saas.website.blocks.bento.md +70 -0
  707. package/dist/knowledge/references/saas.website.blocks.card-grid.md +115 -0
  708. package/dist/knowledge/references/saas.website.blocks.card.md +77 -0
  709. package/dist/knowledge/references/saas.website.blocks.cta-band.md +94 -0
  710. package/dist/knowledge/references/saas.website.blocks.define-block.md +123 -0
  711. package/dist/knowledge/references/saas.website.blocks.definitions.md +132 -0
  712. package/dist/knowledge/references/saas.website.blocks.faq.md +89 -0
  713. package/dist/knowledge/references/saas.website.blocks.feature-row.md +109 -0
  714. package/dist/knowledge/references/saas.website.blocks.hero.md +140 -0
  715. package/dist/knowledge/references/saas.website.blocks.intro.md +68 -0
  716. package/dist/knowledge/references/saas.website.blocks.latest-posts.md +104 -0
  717. package/dist/knowledge/references/saas.website.blocks.marquee.md +76 -0
  718. package/dist/knowledge/references/saas.website.blocks.pricing.md +395 -0
  719. package/dist/knowledge/references/saas.website.blocks.product-tour.md +158 -0
  720. package/dist/knowledge/references/saas.website.blocks.quote-cards.md +64 -0
  721. package/dist/knowledge/references/saas.website.blocks.roadmap.md +108 -0
  722. package/dist/knowledge/references/saas.website.blocks.section-slots.md +64 -0
  723. package/dist/knowledge/references/saas.website.blocks.solution-paths.md +71 -0
  724. package/dist/knowledge/references/saas.website.blocks.stats.md +183 -0
  725. package/dist/knowledge/references/saas.website.blocks.steps.md +69 -0
  726. package/dist/knowledge/references/saas.website.blocks.stylesheet.md +68 -0
  727. package/dist/knowledge/references/saas.website.blocks.tables.md +153 -0
  728. package/dist/knowledge/references/saas.website.blocks.vocabulary.md +227 -0
  729. package/dist/knowledge/references/saas.website.blog.bridge.md +98 -53
  730. package/dist/knowledge/references/saas.website.blog.collection-config.md +105 -49
  731. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +93 -0
  732. package/dist/knowledge/references/saas.website.blog.frontmatter.md +106 -9
  733. package/dist/knowledge/references/saas.website.blog.head-renderer.md +37 -19
  734. package/dist/knowledge/references/saas.website.blog.index-builder.md +63 -0
  735. package/dist/knowledge/references/saas.website.blog.index.md +43 -0
  736. package/dist/knowledge/references/saas.website.blog.post-cover.md +38 -0
  737. package/dist/knowledge/references/saas.website.blog.post-renderer.md +115 -87
  738. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +188 -0
  739. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +26 -0
  740. package/dist/knowledge/references/saas.website.blog.vocabulary-labels.md +113 -0
  741. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +5 -2
  742. package/dist/knowledge/references/saas.website.config.site-context-loader.md +26 -3
  743. package/dist/knowledge/references/saas.website.consent.banner.md +1 -1
  744. package/dist/knowledge/references/saas.website.consent.context.md +1 -1
  745. package/dist/knowledge/references/saas.website.design-tokens.bundle.md +28 -6
  746. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -6
  747. package/dist/knowledge/references/saas.website.design-tokens.compose-function.md +35 -0
  748. package/dist/knowledge/references/saas.website.design-tokens.compose.md +76 -0
  749. package/dist/knowledge/references/saas.website.design-tokens.personality-derivation.md +22 -0
  750. package/dist/knowledge/references/saas.website.design-tokens.personality-lexicon.md +31 -0
  751. package/dist/knowledge/references/saas.website.design-tokens.personality.md +82 -0
  752. package/dist/knowledge/references/saas.website.design-tokens.product.md +122 -0
  753. package/dist/knowledge/references/saas.website.design-tokens.radius.md +12 -1
  754. package/dist/knowledge/references/saas.website.design-tokens.readers.md +58 -0
  755. package/dist/knowledge/references/saas.website.design-tokens.spacing.md +61 -0
  756. package/dist/knowledge/references/saas.website.design-tokens.surface-depth.md +60 -0
  757. package/dist/knowledge/references/saas.website.design-tokens.tones.md +75 -0
  758. package/dist/knowledge/references/saas.website.design-tokens.typography.md +115 -0
  759. package/dist/knowledge/references/saas.website.factories.define-page-manifest.md +23 -21
  760. package/dist/knowledge/references/saas.website.factories.define-section.md +36 -38
  761. package/dist/knowledge/references/saas.website.format.publication-date.md +26 -0
  762. package/dist/knowledge/references/saas.website.label-keys.compose-helper.md +1 -1
  763. package/dist/knowledge/references/saas.website.label-keys.format.md +4 -3
  764. package/dist/knowledge/references/saas.website.label-pack.validator.md +9 -8
  765. package/dist/knowledge/references/saas.website.labels.section-labels.md +34 -0
  766. package/dist/knowledge/references/saas.website.legal.public-document-links.md +19 -4
  767. package/dist/knowledge/references/saas.website.locale-switcher.label-keys.md +35 -0
  768. package/dist/knowledge/references/saas.website.menu.icons.md +123 -0
  769. package/dist/knowledge/references/saas.website.menu.label-keys.md +112 -0
  770. package/dist/knowledge/references/saas.website.menu.schema.md +92 -0
  771. package/dist/knowledge/references/saas.website.menu.vocabulary.md +79 -0
  772. package/dist/knowledge/references/saas.website.motion.demo-player.md +105 -0
  773. package/dist/knowledge/references/saas.website.motion.demo-scenario.md +460 -0
  774. package/dist/knowledge/references/saas.website.motion.demo.md +324 -0
  775. package/dist/knowledge/references/saas.website.motion.element-attributes.md +115 -0
  776. package/dist/knowledge/references/saas.website.motion.reveal-renditions.md +67 -0
  777. package/dist/knowledge/references/saas.website.motion.stylesheet.md +82 -0
  778. package/dist/knowledge/references/saas.website.motion.tempo-table.md +99 -0
  779. package/dist/knowledge/references/saas.website.motion.tokens.md +46 -0
  780. package/dist/knowledge/references/saas.website.motion.vocabulary.md +85 -0
  781. package/dist/knowledge/references/saas.website.page-layout.component.md +34 -8
  782. package/dist/knowledge/references/saas.website.page-manifest.meta-label-keys.md +4 -4
  783. package/dist/knowledge/references/saas.website.page-manifest.route-path.md +1 -1
  784. package/dist/knowledge/references/saas.website.page-manifest.schema.md +25 -29
  785. package/dist/knowledge/references/saas.website.page-manifest.seo.md +1 -1
  786. package/dist/knowledge/references/saas.website.page-navigation.md +44 -0
  787. package/dist/knowledge/references/saas.website.page.context.md +9 -2
  788. package/dist/knowledge/references/saas.website.primitives.button.md +6 -6
  789. package/dist/knowledge/references/saas.website.primitives.heading.md +17 -18
  790. package/dist/knowledge/references/saas.website.primitives.image.md +18 -15
  791. package/dist/knowledge/references/saas.website.primitives.internal-button.md +11 -12
  792. package/dist/knowledge/references/saas.website.primitives.internal-link.md +11 -35
  793. package/dist/knowledge/references/saas.website.primitives.link.md +22 -11
  794. package/dist/knowledge/references/saas.website.primitives.text.md +10 -8
  795. package/dist/knowledge/references/saas.website.product.atoms.md +366 -0
  796. package/dist/knowledge/references/saas.website.product.figures.md +320 -0
  797. package/dist/knowledge/references/saas.website.product.hooks.md +278 -0
  798. package/dist/knowledge/references/saas.website.product.panels.md +324 -0
  799. package/dist/knowledge/references/saas.website.product.stylesheet.md +1086 -0
  800. package/dist/knowledge/references/saas.website.refs.section.md +2 -2
  801. package/dist/knowledge/references/saas.website.root-config.schema.md +34 -17
  802. package/dist/knowledge/references/saas.website.routing.link-target.md +70 -0
  803. package/dist/knowledge/references/saas.website.routing.localized-path.md +15 -8
  804. package/dist/knowledge/references/saas.website.runtime.context.md +44 -17
  805. package/dist/knowledge/references/saas.website.section.component.md +21 -19
  806. package/dist/knowledge/references/saas.website.sections.category-enum.md +21 -2
  807. package/dist/knowledge/references/saas.website.sections.definition-schema.md +47 -39
  808. package/dist/knowledge/references/saas.website.site-footer.menu.md +47 -0
  809. package/dist/knowledge/references/saas.website.site-header.component.md +100 -0
  810. package/dist/knowledge/references/saas.website.site-header.scroll-behavior.md +26 -0
  811. package/dist/knowledge/references/saas.website.stacking.md +86 -0
  812. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +162 -0
  813. package/dist/knowledge/references/saas.website.use-blog-index.hook.md +27 -0
  814. package/dist/knowledge/references/saas.website.use-label.hook.md +6 -4
  815. package/dist/knowledge/references/service-method.config.md +303 -0
  816. package/dist/knowledge/references/vision.constraint.config.md +4 -2
  817. package/dist/knowledge/references/website-plan.config.md +544 -32
  818. package/dist/knowledge/references/website-plan.menu-placement.md +118 -0
  819. package/dist/knowledge/references/website-plan.page-kind-essentials.md +42 -0
  820. package/dist/knowledge/references/website-plan.page-routes.md +39 -0
  821. package/dist/knowledge/references/workers.node.worker-init-contract.md +4 -2
  822. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +133 -9
  823. package/dist/knowledge/references/zod.decorators.chrome-modes.md +92 -0
  824. package/dist/knowledge/references/zod.decorators.data-categories.md +124 -34
  825. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +99 -6
  826. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +34 -1
  827. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +41 -7
  828. package/dist/knowledge/references/zod.decorators.file-schema.md +10 -8
  829. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +25 -9
  830. package/dist/knowledge/references/zod.decorators.primitive-ui.md +15 -3
  831. package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
  832. package/dist/knowledge/references/zod.decorators.schema-metadata.md +6 -0
  833. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +52 -18
  834. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +107 -5
  835. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +193 -9
  836. package/dist/knowledge/references/zod.factories.bigdecimal.md +17 -8
  837. package/dist/knowledge/references/zod.factories.code.md +18 -9
  838. package/dist/knowledge/references/zod.factories.duration.md +23 -14
  839. package/dist/knowledge/references/zod.factories.money.md +24 -15
  840. package/dist/knowledge/references/zod.factories.phone.md +23 -14
  841. package/dist/knowledge/references/zod.factories.range.md +5 -1
  842. package/dist/knowledge/references/zod.factories.year-month.md +79 -0
  843. package/dist/knowledge/registries/assurance-authority-bases.json +3 -3
  844. package/dist/knowledge/registries/framework-topics.json +5250 -2565
  845. package/dist/knowledge/registries/playbooks.json +88 -55
  846. package/dist/knowledge/registries/source-tags.json +9347 -4807
  847. package/dist/knowledge/rules/database-migration-obligation.md +10 -5
  848. package/dist/knowledge/rules/live-context-door.md +1 -1
  849. package/dist/knowledge/skills/INDEX.md +62 -33
  850. package/dist/knowledge/skills/agent-work-review/SKILL.md +86 -23
  851. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +227 -0
  852. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +2 -2
  853. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-decision-contents-api.md +79 -0
  854. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +4 -4
  855. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +6 -5
  856. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +22 -4
  857. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +16 -4
  858. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +20 -3
  859. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +16 -9
  860. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +24 -7
  861. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +376 -0
  862. package/dist/knowledge/skills/ai-use-declaration/SKILL.md +192 -0
  863. package/dist/knowledge/skills/ai-use-declaration/references/choosing-the-domain-and-class.md +73 -0
  864. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-classification-api.md +194 -0
  865. package/dist/knowledge/skills/ai-use-declaration/references/framework-ai-use-posture-api.md +136 -0
  866. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
  867. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
  868. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
  869. package/dist/knowledge/skills/application-database-migrations/SKILL.md +26 -9
  870. package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
  871. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +37 -1
  872. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
  873. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +24 -7
  874. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
  875. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +168 -3
  876. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +92 -0
  877. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
  878. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +66 -0
  879. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +6 -6
  880. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
  881. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +108 -2
  882. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +81 -10
  883. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
  884. package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
  885. package/dist/knowledge/skills/backend-custom-operation/references/framework-assurance-control-markers.md +3 -2
  886. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +5 -2
  887. package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
  888. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
  889. package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
  890. package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +79 -0
  891. package/dist/knowledge/skills/backend-custom-operation/references/framework-operation-base-and-path-api.md +20 -3
  892. package/dist/knowledge/skills/backend-custom-operation/references/framework-target-authority-api.md +61 -0
  893. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +368 -1
  894. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +191 -0
  895. package/dist/knowledge/skills/blueprint-authoring/references/blueprint-content-kinds.md +29 -0
  896. package/dist/knowledge/skills/blueprint-authoring/references/framework-blueprint-definition-api.md +490 -0
  897. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +127 -2
  898. package/dist/knowledge/skills/brand-logo-authoring/references/brand-authoring-decisions.md +15 -3
  899. package/dist/knowledge/skills/brand-logo-authoring/references/framework-brand-snapshot-api.md +26 -8
  900. package/dist/knowledge/skills/brand-logo-authoring/references/framework-style-word-lexicon-api.md +126 -0
  901. package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
  902. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
  903. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +166 -0
  904. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +307 -0
  905. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -1
  906. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -6
  907. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +179 -37
  908. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +4 -3
  909. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +13 -0
  910. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +48 -11
  911. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +10 -1
  912. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +896 -0
  913. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +184 -4
  914. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +46 -0
  915. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +487 -61
  916. package/dist/knowledge/skills/config-app-shell/SKILL.md +62 -29
  917. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +20 -18
  918. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +7 -3
  919. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-hosted-components-api.md +13 -0
  920. package/dist/knowledge/skills/config-app-shell/references/framework-brand-identity-api.md +20 -0
  921. package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
  922. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +21 -6
  923. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +24 -22
  924. package/dist/knowledge/skills/config-app-shell/references/framework-shell-layout-api.md +528 -0
  925. package/dist/knowledge/skills/config-design-system/SKILL.md +245 -162
  926. package/dist/knowledge/skills/config-design-system/references/design-system-file.md +5 -1
  927. package/dist/knowledge/skills/config-design-system/references/framework-focus-indicator-api.md +182 -0
  928. package/dist/knowledge/skills/config-design-system/references/framework-palette-contrast-api.md +195 -0
  929. package/dist/knowledge/skills/config-design-system/references/framework-palette-derivation-api.md +108 -0
  930. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +38 -0
  931. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +278 -0
  932. package/dist/knowledge/skills/config-design-system/references/theme-design-principles.md +202 -0
  933. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
  934. package/dist/knowledge/skills/config-navigation/references/framework-content-width-api.md +16 -5
  935. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +1 -1
  936. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +12 -1
  937. package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
  938. package/dist/knowledge/skills/config-saas/SKILL.md +4 -2
  939. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +51 -6
  940. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +18 -5
  941. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +333 -0
  942. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +29 -1
  943. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +83 -11
  944. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
  945. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -10
  946. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +1370 -0
  947. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +77 -2
  948. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +171 -26
  949. package/dist/knowledge/skills/config-saas/references/framework-value-moments-api.md +22 -0
  950. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +126 -32
  951. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
  952. package/dist/knowledge/skills/config-saas-backend/SKILL.md +16 -4
  953. package/dist/knowledge/skills/config-saas-backend/references/framework-application-owner-organization-codes-api.md +9 -10
  954. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
  955. package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
  956. package/dist/knowledge/skills/config-saas-backend/references/framework-federated-identity-provider-private-networks-api.md +6 -4
  957. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +167 -84
  958. package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
  959. package/dist/knowledge/skills/configure-billing/SKILL.md +20 -0
  960. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +38 -4
  961. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
  962. package/dist/knowledge/skills/configure-billing/references/framework-metered-usage-recording-api.md +109 -0
  963. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
  964. package/dist/knowledge/skills/configure-coding-agent/references/framework-acp-execution-profile-api.md +18 -2
  965. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
  966. package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +61 -0
  967. package/dist/knowledge/skills/email-add-template/SKILL.md +47 -6
  968. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
  969. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +10 -2
  970. package/dist/knowledge/skills/email-add-template/references/framework-email-template-api.md +134 -0
  971. package/dist/knowledge/skills/engine-product-definitions/references/framework-metered-usage-recording-api.md +28 -0
  972. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +102 -23
  973. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +103 -14
  974. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +35 -4
  975. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +98 -9
  976. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +71 -16
  977. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +160 -23
  978. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +10 -3
  979. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +14 -2
  980. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +298 -26
  981. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +78 -19
  982. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +455 -0
  983. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +446 -0
  984. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +208 -0
  985. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +174 -0
  986. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-ask-person-tool-api.md +121 -0
  987. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
  988. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +10 -3
  989. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +69 -0
  990. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +695 -11
  991. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +124 -6
  992. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +276 -0
  993. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-present-records-tool-api.md +150 -0
  994. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-retrieval-tool-api.md +251 -0
  995. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +120 -16
  996. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +339 -0
  997. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +283 -0
  998. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +134 -0
  999. package/dist/knowledge/skills/flows-actors-declared-flow/references/step-kinds.md +16 -0
  1000. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +91 -5
  1001. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +78 -1
  1002. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +16 -3
  1003. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-operation-and-model-api.md +13 -6
  1004. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +5 -4
  1005. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +29 -19
  1006. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +166 -21
  1007. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
  1008. package/dist/knowledge/skills/human-decision-notices/SKILL.md +150 -0
  1009. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-card-wording-api.md +292 -0
  1010. package/dist/knowledge/skills/human-decision-notices/references/framework-decision-notice-handler-api.md +340 -0
  1011. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +17 -1
  1012. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
  1013. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
  1014. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
  1015. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +35 -3
  1016. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
  1017. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
  1018. package/dist/knowledge/skills/inbound-channels/SKILL.md +93 -13
  1019. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +49 -4
  1020. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +245 -27
  1021. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +8 -8
  1022. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +471 -6
  1023. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-pipelines-api.md +73 -0
  1024. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +44 -5
  1025. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +39 -16
  1026. package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
  1027. package/dist/knowledge/skills/infra-environment-config/SKILL.md +226 -73
  1028. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
  1029. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +140 -7
  1030. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +2 -1
  1031. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +370 -0
  1032. package/dist/knowledge/skills/layout-2d-adoption/SKILL.md +158 -0
  1033. package/dist/knowledge/skills/layout-2d-adoption/references/choosing-a-layout.md +43 -0
  1034. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +167 -0
  1035. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-registration-api.md +101 -0
  1036. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-settings-api.md +59 -0
  1037. package/dist/knowledge/skills/layout-2d-adoption/references/framework-shell-motion-api.md +415 -0
  1038. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +1 -0
  1039. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
  1040. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
  1041. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +65 -32
  1042. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +14 -36
  1043. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +7 -3
  1044. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
  1045. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
  1046. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +7 -5
  1047. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
  1048. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
  1049. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
  1050. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +14 -1
  1051. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +33 -2
  1052. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +42 -2
  1053. package/dist/knowledge/skills/market-generation-cli/SKILL.md +49 -7
  1054. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +63 -9
  1055. package/dist/knowledge/skills/minion-authoring/examples/contained-tick.example.md +1 -1
  1056. package/dist/knowledge/skills/minion-authoring/references/framework-minion-tick-contract.md +2 -2
  1057. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +43 -11
  1058. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +58 -3
  1059. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +57 -21
  1060. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +7 -3
  1061. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +257 -46
  1062. package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
  1063. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +30 -2
  1064. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +110 -1
  1065. package/dist/knowledge/skills/module-relationships/SKILL.md +143 -119
  1066. package/dist/knowledge/skills/module-relationships/references/framework-resource-relationship-authoring-api.md +8 -4
  1067. package/dist/knowledge/skills/organization-relationships/SKILL.md +668 -0
  1068. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +1259 -0
  1069. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-capability-grants-api.md +243 -0
  1070. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +284 -0
  1071. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +555 -0
  1072. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +163 -0
  1073. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +149 -0
  1074. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +5 -3
  1075. package/dist/knowledge/skills/professional-qualifications/SKILL.md +173 -0
  1076. package/dist/knowledge/skills/professional-qualifications/references/choosing-who-may-decide.md +53 -0
  1077. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +98 -0
  1078. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-required-qualifications-api.md +39 -0
  1079. package/dist/knowledge/skills/professional-qualifications/references/framework-professional-qualifications-api.md +223 -0
  1080. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +1 -1
  1081. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +3 -3
  1082. package/dist/knowledge/skills/provider-backend-package/SKILL.md +388 -11
  1083. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +31 -28
  1084. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +16 -0
  1085. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
  1086. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
  1087. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +13 -0
  1088. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +755 -0
  1089. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +235 -0
  1090. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
  1091. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
  1092. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +72 -8
  1093. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-subject-erasure-effect-api.md +222 -0
  1094. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +9 -5
  1095. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +11 -2
  1096. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +50 -5
  1097. package/dist/knowledge/skills/provider-frontend-module/references/framework-on-demand-capabilities-api.md +306 -0
  1098. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +11 -3
  1099. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +41 -15
  1100. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +56 -18
  1101. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +1 -1
  1102. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +143 -25
  1103. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +6 -0
  1104. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +9 -6
  1105. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1275 -4
  1106. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +71 -35
  1107. package/dist/knowledge/skills/rate-limit-authoring/references/framework-rate-limit-policy-api.md +27 -13
  1108. package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
  1109. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +32 -12
  1110. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +451 -67
  1111. package/dist/knowledge/skills/resource-add-resource/SKILL.md +57 -8
  1112. package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
  1113. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +165 -44
  1114. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +138 -0
  1115. package/dist/knowledge/skills/resource-chat-commands/references/framework-resource-chat-command-contract.md +72 -0
  1116. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +171 -7
  1117. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +4 -4
  1118. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +17 -8
  1119. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +8 -2
  1120. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +371 -0
  1121. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +51 -7
  1122. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +163 -0
  1123. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
  1124. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +200 -61
  1125. package/dist/knowledge/skills/resource-config-wiring/references/framework-request-field-offers-api.md +168 -0
  1126. package/dist/knowledge/skills/resource-config-wiring/references/framework-required-features-api.md +20 -0
  1127. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +8 -3
  1128. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
  1129. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +8 -6
  1130. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +351 -159
  1131. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +160 -2
  1132. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +440 -119
  1133. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +426 -32
  1134. package/dist/knowledge/skills/resource-config-wiring/references/framework-webhook-events-api.md +116 -0
  1135. package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
  1136. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +344 -62
  1137. package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
  1138. package/dist/knowledge/skills/resource-external-data/SKILL.md +326 -76
  1139. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +335 -0
  1140. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +18 -6
  1141. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +71 -12
  1142. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +6 -0
  1143. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +96 -26
  1144. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +257 -57
  1145. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +111 -11
  1146. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +147 -0
  1147. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +30 -4
  1148. package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
  1149. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +21 -9
  1150. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +62 -15
  1151. package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
  1152. package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
  1153. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +18 -2
  1154. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +3 -1
  1155. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +65 -18
  1156. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +17 -7
  1157. package/dist/knowledge/skills/resource-external-data/references/requested-keys.md +104 -0
  1158. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +77 -7
  1159. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +25 -4
  1160. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/framework-resource-mcp-exposure-contract.md +2 -2
  1161. package/dist/knowledge/skills/resource-mcp-tool-exposure/references/mcp-catalogue-withdrawal-and-verification.md +1 -1
  1162. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +18 -9
  1163. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +42 -3
  1164. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
  1165. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
  1166. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +21 -3
  1167. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +114 -7
  1168. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
  1169. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
  1170. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
  1171. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +46 -0
  1172. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
  1173. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +27 -11
  1174. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +23 -7
  1175. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +13 -8
  1176. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
  1177. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +4 -0
  1178. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +105 -6
  1179. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +19 -22
  1180. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +150 -35
  1181. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +32 -4
  1182. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +58 -18
  1183. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +107 -5
  1184. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +200 -69
  1185. package/dist/knowledge/skills/resource-schema-authoring/references/framework-system-managed-fields-api.md +2 -1
  1186. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +326 -18
  1187. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +7 -0
  1188. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
  1189. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
  1190. package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
  1191. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
  1192. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +219 -77
  1193. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +105 -24
  1194. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +131 -1
  1195. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +41 -7
  1196. package/dist/knowledge/skills/resource-ui-behavior/references/framework-field-tiles-api.md +114 -0
  1197. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +428 -72
  1198. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +25 -9
  1199. package/dist/knowledge/skills/resource-ui-behavior/references/framework-primitive-ui-api.md +15 -3
  1200. package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
  1201. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +223 -6
  1202. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +186 -65
  1203. package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
  1204. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +138 -0
  1205. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +89 -32
  1206. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +73 -0
  1207. package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
  1208. package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
  1209. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
  1210. package/dist/knowledge/skills/seeding-authoring/references/data-seeding-mode-picker.md +16 -1
  1211. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
  1212. package/dist/knowledge/skills/seeding-operations/references/data-seeding-admin-runbook.md +15 -8
  1213. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +3 -0
  1214. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +48 -11
  1215. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +183 -32
  1216. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +72 -13
  1217. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +5 -4
  1218. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +5 -4
  1219. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
  1220. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +30 -2
  1221. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +15 -7
  1222. package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
  1223. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +186 -83
  1224. package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
  1225. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +113 -70
  1226. package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
  1227. package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
  1228. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
  1229. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
  1230. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +14 -5
  1231. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -1
  1232. package/dist/knowledge/skills/views-add-custom-view/references/framework-focus-indicator-api.md +145 -0
  1233. package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
  1234. package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
  1235. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +41 -5
  1236. package/dist/knowledge/skills/views-chart-authoring/references/framework-chart-view-contracts-api.md +13 -0
  1237. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
  1238. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +15 -4
  1239. package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +244 -0
  1240. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +11 -2
  1241. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +57 -3
  1242. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +61 -25
  1243. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +253 -78
  1244. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +1105 -222
  1245. package/dist/knowledge/skills/website-building-blocks/SKILL.md +337 -0
  1246. package/dist/knowledge/skills/website-building-blocks/references/framework-website-blocks-api.md +3050 -0
  1247. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +627 -0
  1248. package/dist/knowledge/skills/website-building-blocks/references/framework-website-product-kit-api.md +3309 -0
  1249. package/dist/knowledge/skills/website-building-blocks/references/website-visual-quality-rubric.md +75 -0
  1250. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +42 -19
  1251. package/dist/knowledge/skills/website-bundle-discipline/references/example-website-button-override.md +8 -12
  1252. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +20 -5
  1253. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +84 -28
  1254. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +67 -64
  1255. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +58 -23
  1256. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +5 -1
  1257. package/dist/knowledge/skills/website-label-pack/SKILL.md +43 -21
  1258. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +112 -77
  1259. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +24 -13
  1260. package/dist/knowledge/skills/website-motion-design/SKILL.md +277 -0
  1261. package/dist/knowledge/skills/website-motion-design/references/framework-motion-api.md +1562 -0
  1262. package/dist/knowledge/skills/website-motion-design/references/industry-practice.md +28 -0
  1263. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +255 -397
  1264. package/dist/knowledge/skills/website-navigation-authoring/references/framework-menu-api.md +712 -0
  1265. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +28 -6
  1266. package/dist/knowledge/skills/website-navigation-authoring/references/menu-keys-and-styling.md +151 -0
  1267. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +131 -326
  1268. package/dist/knowledge/skills/website-page-authoring/SKILL.md +160 -67
  1269. package/dist/knowledge/skills/website-page-authoring/references/framework-page-kinds-api.md +982 -0
  1270. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +29 -5
  1271. package/dist/knowledge/skills/website-page-authoring/references/homepage-content-and-art-direction.md +19 -0
  1272. package/dist/knowledge/skills/website-page-authoring/references/page-kinds.md +118 -0
  1273. package/dist/knowledge/skills/website-page-variants/SKILL.md +70 -69
  1274. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +48 -28
  1275. package/dist/knowledge/skills/website-section-comparison/SKILL.md +1171 -0
  1276. package/dist/knowledge/skills/website-section-comparison/references/define-website-section-api.md +679 -0
  1277. package/dist/knowledge/skills/website-section-comparison/references/framework-website-tables-api.md +487 -0
  1278. package/dist/knowledge/skills/website-section-contact/SKILL.md +409 -186
  1279. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +197 -119
  1280. package/dist/knowledge/skills/website-section-cta/SKILL.md +399 -235
  1281. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +197 -119
  1282. package/dist/knowledge/skills/website-section-faq/SKILL.md +562 -303
  1283. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +197 -119
  1284. package/dist/knowledge/skills/website-section-faq/references/framework-website-faq-api.md +489 -0
  1285. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +648 -275
  1286. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +197 -119
  1287. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +573 -265
  1288. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +197 -119
  1289. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +533 -234
  1290. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +197 -119
  1291. package/dist/knowledge/skills/website-section-hero/SKILL.md +604 -333
  1292. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +198 -120
  1293. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1150 -0
  1294. package/dist/knowledge/skills/website-section-how-it-works/references/define-website-section-api.md +679 -0
  1295. package/dist/knowledge/skills/website-section-how-it-works/references/framework-website-steps-api.md +337 -0
  1296. package/dist/knowledge/skills/website-section-integrations/SKILL.md +974 -0
  1297. package/dist/knowledge/skills/website-section-integrations/references/define-website-section-api.md +679 -0
  1298. package/dist/knowledge/skills/website-section-integrations/references/framework-website-marquee-api.md +825 -0
  1299. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +928 -0
  1300. package/dist/knowledge/skills/website-section-latest-posts/references/define-website-section-api.md +679 -0
  1301. package/dist/knowledge/skills/website-section-latest-posts/references/framework-website-latest-posts-api.md +465 -0
  1302. package/dist/knowledge/skills/website-section-pricing/SKILL.md +594 -379
  1303. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +189 -0
  1304. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +197 -119
  1305. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +5 -2
  1306. package/dist/knowledge/skills/website-section-pricing/references/framework-website-pricing-api.md +670 -0
  1307. package/dist/knowledge/skills/website-section-problem/SKILL.md +1150 -0
  1308. package/dist/knowledge/skills/website-section-problem/references/define-website-section-api.md +679 -0
  1309. package/dist/knowledge/skills/website-section-problem/references/framework-website-card-grid-api.md +664 -0
  1310. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1322 -0
  1311. package/dist/knowledge/skills/website-section-product-showcase/references/define-website-section-api.md +679 -0
  1312. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-card-grid-api.md +533 -0
  1313. package/dist/knowledge/skills/website-section-product-showcase/references/framework-website-product-tour-api.md +917 -0
  1314. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +1133 -0
  1315. package/dist/knowledge/skills/website-section-roadmap/references/define-website-section-api.md +679 -0
  1316. package/dist/knowledge/skills/website-section-roadmap/references/framework-website-roadmap-api.md +475 -0
  1317. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +740 -316
  1318. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +197 -119
  1319. package/dist/knowledge/skills/website-section-social-proof/references/framework-website-quote-cards-api.md +623 -0
  1320. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +1057 -0
  1321. package/dist/knowledge/skills/website-section-solution-paths/references/define-website-section-api.md +679 -0
  1322. package/dist/knowledge/skills/website-section-solution-paths/references/framework-website-solution-paths-api.md +477 -0
  1323. package/dist/knowledge/skills/website-section-stats/SKILL.md +1086 -0
  1324. package/dist/knowledge/skills/website-section-stats/references/define-website-section-api.md +679 -0
  1325. package/dist/knowledge/skills/website-section-stats/references/framework-website-stats-api.md +517 -0
  1326. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +183 -67
  1327. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +576 -57
  1328. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +1 -1
  1329. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +6 -94
  1330. package/dist/knowledge/skills/website-theme-authoring/SKILL.md +226 -0
  1331. package/dist/knowledge/skills/website-theme-authoring/references/framework-website-theme-api.md +893 -0
  1332. package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
  1333. package/dist/knowledge/skills/worker-authoring/references/framework-worker-init-contract.md +4 -2
  1334. package/dist/knowledge/topic-index.json +17998 -8568
  1335. package/dist/tsconfig.build.tsbuildinfo +1 -1
  1336. package/package.json +6 -6
  1337. package/dist/knowledge/references/example.organizations.serves-as-provider.md +0 -12
  1338. package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +0 -169
  1339. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +0 -121
  1340. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +0 -49
  1341. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +0 -567
  1342. package/dist/knowledge/references/saas.website.root-config.navigation.md +0 -37
  1343. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +0 -455
  1344. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +0 -270
  1345. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +0 -129
  1346. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +0 -161
  1347. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +0 -224
  1348. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +0 -576
  1349. package/dist/tsconfig.tsbuildinfo +0 -1
@@ -132,7 +132,7 @@ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a place
132
132
  | `APPLICATION_VIEW` | `viewRef` | an app-level view. With an experience plan, the `viewRef` is the plan's own (`view-…`), verbatim |
133
133
  | `APPLICATION_DOCUMENT` | `documentRef` | a governed document the engine catalog DEFINES — see the closed list below. Never a document you name yourself |
134
134
  | `APPLICATION_MODULE` | `moduleRef` | an ensure-module task. The REGISTRY entry, not the directory |
135
- | `APPLICATION_FRONTEND_CONFIG` | `configSurface` + the `declarationRefs` the file gains | composing ONE app-wide config file — `NAVIGATION`, `DESIGN_SYSTEM`, `APP_SHELL`, `GLOBAL_VIEWS`. The DECLARATIONS (a sidebar section ref, a zone, a token), never the file: `wildo init` writes all four |
135
+ | `APPLICATION_FRONTEND_CONFIG` | `configSurface` + the `declarationRefs` the file gains | composing ONE app-wide config file — `NAVIGATION`, `DESIGN_SYSTEM`, `APP_SHELL`, `GLOBAL_VIEWS`, `SHELL_LAYOUT`. The DECLARATIONS (a sidebar section ref, a zone, a token, the one layout constant), never the file: `wildo init` writes every one of them |
136
136
  | `RESOURCE_COMPOSITE_VIEW` | `resourceRef` + `viewRef` | a composite view of one resource, bound in its ui-behavior's `compositeViews`. The plan's `viewRef`, verbatim |
137
137
  | `RESOURCE_CUSTOM_VIEW` | `resourceRef` + `viewRef` | a custom operation view or an execution view of one resource, bound in its ui-behavior. The plan's `viewRef`, verbatim — it is how the dispatch tells an execution view from a custom one |
138
138
  | `RESOURCE_CHART_VIEW` | `resourceRef` + `chartRef` | a chart view declared under the resource's `chartViews` |
@@ -142,14 +142,24 @@ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a place
142
142
  | `PDF_TEMPLATE` | `resourceRef` + `templateRef` | a PDF template BOUND to a resource's generated-file field (`generatedSummaryPdf`) |
143
143
  | `APPLICATION_WORKER` | `workerRef` + the `jobRefs` its entry file declares | a worker's behaviour. The JOBS, not the package: `add-worker-node` / `add-worker-rust` write the package |
144
144
  | `APPLICATION_MINION` | `minionRef` + the `behaviorRefs` its entry file declares | a minion's tick behaviour. Same rule: `add-minion` writes the package |
145
- | `PROVIDER_BINDING` | `providerRef` + `scope` (`BACKEND`, `COMPANION`, `FRONTEND_APP`, `WEBSITE`) | one provider declared in one runtime owner's scope — the SaaS config block, or the service's `provider-contributions.ts` |
145
+ | `PROVIDER_BINDING` | `providerRef` + `scope` (`BACKEND`, `COMPANION`, `FRONTEND_APP`, `WEBSITE`), + `augments` when the binding has it | one provider declared in one runtime owner's scope — the SaaS config block, or the service's `provider-contributions.ts`. With `augments`, the module's opt-in under `providers.augmentations.<augments>` instead |
146
146
  | `WEBSITE_PAGE` | `pageRef` | a marketing page, registered in `website-root.config.ts` by its manifest |
147
147
  | `WEBSITE_SECTION` | `pageRef` + `sectionRef` | one section of one page, declared in `<pageRef>.sections.tsx` |
148
- | `DOCUMENTATION_CHAPTER` | `chapterRef` | the chapter's authored body, keyed by its `chapterRef` in `specifications/src/technical-documentation/index.ts`, which `wildo docs publish` joins to the documentation plan and publishes under `/guides/<slug>` |
148
+ | `DOCUMENTATION_CHAPTER` | `chapterRef` | the chapter's authored body, in its own file `specifications/src/technical-documentation/chapters/<chapterRef>.ts`, which `wildo docs publish` joins to the documentation plan and publishes under `/guides/<slug>` |
149
149
  | `APPLICATION_BILLING_PRODUCT` | `productKey` | one product of the application's billing catalogue, named by its catalogue `key` (a slug, e.g. `team`) — declared in `shared-lib/src/engine/product.ts` under the `BILLING_CATALOG` target. The KEY, never the file: `wildo init` writes the file with an empty catalogue |
150
150
  | `APPLICATION_ROLE` | `roleRef` | one role the application declares, named by its key in `CUSTOM_ROLES_CONFIGURATION` (upper snake case, e.g. `FIELD_TECHNICIAN`; never a core role such as `ORG_MEMBER`) — declared in `shared-lib/src/engine/roles.ts` under the `APPLICATION_ROLES` target. The NAME, never the file: `wildo init` writes the file with an empty table |
151
151
  | `APPLICATION_DATA_SEED` | `seedKey` + `resourceRef` + `content` (`REFERENCE` or `DEMONSTRATION`) | one data seed a module declares, named by its key (`<moduleRef>:<purpose>`, e.g. `crm:demo-customers`) — the file `backend-api/src/modules/<moduleRef>/seeds/<seedKey with : as .>.seed.ts`, registered by the module. A `DEMONSTRATION` seed lands only once it declares the environments it runs in, without production |
152
152
  | `INBOUND_CHANNEL_HANDLER` | `channel` + the handler's `handlerRef` (`<moduleRef>.<purpose>`, e.g. `matters.mail-intake`) | the handler that decides what a message arriving on a channel the integration plan declared causes. Its file is `backend-api/src/modules/<moduleRef>/inbound/<handlerRef>.inbound-channel-handler.ts`, and it lands when the module's backend `index.ts` imports that file — which is how it is registered on `inboundHandlers` |
153
+ | `APPLICATION_AGENT` | `agentRef` + `shape` (`CHAT_ASSISTANT`, `AUTONOMOUS`, `INVOKED`, `FLOW_STEP`) | one AI agent, named by the `ref` it is registered under (lower case, e.g. `tasks.overdue-triage`). An `AUTONOMOUS` agent is named by its autonomous declaration's `ref`, every other shape by the agent's own. It lands when the TASK'S module registers that ref (`flowsActors.agents`, or `autonomousAgents` for `AUTONOMOUS`) and the module's backend `index.ts`, its `addons/flows-actors/index.ts` and every file that index imports are present. The shape also decides the skill the task is built with |
154
+ | `AGENT_APPROVAL_GATE` | `functionRef` + `route` (`owner`, `role`, `assignee`) + `eligibleRole` for `role` and `assignee` | the approval gate on one function tool an agent calls, named by the `functionRef` it is registered under — `resource.<resourceType>.<operation>` for a resource tool, with the resource type as the code spells it (`resource.adjustmentProposals.post`). Its calls wait for the person the route names. `owner` is the person whose turn it is and takes no role; `role` and `assignee` name the role the approver must hold (a role the application declares, or a core role). It lands only when the registered tool's gate has that route AND that role, so a gate routed to anyone else does not land |
155
+ | `WORK_UNIT_RESOURCE` | `resourceRef` | the resource whose rows are the application's CASES — the unit model spend is attributed to and cost per case is read by. It lands when the resource's configuration declares `workUnit: true` |
156
+ | `METERED_USAGE_RECORDING` | `resourceRef` + `operationRef` + `productKey` + `oncePerRecord`, and `serviceMethodServiceRef` when it bills a service of the firm's method | one operation of one resource that records usage of one METERED billing product when it succeeds (`recordsUsage` on the operation), named by the operation as the resource's configuration keys it (`record-sign-off` for `record_sign_off`) and the product's catalogue `key`. `oncePerRecord: true` counts each row once, which is what a price per case needs. It lands when the resource's configuration declares exactly that recording on that operation |
157
+ | `RESOURCE_RETENTION_BINDING` | `resourceRef` + `retentionClass` (`RESOURCE_DATA`, `FILES`, `AUDIT_LOGS`, `OPERATIONAL_LOGS`, `BUSINESS_RECORDS`) | how long one resource's rows are kept: its configuration's `retentionBinding` in that class. It lands when the resource's configuration declares that class |
158
+ | `RELATIONSHIP_CONFERRED_ROLE` | `relationshipRef` (the relationship kind's key, e.g. `service`) + `roleRef` | one role an organization relationship confers: in `wildo.saas.config.ts`, the kind's `confers.roles` holds it and every organization type the kind grants offers it in `availableOrgRoles`. Under the `APPLICATION_ROLES` target. It lands when the configuration, read fresh, says so |
159
+ | `ORGANIZATION_TYPE` | `organizationTypeRef` (the entry's `ref`, e.g. `regulated-client`), + `ownsApplication: true` for the type that operates the application, + the entry's `offeredRoles`, `userTypes` and `requiresMfa` | one organization type the domain plan's organization model declares, in `organizationTypes` of `wildo.saas.config.ts`. Under the `ORGANIZATION_MODEL` target. The OWNER type is the configuration's own `ownsApplication` type whatever its key; any other type is found by its key. It lands when that type, read fresh, offers those roles, grants those user types and requires a second factor as planned |
160
+ | `ORGANIZATION_RELATIONSHIP_KIND` | `relationshipRef` (the kind's key, e.g. `partnership`) | one kind of relationship between organizations: a key of `organizationRelationships` in `wildo.saas.config.ts`. Under the `ORGANIZATION_MODEL` target. Never a module and never a resource: the engine owns the relationship rows. It lands when the configuration, read fresh, declares the key |
161
+ | `ORGANIZATION_UNIT_CONFINEMENT` | `resourceRef` + `mode` (`ORGANIZATION_UNIT` or `OWN_ROWS`) + `fieldName` | one resource whose rows are confined below the whole organization: to the unit a member holds a role in (`organizationUnitNarrowing`, on the unit field, usually `organizationUnitId`), or to the rows a member owns (`organizationOwnRows`, on the owner's field, usually `createdByUserId`), in `backend-api/src/bootstrap-config.ts`. Under the `ORGANIZATION_MODEL` target. One resource may carry both modes, as two products. It lands when the backend's startup configuration declares the resource in that mode on that field |
162
+ | `SYSTEM_OF_RECORD_BINDING` | `resourceRef` + `systemOfRecordRef` (the instance's key under `systemsOfRecord`, e.g. `odoo`) + `systemOfRecordKind` (the vendor's facet the domain plan names, e.g. `odoo`) + `access` (`READ_THROUGH` or `OWNED_COPY`) + `partitioned` (`true` when the domain plan splits the records by legal entity) | one resource whose records live in another system: its configuration's `httpApiBinding` (read through) or inbound `externalDataPipeline` (copied) names the instance. Carried by the resource's CONFIG task, since the binding is its configuration. It lands when the configuration binds that instance through that lane and `wildo.saas.config.ts` declares the instance with that `vendor`, with `partition: true` exactly when `partitioned` is true; a copy of a partitioned instance also declares `partitionUnitLocalField` and `partitionKeyLocalField` on its pipeline |
153
163
 
154
164
  **A GOVERNED DOCUMENT is chosen from a closed list, never invented.** There are six,
155
165
  and a `documentRef` names one of them in exactly this form:
@@ -236,7 +246,7 @@ export enum BuildPlanTaskTargetKind {
236
246
  MODULE = 'MODULE',
237
247
  /** One build stage of one resource: schema → config → ui-behavior → spec. */
238
248
  RESOURCE_STAGE = 'RESOURCE_STAGE',
239
- /** One relationship between two resources. */
249
+ /** The relationships between resources wired in ONE module's relationships file (#3209): one task per file, not per edge. */
240
250
  RELATIONSHIP = 'RELATIONSHIP',
241
251
  /** A companion-owned deterministic generation step (labels, email templates, logo or database migrations) interleaved by the build loop, never a coding-agent run. */
242
252
  COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',
@@ -283,7 +293,7 @@ export enum BuildPlanTaskTargetKind {
283
293
  MODULE_BACKEND = 'MODULE_BACKEND',
284
294
  /**
285
295
  * ONE application-wide frontend configuration surface — navigation, the design system, the app
286
- * shell's composition, the global views — named by {@link FrontendConfigSurface}.
296
+ * shell's composition, the global views, the shell layout — named by {@link FrontendConfigSurface}.
287
297
  *
288
298
  * Distinct from {@link SHELL_PLACEMENT}, which authors the placement plan's decisions into the
289
299
  * shell files: a placement puts a decided subject in a decided group, while this kind COMPOSES
@@ -333,12 +343,27 @@ export enum BuildPlanTaskTargetKind {
333
343
  * modelled roles as an access-role RESOURCE that nothing reads.
334
344
  */
335
345
  APPLICATION_ROLES = 'APPLICATION_ROLES',
346
+ /**
347
+ * The application's ORGANIZATION MODEL (#3035, #3036): the organization types and the relationship kinds between them,
348
+ * declared in `wildo.saas.config.ts` (`organizationTypes`, `organizationRelationships`), and the confinements of an
349
+ * organization's rows to its units or to their owners, declared in the backend's startup configuration
350
+ * (`backend-api/src/bootstrap-config.ts`: `organizationUnitNarrowing`, `organizationOwnRows`).
351
+ *
352
+ * Its own kind because none of the others is true of it. It is application-wide and names no module, like the role
353
+ * table, but it is not the role table: an organization type is the shape a tenant takes (its user types, the roles it
354
+ * offers, how it is joined), and a relationship kind is what one organization may do for another. Borrowing
355
+ * `APPLICATION_ROLES` would have given a task deciding them the role table's scope and the roles skill. Before it
356
+ * existed, creation could lay these down only from fixed blueprints, and a confinement the requirements stated
357
+ * produced no work at all, so a generated internal tool showed every record to every member.
358
+ */
359
+ ORGANIZATION_MODEL = 'ORGANIZATION_MODEL',
336
360
  }
337
361
 
338
362
  /**
339
- * WHICH application-wide frontend configuration surface a task composes — one file each, in
340
- * `frontend/src/config/`, and the coding policy resolves the member to that file exactly as
341
- * `SHELL_PLACEMENT` resolves a `PlacementSurface`.
363
+ * WHICH application-wide frontend configuration surface a task composes — one file each (in
364
+ * `frontend/src/config/`, except the shell layout, whose one line lives in the engine registrations
365
+ * file), and the coding policy resolves the member to that file exactly as `SHELL_PLACEMENT` resolves
366
+ * a `PlacementSurface`.
342
367
  *
343
368
  * Its own vocabulary rather than a reuse of `PlacementSurface`: a placement surface is WHERE a
344
369
  * subject sits in the shell (settings hub, sidebar, user menu, command palette), and three of
@@ -354,6 +379,14 @@ export enum FrontendConfigSurface {
354
379
  APP_SHELL = 'APP_SHELL',
355
380
  /** `frontend/src/config/global-views.config.ts` — the application-level launcher and view registrations. */
356
381
  GLOBAL_VIEWS = 'GLOBAL_VIEWS',
382
+ /**
383
+ * `frontend/src/engine/component-registrations.frontend.ts` — the ONE animated 2D shell layout the application moves
384
+ * in (`register2DLayout(MORPH_LAYOUT_2D, { speed })`), decided beside the design system because both are the
385
+ * brand's: the design system its palette and pace, the layout how the shell moves at that pace. Its single
386
+ * declaration names the layout constant, written out. A 3D layout is never decided here: it is the operator's
387
+ * opt-in, through the `add-3d-layout` composition scenario.
388
+ */
389
+ SHELL_LAYOUT = 'SHELL_LAYOUT',
357
390
  }
358
391
 
359
392
  /**
@@ -405,6 +438,40 @@ export enum ProviderBindingScope {
405
438
  WEBSITE = 'WEBSITE',
406
439
  }
407
440
 
441
+ /**
442
+ * The inbound channels a creation run can PLAN (#1630, #3394): the members of `InboundChannelKind` an application
443
+ * declares as channels work arrives on, and that a channel handler can be built for. One list, read by the integration
444
+ * plan's declaration and by the build task's product, so the two cannot disagree about what is plannable.
445
+ *
446
+ * `EMAIL` (received by the `EMAIL_INBOUND` provider, routed by the address) and `SMS` (received by the SMS provider's
447
+ * notification endpoint, routed by the number the text was sent TO). `WEBHOOK` is absent on purpose: it is the channel
448
+ * every signed delivery from another system arrives on, derived for that delivery and never declared.
449
+ *
450
+ * ## A NAMED const object, not a TypeScript enum and not an array (#3685)
451
+ *
452
+ * The schemas read it as `z.enum(PlannableInboundChannelKind)`, so the schema node keeps THIS object as its
453
+ * vocabulary, and a landed build or integration plan can name it: `deriveLandingRenderEnumBindings` resolves an
454
+ * enum node by the IDENTITY of that object against the package's exports. `z.enum([EMAIL, SMS])` built a fresh
455
+ * anonymous object, which nothing exports, so every plan landing refused ("Closed vocabularies with no exported
456
+ * name … tasks.*.produces.*.channel (email, sms)"), so no build plan could land at all.
457
+ *
458
+ * Not a TypeScript enum, because a subset of a vocabulary must keep the OWNER's members: an enum would make
459
+ * `PlannableInboundChannelKind.SMS` a nominal type of its own, no longer an `InboundChannelKind`, and every reader
460
+ * that maps a planned channel onto the inbound vocabulary would stop compiling. Each member here IS the
461
+ * `InboundChannelKind` member, so a landed `PlannableInboundChannelKind.SMS` is assignable where the channel is read.
462
+ */
463
+ export const PlannableInboundChannelKind = {
464
+ EMAIL: InboundChannelKind.EMAIL,
465
+ SMS: InboundChannelKind.SMS,
466
+ } as const;
467
+ export type PlannableInboundChannelKind = (typeof PlannableInboundChannelKind)[keyof typeof PlannableInboundChannelKind];
468
+
469
+ /**
470
+ * The same vocabulary as a list, for code that iterates it. Derived from {@link PlannableInboundChannelKind}, never
471
+ * written twice.
472
+ */
473
+ export const PLANNABLE_INBOUND_CHANNEL_KINDS: readonly PlannableInboundChannelKind[] = Object.values(PlannableInboundChannelKind);
474
+
408
475
  /** The per-resource build stages, in their fixed order. */
409
476
  export enum BuildPlanResourceStage {
410
477
  SCHEMA = 'SCHEMA',
@@ -611,6 +678,108 @@ export enum BuildPlanTaskProductKind {
611
678
  * table, so the file proves nothing (#2490).
612
679
  */
613
680
  APPLICATION_ROLE = 'APPLICATION_ROLE',
681
+ /*
682
+ * AGENT WORK (#2966). An agent, the approval gate on one of its tools, and the resource whose rows are the cases its
683
+ * work is costed to. None of them is a name the tree spells in one file: an agent's ref and a gate's role are written
684
+ * through constants in other files, and a gate is a property of a tool object. So each is proven from the REGISTRY the
685
+ * application's backend registers at startup, read through introspection, never from text.
686
+ */
687
+ /**
688
+ * One AI agent the application registers, named by its `ref` — a chat agent's (`agents`) or an autonomous agent's
689
+ * (`autonomousAgents`), as its {@link BuildPlanAgentShape} says. Its shape also decides the skill it is built with.
690
+ */
691
+ APPLICATION_AGENT = 'APPLICATION_AGENT',
692
+ /**
693
+ * The approval gate on one function tool (`humanApproval`): its calls wait for the person the ROUTE names, holding the
694
+ * role the gate requires. Proven when the registered tool's gate has that route and that role, so a gate routed to the
695
+ * wrong role, or a tool left ungated, does not land.
696
+ */
697
+ AGENT_APPROVAL_GATE = 'AGENT_APPROVAL_GATE',
698
+ /**
699
+ * One resource declared as the application's unit of work (`workUnit: true`): its rows are the cases model spend is
700
+ * attributed to, and cost per case is read by them.
701
+ */
702
+ WORK_UNIT_RESOURCE = 'WORK_UNIT_RESOURCE',
703
+ /**
704
+ * One operation of one resource that records usage of one METERED billing product when it succeeds (`recordsUsage`,
705
+ * #2305 S5). How a price per case is billed: the operation that closes a case records one unit, once per case. Proven
706
+ * from the registry like the agent work: the declaration is a property of one operation object in the resource's
707
+ * configuration, which no text in the tree ties to that operation.
708
+ */
709
+ METERED_USAGE_RECORDING = 'METERED_USAGE_RECORDING',
710
+ /**
711
+ * One resource's rows bound to one of the application's retention classes (`retentionBinding`, #2305 S6): how long the
712
+ * firm's case evidence is kept. Proven from the registry: the binding is a property of the resource's configuration.
713
+ */
714
+ RESOURCE_RETENTION_BINDING = 'RESOURCE_RETENTION_BINDING',
715
+ /**
716
+ * One role CONFERRED through one organization relationship kind (#2305 S6): the relationship's `confers.roles` holds it
717
+ * and every organization type the relationship grants offers it (`availableOrgRoles`). How the firm's people come to
718
+ * hold, for a client, the role a decision of its method requires. Proven from the application's configuration
719
+ * (`wildo.saas.config.ts`), read fresh at landing: the role is spelled through constants, so no text can prove it.
720
+ * "Conferred" is the kind's CEILING: each client still grants the role, or not, on its own relationship. And the fresh
721
+ * read re-evaluates the configuration and the files it imports by relative path; a value imported from a package is
722
+ * read from that package's build.
723
+ */
724
+ RELATIONSHIP_CONFERRED_ROLE = 'RELATIONSHIP_CONFERRED_ROLE',
725
+ /*
726
+ * THE ORGANIZATION MODEL (#3035, #3036, #3039). What the domain plan's `organizationModel` decides, each proven from what
727
+ * the application DECLARES: its configuration, read fresh, for a type and a relationship kind; the registry its backend
728
+ * assembles at startup for a confinement and a binding. None of them is a name the tree spells in one place (a
729
+ * resource type is written through its constant, a binding's instance through a declaration helper), so no text probe
730
+ * could prove them.
731
+ */
732
+ /**
733
+ * One organization type the application declares in `wildo.saas.config.ts` `organizationTypes`: the shape a tenant
734
+ * takes. Lands when the configuration, read fresh, declares the type carrying what the plan decided of it (the roles
735
+ * it offers, the user types it grants, a required second factor).
736
+ *
737
+ * The type that OWNS the application is identified by `ownsApplication`, never by its key. By the time the build runs
738
+ * the platform has already created the operator's organization under the scaffold's key (`workspace`), and the
739
+ * application line may have set its joining posture, so a plan naming its owner `group` revises THAT type: adding a
740
+ * second owner type is refused by the configuration at startup, and replacing it would lose the organization already
741
+ * created. Its key and its people's user type are renamed to the plan's through a declared rename (`renamedFrom`,
742
+ * #3044), which the foundation usually makes; the product lands only under the plan's key, granting exactly the plan's
743
+ * user types.
744
+ */
745
+ ORGANIZATION_TYPE = 'ORGANIZATION_TYPE',
746
+ /**
747
+ * One kind of relationship between organizations, by its key in `organizationRelationships` (`partnership`): which
748
+ * types represent and which grant, and what the relationship may confer. Never a module and never a resource
749
+ * (#2617): the engine owns the relationship rows. Lands when the configuration, read fresh, declares the key.
750
+ */
751
+ ORGANIZATION_RELATIONSHIP_KIND = 'ORGANIZATION_RELATIONSHIP_KIND',
752
+ /**
753
+ * One resource's rows confined below the whole organization (#3036), in one {@link OrganizationRowConfinementMode}: to
754
+ * the unit a member holds a role in (`organizationUnitNarrowing`), or to the rows a member owns (`organizationOwnRows`),
755
+ * on the field the plan names. Lands when the backend's startup configuration declares the resource in that mode on
756
+ * that field. One resource may be confined in both modes (a department head sees the department's requests, an
757
+ * employee only their own), so the mode is part of the product's identity.
758
+ */
759
+ ORGANIZATION_UNIT_CONFINEMENT = 'ORGANIZATION_UNIT_CONFINEMENT',
760
+ /**
761
+ * One resource whose records live in a system of record (#3039), bound to the instance the application declares under
762
+ * `systemsOfRecord` (`odoo`), of the vendor the domain plan named. Read through (`httpApiBinding`) or copied (an
763
+ * inbound `externalDataPipeline`), as its {@link SystemOfRecordAccess} says. Lands when the resource's configuration
764
+ * binds that instance through that lane and the configuration declares the instance with that vendor, partitioned
765
+ * exactly when the plan splits the records by legal entity (#3045; a copy then stamps each row's partition).
766
+ */
767
+ SYSTEM_OF_RECORD_BINDING = 'SYSTEM_OF_RECORD_BINDING',
768
+ }
769
+
770
+ /**
771
+ * How an agent is started and talked to (#2966), which decides the skill it is built with
772
+ * ({@link BUILD_PLAN_AGENT_SHAPE_SKILL_REF}) and where its ref is registered.
773
+ */
774
+ export enum BuildPlanAgentShape {
775
+ /** A person converses with it in the application. Registered under the module's `agents`. */
776
+ CHAT_ASSISTANT = 'CHAT_ASSISTANT',
777
+ /** It runs with nobody signed in: on a schedule, or when a message arrives. Registered under `autonomousAgents`. */
778
+ AUTONOMOUS = 'AUTONOMOUS',
779
+ /** The application's own code calls it once and uses its answer. Registered under `agents`. */
780
+ INVOKED = 'INVOKED',
781
+ /** One step of a declared flow. Registered under `agents`. */
782
+ FLOW_STEP = 'FLOW_STEP',
614
783
  }
615
784
 
616
785
 
@@ -638,7 +807,29 @@ export enum BuildPlanDataSeedContent {
638
807
  * product refuses one: a plan naming it would claim to create a role the engine already owns.
639
808
  */
640
809
  export const APPLICATION_ROLE_NAME_PATTERN: RegExp = /^[A-Z][A-Z0-9]*(?:_[A-Z0-9]+)*$/;
641
- const CORE_ROLE_NAMES: ReadonlySet<string> = new Set<string>([...Object.values(CORE_APP_ROLES), ...Object.values(CORE_ORG_ROLES)]);
810
+ /** Every role the ENGINE defines: an application role may not take one of these names, and a qualification may name one without declaring it. */
811
+ export const CORE_ROLE_NAMES: ReadonlySet<string> = new Set<string>([...Object.values(CORE_APP_ROLES), ...Object.values(CORE_ORG_ROLES)]);
812
+
813
+ /**
814
+ * An agent's or a function tool's ref: segments of letters and digits joined by `.`, `-` or `_`
815
+ * (`close-assistant.chat.agent`, `todos.overdue-triage`, `resource.adjustmentProposals.post`). Case is kept, because a
816
+ * tool ref follows the framework's `resource.<resourceType>.<operation>` convention and a multi-word resource type is
817
+ * camelCase. Constrained because the probe compares it EXACTLY with the registered ref: no space, no slash, no empty
818
+ * segment.
819
+ */
820
+ export const AGENT_WORK_REF_PATTERN: RegExp = /^[A-Za-z0-9]+(?:[._-][A-Za-z0-9]+)*$/;
821
+
822
+ /**
823
+ * A step or a decision point of the firm's method (#2305), addressed as `<serviceRef>/<elementRef>`
824
+ * (`month-end-close/approve-posting`). A step's and a decision's ref are unique only within their service, so the
825
+ * service qualifies them; the `service-method` family declares both halves as kebab-case slugs.
826
+ */
827
+ export const SERVICE_METHOD_ELEMENT_REF_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*\/[a-z0-9]+(?:-[a-z0-9]+)*$/;
828
+
829
+ /** The ref a build-plan product carries for one step or decision point of the method (#2305). */
830
+ export function serviceMethodElementRef(serviceRef: string, elementRef: string): string {
831
+ return `${serviceRef}/${elementRef}`;
832
+ }
642
833
 
643
834
  export const DATA_SEED_KEY_PATTERN: RegExp = /^[a-z0-9]+(?:-[a-z0-9]+)*(?::[a-z0-9]+(?:-[a-z0-9]+)*)*$/;
644
835
 
@@ -702,6 +893,11 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
702
893
  resourceRef: SlugSchema,
703
894
  /** The generated-file FIELD the template is bound to (`generatedSummaryPdf`) — a symbol, so any spelling. */
704
895
  templateRef: NonEmptyStringSchema,
896
+ /**
897
+ * #2305 S6: the deliverable of the firm's method this document is, as `<serviceRef>/<deliverableRef>`. Its resource
898
+ * must be the one the deliverable is produced from; the derivation check compares them.
899
+ */
900
+ serviceMethodDeliverableRef: z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN).optional(),
705
901
  }),
706
902
  z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_WORKER).systemEnum('BuildPlanTaskProductKind'), workerRef: SlugSchema, jobRefs: z.array(NonEmptyStringSchema).min(1) }),
707
903
  z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_MINION).systemEnum('BuildPlanTaskProductKind'), minionRef: SlugSchema, behaviorRefs: z.array(NonEmptyStringSchema).min(1) }),
@@ -709,6 +905,12 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
709
905
  kind: z.literal(BuildPlanTaskProductKind.PROVIDER_BINDING).systemEnum('BuildPlanTaskProductKind'),
710
906
  providerRef: SlugSchema,
711
907
  scope: z.enum(ProviderBindingScope).systemEnum('ProviderBindingScope'),
908
+ /**
909
+ * The provider this module adds operations to, copied from the integration plan's binding (#2025). Present, it
910
+ * changes what landing means: the application's opt-in under `providers.augmentations.<augments>` lists the module's
911
+ * package, rather than a scope naming `providerRef` (an augmentation writes no scope entry).
912
+ */
913
+ augments: SlugSchema.optional(),
712
914
  }),
713
915
  z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_BILLING_PRODUCT).systemEnum('BuildPlanTaskProductKind'), productKey: SlugSchema }),
714
916
  z.strictObject({
@@ -727,10 +929,140 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
727
929
  z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_PAGE).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema }),
728
930
  z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WEBSITE_SECTION).systemEnum('BuildPlanTaskProductKind'), pageRef: SlugSchema, sectionRef: SlugSchema }),
729
931
  z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.DOCUMENTATION_CHAPTER).systemEnum('BuildPlanTaskProductKind'), chapterRef: SlugSchema }),
932
+ z.strictObject({
933
+ kind: z.literal(BuildPlanTaskProductKind.APPLICATION_AGENT).systemEnum('BuildPlanTaskProductKind'),
934
+ /** The agent's `ref` exactly as it is registered (`close-assistant.chat.agent`, `todos.overdue-triage`). */
935
+ agentRef: z.string().regex(AGENT_WORK_REF_PATTERN),
936
+ shape: z.enum(BuildPlanAgentShape).systemEnum('BuildPlanAgentShape'),
937
+ /**
938
+ * The firm's method steps this agent carries (#2305), as `<serviceRef>/<stepRef>`: set when the application has a
939
+ * service method, so the derivation can be checked as total (every agent step has its agent). One agent may carry
940
+ * several steps; each must be an AGENT step of the same `shape`.
941
+ */
942
+ serviceMethodStepRefs: z.array(z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN)).min(1).optional(),
943
+ /**
944
+ * The decision points of the firm's method this agent ASKS as a review question (an actor-system question routed
945
+ * to people when its run suspends), as `<serviceRef>/<decisionRef>` (#2305). A decision is realized either so or by
946
+ * a tool's approval gate (`serviceMethodDecisionRef`), never both: a review question IS the review, and its tool
947
+ * carries no gate. Its route is built by the agent's code when it suspends, so only the realization is checked here.
948
+ */
949
+ serviceMethodAskedDecisionRefs: z.array(z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN)).min(1).optional(),
950
+ }),
951
+ z.strictObject({
952
+ kind: z.literal(BuildPlanTaskProductKind.AGENT_APPROVAL_GATE).systemEnum('BuildPlanTaskProductKind'),
953
+ /** The gated tool's `functionRef` exactly as it is registered (`resource.<resourceType>.<operation>` for a resource tool). */
954
+ functionRef: z.string().regex(AGENT_WORK_REF_PATTERN),
955
+ route: z.enum(HumanDecision_RouteKind).systemEnum('HumanDecision_RouteKind'),
956
+ /**
957
+ * The role every answerer must hold, as the role table keys it: required for a ROLE or ASSIGNEE route, refused for
958
+ * an OWNER route (answered by the person whose turn it is) — the engine's own rule for a gate, so a plan cannot name a
959
+ * gate the engine would refuse at startup.
960
+ */
961
+ eligibleRole: z.string().regex(APPLICATION_ROLE_NAME_PATTERN).optional(),
962
+ /**
963
+ * The professional qualifications the answerer must ALSO hold (#2967), as the application's
964
+ * `professionalQualificationKinds` keys them: a ROLE or ASSIGNEE gate only, the engine's own rule. Landing compares
965
+ * them with the gate's, so a gate built without the qualification the plan required does not land.
966
+ */
967
+ requiredQualificationKinds: z.array(z.string().regex(LABEL_KEY_SEGMENT_PATTERN)).min(1).optional(),
968
+ /**
969
+ * The decision point of the firm's method this gate realizes (#2305), as `<serviceRef>/<decisionRef>`: set when the
970
+ * application has a service method. Its route must be the decision's, its role the decision's qualification's
971
+ * role, and its qualifications that qualification's kind; the derivation check compares them.
972
+ */
973
+ serviceMethodDecisionRef: z.string().regex(SERVICE_METHOD_ELEMENT_REF_PATTERN).optional(),
974
+ }).refine((gate) => (gate.route === HumanDecision_RouteKind.OWNER) === (gate.eligibleRole === undefined), {
975
+ message: 'An OWNER gate names no role; a ROLE or ASSIGNEE gate names the role its answerer must hold.',
976
+ path: ['eligibleRole'],
977
+ }).refine((gate) => gate.route !== HumanDecision_RouteKind.OWNER || gate.requiredQualificationKinds === undefined, {
978
+ message: 'An OWNER gate requires no qualification: its answerer is the person whose turn it is, whom nothing vets.',
979
+ path: ['requiredQualificationKinds'],
980
+ }),
981
+ z.strictObject({ kind: z.literal(BuildPlanTaskProductKind.WORK_UNIT_RESOURCE).systemEnum('BuildPlanTaskProductKind'), resourceRef: SlugSchema }),
982
+ z.strictObject({
983
+ kind: z.literal(BuildPlanTaskProductKind.METERED_USAGE_RECORDING).systemEnum('BuildPlanTaskProductKind'),
984
+ resourceRef: SlugSchema,
985
+ /** The operation that records, as the resource's configuration keys it (`record-sign-off` for `record_sign_off`). */
986
+ operationRef: SlugSchema,
987
+ /** The METERED product it records against: an `APPLICATION_BILLING_PRODUCT` of this plan, by its catalogue key. */
988
+ productKey: SlugSchema,
989
+ /** Whether it records at most once per row (`oncePerRecord`). A price per case counts each case once, however often it closes. */
990
+ oncePerRecord: z.boolean(),
991
+ /**
992
+ * #2305 S5: the service of the firm's method whose price PER CASE this records, by its `serviceRef`. Its resource must
993
+ * be that service's case and it must count once per row; the derivation check compares them.
994
+ */
995
+ serviceMethodServiceRef: SlugSchema.optional(),
996
+ }),
997
+ z.strictObject({
998
+ kind: z.literal(BuildPlanTaskProductKind.RESOURCE_RETENTION_BINDING).systemEnum('BuildPlanTaskProductKind'),
999
+ resourceRef: SlugSchema,
1000
+ retentionClass: z.enum(DataRetentionClass).systemEnum('DataRetentionClass'),
1001
+ }),
1002
+ z.strictObject({
1003
+ kind: z.literal(BuildPlanTaskProductKind.RELATIONSHIP_CONFERRED_ROLE).systemEnum('BuildPlanTaskProductKind'),
1004
+ /** The relationship kind, by its key in `organizationRelationships` (`service`). */
1005
+ relationshipRef: SlugSchema,
1006
+ /** The role conferred, by its key in the role table (`ORG_QUALIFIED_ACCOUNTANT`), a core role or the application's. */
1007
+ roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN),
1008
+ }),
1009
+ z.strictObject({
1010
+ kind: z.literal(BuildPlanTaskProductKind.ORGANIZATION_TYPE).systemEnum('BuildPlanTaskProductKind'),
1011
+ /**
1012
+ * The type's ref as the domain plan's organization model names it (`regulated-client`): its key in
1013
+ * `organizationTypes`, except for the owner type, which is found by `ownsApplication` whatever its key.
1014
+ */
1015
+ organizationTypeRef: SlugSchema,
1016
+ /** The type operates the application. Then the configuration's own owner type is the one the plan describes. */
1017
+ ownsApplication: z.literal(true).optional(),
1018
+ /** The roles the type must offer (`availableOrgRoles`, or the engine's default offer). */
1019
+ offeredRoles: z.array(z.string().regex(APPLICATION_ROLE_NAME_PATTERN)).min(1).optional(),
1020
+ /** The user types the type must grant its members (`userTypes`). */
1021
+ userTypes: z.array(SlugSchema).min(1).optional(),
1022
+ /** Whether the type's members must use a second factor (`authOverrides.mfaPolicy.requireMFA`). */
1023
+ requiresMfa: z.boolean().optional(),
1024
+ }),
1025
+ z.strictObject({
1026
+ kind: z.literal(BuildPlanTaskProductKind.ORGANIZATION_RELATIONSHIP_KIND).systemEnum('BuildPlanTaskProductKind'),
1027
+ /** The kind's key in `organizationRelationships` (`partnership`), the same key a `RELATIONSHIP_CONFERRED_ROLE` names. */
1028
+ relationshipRef: SlugSchema,
1029
+ }),
1030
+ z.strictObject({
1031
+ kind: z.literal(BuildPlanTaskProductKind.ORGANIZATION_UNIT_CONFINEMENT).systemEnum('BuildPlanTaskProductKind'),
1032
+ resourceRef: SlugSchema,
1033
+ mode: z.enum(OrganizationRowConfinementMode).systemEnum('OrganizationRowConfinementMode'),
1034
+ /**
1035
+ * The field the confinement reads, as the resource's schema names it: the unit field (`organizationUnitId`) for
1036
+ * `ORGANIZATION_UNIT`, the owning user's field (`createdByUserId`) for `OWN_ROWS`. Compared exactly, because a
1037
+ * confinement on another field confines by something else.
1038
+ */
1039
+ fieldName: z.string().regex(/^[A-Za-z_$][A-Za-z0-9_$]*$/),
1040
+ }),
1041
+ z.strictObject({
1042
+ kind: z.literal(BuildPlanTaskProductKind.SYSTEM_OF_RECORD_BINDING).systemEnum('BuildPlanTaskProductKind'),
1043
+ resourceRef: SlugSchema,
1044
+ /** The instance's key in `systemsOfRecord` (`odoo`), the name a binding's `system` carries. */
1045
+ systemOfRecordRef: z.string().regex(SYSTEM_OF_RECORD_NAME_PATTERN),
1046
+ /**
1047
+ * The system's facet, as the domain plan names it (`odoo`, `sap-s4hana`): the `vendor` the declared instance must
1048
+ * carry, so a binding to an instance of another vendor does not land.
1049
+ */
1050
+ systemOfRecordKind: SlugSchema,
1051
+ /** The lane the domain plan decided: read through on every request, or copied by a pipeline. Required there, so here. */
1052
+ access: z.enum(SystemOfRecordAccess).systemEnum('SystemOfRecordAccess'),
1053
+ /**
1054
+ * Whether the instance's records are split by legal entity (#3045), as the domain plan's record location says
1055
+ * (`domainPlanRecordPartitionPartitionsInstance`): `true` declares `partition: true` on the instance, and a copied
1056
+ * resource then stamps each row's unit and entity key on its pipeline (`partitionUnitLocalField`,
1057
+ * `partitionKeyLocalField`); `false` declares neither. The landing probe compares it with the instance's flag. Absent
1058
+ * (a plan written before #3045): not compared.
1059
+ */
1060
+ partitioned: z.boolean().optional(),
1061
+ }),
730
1062
  z.strictObject({
731
1063
  kind: z.literal(BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER).systemEnum('BuildPlanTaskProductKind'),
732
- /** The channel the handler serves — one the integration plan declared. Email is the only declarable channel. */
733
- channel: z.literal(InboundChannelKind.EMAIL).systemEnum('InboundChannelKind'),
1064
+ /** The channel the handler serves — one the integration plan declared ({@link PlannableInboundChannelKind}). */
1065
+ channel: z.enum(PlannableInboundChannelKind).systemEnum('InboundChannelKind'),
734
1066
  /** The handler's `ref`, exactly as `inboundHandlerRef()` will accept it. */
735
1067
  handlerRef: z.string().regex(INBOUND_HANDLER_REF_PATTERN),
736
1068
  }),
@@ -819,6 +1151,33 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
819
1151
  return [`${product.kind}:${product.chapterRef}`];
820
1152
  case BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER:
821
1153
  return [`${product.kind}:${product.handlerRef}`];
1154
+ case BuildPlanTaskProductKind.APPLICATION_AGENT:
1155
+ return [`${product.kind}:${product.agentRef}`];
1156
+ // The TOOL alone: one tool has one gate, so two tasks gating it differently would make landing ambiguous.
1157
+ case BuildPlanTaskProductKind.AGENT_APPROVAL_GATE:
1158
+ return [`${product.kind}:${product.functionRef}`];
1159
+ case BuildPlanTaskProductKind.WORK_UNIT_RESOURCE:
1160
+ return [`${product.kind}:${product.resourceRef}`];
1161
+ // The operation and the product: one operation may record several products, and two tasks recording one product on
1162
+ // one operation would make landing ambiguous.
1163
+ case BuildPlanTaskProductKind.METERED_USAGE_RECORDING:
1164
+ return [`${product.kind}:${product.resourceRef}:${product.operationRef}:${product.productKey}`];
1165
+ // One resource has one binding, so two tasks binding it would make landing ambiguous.
1166
+ case BuildPlanTaskProductKind.RESOURCE_RETENTION_BINDING:
1167
+ return [`${product.kind}:${product.resourceRef}`];
1168
+ case BuildPlanTaskProductKind.RELATIONSHIP_CONFERRED_ROLE:
1169
+ return [`${product.kind}:${product.relationshipRef}:${product.roleRef}`];
1170
+ // The OWNER type is one per application whatever its key, so two products describing it would make landing ambiguous.
1171
+ case BuildPlanTaskProductKind.ORGANIZATION_TYPE:
1172
+ return [product.ownsApplication === true ? `${product.kind}:application-owner` : `${product.kind}:${product.organizationTypeRef}`];
1173
+ case BuildPlanTaskProductKind.ORGANIZATION_RELATIONSHIP_KIND:
1174
+ return [`${product.kind}:${product.relationshipRef}`];
1175
+ // The MODE is part of the identity: one resource may be confined to the unit AND to its owner's rows (#3036).
1176
+ case BuildPlanTaskProductKind.ORGANIZATION_UNIT_CONFINEMENT:
1177
+ return [`${product.kind}:${product.resourceRef}:${product.mode}`];
1178
+ // The resource alone: one resource's records live in one place, so two bindings of it would make landing ambiguous.
1179
+ case BuildPlanTaskProductKind.SYSTEM_OF_RECORD_BINDING:
1180
+ return [`${product.kind}:${product.resourceRef}`];
822
1181
  default: {
823
1182
  const unhandled: never = product;
824
1183
  throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);
@@ -830,7 +1189,8 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
830
1189
  * The skill every billing-catalogue task is authored with (#1835): the product-catalogue contract, the
831
1190
  * money encoding (minor units), and the pricing-surface facts. The dispatch derives it from an
832
1191
  * `APPLICATION_BILLING_PRODUCT` product whatever the decomposer wrote, so an agent writing the catalogue
833
- * the backend sells from is never without it.
1192
+ * the backend sells from is never without it. A `METERED_USAGE_RECORDING` task carries it too (#2305 S5): the skill
1193
+ * says how an operation records usage of a metered product, and how a price per case counts each case once.
834
1194
  */
835
1195
  export const BILLING_CATALOG_SKILL_REF = 'configure-billing';
836
1196
 
@@ -862,6 +1222,63 @@ export const PDF_TEMPLATE_SKILL_REF = 'pdf-template-authoring';
862
1222
  */
863
1223
  export const RESOURCE_RETENTION_SKILL_REF = 'resource-retention-binding';
864
1224
 
1225
+ /**
1226
+ * The skill a task conferring a role through an organization relationship is authored with (#2305 S6): the relationship
1227
+ * kind's `confers`, the granting types that must offer the role, and the startup checks that refuse a mismatch. The
1228
+ * dispatch derives it from a `RELATIONSHIP_CONFERRED_ROLE` product whatever the decomposer wrote.
1229
+ */
1230
+ export const ORGANIZATION_RELATIONSHIPS_SKILL_REF = 'organization-relationships';
1231
+
1232
+ /**
1233
+ * The skill each agent shape is built with (#2966). The dispatch derives it from an `APPLICATION_AGENT` product whatever
1234
+ * the decomposer wrote. Total over {@link BuildPlanAgentShape}, so a shape added tomorrow must name its skill.
1235
+ */
1236
+ export const BUILD_PLAN_AGENT_SHAPE_SKILL_REF: Readonly<Record<BuildPlanAgentShape, string>> = {
1237
+ [BuildPlanAgentShape.CHAT_ASSISTANT]: 'flows-actors-chat-assistant',
1238
+ [BuildPlanAgentShape.AUTONOMOUS]: 'flows-actors-autonomous-agents',
1239
+ [BuildPlanAgentShape.INVOKED]: 'flows-actors-llm-agent-invocation',
1240
+ [BuildPlanAgentShape.FLOW_STEP]: 'flows-actors-declared-flow',
1241
+ };
1242
+
1243
+ /**
1244
+ * The skill every agent and every approval gate is ALSO built with (#2966): what the agent's use is for, whether it
1245
+ * decides anything about a person, and its gated writes. An agent built from its shape skill alone is the undeclared,
1246
+ * unguarded shape.
1247
+ */
1248
+ export const AI_USE_DECLARATION_SKILL_REF = 'ai-use-declaration';
1249
+
1250
+ /**
1251
+ * The skill an approval gate is built with (#2966): `flows-actors-chat-assistant` is where the `humanApproval` contract
1252
+ * is taught whole — the three routes, the eligible role, an assignee, escalation, deadlines and the review calendar —
1253
+ * whichever kind of agent calls the tool.
1254
+ */
1255
+ export const AGENT_APPROVAL_GATE_SKILL_REF = 'flows-actors-chat-assistant';
1256
+
1257
+ /**
1258
+ * The skill an organization-type task is built with (#3040): `organizationTypes` in the application's configuration, the
1259
+ * user types and roles a type offers, how it is joined, and the identity overrides it may carry. The dispatch derives it
1260
+ * from an `ORGANIZATION_TYPE` product whatever the decomposer wrote. A relationship kind is built with
1261
+ * {@link ORGANIZATION_RELATIONSHIPS_SKILL_REF}.
1262
+ */
1263
+ export const ORGANIZATION_TYPE_SKILL_REF = 'config-saas-backend';
1264
+
1265
+ /**
1266
+ * The skill a confinement task is built with (#3040): `organizationUnitNarrowing` and `organizationOwnRows` at startup,
1267
+ * and why a confined resource's reads are gated above the default member role. Derived from an
1268
+ * `ORGANIZATION_UNIT_CONFINEMENT` product whatever the decomposer wrote.
1269
+ */
1270
+ export const ORGANIZATION_UNIT_CONFINEMENT_SKILL_REF = 'authorization-unit-narrowing';
1271
+
1272
+ /**
1273
+ * The skills a system-of-record binding is built with (#3040): `resource-external-data` for the binding itself (the two
1274
+ * lanes, the field mapping, subject rights), and `config-saas` for the `systemsOfRecord` instance the binding names.
1275
+ * Derived from a `SYSTEM_OF_RECORD_BINDING` product whatever the decomposer wrote.
1276
+ */
1277
+ export const SYSTEM_OF_RECORD_BINDING_SKILL_REFS: readonly string[] = ['resource-external-data', 'config-saas'];
1278
+
1279
+ /** The skill a work-unit task is built with (#2966): the `workUnit` declaration, model prices and the case passed to agent turns. */
1280
+ export const WORK_UNIT_SKILL_REF = 'model-cost-attribution';
1281
+
865
1282
  export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
866
1283
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.MODULE), moduleRef: ModuleRefSchema }),
867
1284
  z.strictObject({
@@ -872,8 +1289,26 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
872
1289
  }),
873
1290
  z.strictObject({
874
1291
  kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),
1292
+ /** The module whose `<module>.relationships.ts` the edges are written into: the task's write scope. */
875
1293
  moduleRef: ModuleRefSchema,
876
- relationshipRef: SlugSchema,
1294
+ /**
1295
+ * Every domain-plan relationship this task wires, by the domain plan's `relationshipRef` (#3209).
1296
+ *
1297
+ * A LIST, because the unit of work is the module's relationships FILE, not one edge. Each edge is a
1298
+ * `createResourcesRelationship(...)` call in that one file, plus the holder's ui-behavior and both
1299
+ * resources' specifications, so two tasks wiring two edges of one module edit the same file. Run
1300
+ * concurrently they overwrite each other, and the build wave re-runs each interfered task alone:
1301
+ * app-creation-test-007 split one module's 23 edges into 23 tasks, and the relationship phase ran one
1302
+ * task at a time for about seven hours with a parallelism of five. One task per file (see
1303
+ * {@link groupRelationshipTasksByModule}) pays the worker's start and the checks once, and lets
1304
+ * different modules' files go in parallel.
1305
+ *
1306
+ * Each ref here has its `RESOURCE_RELATIONSHIP` product on the same task, and that is checked
1307
+ * (`RELATIONSHIP_TARGET_DISAGREES_WITH_PRODUCTS`): the target says what the coverage check counts as
1308
+ * wired, and the products are what landing proves. A target naming an edge no product declares would
1309
+ * count as covered and never be probed.
1310
+ */
1311
+ relationshipRefs: z.array(SlugSchema).min(1),
877
1312
  }),
878
1313
  z.strictObject({
879
1314
  kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),
@@ -920,6 +1355,7 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
920
1355
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
921
1356
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),
922
1357
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_ROLES) }),
1358
+ z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.ORGANIZATION_MODEL) }),
923
1359
  ]);
924
1360
  export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
925
1361
 
@@ -941,8 +1377,8 @@ export const BuildPlanTaskSchema = z.strictObject({
941
1377
  * One sentence of intent: what this task delivers.
942
1378
  *
943
1379
  * Its OWN instance, not the file's shared leaf, which `templateRef` and the product ref lists also
944
- * hold. A display decorator mutates the instance it is applied to, and the workbench gives those
945
- * refs a receding identifier look, which the objective sentence then took too.
1380
+ * hold. The workbench's reading decorations are keyed by INSTANCE, and it gives those refs a receding
1381
+ * identifier look, which the objective sentence took too while it shared their leaf.
946
1382
  */
947
1383
  objective: z.string().trim().min(1),
948
1384
  target: BuildPlanTaskTargetSchema,
@@ -1249,7 +1685,7 @@ tasks editing one file:
1249
1685
  Bind by the FILE the surface is configured in. The settings rail is `settings-hub.config.ts`. The sidebar, the palette
1250
1686
  and the user menu (its `settingsEntries`) are `app-shell.config.ts`, and `settings-placement-authoring` itself sends
1251
1687
  work on them to `config-app-shell`: binding it there hands the agent a skill that tells it to go elsewhere. Only
1252
- `config-app-shell` teaches `runtimeAvailability.visibleToRoles`, which a sidebar group or entry the plan restricts to
1688
+ `config-app-shell` teaches `runtimeAvailability.requiredRoles`, which a sidebar group or entry the plan restricts to
1253
1689
  some roles needs.
1254
1690
 
1255
1691
  Any task whose HOW includes **writing JSX for a bespoke surface** — a ui-behavior
@@ -1274,17 +1710,38 @@ Rules:
1274
1710
  - **Carry the decision, not the config.** The task names the surface and points at
1275
1711
  the skill; which category a destination lands in and in what order is IN the plan,
1276
1712
  read by the coding agent at dispatch. Do not restate placements in the objective.
1713
+ - **Never override the placement plan in an objective.** The sidebar and command-menu tasks land when the
1714
+ shell carries exactly what the plan placed there, so an objective that keeps a placed subject off its surface
1715
+ is a task that can never land. One business concept held in two resources (read through and copied) has ONE
1716
+ sidebar entry, the experience plan's concept view (its `entryForResourceRefs`), with both lists on the command
1717
+ menu (`config-navigation`, `references/one-entry-per-concept.md`). When the coherence report shows
1718
+ `concept-list-on-sidebar`, `concept-view-not-on-sidebar` or `concept-list-not-on-command-menu`, the two plans
1719
+ disagree and the next run of the plan that is wrong resolves it: say so in your notes and decompose the
1720
+ placement plan as it stands.
1277
1721
  - **No placement plan? Emit nothing here and say so.** Do not invent placement — a
1278
1722
  guessed arrangement is exactly what the plan exists to replace, and it would be
1279
1723
  invisible to the reader who assumes a placement task came from a decision.
1280
1724
 
1281
1725
  ## Step 2 — Emit the relationship-wiring tasks
1282
1726
 
1283
- For each **relationship-draft**, emit one wiring task:
1727
+ Emit one wiring task per MODULE, for the relationship-drafts that module holds:
1284
1728
 
1285
1729
  | Task | Functional topic | Skill (the HOW) |
1286
1730
  |---|---|---|
1287
- | Wire relationship `<A> <-> <B>` (`<cardinality>`, `<owner>` holds the ref) | `model_domain_graph` | `module-relationships` |
1731
+ | Wire the `<module>` relationships: `<A> <-> <B>` (`<cardinality>`, `<owner>` holds the ref), … | `model_domain_graph` | `module-relationships` |
1732
+
1733
+ Its target is `RELATIONSHIP` with the module and EVERY relationship it wires in `relationshipRefs`, and it
1734
+ declares one `RESOURCE_RELATIONSHIP` product per relationship, with both endpoints. The target and the
1735
+ products name the same relationships: one named in only one of them is refused.
1736
+
1737
+ **Why per module and not per relationship.** Every relationship of a module is written into that module's ONE
1738
+ relationships file. Two tasks wiring two relationships of one module edit the same file; run at the same time,
1739
+ the later write loses the earlier relationship, and the build re-runs each task alone. One application split one
1740
+ module's 23 relationships into 23 tasks, and its whole relationship phase ran one task at a time for seven hours.
1741
+ One task per module pays the worker's start and its checks once, and different modules' tasks run in parallel.
1742
+ The build also does this for you: a plan with one task per relationship is regrouped per module when it lands,
1743
+ cut into chained tasks of at most six relationships each, so a module with many relationships becomes a few
1744
+ tasks run one after the other. Group them yourself anyway, so the plan you return is the plan you meant.
1288
1745
 
1289
1746
  Rules:
1290
1747
 
@@ -1330,11 +1787,19 @@ Default verbs (create, read, update, list, delete) are what Step 1 already gives
1330
1787
  Everything a requirement says the product DOES beyond them is work this step must emit.
1331
1788
 
1332
1789
  **Start with the domain plan's `lifecycles`.** Each declared transition is one `RESOURCE_OPERATION`
1333
- task on its resource (target `RESOURCE_STAGE` CONFIG, `operationRef` = the `transitionRef`), skill
1334
- `resource-status-lifecycle`, ordered after that resource's config task; its objective names the
1335
- states it moves between and who performs it. A transition with `createsResourceRef` adds a
1336
- `MODULE_BACKEND` task for the write that creates the target, skill `backend-custom-operation`,
1337
- ordered after both resources' config tasks. The resource's SCHEMA task objective names the status
1790
+ product on its resource (target `RESOURCE_STAGE` CONFIG, `operationRef` = the `transitionRef`, exactly),
1791
+ skill `resource-status-lifecycle`, ordered after that resource's config task; its objective names the
1792
+ states it moves between and who performs it. One task may carry all of a resource's transitions.
1793
+
1794
+ **A transition that creates a record (`createsResourceRef`) creates it in its OWN operation**, in the same
1795
+ transaction: accepting a quote IS the operation that creates the job. So the conversion is part of the
1796
+ transition's task, never a task of its own. That task's objective names the record it creates and what it
1797
+ carries over, it adds the skill `backend-custom-operation` (the write is a custom implementation of the
1798
+ transition's operation), and it is ordered after BOTH resources' config tasks. Do NOT add a second task for the
1799
+ write, and never name an operation that is the transition plus something else (`approve-create-job`,
1800
+ `qualify-create-opportunity`): no such operation is declared, the only code that could carry that name is a
1801
+ second operation doing what the transition already does, and the plan is refused for it. The only operation
1802
+ names a lifecycle gives you are its `transitionRef`s. The resource's SCHEMA task objective names the status
1338
1803
  enum with every declared state, the `initialState` as its default, and each transition's `stampsField`,
1339
1804
  all excluded from create and update: a transition is the only way to move them.
1340
1805
  For a resource with `lockedStates` or `finalStates`, the objective of each transition task that moves INTO
@@ -1342,18 +1807,132 @@ one of them also restricts the resource's UPDATE to the states that are neither
1342
1807
  that freeze as its own `update` operation task: the scaffold already writes `update`, so such a task reads
1343
1808
  as built before it runs.
1344
1809
 
1810
+ **A step is offered only where it can succeed, and a refusal says why.** Each transition task's objective
1811
+ names its `from` states as the only states in which the action is offered, on EVERY variant of the
1812
+ operation (an administrator's variant included): the engine then refuses the step from any other state,
1813
+ and the screen does not offer it there. Wonder Procurement offered "Department-head decision" on a draft,
1814
+ and the backend answered 409. When the operation can ALSO be refused for a reason its state does not show
1815
+ (a supplier no longer in the directory, a budget already spent), the objective names that refusal and
1816
+ says it reaches the person as a sentence worded through the labels, like every other display text,
1817
+ never as a bare "conflict": the refusal carries a declared code (`backend-custom-operation`,
1818
+ `references/declared-refusal-codes.md`). The words come from the resource's specification, so its SPEC
1819
+ task's objective names them too: each refusal code as an operation's `errorScenarios[].errorCode` with
1820
+ a `when` written as what the person reads and does next, and each transition's `unavailableWhen`, the
1821
+ sentence a disabled action shows (`spec-resource-update`).
1822
+
1823
+ **A resource with a lifecycle has a record page, and its ui-behavior task builds it.** That task's
1824
+ objective states the page, because the engine's generated page puts the status first and who made the
1825
+ record last but cannot know the route, or which facts belong to which stage
1826
+ (`resource-ui-behavior`, `references/workflow-record-page.md`; its spec task documents it, `spec-resource-update`,
1827
+ `references/workflow-record-page-specification.md`):
1828
+
1829
+ - the status as the page's leading pill, read-only, shown once: on `layout.header` when the page
1830
+ authors one (a workflow page does), otherwise `<RecordState>` first in `layout.display`, never both,
1831
+ its name kept for a screen reader (`labelPlacement="hidden"`, never `hideLabel`, which removes it);
1832
+ with where the record stands in its lifecycle;
1833
+ - the next steps from that status as actions with words (its transitions, offered only from their
1834
+ `from` states), never bare icons, each with a `displayPriority` so the main verb of each state comes
1835
+ first: a desktop list row keeps ONE action in view and a phone header one, and the action with the
1836
+ lowest `displayPriority` value that can run is the one that stays;
1837
+ - the fields in sections, in business order: what the record is first, then its workflow and the moments
1838
+ its transitions stamp (`stampsField`);
1839
+ - the record keeping last: its creator and timestamps (`createdByUserId`, `createdAt`, `updatedAt`) on
1840
+ one quiet line in `<RecordKeepingFacts>`, never as tiles in a section, and the organization it belongs
1841
+ to not shown at all (`references/framework-record-page-parts-api.md`).
1842
+
1843
+ A date the business needs in the future (needed by, due on) is refused when it is in the past by the
1844
+ OPERATIONS that write it, never by the page alone: the schema task's objective says so for create and
1845
+ edit, the transition task's for the step that relies on it (submit), each refusal with its declared code.
1846
+
1847
+ A lifecycle resource whose build plan carries no `RESOURCE_UI_BEHAVIOR` product is reported by the
1848
+ coherence report (`lifecycle-resource-no-record-page`), and its page is the engine's generated one, which
1849
+ knows no route.
1850
+
1345
1851
  Then read every functional requirement's acceptance criteria for verbs no lifecycle carries, and
1346
1852
  classify each:
1347
1853
 
1348
1854
  | The criterion says… | Emit | Skill |
1349
1855
  |---|---|---|
1350
1856
  | a record CHANGES STATE ("an accepted quote", "issue the invoice", "mark it paid", "close the case", "a submitted request can be approved") | one `RESOURCE_OPERATION` per transition, on the resource whose state changes, target `RESOURCE_STAGE` (CONFIG). Its objective names the states it moves between and who may call it | `resource-status-lifecycle` |
1351
- | one record CREATES or FILLS another ("an accepted quote creates a job", "invoice the job") | a `RESOURCE_OPERATION` on the SOURCE resource, plus a `MODULE_BACKEND` task carrying the implementation that writes the target; ordered after both resources' config tasks | `backend-custom-operation` |
1857
+ | one record CREATES or FILLS another ("an accepted quote creates a job", "invoice the job") | when a declared transition does it: that transition's `RESOURCE_OPERATION` task, whose objective names what it creates, ordered after both resources' config tasks (no second task). Otherwise one `RESOURCE_OPERATION` on the SOURCE resource naming the new operation, target `MODULE_BACKEND` when the write is a custom implementation | `backend-custom-operation` |
1352
1858
  | a record must not change any more ("an issued invoice cannot be edited") | the objective of the `RESOURCE_OPERATION` task for the transition into that locked or final state also restricts its UPDATE to the open states (never a separate `update` task, which the scaffold already writes) | `resource-status-lifecycle` |
1353
1859
  | a user group may or may not do something ("technicians cannot see invoices") | an `APPLICATION_ROLES` task (see below), or, for core roles alone, the config tasks' objectives | `application-roles-authoring` / `resource-config-wiring` |
1860
+ | a member sees only PART of the organization's records ("department heads see their department's requests", "employees see only the requests they raised") | an `ORGANIZATION_UNIT_CONFINEMENT` product of the confinement task (see "The organization model" below), never a `RESOURCE_OPERATION` and never a membership feature; the domain plan records it in `organizationModel.unitConfinements` | `authorization-unit-narrowing` |
1861
+ | only a QUALIFIED person may take a decision ("only a chartered accountant approves postings", "the reviewer must be licensed") | the `APPLICATION_ROLES` task for the role, and in the same task's objective the declared `professionalQualificationKinds` and the register's Settings placement; the task that raises the decision (an agent's gate, an operation's `requiresApproval`, a flow's person step) names `requiredQualificationKinds` beside its `eligibleRole` | `professional-qualifications` |
1354
1862
  | the product PRODUCES a document ("send the quote as a PDF", "print the invoice") | a `PDF_TEMPLATE` task bound to a generated-file field of that resource | `pdf-template-authoring` |
1355
1863
  | the product SENDS a message ("email the customer", "remind the office") | the `email-templates` generation step, and a `RESOURCE_OPERATION` task whose objective declares the notification on the operation that triggers it | `email-add-template` |
1356
1864
  | something is shown or computed from other records ("the next action", "what is overdue") | NOT a stored field: a view task from the experience plan, or a computed value in the owning resource's config task objective | — |
1865
+ | the product uses AI ("an assistant answers questions about…", "summarise", "classify automatically", "triage every morning", "an agent proposes, a person approves") | one `MODULE_BACKEND` task per AGENT, in the module whose records it reads, ordered after the config tasks of every resource its tools read or write. Its objective states the agent's use (what it is for, whether it decides anything about a person, who reviews), its `contentGuardrails` wherever they can treat something, and which of its writes wait for whose approval | the shape skill: `flows-actors-chat-assistant` (a person converses with it), `flows-actors-llm-agent-invocation` (your code calls it once), `flows-actors-autonomous-agents` (it runs with nobody signed in), `flows-actors-declared-flow` (a step of a flow) — AND `ai-use-declaration` |
1866
+
1867
+ An agent task always names BOTH skills: the shape skill builds it, and `ai-use-declaration` is what makes it
1868
+ declare its use — every agent carries `aiUse`, `contentGuardrails` and gated writes, and an agent built from
1869
+ the shape skill alone is the unguarded shape. The dispatch adds both from the task's products whatever you list.
1870
+
1871
+ An agent task DECLARES what it produces, so landing can prove it:
1872
+
1873
+ - one `APPLICATION_AGENT` product, with the `agentRef` the code will register and the `shape` the requirement
1874
+ describes (a person converses with it → `CHAT_ASSISTANT`; it runs on a schedule or when a message arrives →
1875
+ `AUTONOMOUS`; your code calls it once → `INVOKED`; a step of a flow → `FLOW_STEP`);
1876
+ - one `AGENT_APPROVAL_GATE` product for EVERY tool that changes something and waits for a person, with the
1877
+ route the requirement implies: "the person asking confirms" → `owner`; "a manager approves" → `role` with the
1878
+ role that group holds; "a chartered (licensed, certified) accountant approves" → `role` with that role AND
1879
+ `requiredQualificationKinds` naming the declared kind; "the account's partner signs off" → `assignee` with the
1880
+ role that person must hold. The role is the one an `APPLICATION_ROLE` product declares, or a core role, so a
1881
+ gate whose approver group has its own role is ordered after that roles task. An `owner` gate never names a role
1882
+ or a qualification.
1883
+
1884
+ An assistant's view is still its own `APPLICATION_VIEW` task from the experience plan.
1885
+
1886
+ When a requirement prices, budgets or reports cost PER CASE ("what each engagement costs us in AI", "margin per
1887
+ matter", "cost per ticket"), or names the record the agents' work is about ("each close", "each claim"), the
1888
+ config task of that resource also produces `WORK_UNIT_RESOURCE`, so every model call is attributed to its case.
1889
+
1890
+ ### When the application has a service method, realize it whole
1891
+
1892
+ A firm's method (the `service-method` family, #2305) is the application's agent work written down, so read it
1893
+ before the requirement verbs above and realize every element of it:
1894
+
1895
+ - each service's CASE: the config task of the resource named by `case.caseRef` also produces
1896
+ `WORK_UNIT_RESOURCE` for it;
1897
+ - each step `performedBy: AGENT`: an `APPLICATION_AGENT` product in the step's `agentShape`, naming the step in
1898
+ `serviceMethodStepRefs` as `<serviceRef>/<stepRef>`. One agent may carry several steps of one shape;
1899
+ - each decision point, realized ONE way:
1900
+ - when a tool waits for the person's approval before it writes: an `AGENT_APPROVAL_GATE` product on that tool,
1901
+ naming the decision in `serviceMethodDecisionRef` as `<serviceRef>/<decisionRef>`, with the decision's `route`,
1902
+ its qualification's `role` as `eligibleRole` (none for `owner`), and its qualification's
1903
+ `professionalQualificationKind` as the only entry of `requiredQualificationKinds` (none when it names none);
1904
+ - when the agent ASKS the person and continues from the answer (a review question its run suspends on, such as
1905
+ choosing which document pays a bank line): the agent's `APPLICATION_AGENT` product names the decision in
1906
+ `serviceMethodAskedDecisionRefs`, and the task's objective says the question's route and role. Its tool has no
1907
+ gate: the question is the review;
1908
+ - either way, its `decisionDeadline` goes in the task's objective, which the gate's or the question's deadlines are
1909
+ built from;
1910
+ - each qualification's role: an engine role, or an `APPLICATION_ROLE` product. The `APPLICATION_ROLES` task declares
1911
+ every `professionalQualificationKind` the method names in `professionalQualificationKinds`, and is emitted for that
1912
+ even when every qualification's role is an engine role;
1913
+ - each service with `pricing: PER_CASE`: the billing catalogue task produces a METERED product for it (its
1914
+ `productKey` names the case, priced per unit), and a task on the case resource produces a `METERED_USAGE_RECORDING`
1915
+ on the operation that CLOSES the case (`case.closesWhen` says which), with that `productKey`, `oncePerRecord: true`
1916
+ and the service in `serviceMethodServiceRef`. Order it after the catalogue task and after the case's closing
1917
+ operation exists. A service priced `INCLUDED_IN_PLAN` or `BILLED_OUTSIDE` records nothing;
1918
+ - each deliverable: a `PDF_TEMPLATE` product on the resource the deliverable is produced from (`fromResourceRef`), bound
1919
+ to its generated-file field, naming the deliverable in `serviceMethodDeliverableRef` as `<serviceRef>/<deliverableRef>`;
1920
+ - the case's evidence: the config task of the case resource, and of each deliverable's resource, also produces a
1921
+ `RESOURCE_RETENTION_BINDING` in the service's `evidenceRetention.retentionClass`. A `BUSINESS_RECORDS` binding also
1922
+ declares the statutory retention policy (the `resource-retention-binding` skill says how; the dispatch adds it);
1923
+ - each qualification the firm's people hold for the client (`heldBy: FIRM`), unless its role is `ORG_REPRESENTATIVE`
1924
+ (conferred already): the `APPLICATION_ROLES` task also produces a `RELATIONSHIP_CONFERRED_ROLE` for its role on the
1925
+ relationship the firm serves its clients through (`service` in the configuration's `organizationRelationships`). The
1926
+ firm's people hold that role for a client only through the relationship: the task adds it to the kind's
1927
+ `confers.roles` and offers it on every organization type the kind grants. A role the client's own staff hold
1928
+ (`heldBy: CLIENT`) is offered on the client's organization type and conferred nowhere.
1929
+
1930
+ This is checked at landing: a plan that leaves a case without its work unit, an agent step without its agent or a
1931
+ decision point unrealized (or a gate with another route, role or qualification), or a service priced per case with
1932
+ no recording of its case (or one recording elsewhere, every run, or a product the catalogue does not sell), a
1933
+ deliverable with no document, a case's evidence unbound or bound to another class, or a firm-held role no
1934
+ relationship confers is refused, with the list of what is missing. A case's lifecycle that lacks one of its stages is
1935
+ the domain plan's to fix, and is reported rather than refused. A case the domain plan does not declare is the domain plan's to fix, and is reported rather than refused. Name the method's services in `servesRefs` only where a requirement also justifies the task.
1357
1936
 
1358
1937
  A task emitted from a requirement verb is justified by that requirement: name it in `servesRefs`.
1359
1938
  It is never the "justified by nothing" speculative work the rule further down warns about. A plan
@@ -1370,8 +1949,10 @@ replaced — the judge reports it as a gap.
1370
1949
  - **`define_interaction_semantics`** — custom operations, lifecycle behaviour, access /
1371
1950
  role / scope rules, rate limits — interaction beyond the default resource verbs.
1372
1951
  Target `RESOURCE_STAGE` (CONFIG), product `RESOURCE_OPERATION`. Skills: the Backend and
1373
- Resources domains of the router (`backend-custom-operation`, `rate-limit-authoring`,
1374
- `authorization-unit-narrowing`). **Derive these from the requirements' VERBS** — read
1952
+ Resources domains of the router (`backend-custom-operation`, `rate-limit-authoring`). A
1953
+ requirement that confines records to a department or to their author is NOT an operation:
1954
+ it is a row confinement, emitted under "The organization model" below, whose product a
1955
+ `RESOURCE_OPERATION` could never prove. **Derive these from the requirements' VERBS** — read
1375
1956
  "Every requirement verb becomes a task" below before emitting anything else in this step.
1376
1957
  - **`shape_user_experience`** — the cross-resource UX, and you do NOT decide it here. The
1377
1958
  **experience plan** (`bottom_up.experience-plan`) already did: which surfaces exist, what
@@ -1390,7 +1971,25 @@ replaced — the judge reports it as a gap.
1390
1971
  - one task per CONFIGURATION, target `APPLICATION_FRONTEND_CONFIG` with that surface,
1391
1972
  product `APPLICATION_FRONTEND_CONFIG` naming the surface's own `declarationRefs`, and
1392
1973
  its skill the one the surface names (`config-navigation`, `config-design-system`,
1393
- `config-app-shell`; `views-app-level` for global views — derived at dispatch too).
1974
+ `config-app-shell`, `layout-2d-adoption` for the shell layout; `views-app-level` for global views
1975
+ — derived at dispatch too). A shell layout task depends on the design-system task when both are
1976
+ planned: the layout moves at the theme's pace.
1977
+ A product's `declarationRefs` are NAMES THE FILE DECLARES IN CODE, never names of decisions, because
1978
+ landing looks for them in the file with its comments removed. For `NAVIGATION` that means
1979
+ zone keys only: `secondary` for a list-and-detail layout, `companion` for a persistent side panel. The
1980
+ transitions and viewport behaviour you decided (a split from list to detail, a phone that replaces the
1981
+ detail) go in the objective; a navigation product naming `navigation-transition-list-to-detail-split`
1982
+ is refused, because a navigation config has no place to declare it. `primary` is written by `wildo
1983
+ init`, so a plan keeping the one-zone default plans no navigation task at all.
1984
+ **The shell's CONTENT belongs to the placement tasks.** When a placement plan exists, the sidebar, the
1985
+ user menu and the command palette are each written by Step 1b's `SHELL_PLACEMENT` task for that surface,
1986
+ the only task whose landing can prove them (it compares the shell with what the plan placed). So the
1987
+ experience plan's `APP_SHELL` declarations that name a sidebar section or an entry go into the objective
1988
+ of the `SHELL_PLACEMENT` task for that surface, not into an `APP_SHELL` product. Emit an `APP_SHELL` task
1989
+ only for what no placement task writes (the shell's frame: which shell components are on, their chrome);
1990
+ its objective says the entries are left to the placement tasks, and the placement tasks wait on it.
1991
+ One application had its app-shell task write the whole sidebar, user menu and palette; three placement
1992
+ tasks then found their work already done, changed nothing, and ran for an hour and a half.
1394
1993
  When the plan decides a `home`, the `GLOBAL_VIEWS` task sets it: its objective says to make
1395
1994
  `homeDefinitionFactory` in `frontend/src/config/global-views.config.ts` return that home, carrying
1396
1995
  the home's rationale. A `VIEW` home is an application view: `{ compositeViewReference: <the view's
@@ -1400,6 +1999,17 @@ replaced — the judge reports it as a gap.
1400
1999
  `variantKey`: the root matches all of them exactly and silently shows the welcome page on a
1401
2000
  mismatch. That task depends on the resource's config task. Without the home the application opens
1402
2001
  on the framework's welcome page whatever the plan says.
2002
+ A `VIEW` home's `blocks` are what that view shows: the task that builds the home's application view
2003
+ carries every block into its objective — for an `AWAITING_DECISION` block, the resource, the
2004
+ transitions whose waiting records it lists (their `from` states) and the people who take them (the
2005
+ block is drawn only for a viewer who may perform that operation, `useViewerMayPerformResourceOperation`;
2006
+ `views-app-level`, `references/workflow-home.md`); for
2007
+ `MY_RECORDS`, the resource and whose records they are; for `KEY_FIGURE`, the figure — and depends on
2008
+ the config tasks of the resources it reads and on the operation tasks of the transitions it awaits.
2009
+ A block that lists records embeds the resource's own LIST drawn as its rows only, so the objective
2010
+ says `collectionToolbar: CollectionToolbarPresence.HIDDEN`: without it every block repeats the list
2011
+ page's search, view switch and Create.
2012
+ An objective that drops a block hands the agent the "Welcome" page under another title.
1403
2013
  - one task per planned MILESTONE, target `MODULE_BACKEND` on the milestone's module,
1404
2014
  product `APPLICATION_MILESTONE` naming its `milestoneRef`, skill
1405
2015
  `milestones-and-celebrations` (`EXPERIENCE_MILESTONE_SKILL_REF`). It depends on the config stage of its
@@ -1446,7 +2056,8 @@ replaced — the judge reports it as a gap.
1446
2056
  the foundation, one scenario per surface, so the task authors the BEHAVIOUR. With no
1447
2057
  integration plan, emit nothing here.
1448
2058
  - inbound channels → also decided by the **integration plan** (`inboundChannels`): work that
1449
- ARRIVES — clients emailing documents to a matter, customers writing to a support address.
2059
+ ARRIVES — clients emailing documents to a matter, customers writing to a support address,
2060
+ people texting an organization's number (`sms`).
1450
2061
  Emit one task per declared channel: target `MODULE_BACKEND` in the module whose records the
1451
2062
  messages concern, product `INBOUND_CHANNEL_HANDLER` with the channel and a `handlerRef`
1452
2063
  (`<moduleRef>.<purpose>`), skill `inbound-channels` (the dispatch adds it whatever you write,
@@ -1457,7 +2068,7 @@ replaced — the judge reports it as a gap.
1457
2068
  - **`connect_runtime_and_external_capabilities`** — providers and external connectors,
1458
2069
  and the **integration plan** decided these too: one task per PROVIDER BINDING it
1459
2070
  declares, target `PROVIDER_BINDING`, product `PROVIDER_BINDING` with the binding's own
1460
- `scope`, and its skill taken from that scope through
2071
+ `scope` (and its `augments`, copied as written: it is what that task is judged landed by), and its skill taken from that scope through
1461
2072
  `INTEGRATION_PROVIDER_BINDING_SKILL_REF` — do not choose it yourself, the map is total
1462
2073
  over the scope vocabulary. The binding's `rationale` is the task's objective. Reach for
1463
2074
  `provider-operation-calls` and `configure-billing` as the task's further reading when the
@@ -1469,7 +2080,12 @@ replaced — the judge reports it as a gap.
1469
2080
  (the verb table above); `PERSONAL_DATA` and `AUDIT_TRAIL` → the declarations in the resource
1470
2081
  config tasks' objectives; `BILLING` → the billing catalogue task; `GUIDANCE` → the experience
1471
2082
  plan's guidance tasks; `GOVERNED_DOCUMENT` → no build task (the compliance lane composes it);
1472
- `ORGANIZATION_MEMBERSHIP` and `LOCALIZATION` → no task beyond the foundation's capabilities.
2083
+ `ORGANIZATION_RELATIONSHIPS` → the organization-model task below (its relationship kinds), never
2084
+ a module: the engine owns the relationship rows between organizations; `ORGANIZATION_MEMBERSHIP`
2085
+ → no task for membership itself (members, invitations, units and their roles are the foundation's
2086
+ capabilities), BUT a requirement confining records to a unit or to their owner owes the
2087
+ confinement task below, which the domain plan records in `organizationModel.unitConfinements`;
2088
+ `LOCALIZATION` → no task beyond the foundation's capabilities.
1473
2089
  Never emit a task that builds one of these as a resource.
1474
2090
  - **The application roles** — target `APPLICATION_ROLES`, when a requirement names groups of
1475
2091
  users with different access ("office and field staff", "technicians cannot see invoices",
@@ -1483,6 +2099,88 @@ replaced — the judge reports it as a gap.
1483
2099
  resource it narrows, and say in its objective which operations each role may call. Never answer a
1484
2100
  role requirement with a resource holding roles, permissions or role assignments: nothing in the
1485
2101
  engine reads it.
2102
+ - **The organization model** — target `ORGANIZATION_MODEL`, and the **domain plan** decided it (your
2103
+ brief renders it under the domain plan). What the application's configuration ALREADY declares (its
2104
+ organization types with the one that owns the application, its relationship kinds, its system-of-record
2105
+ instances and their vendors) is the workspace section's "The organization model this application's
2106
+ configuration already declares": read every comparison below against it. Its `organizationModel` lists the organization types, the relationship kinds between them, the
2107
+ resources whose rows are confined below the organization, and where each resource's records live.
2108
+ Never a module or a resource for any of these, and above all never one for a relationship between
2109
+ organizations: the engine owns those rows, their record separation and their invitations (#2617).
2110
+ Emit, when the domain plan's organization model carries the entries:
2111
+ - ONE organization-model task (both lists live in `wildo.saas.config.ts`, so two tasks would write
2112
+ over each other) producing one `ORGANIZATION_TYPE` per entry of `organizationTypes`, carrying the
2113
+ entry's `ref`, `offeredRoles`, `userTypes` and `requiresMfa`, and one `ORGANIZATION_RELATIONSHIP_KIND`
2114
+ per entry of `relationshipKinds` the configuration does not already carry.
2115
+ **The OWNER type is identified by `ownsApplication`, never by its key.** By the time the build runs
2116
+ the platform has already created the operator's organization and its administrator under the
2117
+ scaffold's key (`workspace`), and the application line may have set its joining posture (an
2118
+ internal tool admits by invitation only). So the plan's owning type (`ownsApplication: true`),
2119
+ whatever it calls it (`group`), describes the configuration's EXISTING owner type: its product
2120
+ carries `ownsApplication: true`, and the task REVISES that type, keeping its joining posture and any
2121
+ sign-in or directory settings it carries. Its product lands only under the plan's key and granting
2122
+ exactly the plan's user types. The foundation has usually renamed it already; where the
2123
+ configuration still holds the scaffold's names (`workspace`, `member`), the task's objective says to
2124
+ RENAME them with a declared rename: the new organization type and the new user type each carry
2125
+ `renamedFrom: [{ key: '<old key>', justification: '…' }]`, every reference follows, and the backend
2126
+ then moves the organization and the accounts already created at its next start (skill
2127
+ `config-saas-backend`, reference `renaming-organization-and-user-types.md`). A key renamed without
2128
+ it strands them. Never add a second type with `ownsApplication` (the configuration refuses it at
2129
+ startup), and never replace the existing owner. Relationship kinds name the owner by the plan's key, which
2130
+ the configuration carries once renamed.
2131
+ A type's product lands when the type carries what the plan decided of it, so a type the
2132
+ configuration already declares as planned owes nothing and lands at once, and one declared
2133
+ differently lands only after the task revises it. A relationship kind proves only its KEY, so for
2134
+ a kind the configuration already carries but declares differently from the entry (other sides,
2135
+ `mutual`, conferred roles or `tenantRecords`), the task's objective names each difference and that
2136
+ kind declares no product. Its objective carries
2137
+ what each entry decided: for a type, its purpose, its user types, the roles it offers, whether it
2138
+ owns the application, whether its members must use a second factor (`requiresMfa`) and how an
2139
+ organization of it is joined; for a kind, which types represent
2140
+ and which grant, whether it is mutual, the roles it may confer and which records each relationship
2141
+ keeps apart (`tenantRecords`). Skills `config-saas-backend` and `organization-relationships` (the
2142
+ dispatch adds both whatever you write). Order it before the `APPLICATION_ROLES` task, which offers
2143
+ roles on these types and confers roles through these kinds; a role a relationship confers is that
2144
+ task's `RELATIONSHIP_CONFERRED_ROLE`, never this one's.
2145
+ - ONE confinement task producing one `ORGANIZATION_UNIT_CONFINEMENT` per entry of
2146
+ `unitConfinements`: the resource, its `mode` and its `fieldName`, verbatim. A resource confined to
2147
+ its unit AND to its owner's rows is two entries and two products. Skill
2148
+ `authorization-unit-narrowing` (added by the dispatch). Narrowing is ADDITIVE: a member whose
2149
+ organization-wide role already satisfies a read is not confined, so the task also gates the
2150
+ confined resource's reads above the default member role, and its objective says which role reads
2151
+ what. Order it after the config task of every confined resource and after the roles task.
2152
+ - each entry of `recordLocations` whose `location` is `SYSTEM_OF_RECORD` becomes a
2153
+ `SYSTEM_OF_RECORD_BINDING` product of THAT RESOURCE'S CONFIG task (not a separate task, since the
2154
+ binding is its configuration), carrying the entry's `systemOfRecordKind` and `access` verbatim, and
2155
+ an INSTANCE key derived, never invented: the key of the instance the workspace's configuration
2156
+ already declares under `systemsOfRecord` with that `vendor` (listed as "system-of-record instance
2157
+ `<key>` of vendor `<vendor>`" in the workspace section); when it declares none, the `systemOfRecordKind` itself (`odoo`). In that second
2158
+ case the CONFIG task's objective also declares the instance in `wildo.saas.config.ts`
2159
+ (`systemsOfRecord.<key>`, with `vendor` set to the kind, its dialect and its personal-data origin):
2160
+ the binding lands only on a declared instance of that vendor, and the task may write the
2161
+ configuration. Several resources from one system share one instance, so only the first of their
2162
+ config tasks declares it and the others depend on that task. The dispatch adds
2163
+ `resource-external-data` and `config-saas`. The resource keeps its other stages: a read-through
2164
+ resource has no table, so its schema task owes no migration.
2165
+ `partitioned` comes from the entry's `partition`, never from a guess: `true` for `BY_LEGAL_ENTITY`
2166
+ and `UNCONFIRMED`, `false` for `NOT_SPLIT` and `CANNOT_BE_SPLIT`. When it is `true`, the task that
2167
+ declares the instance gives it `partition: true`, and when the workspace section already lists the
2168
+ instance without "partitioned", the FIRST config task binding that system revises it (the others
2169
+ depend on that task); either objective says so: each legal entity of the system is then assigned
2170
+ to an organization unit by the operator, and a member reads only the entities of the units they
2171
+ hold a role in, so the resource's reads are gated above the default member role. A COPIED resource
2172
+ of a partitioned instance also declares `partitionUnitLocalField` and `partitionKeyLocalField` on
2173
+ its pipeline (two optional string fields of its schema, which its schema task adds); when the plan
2174
+ also confines that resource `ORGANIZATION_UNIT`, `partitionUnitLocalField` is the confinement's
2175
+ `fieldName`, since the engine narrows the copy on that field and refuses a second one. A
2176
+ read-through resource declares nothing, as the engine confines it on its own field. The split was
2177
+ read off the vendor's EFFECTIVE facet: its base facet plus any facet augmentation a declared instance
2178
+ opts into (when several instances use one vendor, the instance named like the vendor, else the
2179
+ first). `UNCONFIRMED` means that facet could not be read when the plan was written, or the engine
2180
+ refused to resolve it (an augmentation `wildo config sync` has not recorded, a vendor partitioned
2181
+ twice): the binding does not land on an instance whose effective facet declares no split (the
2182
+ backend refuses `partition: true` there at startup), and the task reports it.
2183
+ No organization model, or an empty one, emits nothing here.
1486
2184
  - **The billing catalogue** — target `BILLING_CATALOG`, and the **business model** decided it:
1487
2185
  its pricing plans are the products the application sells. Emit ONE task (the catalogue is one
1488
2186
  file, so two tasks would write over each other) producing one `APPLICATION_BILLING_PRODUCT` per
@@ -1496,7 +2194,9 @@ replaced — the judge reports it as a gap.
1496
2194
  is announced but the requirements do not yet build it. Order it after the module and resource
1497
2195
  tasks whose features the plans grant. The website's PRICING section task depends on it: the
1498
2196
  section reads this catalogue, so it must exist first. No business model, or one with no plans,
1499
- emits nothing.
2197
+ emits nothing. A plan priced `per_usage` is a METERED product, priced per unit of its `usageUnit`
2198
+ (the objective names the unit); its usage is recorded by a `METERED_USAGE_RECORDING` task on the
2199
+ operation that consumes it, ordered after this one.
1500
2200
  - **Data seeds** — target `MODULE_BACKEND` on the seed's module, product `APPLICATION_DATA_SEED`,
1501
2201
  skill `seeding-authoring` (the dispatch adds it whatever you write). A built application must not
1502
2202
  open EMPTY: an empty list is not something a creator can judge, try or show. Emit two kinds, and
@@ -1526,18 +2226,24 @@ replaced — the judge reports it as a gap.
1526
2226
  emit, in this order:
1527
2227
  - one `WEBSITE_PAGE` task per page (`produces: { kind: WEBSITE_PAGE, pageRef }`), skill
1528
2228
  `website-page-authoring`, its objective the page's own purpose. A page task authors the
1529
- PAGE — route, bridge, component, manifest, registration and an EMPTY sections list —
1530
- and never its sections: say so in the objective. On the first run that built a website
1531
- the page tasks wrote every section themselves, so no section skill was ever applied;
2229
+ PAGE — route (derived from the page's KIND: `/product/<slug>`, `/solutions/<slug>`, …),
2230
+ bridge, component, manifest, registration, its own entry in the site menu, and an EMPTY
2231
+ sections list — and never its sections: say so in the objective. On the first run that
2232
+ built a website the page tasks wrote every section themselves, so no section skill was
2233
+ ever applied. A `PRODUCT_OVERVIEW` page task comes after every `PRODUCT` page task: its
2234
+ menu link is the Product panel's overview, and the panel exists once its first product
2235
+ page does (the dispatch host derives that edge from the plan, so you need not write it);
1532
2236
  - one `WEBSITE_SECTION` task per section (`produces: { kind: WEBSITE_SECTION, pageRef,
1533
2237
  sectionRef }`), **with its page's task as a prerequisite** — a section is declared in
1534
2238
  its page's sections file, so the page must exist first — and its skill taken from the
1535
- section's KIND through `WEBSITE_SECTION_SKILL_REF`: `HERO` → `website-section-hero`,
1536
- `FEATURE_BENEFIT_SUMMARY` → `website-section-feature-benefit-summary`,
1537
- `FEATURE_DETAIL` → `website-section-feature-detail`, `PRICING` →
1538
- `website-section-pricing`, `SOCIAL_PROOF` → `website-section-social-proof`, `FAQ` →
1539
- `website-section-faq`, `CTA` → `website-section-cta`, `FOOTER_CTA` →
1540
- `website-section-footer-cta`, `CONTACT` → `website-section-contact`. Name it; the
2239
+ section's KIND through `WEBSITE_SECTION_SKILL_REF`, which gives every kind one: the kind's
2240
+ name in kebab case after `website-section-` (`HERO` → `website-section-hero`,
2241
+ `FEATURE_BENEFIT_SUMMARY` → `website-section-feature-benefit-summary`, `LATEST_POSTS` →
2242
+ `website-section-latest-posts`, and so on for all eighteen kinds, `STATS`, `INTEGRATIONS`
2243
+ and `ROADMAP` included). A
2244
+ `SOLUTION_PATHS` section comes after every `SOLUTION` page task: its cards link to those
2245
+ pages, and nothing at build checks a section's links, so built first it would publish links
2246
+ to pages that do not exist yet (the dispatch host derives that edge too). Name the skill; the
1541
2247
  dispatch derives the same skill from the plan and puts it first whatever you wrote, so a
1542
2248
  wrong one is harmless but a right one keeps the plan readable.
1543
2249
  A plan whose disposition is `NOT_APPLICABLE`, or no plan at all, emits NOTHING here — the
@@ -1553,8 +2259,8 @@ replaced — the judge reports it as a gap.
1553
2259
 
1554
2260
  ## Posture constraints are work, not commentary
1555
2261
 
1556
- The vision family's compliance posture and constraints are INPUT on equal footing with the
1557
- requirements: an obligation the posture states — a retention/erasure rule over customer data, a
2262
+ The compliance posture (the `compliance-posture` family) and the vision's constraints are INPUT on
2263
+ equal footing with the requirements: an obligation the posture states — a retention/erasure rule over customer data, a
1558
2264
  terminal-access (cookie/telemetry) posture, an operational-vs-marketing email distinction — needs a
1559
2265
  task that lands it, serving the nfr it substantiates. Do not compress a posture into an adjective
1560
2266
  inside another task's objective ("GDPR-appropriate handling"): an adjective is not schedulable,
@@ -1609,10 +2315,13 @@ surfaces whose output they consume**:
1609
2315
 
1610
2316
  - **`database-migrations`** — `wildo db generate`: turns the drift the schema stages created into a
1611
2317
  committed migration, and advances the accepted plan with it. **PostgreSQL-backed applications
1612
- ONLY** (`applicationDatabase: { engine: DatabaseEngine.POSTGRESQL }`); on MongoDB a collection
1613
- appears on first write and this step must not be authored at all — it REFUSES on an application
1614
- whose declared store is not PostgreSQL (or cannot be read), because generating there would author
1615
- a table set nothing uses. A PostgreSQL application with no accepted plan yet is the opposite case:
2318
+ ONLY**: an application ANY of whose environments declares
2319
+ `applicationDatabase: { engine: DatabaseEngine.POSTGRESQL }` (or declares no store, which selects
2320
+ PostgreSQL). One plan serves every environment, so a MongoDB `local` beside a PostgreSQL
2321
+ `production` still owes it. When EVERY environment is on MongoDB a collection appears on first
2322
+ write and this step must not be authored at all. It REFUSES there, and also when no readable
2323
+ environment declares PostgreSQL but one cannot be read, because generating would author a table
2324
+ set nothing uses. A PostgreSQL application with no accepted plan yet is the opposite case:
1616
2325
  the step renders the whole model as the INITIAL migration and writes the baseline beside it, and
1617
2326
  the dispatch host derives that step itself when the plan omits it.
1618
2327
 
@@ -1622,6 +2331,15 @@ surfaces whose output they consume**:
1622
2331
  migration. It needs a BUILT `backend-api`, because the plan is computed by importing the compiled
1623
2332
  registry; it refuses on an unbuilt tree instead of authoring a migration for a model nobody has.
1624
2333
 
2334
+ - **`design-system-brand` and `design-tokens`** — derived by the dispatch host around every
2335
+ DESIGN_SYSTEM config task, so do **not** author either. The brand step runs before that task and
2336
+ writes the brand's palette seeds and theme personality to `frontend/src/config/brand-design.ts`, and,
2337
+ when the application has a website, the same palette and point to `website/src/brand-theme.ts`; the
2338
+ tokens step runs after it and regenerates the stylesheet's design-token block from the config. The
2339
+ DESIGN_SYSTEM task itself derives its palette from those seeds and composes its theme from that
2340
+ personality rather than choosing colours or copying a theme (the `config-design-system` skill shows
2341
+ how), so name that skill on it.
2342
+
1625
2343
  There is no seeds GENERATION step: do **not** author one — an unknown `generationStepRef`
1626
2344
  refuses at dispatch instead of parking the build. Seeding is a CODING task: an
1627
2345
  `APPLICATION_DATA_SEED` product under the module's backend (Step 3, "Data seeds").
@@ -1643,6 +2361,21 @@ playbook's job — see the boundary below).
1643
2361
  already correct; carry them over as they are.
1644
2362
  - **Reuse existing task refs.** A task that already exists keeps its ref — never mint a
1645
2363
  second ref for the same unit of work.
2364
+ - **A task already built is never dropped, renamed or reshaped.** Your brief lists the build
2365
+ tasks that are built and committed, each with its target and what it produces. Each stays in
2366
+ your plan under the same ref (author its slug as the ref without its `build-task-` prefix),
2367
+ with that target and those products exactly, even when the domain plan moved around it:
2368
+ refine what its objective says if it must, never remove it, never give it a new name, and
2369
+ never change what it produces on your own initiative. Built work dropped from the plan is
2370
+ orphaned from it, a renamed task reads downstream as a change, and a task whose products
2371
+ changed reads unbuilt again although nothing in the code moved. Work you would add goes in a
2372
+ NEW task. When an input of the plan REQUIRES a built task's target or products to change (a
2373
+ service method that now decides its retention class, a step its agent must name), declare it
2374
+ in `reshapedBuiltTasks` with the task's slug and the reason: the task is then rebuilt. The
2375
+ reason is not the proof: a declared reshape is kept only when the task AS BUILT fails a check
2376
+ of this plan against its inputs (the domain-plan coverage, the firm's method, a reference that
2377
+ no longer resolves) and the new shape repairs it. A plan that drops or renames a built task,
2378
+ changes one it does not declare, or declares a reshape nothing requires, is refused.
1646
2379
  - **Never orphan an ordering reference.** A task's prerequisite reference must name a
1647
2380
  task that is actually in the plan. If you remove or rename a task, follow it into
1648
2381
  every prerequisite reference.
@@ -1706,7 +2439,8 @@ One artifact for this journey:
1706
2439
  relationship-wiring tasks, the interaction / UX / extension / integration tasks (views,
1707
2440
  frontend configuration, components, PDF templates, workers, minions, provider bindings,
1708
2441
  website pages and sections, documentation chapters — each over its own target and
1709
- product kind), any module-ensure tasks foundation did not cover, and the interleaved
2442
+ product kind), the organization-model tasks (types, relationship kinds, row confinements),
2443
+ any module-ensure tasks foundation did not cover, and the interleaved
1710
2444
  companion-generation steps — each carrying its target, **the artifacts it produces**,
1711
2445
  its one functional topic, its skill(s), and explicit `prerequisiteTaskRefs`.
1712
2446
 
@@ -1737,12 +2471,17 @@ what reaches you is this method, your declared inputs, and the brief's own secti
1737
2471
  (cardinality-to-FK-holder resolution, at dispatch time — named here, not performed).
1738
2472
  - `module-registration` — the cross-runtime module-registration
1739
2473
  task's HOW.
2474
+ - `config-saas-backend` — the organization-model task's organization types (`organizationTypes`).
2475
+ - `organization-relationships` — the organization-model task's relationship kinds, and the roles a
2476
+ relationship confers.
2477
+ - `authorization-unit-narrowing` — the confinement task's unit narrowing and own rows.
2478
+ - `resource-external-data` — a CONFIG task whose resource is bound to a system of record.
1740
2479
  - the skills CATALOG, which your brief carries as its own section — the skills router: consult it to bind each interaction /
1741
2480
  UX / extension / integration task to its real skill folder from the full catalog. Do
1742
2481
  not invent skill names; route through the index.
1743
2482
 
1744
2483
  ## Reviewer checklist — `build-plan-coherent`
1745
2484
 
1746
- These twelve invariants are the criteria of this playbook's compiled evaluation treatment (`application-creation:evaluation-treatment/build-plan-coherent`, one criterion per invariant, invariants 2 and 2b sharing one), which the advisory judge runs after every landing. They are kept here as creator-facing review guidance too, so a reviewer and the judge read the same words:
2485
+ These thirteen invariants are the criteria of this playbook's compiled evaluation treatment (`application-creation:evaluation-treatment/build-plan-coherent`, one criterion per invariant, invariants 2 and 2b sharing one), which the advisory judge runs after every landing. They are kept here as creator-facing review guidance too, so a reviewer and the judge read the same words:
1747
2486
 
1748
- Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess twelve invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product is a GAP. A plan with main resources and no `DEMONSTRATION` `APPLICATION_DATA_SEED` task is a CONCERN: the application would open empty. A seed task whose rows reference another seed's rows (a contact's customer) that is not ordered after that seed's task is a GAP — the reference resolves only against rows already written. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft whose two endpoints are resources the domain plan declares has a wiring task (bound to the module-relationships skill) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP. A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. The migration step follows the schema stages whose drift it migrates and is not authored for MongoDB. Do NOT flag the absence of an `i18n-translations` step — the dispatch host derives it after `i18n-labels`. Do NOT flag the absence of a seeds GENERATION step — none exists; seeding is an `APPLICATION_DATA_SEED` coding task, judged under invariant (1). (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (dispatch locking and concurrency, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises) that the build would have to invent to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (9) EXPERIENCE COVERAGE — every view, configuration, milestone and piece of guidance the experience plan declares has its task (a view task carrying the plan's viewRef verbatim, an onboarding document's objective naming its hostViewRef), and a decided `home` is set by the `GLOBAL_VIEWS` task's objective (it names `homeDefinitionFactory` and the home); an entry with no task, or a decided home no objective sets, is a GAP, and an objective that drops what the plan decided for its entry (reused components, the moment, the gate) is a CONCERN. With NO experience plan the plan rightly carries none of these tasks: mark PASS and begin the note with 'NO EXPERIENCE PLAN:' naming what the application will lack — never a CONCERN or GAP, because the decomposer cannot produce an upstream family by revising. (10) ROLE COVERAGE — every requirement that names groups of users with different access is served by an `APPLICATION_ROLES` task producing one `APPLICATION_ROLE` per group no core role covers, ordered after the config tasks of the resources it narrows; a group with no role, or a role requirement answered by a task or resource that stores roles or permissions as data, is a GAP; a roles task ordered before a config task it narrows, or whose objective does not say which operations each role may call, is a CONCERN. (11) INTERACTION COVERAGE — every transition the domain plan's lifecycles declare has its `RESOURCE_OPERATION` task (and a `MODULE_BACKEND` task when it creates a resource), and every functional acceptance criterion whose verb goes beyond the default resource verbs (a state change, one record creating or filling another, a record that must stop changing, a produced document, a sent message) is served by a task of the matching kind (`RESOURCE_OPERATION`, a `MODULE_BACKEND` implementation, `PDF_TEMPLATE`, the email generation step) whose `servesRefs` name the requirement; a plan whose requirements describe a workflow and which carries no interaction task, or a state change served only by a config task that leaves the status freely editable, is a GAP; a derived value (a next action, an overdue flag) planned as a stored field is a CONCERN. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)
2487
+ Judge whether the drafted build plan is a coherent, complete, correctly-ordered decomposition of the approved domain plan into coding-agent tasks — WITHOUT straying into how those tasks execute. Assess thirteen invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) MODULE + RESOURCE COVERAGE — every resource in every module's inventory (mainResources + supportingResources) has build tasks; a resource with no task is a GAP (the build would not produce it). Task `moduleRef` values must be module ids the workspace section lists (an invented module id is a GAP — the dispatcher cannot route it), and a task whose objective CREATES a resource the workspace section shows already exists — instead of enriching it — is a CONCERN (it dispatches a no-op). Module slices are scaffolded by the foundation step (a sibling playbook), so a module needs a dedicated ensure-module task ONLY where foundation did not establish it — a module whose resources have tasks but which carries no redundant scaffold task is NOT a GAP (do not flag the absence of a module-scaffold task foundation already owns); a module added to the plan after foundation with neither a foundation slice nor an ensure-module task IS a GAP. Every pricing plan the business model declares must be an `APPLICATION_BILLING_PRODUCT` of a `BILLING_CATALOG` task whose `servesRefs` name it; a declared plan with no billing product is a GAP. A plan with main resources and no `DEMONSTRATION` `APPLICATION_DATA_SEED` task is a CONCERN: the application would open empty. A seed task whose rows reference another seed's rows (a contact's customer) that is not ordered after that seed's task is a GAP — the reference resolves only against rows already written. (2) TASK WELL-FORMEDNESS — every task names exactly ONE functional topic that is a real MetaWorkflow_FunctionalTopic value (configure_application_foundation / model_domain_graph / define_interaction_semantics / shape_user_experience / extend_application / connect_runtime_and_external_capabilities / assemble_verify_and_iterate) and at least one skill that is a real folder in the app-knowledge skill catalog; a task with an invented topic or a dangling skill is a GAP. (2b) PRODUCT DECLARATION — every task except a COMPANION_GENERATION_STEP declares at least one product in `produces`, and a generation step declares none; a coding task with an empty `produces` is a GAP, because it has no declared output to probe. The host can advance after a COMPLETED durable run, but carries the task in `unverifiableLandedTaskRefs`; that means ran, not proven. Repair the product declaration rather than treating this fallback as evidence of correct output. A product must name something COMPOSITION DOES NOT ALREADY WRITE — the fields a schema gains rather than its file, the verbs a config gains rather than its file, both endpoints of a relationship rather than one — so a product naming only a scaffolded artifact is a GAP wearing a declaration. Two tasks claiming the SAME artifact is a GAP as well (landing becomes undecidable); two tasks enriching one resource with DIFFERENT fields is correct and not a finding. A cross-resource FOREIGN KEY declared on a schema task's `produces` is a GAP — the relationship task is its single home (Step 2), and declaring it twice attributes one artifact to two tasks; a schema task's products are the resource's OWN domain fields. (3) PER-RESOURCE STAGE ORDER — for each resource, its tasks respect the inner order schema -> config -> ui-behavior -> spec; a config task ordered before that resource's schema task, or a spec task before its ui-behavior task, is a GAP (the build stage would run against a missing prerequisite). A supportingResource (e.g. a pure junction / lookup entity) may legitimately OMIT stages it does not need — a junction with schema + config and no ui-behavior is fine; only an out-of-ORDER stage (or a mainResource missing schema/config) is a GAP, not an intentionally-omitted stage on a supporting resource. (4) TOPIC DEPENDENCY ORDER — tasks respect the topic dependency edges (model_domain_graph before define_interaction_semantics; app-level shape_user_experience [views / navigation composing multiple resources or operations] after the interaction semantics and resources it composes; extend_application after the UX it extends; connect_runtime_and_external_capabilities after the resources it connects). Note the deliberate exception: a resource's OWN ui-behavior (its field displays / forms, a shape_user_experience task) depends only on that resource's own schema + config and MAY precede cross-resource operations — that is NOT a violation. What IS a GAP: an app-level view composing resources/operations placed before they exist, an integration task before the resources it connects, or any user-experience task before that resource's schema task. The per-resource spec task is a documentation capstone (topic model_domain_graph) and must be ordered after the schema / config / ui-behavior stages it documents; a spec task before its ui-behavior stage is a GAP. (5) RELATIONSHIP COVERAGE — every relationship-draft whose two endpoints are resources the domain plan declares is named in the `relationshipRefs` of a wiring task (bound to the module-relationships skill, one task per module, with one product per relationship) ordered AFTER both endpoint resources' schema tasks; a relationship with no wiring task, or one ordered before its endpoints exist, is a GAP; two wiring tasks of one module that neither waits on the other are a CONCERN (they edit one file). A relationship to a resource no module declares is NOT this invariant: no task can wire it, so it is invariant (8)'s. (6) COMPANION-GENERATION INTERLEAVE — the executable companion-owned generation steps (`i18n-labels`, `email-templates`, `logo`, plus `database-migrations` for a PostgreSQL-backed application) are present and placed AFTER the resources / modules whose output they consume; a labels-generation task ordered before the resources it labels, or a missing executable generation step for authored surfaces, is a CONCERN. `logo` is the exception to the ordering half — it consumes the brand brief rather than any code surface, so it is unordered with respect to resource work and only its ABSENCE (on an application with a brand brief) is a CONCERN. The migration step follows the schema stages whose drift it migrates and is not authored when every environment of the application is on MongoDB (one environment on PostgreSQL makes it owed). Do NOT flag the absence of an `i18n-translations` step — the dispatch host derives it after `i18n-labels`. Do NOT flag the absence of a seeds GENERATION step — none exists; seeding is an `APPLICATION_DATA_SEED` coding task, judged under invariant (1). (7) BOUNDARY DISCIPLINE — the plan stays at DECOMPOSITION depth: it names tasks, their topic, their skill(s), their target, and their ordering intent; it does NOT specify how a task is DISPATCHED (dispatch locking and concurrency, change-set capture, git baseline, verify/quality-gate mechanics = the dispatch-orchestration playbook) and does NOT solve multi-agent SCALE or interleaving concurrency (= the scale playbook). Any task that describes how a task EXECUTES rather than WHAT it builds, or that authors a schema / resolves a cardinality into a concrete FK / generates code, is a CONCERN (scope creep out of the decomposition phase). (8) CONCEPTION BUILDABLE — this one faults the CONCEPTION, never the plan: a GAP when the domain plan declares a module, resource or relationship no build target can express however it is decomposed, or when the computed coherence report shows a dangling reference or unrealised decision in the conception (a domain-plan resource another family names that does not exist, a composition surface no plan realises, a placement plan that still puts a concept's list on the sidebar or leaves the concept's view off it) that the build would have to invent, or override, to proceed. An element the plan merely FORGOT is invariant (1), not this one — only a conception GAP sends the application back to its conception lane, which is the most expensive way to fix an omission. Name the conception element. (9) EXPERIENCE COVERAGE — every view, configuration, milestone and piece of guidance the experience plan declares has its task (a view task carrying the plan's viewRef verbatim, an onboarding document's objective naming its hostViewRef), and a decided `home` is set by the `GLOBAL_VIEWS` task's objective (it names `homeDefinitionFactory` and the home), and a `VIEW` home's blocks are carried by the objective of the task that builds the home view, each listing block drawn as its rows (`collectionToolbar: CollectionToolbarPresence.HIDDEN`); an entry with no task, or a decided home no objective sets, is a GAP, and an objective that drops what the plan decided for its entry (reused components, the moment, the gate, a home block) is a CONCERN. With NO experience plan the plan rightly carries none of these tasks: mark PASS and begin the note with 'NO EXPERIENCE PLAN:' naming what the application will lack — never a CONCERN or GAP, because the decomposer cannot produce an upstream family by revising. (10) ROLE COVERAGE — every requirement that names groups of users with different access is served by an `APPLICATION_ROLES` task producing one `APPLICATION_ROLE` per group no core role covers, ordered after the config tasks of the resources it narrows; a group with no role, or a role requirement answered by a task or resource that stores roles or permissions as data, is a GAP; a roles task ordered before a config task it narrows, or whose objective does not say which operations each role may call, is a CONCERN. (11) INTERACTION COVERAGE — every transition the domain plan's lifecycles declare has its `RESOURCE_OPERATION` product named by its `transitionRef` (a transition that creates a resource says so in that task's objective; a separate task for the write, or an operation named after a transition with something added, is a GAP), and every functional acceptance criterion whose verb goes beyond the default resource verbs (a state change, one record creating or filling another, a record that must stop changing, a produced document, a sent message) is served by a task of the matching kind (`RESOURCE_OPERATION`, a `MODULE_BACKEND` implementation, `PDF_TEMPLATE`, the email generation step) whose `servesRefs` name the requirement; a plan whose requirements describe a workflow and which carries no interaction task, or a state change served only by a config task that leaves the status freely editable, is a GAP; a derived value (a next action, an overdue flag) planned as a stored field is a CONCERN. On the person's side of each lifecycle, a resource with a lifecycle and no `RESOURCE_UI_BEHAVIOR` task is a GAP (its page is the engine's generated one, which knows no route), and a transition objective that does not offer the step only from its `from` states on every variant, a refusal the operation can raise left unworded for the person, or a lifecycle resource's ui-behavior objective that does not state its record page (status as the leading pill shown once — on the header or as `<RecordState>`, never both — next steps as worded actions ordered by `displayPriority`, sections in business order, record keeping last in `<RecordKeepingFacts>`) is a CONCERN. (12) ORGANIZATION MODEL COVERAGE — every organization type the domain plan's `organizationModel` declares is an `ORGANIZATION_TYPE` product of an `ORGANIZATION_MODEL` task carrying its offered roles, user types and `requiresMfa`, the owning type with `ownsApplication: true` revising the configuration's existing owner type whatever its key and, where the configuration still holds other names, renaming it and its people to the plan's names with `renamedFrom` (a second owner type, or a replaced one, is a GAP), and every relationship kind the configuration does not already carry is an `ORGANIZATION_RELATIONSHIP_KIND` product; every unit confinement is an `ORGANIZATION_UNIT_CONFINEMENT` product with its mode and field; every resource whose records live in a system of record carries a `SYSTEM_OF_RECORD_BINDING` product on its config task, `partitioned` exactly as the entry's split by legal entity decides (true for `BY_LEGAL_ENTITY` or `UNCONFIRMED`). An entry with no product, or a binding whose `partitioned` is absent or says otherwise, is a GAP; a relationship between organizations built as a module or a resource is a GAP (the engine owns those rows); a confinement task ordered before the config task of a resource it confines is a CONCERN. With no organization model, mark PASS. (The deterministic gates and the creator's approval remain the floors; the judge's verdicts are advisory notes beside them.)