@wildo-ai/framework-knowledge 1.1.11 → 1.1.13

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 (812) 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 +3 -3
  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 +180 -32
  13. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  14. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  15. package/dist/esm/framework-knowledge.loader.js.map +1 -1
  16. package/dist/esm/framework-knowledge.research-provenance.d.ts +6 -4
  17. package/dist/esm/framework-knowledge.research-provenance.d.ts.map +1 -1
  18. package/dist/esm/framework-knowledge.research-provenance.js.map +1 -1
  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.map +1 -1
  22. package/dist/esm/index.js.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -3
  24. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +4 -12
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +12 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +7 -4
  31. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +76 -14
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
  35. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -15
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
  41. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  43. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +1 -1
  45. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +1 -1
  47. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  49. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +35 -14
  50. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  51. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +16 -8
  52. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  53. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +19 -8
  54. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  55. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +30 -3
  56. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  57. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +87 -16
  58. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  61. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +2 -2
  62. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
  63. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +2 -2
  64. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
  65. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +5 -1
  66. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +3 -2
  68. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  69. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  71. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +45 -10
  72. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +61 -21
  74. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +4 -3
  76. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +8 -5
  78. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
  79. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  80. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +2 -2
  82. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  83. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +3 -5
  84. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -1
  85. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +1 -1
  86. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +3 -3
  88. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
  89. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  90. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +8 -6
  91. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  92. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +5 -0
  93. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  94. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +8 -1
  95. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -1
  96. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  97. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +4 -1
  99. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +11 -3
  101. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  103. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +1 -1
  104. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  105. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  106. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +6 -4
  107. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  108. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +3 -1
  109. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  110. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +4 -1
  111. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +10 -1
  113. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +36 -13
  115. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  116. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +8 -2
  117. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  118. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +7 -1
  119. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +4 -1
  121. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +34 -6
  123. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  124. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +5 -2
  125. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  126. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +4 -3
  127. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  128. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  129. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +2 -2
  130. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  131. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +22 -10
  132. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  133. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +39 -29
  134. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  135. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  136. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  137. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +8 -3
  138. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  139. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -7
  140. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  141. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  142. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  143. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  144. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -1
  145. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  146. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  147. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  148. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +2 -2
  149. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  150. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  151. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  152. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  153. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +1 -1
  154. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  156. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +13 -5
  157. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  158. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +3 -7
  159. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  160. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +12 -14
  161. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  162. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +3 -0
  163. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  164. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +2 -1
  165. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  166. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +3 -1
  167. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  168. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +2 -1
  169. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  170. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts +4 -1
  171. package/dist/esm/playbooks/top_down.service-method/playbook.definition.d.ts.map +1 -1
  172. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js +14 -1
  173. package/dist/esm/playbooks/top_down.service-method/playbook.definition.js.map +1 -1
  174. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +3 -1
  175. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  176. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +4 -2
  177. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  178. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +34 -1
  179. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  180. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +35 -17
  181. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  182. package/dist/esm/source-anchor-grammar.d.ts.map +1 -1
  183. package/dist/esm/source-anchor-grammar.js.map +1 -1
  184. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  185. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  186. package/dist/knowledge/manifest.json +7 -7
  187. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +6 -0
  188. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +4 -4
  189. package/dist/knowledge/playbooks/bottom_up.build/method.md +12 -2
  190. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +5 -3
  191. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  192. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  193. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +439 -27
  194. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +15 -4
  195. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +203 -7
  196. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -5
  197. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +1 -0
  198. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -0
  199. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +1 -0
  200. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +2 -2
  201. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +2 -1
  202. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  203. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  204. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +104 -2
  205. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +8 -4
  206. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +59 -4
  207. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +18 -6
  208. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +121 -24
  209. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +55 -8
  210. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +15 -8
  211. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +2 -1
  212. package/dist/knowledge/playbooks/bottom_up.maturity-reading/method.md +19 -2
  213. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +4 -3
  214. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +34 -0
  215. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +9 -2
  216. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +1 -0
  217. package/dist/knowledge/playbooks/cross_cutting.application-creation/method.md +27 -12
  218. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +11 -5
  219. package/dist/knowledge/playbooks/cross_cutting.compliance/method.md +4 -4
  220. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +7 -2
  221. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +1 -0
  222. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +6 -6
  223. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +3 -4
  224. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-protocol.json +1 -1
  225. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/evaluation-treatment.json +1 -1
  226. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +56 -5
  227. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +3 -2
  228. package/dist/knowledge/playbooks/refinement.document-facts/method.md +6 -4
  229. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +5 -1
  230. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +8 -1
  231. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -0
  232. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  233. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  234. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +15 -3
  235. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +11 -4
  236. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +3 -2
  237. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  238. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  239. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +16 -6
  240. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +3 -2
  241. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +5 -1
  242. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  243. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  244. package/dist/knowledge/playbooks/top_down.business-model/method.md +43 -11
  245. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +24 -8
  246. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +6 -2
  247. package/dist/knowledge/playbooks/top_down.compliance-analysis/method.md +1 -1
  248. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +49 -14
  249. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +3 -3
  250. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +6 -2
  251. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/method.md +20 -0
  252. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +4 -3
  253. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-protocol.json +1 -1
  254. package/dist/knowledge/playbooks/top_down.compliance-posture/evaluation-treatment.json +1 -1
  255. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +69 -65
  256. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +11 -7
  257. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -0
  258. package/dist/knowledge/playbooks/top_down.definition/method.md +3 -1
  259. package/dist/knowledge/playbooks/top_down.definition/playbook.json +11 -3
  260. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +1 -0
  261. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -0
  262. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +1 -0
  263. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +4 -2
  264. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +4 -3
  265. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +1 -0
  266. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +3 -0
  267. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +3 -2
  268. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  269. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  270. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -0
  271. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +14 -0
  272. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +11 -7
  273. package/dist/knowledge/playbooks/top_down.risk-register/method.md +7 -0
  274. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +5 -1
  275. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +6 -1
  276. package/dist/knowledge/playbooks/top_down.service-method/method.md +19 -1
  277. package/dist/knowledge/playbooks/top_down.service-method/playbook.json +16 -4
  278. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +5 -2
  279. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +9 -3
  280. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-protocol.json +1 -1
  281. package/dist/knowledge/playbooks/top_down.vision-elicitation/evaluation-treatment.json +1 -1
  282. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +17 -2
  283. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +59 -15
  284. package/dist/knowledge/references/application-documentation-chapters.config.md +45 -10
  285. package/dist/knowledge/references/application-documentation-plan.config.md +2 -2
  286. package/dist/knowledge/references/application-maturity.config.md +70 -1
  287. package/dist/knowledge/references/backend.inbound-channels.attachment-adoption.md +4 -2
  288. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +52 -11
  289. package/dist/knowledge/references/backend.inbound-handlers.definition.md +38 -1
  290. package/dist/knowledge/references/brand.name-screening.config.md +30 -3
  291. package/dist/knowledge/references/build-plan.task-graph.config.md +200 -4
  292. package/dist/knowledge/references/business-model.pricing-plan.config.md +12 -9
  293. package/dist/knowledge/references/business-model.snapshot.config.md +29 -2
  294. package/dist/knowledge/references/business-model.snapshot.validation.md +11 -8
  295. package/dist/knowledge/references/companion.introspection.behaviors.market.md +3 -0
  296. package/dist/knowledge/references/companion.market.generation-service.md +46 -5
  297. package/dist/knowledge/references/companion.market.prompt-renderer.md +1 -1
  298. package/dist/knowledge/references/companion.technical-doc.service.md +195 -63
  299. package/dist/knowledge/references/domain-plan.record-partition.md +105 -0
  300. package/dist/knowledge/references/engine.client-bundle.allow-list.md +3 -1
  301. package/dist/knowledge/references/engine.saas-technical-doc.config.md +69 -15
  302. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +10 -0
  303. package/dist/knowledge/references/example.backend.addon-wiring.module.md +6 -0
  304. package/dist/knowledge/references/example.backend.custom-operation.declared-refusal-code.md +41 -0
  305. package/dist/knowledge/references/example.backend.custom-operation.external-effect-reservation.md +107 -0
  306. package/dist/knowledge/references/example.blueprint.definition.internal-tool.md +4 -2
  307. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +8 -5
  308. package/dist/knowledge/references/example.infra.environment-config.local.md +13 -66
  309. package/dist/knowledge/references/example.module.companion-exports.full.md +1 -0
  310. package/dist/knowledge/references/example.module.relationships.actor-edge-back-to-scope-owner.md +35 -35
  311. package/dist/knowledge/references/example.navigation.one-entry-per-concept.md +47 -0
  312. package/dist/knowledge/references/example.organization-identity.system-of-record-partitions.md +18 -0
  313. package/dist/knowledge/references/example.provider.backend-module-shape.md +28 -4
  314. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +0 -4
  315. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +21 -0
  316. package/dist/knowledge/references/example.resource.custom-view.backend-refusal.md +75 -0
  317. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +8 -7
  318. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +37 -2
  319. package/dist/knowledge/references/example.resource.ui-behavior.record-template.md +0 -1
  320. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +1 -1
  321. package/dist/knowledge/references/example.resource.ui-behavior.workflow-record-page.md +212 -0
  322. package/dist/knowledge/references/example.subject-export.portability-archive.md +42 -0
  323. package/dist/knowledge/references/example.views.app-level.workflow-home.md +238 -0
  324. package/dist/knowledge/references/example.website.demo.complete-items.md +3 -3
  325. package/dist/knowledge/references/example.website.pricing.audit-payloads.md +38 -0
  326. package/dist/knowledge/references/example.website.pricing.catalog-load.md +77 -0
  327. package/dist/knowledge/references/example.website.pricing.offers.md +43 -0
  328. package/dist/knowledge/references/example.website.pricing.plans-section.md +20 -0
  329. package/dist/knowledge/references/example.website.pricing.plans.md +88 -0
  330. package/dist/knowledge/references/example.website.section.stats.md +1 -1
  331. package/dist/knowledge/references/experience-plan.config.md +111 -1
  332. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +2 -0
  333. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +8 -1
  334. package/dist/knowledge/references/external-connectors.models.hook-signature-algorithms.md +104 -0
  335. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +11 -6
  336. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +165 -0
  337. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +1035 -19
  338. package/dist/knowledge/references/external-connectors.private.provider-compliance-state-collector.md +36 -0
  339. package/dist/knowledge/references/external-connectors.private.provider-configuration-check.md +69 -0
  340. package/dist/knowledge/references/integration-plan.config.md +7 -7
  341. package/dist/knowledge/references/placement-plan.config.md +19 -0
  342. package/dist/knowledge/references/platform.config.backing-services.md +9 -11
  343. package/dist/knowledge/references/platform.config.environment.deployment.md +133 -8
  344. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +3 -3
  345. package/dist/knowledge/references/platform.config.infrastructure-host.md +1 -1
  346. package/dist/knowledge/references/platform.config.platform-key-management.md +89 -10
  347. package/dist/knowledge/references/platform.config.saas.md +20 -18
  348. package/dist/knowledge/references/presets.3d.frame-style-resolution.md +65 -0
  349. package/dist/knowledge/references/presets.layouts-2d.authoring.md +1 -1
  350. package/dist/knowledge/references/presets.models.field-form-control-variant.md +32 -0
  351. package/dist/knowledge/references/presets.models.labelling.sections.md +39 -0
  352. package/dist/knowledge/references/presets.models.surface-policy.defaults.md +3 -3
  353. package/dist/knowledge/references/presets.models.surface-variant.md +5 -4
  354. package/dist/knowledge/references/presets.themes.compose-theme.md +2 -1
  355. package/dist/knowledge/references/requirements.engine-substance.md +38 -0
  356. package/dist/knowledge/references/requirements.functional-requirement.config.md +11 -0
  357. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +15 -4
  358. package/dist/knowledge/references/requirements.snapshot.config.md +2 -3
  359. package/dist/knowledge/references/saas.approval-seals.admin-endpoints.md +49 -2
  360. package/dist/knowledge/references/saas.backend.a2a.token-budget.md +11 -4
  361. package/dist/knowledge/references/saas.backend.actor-execution-continuation.md +21 -0
  362. package/dist/knowledge/references/saas.backend.app-config.backend-authored.md +5 -1
  363. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
  364. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +13 -1
  365. package/dist/knowledge/references/saas.backend.custom-operation.authoritative-fields.md +4 -1
  366. package/dist/knowledge/references/saas.backend.custom-operation.core-write-precondition.md +38 -0
  367. package/dist/knowledge/references/saas.backend.custom-operation.external-effect-reservation.md +109 -0
  368. package/dist/knowledge/references/saas.backend.custom-operation.hook-transaction-posture.md +43 -0
  369. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +1 -1
  370. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +62 -13
  371. package/dist/knowledge/references/saas.backend.domain-module.md +30 -1
  372. package/dist/knowledge/references/saas.backend.flows-actors.a2a-task-surface.md +26 -3
  373. package/dist/knowledge/references/saas.backend.flows-actors.chat-reply-handler.md +13 -1
  374. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +435 -2
  375. package/dist/knowledge/references/saas.backend.flows-actors.invoke-agent.md +5 -3
  376. package/dist/knowledge/references/saas.backend.flows-actors.resource-read-tool.md +1 -1
  377. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +9 -4
  378. package/dist/knowledge/references/saas.backend.flows.start-flow-method.md +2 -1
  379. package/dist/knowledge/references/saas.backend.privacy.subject-export-archive.md +26 -0
  380. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +21 -19
  381. package/dist/knowledge/references/saas.backend.system-access-service.md +159 -4
  382. package/dist/knowledge/references/saas.config.content-security-policy.md +26 -9
  383. package/dist/knowledge/references/saas.data-seeding.definition-input.md +1 -1
  384. package/dist/knowledge/references/saas.data-seeding.modes.md +4 -1
  385. package/dist/knowledge/references/saas.data-seeding.row-reference.md +2 -4
  386. package/dist/knowledge/references/saas.external-providers.backend-provider-loader.md +6 -0
  387. package/dist/knowledge/references/saas.external-providers.backend-provider-registry.runtime-filter.md +2 -0
  388. package/dist/knowledge/references/saas.frontend.chart-dashboard-view.md +43 -0
  389. package/dist/knowledge/references/saas.frontend.chart-dashboard.md +133 -0
  390. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +8 -4
  391. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +76 -9
  392. package/dist/knowledge/references/saas.frontend.command-menu.search-resource.md +3 -3
  393. package/dist/knowledge/references/saas.frontend.errors.backend-refusal.md +96 -0
  394. package/dist/knowledge/references/saas.frontend.execution-view.definition.md +40 -0
  395. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +4 -0
  396. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +3 -5
  397. package/dist/knowledge/references/saas.frontend.record-page-parts.md +117 -0
  398. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +46 -16
  399. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +6 -0
  400. package/dist/knowledge/references/saas.frontend.resource-header-title.md +1 -1
  401. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +43 -9
  402. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +259 -15
  403. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -2
  404. package/dist/knowledge/references/saas.frontend.section-stages.md +63 -0
  405. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +42 -0
  406. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +6 -9
  407. package/dist/knowledge/references/saas.frontend.viewer-may-perform-operation.md +52 -0
  408. package/dist/knowledge/references/saas.models.agent-suspension.md +8 -8
  409. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +21 -0
  410. package/dist/knowledge/references/saas.models.auth.relationship-grantor-authentication.md +2 -2
  411. package/dist/knowledge/references/saas.models.chart-dashboard-tile-sizes.md +40 -0
  412. package/dist/knowledge/references/saas.models.config.declared-type-renames.md +246 -0
  413. package/dist/knowledge/references/saas.models.config.organization-types.md +20 -0
  414. package/dist/knowledge/references/saas.models.conversation-threads.md +39 -3
  415. package/dist/knowledge/references/saas.models.crypto-keys.floors.md +10 -0
  416. package/dist/knowledge/references/saas.models.crypto-keys.local-provider.md +2 -0
  417. package/dist/knowledge/references/saas.models.crypto-keys.purpose-descriptor.md +39 -0
  418. package/dist/knowledge/references/saas.models.crypto-keys.purposes.md +7 -0
  419. package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -78
  420. package/dist/knowledge/references/saas.models.engine-capabilities.md +11 -2
  421. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +3 -0
  422. package/dist/knowledge/references/saas.models.external-data-pipeline.md +15 -8
  423. package/dist/knowledge/references/saas.models.flows-actors.agent-behavior-report.md +13 -9
  424. package/dist/knowledge/references/saas.models.flows-actors.agent-configuration.md +29 -0
  425. package/dist/knowledge/references/saas.models.flows-actors.agent-content-guardrails-environment.md +52 -0
  426. package/dist/knowledge/references/saas.models.flows-actors.agent-operation-record.md +7 -0
  427. package/dist/knowledge/references/saas.models.flows-actors.human-decision-decider.md +8 -0
  428. package/dist/knowledge/references/saas.models.flows-actors.human-input-form.md +47 -12
  429. package/dist/knowledge/references/saas.models.flows-actors.operation-approval-requirement.md +31 -0
  430. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +3 -3
  431. package/dist/knowledge/references/saas.models.flows.runnable-model.md +21 -2
  432. package/dist/knowledge/references/saas.models.guidance-flow.md +1 -1
  433. package/dist/knowledge/references/saas.models.http-api-binding.md +19 -8
  434. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +1 -1
  435. package/dist/knowledge/references/saas.models.inbound-channels.md +71 -2
  436. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +1 -1
  437. package/dist/knowledge/references/saas.models.notifications.targets.md +3 -1
  438. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +201 -15
  439. package/dist/knowledge/references/saas.models.organization-assigned-rows-declaration.md +2 -1
  440. package/dist/knowledge/references/saas.models.organization-dashboard-layout.md +61 -0
  441. package/dist/knowledge/references/saas.models.organization-own-rows-declaration.md +5 -2
  442. package/dist/knowledge/references/saas.models.organizations.identity-declaration.md +201 -0
  443. package/dist/knowledge/references/saas.models.organizations.organization-relationships.md +25 -3
  444. package/dist/knowledge/references/saas.models.organizations.relationship-invitations.md +6 -2
  445. package/dist/knowledge/references/saas.models.organizations.relationship-kinds.md +14 -0
  446. package/dist/knowledge/references/saas.models.organizations.relationship-record-separation.md +1 -0
  447. package/dist/knowledge/references/saas.models.privacy.data-residency.md +676 -0
  448. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +46 -2
  449. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +6 -0
  450. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +84 -1
  451. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +10 -0
  452. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +5 -3
  453. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +2 -0
  454. package/dist/knowledge/references/saas.models.privacy.subject-export.md +134 -0
  455. package/dist/knowledge/references/saas.models.provider-capabilities.md +5 -0
  456. package/dist/knowledge/references/saas.models.providers.capability-resolution-mode.md +12 -6
  457. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +15 -0
  458. package/dist/knowledge/references/saas.models.providers.processing-region-reach.md +132 -0
  459. package/dist/knowledge/references/saas.models.providers.processing-region-selection.md +139 -0
  460. package/dist/knowledge/references/saas.models.representative-activity.md +4 -0
  461. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +107 -42
  462. package/dist/knowledge/references/saas.models.resource-config.operation-api-call.md +35 -0
  463. package/dist/knowledge/references/saas.models.resource-config.operation-auditable-event.md +4 -2
  464. package/dist/knowledge/references/saas.models.resource-config.operation-condition-parameters.md +56 -0
  465. package/dist/knowledge/references/saas.models.resource-config.operation-idempotency-key.md +16 -6
  466. package/dist/knowledge/references/saas.models.resource-config.operation-scope-admissions.md +38 -0
  467. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +14 -16
  468. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +2 -2
  469. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +21 -0
  470. package/dist/knowledge/references/saas.models.resource-config.system-access-policy.md +32 -15
  471. package/dist/knowledge/references/saas.models.resource-operation-display-risk.md +5 -4
  472. package/dist/knowledge/references/saas.models.roles.definition.md +12 -1
  473. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +6 -0
  474. package/dist/knowledge/references/saas.models.schema-family-builder.md +17 -2
  475. package/dist/knowledge/references/saas.models.system-of-record-actions.md +65 -1
  476. package/dist/knowledge/references/saas.models.system-of-record-capabilities.md +3 -1
  477. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +16 -0
  478. package/dist/knowledge/references/saas.models.systems-of-record.md +75 -14
  479. package/dist/knowledge/references/saas.public-runtime.contract.md +41 -23
  480. package/dist/knowledge/references/saas.rag.retrieval-refusals.md +3 -2
  481. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +12 -4
  482. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +21 -2
  483. package/dist/knowledge/references/saas.specifications.engine-resource-sub-domain.md +105 -0
  484. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +6 -2
  485. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +20 -3
  486. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +100 -71
  487. package/dist/knowledge/references/saas.specifications.translation-glossary.md +80 -0
  488. package/dist/knowledge/references/saas.website.astro.label-loader.md +44 -10
  489. package/dist/knowledge/references/saas.website.astro.runtime-helper.md +3 -2
  490. package/dist/knowledge/references/saas.website.blog.collection-config.md +36 -32
  491. package/dist/knowledge/references/saas.website.blog.cover-resolver.md +1 -1
  492. package/dist/knowledge/references/saas.website.blog.frontmatter.md +2 -2
  493. package/dist/knowledge/references/saas.website.blog.post-renderer.md +2 -2
  494. package/dist/knowledge/references/saas.website.blog.react-mdx-integration.md +26 -19
  495. package/dist/knowledge/references/saas.website.blog.react-mdx-query.md +1 -1
  496. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +3 -1
  497. package/dist/knowledge/references/saas.website.config.site-context-loader.md +6 -3
  498. package/dist/knowledge/references/saas.website.label-keys.format.md +3 -2
  499. package/dist/knowledge/references/saas.website.label-pack.validator.md +3 -1
  500. package/dist/knowledge/references/service-method.config.md +35 -2
  501. package/dist/knowledge/references/vision.constraint.config.md +4 -2
  502. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +60 -0
  503. package/dist/knowledge/references/zod.decorators.data-categories.md +46 -46
  504. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +24 -0
  505. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +11 -0
  506. package/dist/knowledge/references/zod.decorators.file-schema.md +4 -3
  507. package/dist/knowledge/references/zod.decorators.rag-source.md +20 -20
  508. package/dist/knowledge/references/zod.decorators.schema-metadata.md +2 -0
  509. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +30 -24
  510. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +63 -0
  511. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +63 -0
  512. package/dist/knowledge/references/zod.factories.bigdecimal.md +4 -4
  513. package/dist/knowledge/references/zod.factories.code.md +4 -4
  514. package/dist/knowledge/references/zod.factories.duration.md +4 -4
  515. package/dist/knowledge/references/zod.factories.money.md +4 -4
  516. package/dist/knowledge/references/zod.factories.phone.md +4 -4
  517. package/dist/knowledge/references/zod.factories.year-month.md +79 -0
  518. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  519. package/dist/knowledge/registries/framework-topics.json +455 -2
  520. package/dist/knowledge/registries/playbooks.json +51 -39
  521. package/dist/knowledge/registries/source-tags.json +2505 -1627
  522. package/dist/knowledge/rules/database-migration-obligation.md +6 -7
  523. package/dist/knowledge/rules/live-context-door.md +1 -1
  524. package/dist/knowledge/skills/INDEX.md +3 -1
  525. package/dist/knowledge/skills/agent-work-review/references/framework-actor-execution-continuation-api.md +24 -0
  526. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +1 -1
  527. package/dist/knowledge/skills/agent-work-review/references/framework-human-input-form-api.md +47 -12
  528. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +30 -19
  529. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/framework-documentation-chapters-api.md +48 -13
  530. package/dist/knowledge/skills/application-consumer-documentation-authoring/references/source-and-ownership-routing.md +2 -2
  531. package/dist/knowledge/skills/application-database-migrations/SKILL.md +10 -11
  532. package/dist/knowledge/skills/application-database-migrations/references/postgresql-supported-surfaces.md +64 -0
  533. package/dist/knowledge/skills/application-database-migrations/references/postgresql-vs-mongodb-obligations.md +13 -11
  534. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +28 -3
  535. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +18 -1
  536. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +22 -1
  537. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +46 -2
  538. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-assigned-rows-declaration-api.md +5 -3
  539. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-organization-identity-declaration-api.md +247 -0
  540. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-own-rows-declaration-api.md +12 -5
  541. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
  542. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +31 -2
  543. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +51 -14
  544. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +4 -1
  545. package/dist/knowledge/skills/backend-custom-operation/references/declared-refusal-codes.md +95 -0
  546. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +2 -2
  547. package/dist/knowledge/skills/backend-custom-operation/references/framework-core-write-precondition-api.md +73 -0
  548. package/dist/knowledge/skills/backend-custom-operation/references/framework-error-handling-api.md +5 -0
  549. package/dist/knowledge/skills/backend-custom-operation/references/framework-external-effect-reservation-api.md +276 -0
  550. package/dist/knowledge/skills/backend-custom-operation/references/framework-hook-transaction-posture-api.md +90 -0
  551. package/dist/knowledge/skills/blueprint-authoring/SKILL.md +4 -2
  552. package/dist/knowledge/skills/brand-name-screening/SKILL.md +13 -2
  553. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +30 -3
  554. package/dist/knowledge/skills/chat-agent-conversations/SKILL.md +3 -0
  555. package/dist/knowledge/skills/chat-agent-conversations/references/framework-chat-conversations-api.md +13 -1
  556. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +45 -4
  557. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +17 -7
  558. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +859 -0
  559. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +6 -0
  560. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +2 -0
  561. package/dist/knowledge/skills/config-app-shell/SKILL.md +5 -1
  562. package/dist/knowledge/skills/config-app-shell/references/framework-command-menu-omnibox-api.md +3 -3
  563. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +4 -0
  564. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -1
  565. package/dist/knowledge/skills/config-design-system/references/framework-surface-policy-api.md +8 -7
  566. package/dist/knowledge/skills/config-design-system/references/framework-theme-composition-api.md +44 -1
  567. package/dist/knowledge/skills/config-navigation/SKILL.md +2 -0
  568. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +5 -0
  569. package/dist/knowledge/skills/config-navigation/references/one-entry-per-concept.md +101 -0
  570. package/dist/knowledge/skills/config-saas/SKILL.md +2 -2
  571. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +40 -3
  572. package/dist/knowledge/skills/config-saas/references/framework-auditable-event-catalog.md +20 -1
  573. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +75 -11
  574. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +21 -19
  575. package/dist/knowledge/skills/config-saas/references/framework-content-security-policy-api.md +26 -9
  576. package/dist/knowledge/skills/config-saas/references/framework-key-management-api.md +240 -9
  577. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +16 -2
  578. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +116 -16
  579. package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +20 -18
  580. package/dist/knowledge/skills/config-saas/references/saas-config-scope.md +1 -1
  581. package/dist/knowledge/skills/config-saas-backend/SKILL.md +11 -1
  582. package/dist/knowledge/skills/config-saas-backend/references/framework-backend-authored-config-api.md +5 -1
  583. package/dist/knowledge/skills/config-saas-backend/references/framework-declared-type-renames-api.md +261 -0
  584. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +20 -0
  585. package/dist/knowledge/skills/config-saas-backend/references/renaming-organization-and-user-types.md +69 -0
  586. package/dist/knowledge/skills/configure-billing/SKILL.md +6 -0
  587. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +28 -4
  588. package/dist/knowledge/skills/configure-billing/references/framework-backend-provider-reachability-api.md +2 -0
  589. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +4 -1
  590. package/dist/knowledge/skills/electronic-signature-deliverables/SKILL.md +131 -0
  591. package/dist/knowledge/skills/electronic-signature-deliverables/references/what-makes-a-request-signed.md +78 -0
  592. package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
  593. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +11 -8
  594. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +3 -2
  595. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +31 -9
  596. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-a2a-token-budget-api.md +11 -4
  597. package/dist/knowledge/skills/flows-actors-a2a-exposure/references/framework-flows-actors-a2a-contract.md +26 -3
  598. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +13 -3
  599. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +27 -0
  600. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +34 -11
  601. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +8 -5
  602. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-behavior-reports-api.md +13 -9
  603. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-content-guardrails-api.md +188 -10
  604. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-operation-record-api.md +7 -0
  605. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-agent-suspension-api.md +11 -9
  606. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +21 -0
  607. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +3 -3
  608. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-realtime-catalog.md +7 -1
  609. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +447 -8
  610. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +30 -1
  611. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-model-spend-limits-api.md +36 -15
  612. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +8 -0
  613. package/dist/knowledge/skills/flows-actors-declared-flow/SKILL.md +13 -3
  614. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-flow-model-api.md +21 -2
  615. package/dist/knowledge/skills/flows-actors-declared-flow/references/framework-start-flow-api.md +2 -1
  616. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +13 -3
  617. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-definition-api.md +33 -1
  618. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/references/framework-llm-agent-invocation-api.md +5 -3
  619. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -1
  620. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +6 -5
  621. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +50 -14
  622. package/dist/knowledge/skills/guidance-onboarding-authoring/references/framework-guidance-flow-api.md +1 -1
  623. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +39 -0
  624. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +39 -0
  625. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +31 -2
  626. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +39 -0
  627. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-translation-glossary-api.md +87 -0
  628. package/dist/knowledge/skills/inbound-channels/SKILL.md +31 -9
  629. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +16 -4
  630. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +169 -23
  631. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +38 -1
  632. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +43 -4
  633. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +15 -3
  634. package/dist/knowledge/skills/inbound-channels/references/sms-channel.md +93 -0
  635. package/dist/knowledge/skills/infra-environment-config/SKILL.md +149 -77
  636. package/dist/knowledge/skills/infra-environment-config/references/framework-agent-content-guardrails-environment-api.md +67 -0
  637. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +12 -14
  638. package/dist/knowledge/skills/infra-environment-config/references/framework-environment-deployment-api.md +133 -8
  639. package/dist/knowledge/skills/infra-environment-config/references/framework-infrastructure-host-api.md +1 -1
  640. package/dist/knowledge/skills/infra-environment-config/references/framework-platform-key-management-api.md +89 -10
  641. package/dist/knowledge/skills/layout-2d-adoption/references/framework-2d-layout-authoring-api.md +1 -1
  642. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +16 -0
  643. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +72 -0
  644. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +2 -2
  645. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +12 -9
  646. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +3 -3
  647. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +2 -2
  648. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +18 -10
  649. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +7 -7
  650. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +24 -2
  651. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +33 -2
  652. package/dist/knowledge/skills/market-generation-cli/SKILL.md +47 -6
  653. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +61 -8
  654. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +3 -1
  655. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +1 -1
  656. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +107 -42
  657. package/dist/knowledge/skills/module-companion-exports/SKILL.md +1 -0
  658. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +21 -2
  659. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +30 -1
  660. package/dist/knowledge/skills/module-relationships/SKILL.md +92 -91
  661. package/dist/knowledge/skills/organization-relationships/references/framework-organization-relationships-api.md +31 -5
  662. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-grantor-authentication-api.md +2 -2
  663. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-kinds-api.md +34 -0
  664. package/dist/knowledge/skills/organization-relationships/references/framework-relationship-record-separation-api.md +1 -0
  665. package/dist/knowledge/skills/organization-relationships/references/framework-representative-activity-api.md +4 -0
  666. package/dist/knowledge/skills/professional-qualifications/references/framework-operation-approval-requirement-api.md +31 -0
  667. package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -15
  668. package/dist/knowledge/skills/provider-backend-package/references/framework-optional-runtime-peers.md +4 -5
  669. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-compliance-state-collector-api.md +96 -0
  670. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-configuration-check-api.md +130 -0
  671. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +8 -1
  672. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-inbound-endpoint-api.md +124 -3
  673. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +165 -0
  674. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-loader-api.md +6 -0
  675. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-processing-region-api.md +340 -0
  676. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +11 -6
  677. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +2 -0
  678. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +5 -2
  679. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +1 -1
  680. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +17 -3
  681. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +1035 -19
  682. package/dist/knowledge/skills/resource-add-field/SKILL.md +7 -0
  683. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +322 -15
  684. package/dist/knowledge/skills/resource-add-resource/SKILL.md +9 -5
  685. package/dist/knowledge/skills/resource-add-resource/references/framework-engine-api-reference-categories-api.md +119 -0
  686. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +107 -42
  687. package/dist/knowledge/skills/resource-chat-commands/SKILL.md +2 -1
  688. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +71 -5
  689. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +2 -2
  690. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-approval-api.md +48 -0
  691. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +34 -7
  692. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-bulk-api.md +15 -11
  693. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-idempotency-key-api.md +66 -27
  694. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +140 -58
  695. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +28 -2
  696. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +34 -10
  697. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-operation-scope-enums-api.md +5 -4
  698. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +158 -138
  699. package/dist/knowledge/skills/resource-config-wiring/references/framework-scope-admissions-api.md +52 -0
  700. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +205 -19
  701. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +253 -25
  702. package/dist/knowledge/skills/resource-custom-view/SKILL.md +126 -1
  703. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +259 -15
  704. package/dist/knowledge/skills/resource-custom-view/references/framework-backend-refusal-api.md +110 -0
  705. package/dist/knowledge/skills/resource-external-data/SKILL.md +46 -12
  706. package/dist/knowledge/skills/resource-external-data/references/bidirectional-pipelines.md +1 -1
  707. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +15 -8
  708. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +19 -8
  709. package/dist/knowledge/skills/resource-external-data/references/framework-system-of-record-capabilities-api.md +3 -1
  710. package/dist/knowledge/skills/resource-external-data/references/local-test-doubles.md +121 -0
  711. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +1 -1
  712. package/dist/knowledge/skills/resource-external-data/references/partition-from-the-domain-plan.md +230 -0
  713. package/dist/knowledge/skills/resource-external-data/references/presenting-a-copy-and-a-read-through.md +73 -0
  714. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +26 -5
  715. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +76 -6
  716. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +8 -0
  717. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +12 -9
  718. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +11 -2
  719. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-retrieval-api.md +29 -2
  720. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-rag-source-decorator-api.md +20 -20
  721. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +18 -2
  722. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +46 -2
  723. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +84 -1
  724. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +10 -0
  725. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +5 -3
  726. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +21 -0
  727. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +14 -2
  728. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +1 -1
  729. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +4 -1
  730. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +78 -17
  731. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +2 -0
  732. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +26 -0
  733. package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +46 -46
  734. package/dist/knowledge/skills/resource-schema-authoring/references/framework-schema-family-api.md +17 -2
  735. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +36 -24
  736. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +63 -0
  737. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +104 -23
  738. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +123 -0
  739. package/dist/knowledge/skills/resource-schema-authoring/references/shared-layer-decorator-checklist.md +1 -0
  740. package/dist/knowledge/skills/resource-schema-authoring/references/special-factories.md +72 -0
  741. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +42 -2
  742. package/dist/knowledge/skills/resource-status-lifecycle/references/framework-operation-condition-parameters-api.md +67 -0
  743. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +16 -12
  744. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +66 -3
  745. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +89 -10
  746. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +11 -0
  747. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +263 -17
  748. package/dist/knowledge/skills/resource-ui-behavior/references/framework-record-page-parts-api.md +155 -0
  749. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +83 -16
  750. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +44 -10
  751. package/dist/knowledge/skills/resource-ui-behavior/references/framework-section-stages-api.md +102 -0
  752. package/dist/knowledge/skills/resource-ui-behavior/references/record-page-anatomy.md +9 -2
  753. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +33 -2
  754. package/dist/knowledge/skills/resource-ui-behavior/references/visual-quality-rubric.md +19 -2
  755. package/dist/knowledge/skills/resource-ui-behavior/references/workflow-record-page.md +264 -0
  756. package/dist/knowledge/skills/seeding-authoring/SKILL.md +24 -4
  757. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +12 -0
  758. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +7 -6
  759. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +6 -0
  760. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +42 -0
  761. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +6 -9
  762. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +1 -0
  763. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +21 -2
  764. package/dist/knowledge/skills/spec-resource-update/SKILL.md +26 -0
  765. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +121 -75
  766. package/dist/knowledge/skills/spec-resource-update/references/workflow-record-page-specification.md +237 -0
  767. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +100 -71
  768. package/dist/knowledge/skills/subject-data-export/SKILL.md +176 -0
  769. package/dist/knowledge/skills/subject-data-export/references/file-content-exclusions.md +15 -0
  770. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-api.md +142 -0
  771. package/dist/knowledge/skills/subject-data-export/references/framework-subject-export-archive-api.md +33 -0
  772. package/dist/knowledge/skills/views-app-level/SKILL.md +3 -1
  773. package/dist/knowledge/skills/views-app-level/references/workflow-home.md +373 -0
  774. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +36 -5
  775. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +9 -5
  776. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +4 -0
  777. package/dist/knowledge/skills/views-composite-authoring/references/framework-chart-dashboard-api.md +371 -0
  778. package/dist/knowledge/skills/views-execution-authoring/references/framework-execution-view-contracts-api.md +40 -0
  779. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +8 -6
  780. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +70 -59
  781. package/dist/knowledge/skills/website-building-blocks/SKILL.md +1 -1
  782. package/dist/knowledge/skills/website-building-blocks/references/framework-website-demo-examples.md +3 -3
  783. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +4 -2
  784. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +3 -1
  785. package/dist/knowledge/skills/website-label-pack/SKILL.md +20 -5
  786. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +6 -3
  787. package/dist/knowledge/skills/website-section-comparison/SKILL.md +2 -2
  788. package/dist/knowledge/skills/website-section-contact/SKILL.md +1 -1
  789. package/dist/knowledge/skills/website-section-cta/SKILL.md +1 -1
  790. package/dist/knowledge/skills/website-section-faq/SKILL.md +1 -1
  791. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +1 -1
  792. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +1 -1
  793. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +1 -1
  794. package/dist/knowledge/skills/website-section-hero/SKILL.md +1 -1
  795. package/dist/knowledge/skills/website-section-how-it-works/SKILL.md +1 -1
  796. package/dist/knowledge/skills/website-section-integrations/SKILL.md +3 -3
  797. package/dist/knowledge/skills/website-section-latest-posts/SKILL.md +1 -1
  798. package/dist/knowledge/skills/website-section-pricing/SKILL.md +142 -98
  799. package/dist/knowledge/skills/website-section-pricing/examples/pricing-offers.example.md +178 -66
  800. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +3 -1
  801. package/dist/knowledge/skills/website-section-problem/SKILL.md +3 -3
  802. package/dist/knowledge/skills/website-section-product-showcase/SKILL.md +1 -1
  803. package/dist/knowledge/skills/website-section-roadmap/SKILL.md +4 -4
  804. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +1 -1
  805. package/dist/knowledge/skills/website-section-solution-paths/SKILL.md +2 -2
  806. package/dist/knowledge/skills/website-section-stats/SKILL.md +3 -3
  807. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +3 -2
  808. package/dist/knowledge/skills/worker-authoring/SKILL.md +4 -2
  809. package/dist/knowledge/topic-index.json +2422 -723
  810. package/dist/tsconfig.build.tsbuildinfo +1 -1
  811. package/package.json +6 -6
  812. package/dist/tsconfig.tsbuildinfo +0 -1
@@ -145,17 +145,21 @@ product, and `TASK_DECLARES_NO_PRODUCT` is the honest answer rather than a place
145
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 committed. The shape also decides the skill the task is built with |
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
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
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
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
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
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 |
159
163
 
160
164
  **A GOVERNED DOCUMENT is chosen from a closed list, never invented.** There are six,
161
165
  and a `documentRef` names one of them in exactly this form:
@@ -242,7 +246,7 @@ export enum BuildPlanTaskTargetKind {
242
246
  MODULE = 'MODULE',
243
247
  /** One build stage of one resource: schema → config → ui-behavior → spec. */
244
248
  RESOURCE_STAGE = 'RESOURCE_STAGE',
245
- /** 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. */
246
250
  RELATIONSHIP = 'RELATIONSHIP',
247
251
  /** A companion-owned deterministic generation step (labels, email templates, logo or database migrations) interleaved by the build loop, never a coding-agent run. */
248
252
  COMPANION_GENERATION_STEP = 'COMPANION_GENERATION_STEP',
@@ -339,6 +343,20 @@ export enum BuildPlanTaskTargetKind {
339
343
  * modelled roles as an access-role RESOURCE that nothing reads.
340
344
  */
341
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',
342
360
  }
343
361
 
344
362
  /**
@@ -420,6 +438,40 @@ export enum ProviderBindingScope {
420
438
  WEBSITE = 'WEBSITE',
421
439
  }
422
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
+
423
475
  /** The per-resource build stages, in their fixed order. */
424
476
  export enum BuildPlanResourceStage {
425
477
  SCHEMA = 'SCHEMA',
@@ -670,6 +722,49 @@ export enum BuildPlanTaskProductKind {
670
722
  * read from that package's build.
671
723
  */
672
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',
673
768
  }
674
769
 
675
770
  /**
@@ -911,10 +1006,63 @@ export const BuildPlanTaskProductSchema = z.discriminatedUnion('kind', [
911
1006
  /** The role conferred, by its key in the role table (`ORG_QUALIFIED_ACCOUNTANT`), a core role or the application's. */
912
1007
  roleRef: z.string().regex(APPLICATION_ROLE_NAME_PATTERN),
913
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
+ }),
914
1062
  z.strictObject({
915
1063
  kind: z.literal(BuildPlanTaskProductKind.INBOUND_CHANNEL_HANDLER).systemEnum('BuildPlanTaskProductKind'),
916
- /** The channel the handler serves — one the integration plan declared. Email is the only declarable channel. */
917
- 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'),
918
1066
  /** The handler's `ref`, exactly as `inboundHandlerRef()` will accept it. */
919
1067
  handlerRef: z.string().regex(INBOUND_HANDLER_REF_PATTERN),
920
1068
  }),
@@ -1019,6 +1167,17 @@ export function buildPlanTaskProductIdentities(product: BuildPlanTaskProduct): r
1019
1167
  return [`${product.kind}:${product.resourceRef}`];
1020
1168
  case BuildPlanTaskProductKind.RELATIONSHIP_CONFERRED_ROLE:
1021
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}`];
1022
1181
  default: {
1023
1182
  const unhandled: never = product;
1024
1183
  throw new Error(`Unhandled build-plan task product ${JSON.stringify(unhandled)}.`);
@@ -1095,6 +1254,28 @@ export const AI_USE_DECLARATION_SKILL_REF = 'ai-use-declaration';
1095
1254
  */
1096
1255
  export const AGENT_APPROVAL_GATE_SKILL_REF = 'flows-actors-chat-assistant';
1097
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
+
1098
1279
  /** The skill a work-unit task is built with (#2966): the `workUnit` declaration, model prices and the case passed to agent turns. */
1099
1280
  export const WORK_UNIT_SKILL_REF = 'model-cost-attribution';
1100
1281
 
@@ -1108,8 +1289,26 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
1108
1289
  }),
1109
1290
  z.strictObject({
1110
1291
  kind: z.literal(BuildPlanTaskTargetKind.RELATIONSHIP),
1292
+ /** The module whose `<module>.relationships.ts` the edges are written into: the task's write scope. */
1111
1293
  moduleRef: ModuleRefSchema,
1112
- 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),
1113
1312
  }),
1114
1313
  z.strictObject({
1115
1314
  kind: z.literal(BuildPlanTaskTargetKind.COMPANION_GENERATION_STEP),
@@ -1156,6 +1355,7 @@ export const BuildPlanTaskTargetSchema = z.discriminatedUnion('kind', [
1156
1355
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.PROVIDER_BINDING), providerRef: SlugSchema }),
1157
1356
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.BILLING_CATALOG) }),
1158
1357
  z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.APPLICATION_ROLES) }),
1358
+ z.strictObject({ kind: z.literal(BuildPlanTaskTargetKind.ORGANIZATION_MODEL) }),
1159
1359
  ]);
1160
1360
  export type BuildPlanTaskTarget = z.infer<typeof BuildPlanTaskTargetSchema>;
1161
1361
 
@@ -1510,17 +1710,38 @@ Rules:
1510
1710
  - **Carry the decision, not the config.** The task names the surface and points at
1511
1711
  the skill; which category a destination lands in and in what order is IN the plan,
1512
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.
1513
1721
  - **No placement plan? Emit nothing here and say so.** Do not invent placement — a
1514
1722
  guessed arrangement is exactly what the plan exists to replace, and it would be
1515
1723
  invisible to the reader who assumes a placement task came from a decision.
1516
1724
 
1517
1725
  ## Step 2 — Emit the relationship-wiring tasks
1518
1726
 
1519
- For each **relationship-draft**, emit one wiring task:
1727
+ Emit one wiring task per MODULE, for the relationship-drafts that module holds:
1520
1728
 
1521
1729
  | Task | Functional topic | Skill (the HOW) |
1522
1730
  |---|---|---|
1523
- | 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.
1524
1745
 
1525
1746
  Rules:
1526
1747
 
@@ -1566,11 +1787,19 @@ Default verbs (create, read, update, list, delete) are what Step 1 already gives
1566
1787
  Everything a requirement says the product DOES beyond them is work this step must emit.
1567
1788
 
1568
1789
  **Start with the domain plan's `lifecycles`.** Each declared transition is one `RESOURCE_OPERATION`
1569
- task on its resource (target `RESOURCE_STAGE` CONFIG, `operationRef` = the `transitionRef`), skill
1570
- `resource-status-lifecycle`, ordered after that resource's config task; its objective names the
1571
- states it moves between and who performs it. A transition with `createsResourceRef` adds a
1572
- `MODULE_BACKEND` task for the write that creates the target, skill `backend-custom-operation`,
1573
- 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
1574
1803
  enum with every declared state, the `initialState` as its default, and each transition's `stampsField`,
1575
1804
  all excluded from create and update: a transition is the only way to move them.
1576
1805
  For a resource with `lockedStates` or `finalStates`, the objective of each transition task that moves INTO
@@ -1578,15 +1807,57 @@ one of them also restricts the resource's UPDATE to the states that are neither
1578
1807
  that freeze as its own `update` operation task: the scaffold already writes `update`, so such a task reads
1579
1808
  as built before it runs.
1580
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
+
1581
1851
  Then read every functional requirement's acceptance criteria for verbs no lifecycle carries, and
1582
1852
  classify each:
1583
1853
 
1584
1854
  | The criterion says… | Emit | Skill |
1585
1855
  |---|---|---|
1586
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` |
1587
- | 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` |
1588
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` |
1589
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` |
1590
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` |
1591
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` |
1592
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` |
@@ -1678,8 +1949,10 @@ replaced — the judge reports it as a gap.
1678
1949
  - **`define_interaction_semantics`** — custom operations, lifecycle behaviour, access /
1679
1950
  role / scope rules, rate limits — interaction beyond the default resource verbs.
1680
1951
  Target `RESOURCE_STAGE` (CONFIG), product `RESOURCE_OPERATION`. Skills: the Backend and
1681
- Resources domains of the router (`backend-custom-operation`, `rate-limit-authoring`,
1682
- `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
1683
1956
  "Every requirement verb becomes a task" below before emitting anything else in this step.
1684
1957
  - **`shape_user_experience`** — the cross-resource UX, and you do NOT decide it here. The
1685
1958
  **experience plan** (`bottom_up.experience-plan`) already did: which surfaces exist, what
@@ -1701,6 +1974,22 @@ replaced — the judge reports it as a gap.
1701
1974
  `config-app-shell`, `layout-2d-adoption` for the shell layout; `views-app-level` for global views
1702
1975
  — derived at dispatch too). A shell layout task depends on the design-system task when both are
1703
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.
1704
1993
  When the plan decides a `home`, the `GLOBAL_VIEWS` task sets it: its objective says to make
1705
1994
  `homeDefinitionFactory` in `frontend/src/config/global-views.config.ts` return that home, carrying
1706
1995
  the home's rationale. A `VIEW` home is an application view: `{ compositeViewReference: <the view's
@@ -1710,6 +1999,17 @@ replaced — the judge reports it as a gap.
1710
1999
  `variantKey`: the root matches all of them exactly and silently shows the welcome page on a
1711
2000
  mismatch. That task depends on the resource's config task. Without the home the application opens
1712
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.
1713
2013
  - one task per planned MILESTONE, target `MODULE_BACKEND` on the milestone's module,
1714
2014
  product `APPLICATION_MILESTONE` naming its `milestoneRef`, skill
1715
2015
  `milestones-and-celebrations` (`EXPERIENCE_MILESTONE_SKILL_REF`). It depends on the config stage of its
@@ -1756,7 +2056,8 @@ replaced — the judge reports it as a gap.
1756
2056
  the foundation, one scenario per surface, so the task authors the BEHAVIOUR. With no
1757
2057
  integration plan, emit nothing here.
1758
2058
  - inbound channels → also decided by the **integration plan** (`inboundChannels`): work that
1759
- 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`).
1760
2061
  Emit one task per declared channel: target `MODULE_BACKEND` in the module whose records the
1761
2062
  messages concern, product `INBOUND_CHANNEL_HANDLER` with the channel and a `handlerRef`
1762
2063
  (`<moduleRef>.<purpose>`), skill `inbound-channels` (the dispatch adds it whatever you write,
@@ -1779,7 +2080,12 @@ replaced — the judge reports it as a gap.
1779
2080
  (the verb table above); `PERSONAL_DATA` and `AUDIT_TRAIL` → the declarations in the resource
1780
2081
  config tasks' objectives; `BILLING` → the billing catalogue task; `GUIDANCE` → the experience
1781
2082
  plan's guidance tasks; `GOVERNED_DOCUMENT` → no build task (the compliance lane composes it);
1782
- `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.
1783
2089
  Never emit a task that builds one of these as a resource.
1784
2090
  - **The application roles** — target `APPLICATION_ROLES`, when a requirement names groups of
1785
2091
  users with different access ("office and field staff", "technicians cannot see invoices",
@@ -1793,6 +2099,88 @@ replaced — the judge reports it as a gap.
1793
2099
  resource it narrows, and say in its objective which operations each role may call. Never answer a
1794
2100
  role requirement with a resource holding roles, permissions or role assignments: nothing in the
1795
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.
1796
2184
  - **The billing catalogue** — target `BILLING_CATALOG`, and the **business model** decided it:
1797
2185
  its pricing plans are the products the application sells. Emit ONE task (the catalogue is one
1798
2186
  file, so two tasks would write over each other) producing one `APPLICATION_BILLING_PRODUCT` per
@@ -1871,8 +2259,8 @@ replaced — the judge reports it as a gap.
1871
2259
 
1872
2260
  ## Posture constraints are work, not commentary
1873
2261
 
1874
- The vision family's compliance posture and constraints are INPUT on equal footing with the
1875
- 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
1876
2264
  terminal-access (cookie/telemetry) posture, an operational-vs-marketing email distinction — needs a
1877
2265
  task that lands it, serving the nfr it substantiates. Do not compress a posture into an adjective
1878
2266
  inside another task's objective ("GDPR-appropriate handling"): an adjective is not schedulable,
@@ -1927,10 +2315,13 @@ surfaces whose output they consume**:
1927
2315
 
1928
2316
  - **`database-migrations`** — `wildo db generate`: turns the drift the schema stages created into a
1929
2317
  committed migration, and advances the accepted plan with it. **PostgreSQL-backed applications
1930
- ONLY** (`applicationDatabase: { engine: DatabaseEngine.POSTGRESQL }`); on MongoDB a collection
1931
- appears on first write and this step must not be authored at all — it REFUSES on an application
1932
- whose declared store is not PostgreSQL (or cannot be read), because generating there would author
1933
- 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:
1934
2325
  the step renders the whole model as the INITIAL migration and writes the baseline beside it, and
1935
2326
  the dispatch host derives that step itself when the plan omits it.
1936
2327
 
@@ -1970,6 +2361,21 @@ playbook's job — see the boundary below).
1970
2361
  already correct; carry them over as they are.
1971
2362
  - **Reuse existing task refs.** A task that already exists keeps its ref — never mint a
1972
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.
1973
2379
  - **Never orphan an ordering reference.** A task's prerequisite reference must name a
1974
2380
  task that is actually in the plan. If you remove or rename a task, follow it into
1975
2381
  every prerequisite reference.
@@ -2033,7 +2439,8 @@ One artifact for this journey:
2033
2439
  relationship-wiring tasks, the interaction / UX / extension / integration tasks (views,
2034
2440
  frontend configuration, components, PDF templates, workers, minions, provider bindings,
2035
2441
  website pages and sections, documentation chapters — each over its own target and
2036
- 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
2037
2444
  companion-generation steps — each carrying its target, **the artifacts it produces**,
2038
2445
  its one functional topic, its skill(s), and explicit `prerequisiteTaskRefs`.
2039
2446
 
@@ -2064,12 +2471,17 @@ what reaches you is this method, your declared inputs, and the brief's own secti
2064
2471
  (cardinality-to-FK-holder resolution, at dispatch time — named here, not performed).
2065
2472
  - `module-registration` — the cross-runtime module-registration
2066
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.
2067
2479
  - the skills CATALOG, which your brief carries as its own section — the skills router: consult it to bind each interaction /
2068
2480
  UX / extension / integration task to its real skill folder from the full catalog. Do
2069
2481
  not invent skill names; route through the index.
2070
2482
 
2071
2483
  ## Reviewer checklist — `build-plan-coherent`
2072
2484
 
2073
- 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:
2074
2486
 
2075
- 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.)