@wildo-ai/framework-knowledge 1.1.5 → 1.1.7

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 (837) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +14 -0
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +8 -0
  3. package/dist/claude-marketplace/plugins/wildo/agents/wildo-deriver.md +41 -0
  4. package/dist/claude-marketplace/plugins/wildo/hooks/hooks.json +18 -0
  5. package/dist/claude-marketplace/plugins/wildo/monitors/monitors.json +8 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +38 -0
  7. package/dist/{knowledge/skills/journey-run/references/framework-playbook-approval-policy.md → claude-marketplace/plugins/wildo/references/approval-and-failure-policy.md} +10 -8
  8. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +29 -0
  9. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +61 -0
  10. package/dist/{knowledge/skills/journey-run → claude-marketplace/plugins/wildo}/references/expert-personas-and-deliberations.md +8 -8
  11. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +67 -0
  12. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +43 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +70 -0
  14. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +38 -0
  15. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +23 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/next/SKILL.md +39 -0
  17. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +39 -0
  18. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +38 -0
  19. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +38 -0
  20. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +37 -0
  21. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  22. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  23. package/dist/esm/framework-knowledge.definitions.js +321 -11
  24. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +0 -3
  28. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +12 -2
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +33 -2
  32. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +8 -5
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +55 -10
  36. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +1 -6
  40. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  42. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
  43. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -6
  44. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  45. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts +1 -1
  46. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.d.ts.map +1 -1
  47. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js +0 -1
  48. package/dist/esm/playbooks/bottom_up.capability-composition/playbook.definition.js.map +1 -1
  49. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +2 -2
  50. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  51. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -4
  52. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  53. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts +10 -3
  54. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.d.ts.map +1 -1
  55. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js +7 -3
  56. package/dist/esm/playbooks/bottom_up.documentation-plan/playbook.definition.js.map +1 -1
  57. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  58. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +8 -3
  59. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +1 -1
  61. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  62. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +0 -1
  63. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +7 -3
  65. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  66. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +9 -4
  67. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  68. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts +3 -2
  69. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js +4 -3
  71. package/dist/esm/playbooks/bottom_up.integration-plan/playbook.definition.js.map +1 -1
  72. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts +1 -1
  73. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js +1 -3
  75. package/dist/esm/playbooks/bottom_up.maturity-reading/playbook.definition.js.map +1 -1
  76. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -1
  77. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +0 -1
  79. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  80. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +10 -3
  81. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  82. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +8 -3
  83. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  84. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts +12 -5
  85. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js +33 -5
  87. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.js.map +1 -1
  88. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts +1 -1
  89. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js +1 -1
  90. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts +59 -0
  92. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -0
  93. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js +72 -0
  94. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.js.map +1 -0
  95. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts +66 -0
  96. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -0
  97. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js +115 -0
  98. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.js.map +1 -0
  99. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  100. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +1 -1
  101. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts +50 -0
  103. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -0
  104. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js +54 -0
  105. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.js.map +1 -0
  106. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +1 -1
  107. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +1 -1
  108. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  109. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +1 -1
  110. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +1 -1
  111. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  112. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +1 -1
  113. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
  114. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +1 -1
  115. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +1 -1
  116. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  117. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +1 -1
  118. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +1 -1
  119. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +1 -1
  121. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +1 -1
  122. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -1
  123. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +1 -1
  124. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +1 -1
  125. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  126. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +1 -1
  127. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +1 -1
  128. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -1
  129. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +36 -17
  130. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  131. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +67 -17
  132. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  133. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +1 -1
  134. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +1 -1
  135. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts +45 -0
  137. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -0
  138. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js +46 -0
  139. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.js.map +1 -0
  140. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +1 -1
  141. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
  142. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +1 -1
  143. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
  144. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +1 -1
  145. package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
  146. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -1
  148. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  149. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +1 -1
  150. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +1 -1
  151. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  152. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +1 -1
  153. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +1 -1
  154. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  155. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +1 -1
  156. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +1 -1
  157. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  158. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +1 -1
  159. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +1 -1
  160. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  161. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +1 -1
  162. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  163. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -1
  164. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
  165. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +1 -1
  166. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  167. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -3
  168. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  169. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  170. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  171. package/dist/knowledge/manifest.json +8 -8
  172. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +0 -3
  173. package/dist/knowledge/playbooks/bottom_up.build/method.md +4 -2
  174. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +31 -7
  175. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  176. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  177. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +134 -26
  178. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +7 -4
  179. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +84 -29
  180. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -7
  181. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +12 -23
  182. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -7
  183. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +12 -14
  184. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -2
  185. package/dist/knowledge/playbooks/bottom_up.conception/method.md +20 -2
  186. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +15 -7
  187. package/dist/knowledge/playbooks/bottom_up.documentation-plan/method.md +8 -6
  188. package/dist/knowledge/playbooks/bottom_up.documentation-plan/playbook.json +11 -4
  189. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +2 -4
  190. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
  191. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +18 -2
  192. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +1 -2
  193. package/dist/knowledge/playbooks/bottom_up.foundation/method.md +2 -4
  194. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +8 -5
  195. package/dist/knowledge/playbooks/bottom_up.integration-plan/method.md +16 -2
  196. package/dist/knowledge/playbooks/bottom_up.integration-plan/playbook.json +3 -3
  197. package/dist/knowledge/playbooks/bottom_up.maturity-reading/playbook.json +1 -3
  198. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +1 -2
  199. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +8 -7
  200. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +11 -4
  201. package/dist/knowledge/playbooks/cross_cutting.application-creation/playbook.json +27 -5
  202. package/dist/knowledge/playbooks/cross_cutting.compliance/playbook.json +1 -4
  203. package/dist/knowledge/playbooks/cross_cutting.feature-development/method.md +42 -0
  204. package/dist/knowledge/playbooks/cross_cutting.feature-development/playbook.json +73 -0
  205. package/dist/knowledge/playbooks/cross_cutting.refinement/method.md +46 -0
  206. package/dist/knowledge/playbooks/cross_cutting.refinement/playbook.json +108 -0
  207. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +112 -21
  208. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  209. package/dist/knowledge/playbooks/refinement.document-facts/method.md +7 -2
  210. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +2 -4
  211. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +48 -0
  212. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +66 -0
  213. package/dist/knowledge/playbooks/refinement.governance-document-candidate/method.md +6 -0
  214. package/dist/knowledge/playbooks/refinement.governance-document-candidate/playbook.json +1 -1
  215. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +0 -4
  216. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +1 -2
  217. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +1 -3
  218. package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -4
  219. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -2
  220. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +1 -3
  221. package/dist/knowledge/playbooks/top_down.compliance-conception/method.md +5 -3
  222. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +2 -4
  223. package/dist/knowledge/playbooks/top_down.compliance-evidence-adequacy/playbook.json +1 -3
  224. package/dist/knowledge/playbooks/top_down.compliance-posture/method.md +0 -4
  225. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +2 -4
  226. package/dist/knowledge/playbooks/top_down.compliance-research/playbook.json +1 -3
  227. package/dist/knowledge/playbooks/top_down.definition/method.md +7 -4
  228. package/dist/knowledge/playbooks/top_down.definition/playbook.json +52 -7
  229. package/dist/knowledge/playbooks/top_down.expert-personas/method.md +1 -1
  230. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +2 -4
  231. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +72 -0
  232. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +57 -0
  233. package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +0 -1
  234. package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -1
  235. package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -1
  236. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +2 -4
  237. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +1 -2
  238. package/dist/knowledge/playbooks/top_down.phase-gate/method.md +1 -1
  239. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
  240. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +17 -1
  241. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +2 -5
  242. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +1 -3
  243. package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +15 -7
  244. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +2 -4
  245. package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -4
  246. package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +1 -2
  247. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +7 -3
  248. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +12 -5
  249. package/dist/knowledge/references/backend.inbound-channels.handler-definition.md +212 -0
  250. package/dist/knowledge/references/backend.inbound-handlers.agents.md +45 -0
  251. package/dist/knowledge/references/backend.inbound-handlers.definition.md +218 -0
  252. package/dist/knowledge/references/build-plan.task-graph.config.md +71 -6
  253. package/dist/knowledge/references/capability-composition.config.md +20 -1
  254. package/dist/knowledge/references/cli.market.generate-command.md +18 -2
  255. package/dist/knowledge/references/engine.client-bundle.allow-list.md +7 -22
  256. package/dist/knowledge/references/engine.saas-technical-doc.provider-component.slot.md +83 -0
  257. package/dist/knowledge/references/example.authorization.service-provider-organization-wide-access.md +12 -0
  258. package/dist/knowledge/references/example.backend.addon-wiring.module.md +5 -0
  259. package/dist/knowledge/references/example.backend.custom-operation.create-postfix.md +7 -3
  260. package/dist/knowledge/references/example.config.app-shell.command-menu-items.md +7 -0
  261. package/dist/knowledge/references/example.config.app-shell.full.md +11 -0
  262. package/dist/knowledge/references/example.config.backend.billing-enable.md +14 -0
  263. package/dist/knowledge/references/example.config.backend.inbound-email.md +14 -0
  264. package/dist/knowledge/references/example.config.backend.required-floors.md +7 -0
  265. package/dist/knowledge/references/example.config.navigation.full.md +45 -2
  266. package/dist/knowledge/references/example.config.provider-usage-pricing.md +36 -0
  267. package/dist/knowledge/references/example.config.provider.backend-scope-billing.md +5 -3
  268. package/dist/knowledge/references/example.config.provider.backend-scope-inbound-email.md +16 -0
  269. package/dist/knowledge/references/example.flows-actors.autonomous-agent.md +23 -0
  270. package/dist/knowledge/references/example.flows-actors.autonomous-agent.reviewed-write.md +36 -0
  271. package/dist/knowledge/references/example.flows-actors.chat-assistant.md +26 -3
  272. package/dist/knowledge/references/example.flows-actors.llm-agent-one-shot.md +1 -1
  273. package/dist/knowledge/references/example.inbound.application-endpoint-handler.md +72 -0
  274. package/dist/knowledge/references/example.inbound.email-channel-handler.md +47 -0
  275. package/dist/knowledge/references/example.inbound.email-to-todo.md +150 -0
  276. package/dist/knowledge/references/example.infra.environment-config.local.md +14 -30
  277. package/dist/knowledge/references/example.layout-3d.own-layout.md +16 -0
  278. package/dist/knowledge/references/example.layout-3d.registration.md +15 -0
  279. package/dist/knowledge/references/example.module.companion-exports.full.md +8 -13
  280. package/dist/knowledge/references/example.module.relationships.discriminator.md +2 -2
  281. package/dist/knowledge/references/example.organizations.serves-as-provider.md +12 -0
  282. package/dist/knowledge/references/example.provider.address-lookup.adapter.md +64 -0
  283. package/dist/knowledge/references/example.provider.backend-module-shape.md +3 -0
  284. package/dist/knowledge/references/example.provider.frontend-app.module.md +9 -0
  285. package/dist/knowledge/references/example.provider.frontend-facet.package-module.md +85 -0
  286. package/dist/knowledge/references/example.provider.frontend-file-picker.contribution.md +14 -13
  287. package/dist/knowledge/references/example.provider.frontend-file-picker.module.md +18 -0
  288. package/dist/knowledge/references/example.provider.operation.backend-typed-client.md +11 -11
  289. package/dist/knowledge/references/example.rate-limit.resource-operation-surface.md +5 -0
  290. package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +2 -0
  291. package/dist/knowledge/references/example.resource.retention-binding.closure-event.md +21 -0
  292. package/dist/knowledge/references/example.resource.ui-behavior.enum-badge.md +1 -2
  293. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +24 -6
  294. package/dist/knowledge/references/example.resource.ui-behavior.surface-decision.md +36 -25
  295. package/dist/knowledge/references/example.resource.work-unit.declaration.md +13 -0
  296. package/dist/knowledge/references/example.spec.composite-view.workspace.md +0 -12
  297. package/dist/knowledge/references/example.views.app-level.composite-views-config.md +1 -1
  298. package/dist/knowledge/references/example.views.chart-view.resource-owned.md +27 -0
  299. package/dist/knowledge/references/example.views.composite-view.workspace.md +4 -1
  300. package/dist/knowledge/references/example.website.page.manifest.md +30 -0
  301. package/dist/knowledge/references/experience-plan.config.md +11 -4
  302. package/dist/knowledge/references/external-connectors.app.frontend-provider-module.md +20 -0
  303. package/dist/knowledge/references/external-connectors.backend.provider-augmentation.md +75 -0
  304. package/dist/knowledge/references/external-connectors.frontend-provider-component-declaration.md +85 -0
  305. package/dist/knowledge/references/external-connectors.frontend-provider-consent-classification.md +52 -0
  306. package/dist/knowledge/references/external-connectors.models.connection-rate-budgets.md +113 -0
  307. package/dist/knowledge/references/external-connectors.models.file-storage-adapter.md +165 -0
  308. package/dist/knowledge/references/external-connectors.models.oauth2-audiences.md +133 -0
  309. package/dist/knowledge/references/external-connectors.models.oauth2-incremental-consent.md +44 -0
  310. package/dist/knowledge/references/external-connectors.models.rest-operation-contract.md +21 -0
  311. package/dist/knowledge/references/external-connectors.provider-component-load-state.md +45 -0
  312. package/dist/knowledge/references/external-connectors.provider-component-loader-contribution.md +32 -0
  313. package/dist/knowledge/references/external-connectors.provider-component-registry.md +190 -0
  314. package/dist/knowledge/references/external-connectors.techdoc.frontend-provider-module.md +91 -0
  315. package/dist/knowledge/references/external-connectors.website.frontend-provider-module.md +91 -0
  316. package/dist/knowledge/references/integration-plan.config.md +34 -2
  317. package/dist/knowledge/references/market.alternative.config.md +1 -1
  318. package/dist/knowledge/references/market.buying-journey.config.md +1 -1
  319. package/dist/knowledge/references/market.category.config.md +1 -1
  320. package/dist/knowledge/references/market.channel.config.md +1 -1
  321. package/dist/knowledge/references/market.feature-benefit.config.md +1 -1
  322. package/dist/knowledge/references/market.gain.config.md +1 -1
  323. package/dist/knowledge/references/market.icp.config.md +1 -1
  324. package/dist/knowledge/references/market.job.config.md +1 -1
  325. package/dist/knowledge/references/market.message-template.config.md +1 -1
  326. package/dist/knowledge/references/market.objection.config.md +1 -1
  327. package/dist/knowledge/references/market.pain.config.md +1 -1
  328. package/dist/knowledge/references/market.persona.config.md +1 -1
  329. package/dist/knowledge/references/market.positioning.config.md +1 -1
  330. package/dist/knowledge/references/market.proof.config.md +1 -1
  331. package/dist/knowledge/references/market.references.weighted-edges.md +7 -0
  332. package/dist/knowledge/references/market.tone-of-voice.config.md +1 -1
  333. package/dist/knowledge/references/market.trigger.config.md +1 -1
  334. package/dist/knowledge/references/placement-plan.config.md +7 -1
  335. package/dist/knowledge/references/platform.config.backing-services.md +15 -15
  336. package/dist/knowledge/references/platform.config.infra-provider-resolution.md +57 -57
  337. package/dist/knowledge/references/presets.3d.focal-plane-settings.md +45 -0
  338. package/dist/knowledge/references/presets.3d.frame-style-overrides.md +134 -0
  339. package/dist/knowledge/references/presets.3d.layout-contract.md +235 -0
  340. package/dist/knowledge/references/presets.3d.register-layout.md +100 -0
  341. package/dist/knowledge/references/presets.models.labelling.sections.md +5 -0
  342. package/dist/knowledge/references/presets.models.shell-region.md +47 -0
  343. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -0
  344. package/dist/knowledge/references/saas.backend.actor-execution-decision-record.md +41 -0
  345. package/dist/knowledge/references/saas.backend.application-initialization.assembly.md +1 -1
  346. package/dist/knowledge/references/saas.backend.authorization.role-ceiling.md +7 -6
  347. package/dist/knowledge/references/saas.backend.compliance.governed-documents-pdf-template.md +370 -0
  348. package/dist/knowledge/references/saas.backend.custom-operation.transactional-core.md +7 -0
  349. package/dist/knowledge/references/saas.backend.domain-module.md +93 -15
  350. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-declaration.md +66 -0
  351. package/dist/knowledge/references/saas.backend.flows-actors.autonomous-agent-schedule.md +31 -0
  352. package/dist/knowledge/references/saas.backend.flows-actors.function-tool.md +200 -0
  353. package/dist/knowledge/references/saas.backend.flows-actors.resource-write-tool.md +2 -0
  354. package/dist/knowledge/references/saas.backend.pdf-template.collection-definition.md +73 -0
  355. package/dist/knowledge/references/saas.backend.providers.connection-target-credential-resolution.md +33 -9
  356. package/dist/knowledge/references/saas.backend.submission-challenge.md +118 -0
  357. package/dist/knowledge/references/saas.backend.system-access-service.md +98 -0
  358. package/dist/knowledge/references/saas.backend.system-of-record-action-runner.md +73 -0
  359. package/dist/knowledge/references/saas.config.providers.augmentations.md +61 -0
  360. package/dist/knowledge/references/saas.config.providers.packages.md +59 -0
  361. package/dist/knowledge/references/saas.config.providers.shared-connections.md +84 -0
  362. package/dist/knowledge/references/saas.external-data.admin-endpoints.md +56 -2
  363. package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +2 -2
  364. package/dist/knowledge/references/saas.frontend.app-shell.building-blocks.md +253 -0
  365. package/dist/knowledge/references/saas.frontend.billing-context.md +25 -2
  366. package/dist/knowledge/references/saas.frontend.chart-view.resource-chart-data.md +92 -0
  367. package/dist/knowledge/references/saas.frontend.consent-based-provider-activation.md +22 -0
  368. package/dist/knowledge/references/saas.frontend.form-field-address.lookup-slot.md +74 -0
  369. package/dist/knowledge/references/saas.frontend.linked-conversations-embed.md +60 -0
  370. package/dist/knowledge/references/saas.frontend.navigation.operation-override.md +7 -5
  371. package/dist/knowledge/references/saas.frontend.notifications.publish-badge-count.md +60 -0
  372. package/dist/knowledge/references/saas.frontend.providers.execute-operation.md +17 -2
  373. package/dist/knowledge/references/saas.frontend.related-resource-embeds.md +49 -0
  374. package/dist/knowledge/references/saas.frontend.related-resource-sections.md +8 -1
  375. package/dist/knowledge/references/saas.frontend.resource-layout-templates.md +9 -0
  376. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +100 -5
  377. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +25 -1
  378. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +61 -0
  379. package/dist/knowledge/references/saas.market.generation-agent.md +0 -1
  380. package/dist/knowledge/references/saas.models.agent-work-capture-settings.md +34 -0
  381. package/dist/knowledge/references/saas.models.agent-work-decision-surface.md +45 -0
  382. package/dist/knowledge/references/saas.models.agent-work-decision-vocabulary.md +107 -0
  383. package/dist/knowledge/references/saas.models.agent-work-output-review.md +36 -0
  384. package/dist/knowledge/references/saas.models.agent-work-override-rate.md +50 -0
  385. package/dist/knowledge/references/saas.models.agent-work-review-config.md +24 -0
  386. package/dist/knowledge/references/saas.models.audit-trails.actor-attribution.md +97 -0
  387. package/dist/knowledge/references/saas.models.audit.trail-config.md +15 -9
  388. package/dist/knowledge/references/saas.models.auth.service-provider-client-authentication.md +169 -0
  389. package/dist/knowledge/references/saas.models.authorization.administrative-continuity-codes.md +8 -0
  390. package/dist/knowledge/references/saas.models.billing.catalog-vocabularies.md +54 -1
  391. package/dist/knowledge/references/saas.models.billing.referral-program.md +47 -0
  392. package/dist/knowledge/references/saas.models.config.organization-types.md +74 -0
  393. package/dist/knowledge/references/saas.models.config.tenant-teardown.md +31 -14
  394. package/dist/knowledge/references/saas.models.conversation-threads.md +242 -0
  395. package/dist/knowledge/references/saas.models.data-mode-read-list.md +4 -4
  396. package/dist/knowledge/references/saas.models.engine-capabilities.md +12 -0
  397. package/dist/knowledge/references/saas.models.engine-capabilities.required-provider-floor.md +5 -1
  398. package/dist/knowledge/references/saas.models.evaluation-dataset-export.md +39 -0
  399. package/dist/knowledge/references/saas.models.evaluation-export-authorization.md +38 -0
  400. package/dist/knowledge/references/saas.models.external-data-pipeline.md +667 -6
  401. package/dist/knowledge/references/saas.models.flows-actors.autonomous-agents-vocabulary.md +98 -0
  402. package/dist/knowledge/references/saas.models.flows-actors.human-decision-vocabulary.md +52 -0
  403. package/dist/knowledge/references/saas.models.flows-actors.review-calendar.md +42 -0
  404. package/dist/knowledge/references/saas.models.flows-actors.review-deadline-vocabulary.md +84 -0
  405. package/dist/knowledge/references/saas.models.flows-actors.review-deadlines-declaration.md +69 -0
  406. package/dist/knowledge/references/saas.models.frontend-provider-public-config-contract.md +72 -0
  407. package/dist/knowledge/references/saas.models.http-api-binding.md +812 -29
  408. package/dist/knowledge/references/saas.models.http-api-binding.rest-write-operations.md +81 -0
  409. package/dist/knowledge/references/saas.models.human-decision-review-marker.md +20 -0
  410. package/dist/knowledge/references/saas.models.inbound-channels.md +277 -0
  411. package/dist/knowledge/references/saas.models.inbound-email-domains.md +101 -0
  412. package/dist/knowledge/references/saas.models.inbound-email.md +111 -0
  413. package/dist/knowledge/references/saas.models.model-cost-accounting-config.md +28 -0
  414. package/dist/knowledge/references/saas.models.model-cost-summary.md +87 -0
  415. package/dist/knowledge/references/saas.models.navigation.layout.md +11 -7
  416. package/dist/knowledge/references/saas.models.navigation.surface-vocabulary.md +32 -23
  417. package/dist/knowledge/references/saas.models.navigation.transition-vocabulary.md +8 -4
  418. package/dist/knowledge/references/saas.models.navigation.zone-declaration.md +22 -20
  419. package/dist/knowledge/references/saas.models.notifications.badge-vocabularies.md +14 -0
  420. package/dist/knowledge/references/saas.models.notifications.targets.md +20 -12
  421. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +61 -34
  422. package/dist/knowledge/references/saas.models.organization-unit-narrowing-containment.md +9 -0
  423. package/dist/knowledge/references/saas.models.organizations.service-provider-activity-feed.md +121 -0
  424. package/dist/knowledge/references/saas.models.organizations.service-provider-capability-grants.md +152 -0
  425. package/dist/knowledge/references/saas.models.organizations.service-provider-client-controls.md +49 -0
  426. package/dist/knowledge/references/saas.models.organizations.service-provider-relationships.md +567 -0
  427. package/dist/knowledge/references/saas.models.privacy.legal-holds.md +172 -0
  428. package/dist/knowledge/references/saas.models.privacy.provider-capability-disclosure.md +104 -0
  429. package/dist/knowledge/references/saas.models.privacy.retention-binding.md +103 -0
  430. package/dist/knowledge/references/saas.models.privacy.retention-enforcement-record.md +120 -0
  431. package/dist/knowledge/references/saas.models.privacy.retention-schedule.md +147 -0
  432. package/dist/knowledge/references/saas.models.privacy.statutory-retention-ground.md +50 -0
  433. package/dist/knowledge/references/saas.models.privacy.subject-data-recipients.md +388 -0
  434. package/dist/knowledge/references/saas.models.provider-address-lookup-contract.md +139 -0
  435. package/dist/knowledge/references/saas.models.provider-address-lookup-declaration.md +61 -0
  436. package/dist/knowledge/references/saas.models.provider-capabilities.md +34 -0
  437. package/dist/knowledge/references/saas.models.provider-credential-identity.md +67 -0
  438. package/dist/knowledge/references/saas.models.provider-usage-pricing-authority.md +139 -0
  439. package/dist/knowledge/references/saas.models.providers.browser-operation-policy.md +61 -0
  440. package/dist/knowledge/references/saas.models.providers.compliance-choice.md +98 -13
  441. package/dist/knowledge/references/saas.models.providers.scope-reauthorization.md +57 -0
  442. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +122 -28
  443. package/dist/knowledge/references/saas.models.resource-config.operation-submission-challenge.md +54 -0
  444. package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +6 -0
  445. package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +8 -0
  446. package/dist/knowledge/references/saas.models.resource-config.retention-policy.md +82 -0
  447. package/dist/knowledge/references/saas.models.system-of-record-actions.md +226 -0
  448. package/dist/knowledge/references/saas.models.system-of-record-error-codes.md +461 -0
  449. package/dist/knowledge/references/saas.models.systems-of-record.facet-augmentation.md +63 -0
  450. package/dist/knowledge/references/saas.models.systems-of-record.md +242 -7
  451. package/dist/knowledge/references/saas.models.work-attribution-vocabulary.md +109 -0
  452. package/dist/knowledge/references/saas.models.work-unit-ref.md +28 -0
  453. package/dist/knowledge/references/saas.public-runtime.contract.md +75 -7
  454. package/dist/knowledge/references/saas.specifications.assurance-document-blueprint.contract.md +20 -0
  455. package/dist/knowledge/references/saas.specifications.assurance-program.contract.md +106 -13
  456. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.catalog-spec-shared.md +14 -13
  457. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.discriminated-union.md +36 -14
  458. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-aggregate-offer.md +4 -3
  459. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-product.md +4 -4
  460. package/dist/knowledge/references/saas.specifications.catalogs.schema-org.entity-software-application.md +71 -0
  461. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +6 -4
  462. package/dist/knowledge/references/saas.specifications.compliance.retention-enforcement-state.md +32 -0
  463. package/dist/knowledge/references/saas.specifications.governed-document-release.contract.md +14 -2
  464. package/dist/knowledge/references/saas.specifications.processor-register.md +77 -0
  465. package/dist/knowledge/references/saas.specifications.recipient-disclosures.md +71 -0
  466. package/dist/knowledge/references/saas.specifications.recipient-population.md +549 -0
  467. package/dist/knowledge/references/saas.specifications.resource-operation-spec.md +112 -45
  468. package/dist/knowledge/references/saas.specifications.resource-spec-config.md +13 -1
  469. package/dist/knowledge/references/saas.specifications.resource-spec-factory.md +17 -0
  470. package/dist/knowledge/references/saas.specifications.resource-spec-frontend-prose.md +16 -0
  471. package/dist/knowledge/references/saas.specifications.subject-data-recipients.md +98 -0
  472. package/dist/knowledge/references/saas.website.astro.bridge.md +32 -9
  473. package/dist/knowledge/references/saas.website.astro.head-renderer.md +1 -1
  474. package/dist/knowledge/references/saas.website.astro.label-loader.md +7 -4
  475. package/dist/knowledge/references/saas.website.astro.robots-renderer.md +15 -15
  476. package/dist/knowledge/references/saas.website.astro.site-context.md +5 -2
  477. package/dist/knowledge/references/saas.website.blog.bridge.md +17 -4
  478. package/dist/knowledge/references/saas.website.config.pricing-catalog-loader.md +61 -0
  479. package/dist/knowledge/references/saas.website.config.site-context-loader.md +154 -0
  480. package/dist/knowledge/references/saas.website.consent.banner.md +10 -10
  481. package/dist/knowledge/references/saas.website.design-tokens.colors.md +7 -4
  482. package/dist/knowledge/references/saas.website.design-tokens.radius.md +1 -1
  483. package/dist/knowledge/references/saas.website.factories.define-section.md +3 -3
  484. package/dist/knowledge/references/saas.website.page-layout.component.md +5 -2
  485. package/dist/knowledge/references/saas.website.pricing-offer-structured-data.md +140 -0
  486. package/dist/knowledge/references/saas.website.provider-component.slot.md +99 -0
  487. package/dist/knowledge/references/saas.website.root-config.schema.md +6 -6
  488. package/dist/knowledge/references/saas.website.runtime.context.md +23 -4
  489. package/dist/knowledge/references/saas.website.sections.definition-schema.md +14 -7
  490. package/dist/knowledge/references/saas.website.seo.robots-config.md +4 -3
  491. package/dist/knowledge/references/saas.website.structured-data.payload-shape.md +7 -5
  492. package/dist/knowledge/references/saas.website.submission-challenge.md +77 -0
  493. package/dist/knowledge/references/saas.website.use-pricing-catalog.hook.md +36 -0
  494. package/dist/knowledge/references/saas.website.use-runtime.hook.md +3 -2
  495. package/dist/knowledge/references/website-plan.config.md +39 -6
  496. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +2 -1
  497. package/dist/knowledge/references/zod.decorators.display-edit-modes.md +21 -0
  498. package/dist/knowledge/references/zod.decorators.enums.frontend-handling.md +1 -2
  499. package/dist/knowledge/references/zod.decorators.file-schema.md +11 -10
  500. package/dist/knowledge/references/zod.decorators.file-vocabularies.md +7 -4
  501. package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +8 -2
  502. package/dist/knowledge/references/zod.decorators.shared-structural-params.md +5 -1
  503. package/dist/knowledge/references/zod.decorators.structural-lifecycle-params.md +5 -1
  504. package/dist/knowledge/references/zod.factories.address.md +7 -7
  505. package/dist/knowledge/references/zod.factories.code.md +2 -2
  506. package/dist/knowledge/references/zod.factories.duration.md +4 -4
  507. package/dist/knowledge/references/zod.factories.money.md +3 -3
  508. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  509. package/dist/knowledge/registries/framework-topics.json +1248 -54
  510. package/dist/knowledge/registries/playbooks.json +81 -109
  511. package/dist/knowledge/registries/source-tags.json +3201 -1118
  512. package/dist/knowledge/rules/live-context-door.md +29 -0
  513. package/dist/knowledge/skills/INDEX.md +27 -24
  514. package/dist/knowledge/skills/agent-work-review/SKILL.md +141 -0
  515. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-capture-settings-api.md +38 -0
  516. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-output-review-api.md +40 -0
  517. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-override-rate-api.md +54 -0
  518. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-config-api.md +28 -0
  519. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-review-marker-api.md +108 -0
  520. package/dist/knowledge/skills/agent-work-review/references/framework-agent-work-vocabulary-api.md +111 -0
  521. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-dataset-export-api.md +43 -0
  522. package/dist/knowledge/skills/agent-work-review/references/framework-evaluation-export-authorization-api.md +42 -0
  523. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +31 -0
  524. package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -0
  525. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +1 -0
  526. package/dist/knowledge/skills/authorization-unit-narrowing/references/framework-unit-narrowing-declaration-api.md +9 -0
  527. package/dist/knowledge/skills/backend-addon-wiring/SKILL.md +6 -0
  528. package/dist/knowledge/skills/backend-addon-wiring/references/framework-backend-bootstrap-api.md +94 -16
  529. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +21 -8
  530. package/dist/knowledge/skills/backend-custom-operation/references/framework-transactional-core-api.md +7 -0
  531. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +13 -5
  532. package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +30 -6
  533. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +160 -32
  534. package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +20 -0
  535. package/dist/knowledge/skills/compliance-document-authoring/references/framework-governed-document-after-drafting.md +14 -2
  536. package/dist/knowledge/skills/compliance-document-authoring/references/framework-processor-register-authoring.md +88 -0
  537. package/dist/knowledge/skills/compliance-document-authoring/references/framework-provider-compliance-choice-api.md +112 -14
  538. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-disclosures.md +209 -0
  539. package/dist/knowledge/skills/compliance-document-authoring/references/framework-recipient-population.md +577 -0
  540. package/dist/knowledge/skills/compliance-document-authoring/references/framework-subject-data-recipients.md +549 -0
  541. package/dist/knowledge/skills/config-app-shell/SKILL.md +21 -0
  542. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +2 -2
  543. package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-building-blocks-api.md +279 -0
  544. package/dist/knowledge/skills/config-app-shell/references/framework-shell-region-markers-api.md +66 -0
  545. package/dist/knowledge/skills/config-design-system/SKILL.md +1 -0
  546. package/dist/knowledge/skills/config-navigation/SKILL.md +114 -16
  547. package/dist/knowledge/skills/config-navigation/references/choosing-a-navigation-shape.md +314 -0
  548. package/dist/knowledge/skills/config-navigation/references/framework-navigation-layout-api.md +11 -7
  549. package/dist/knowledge/skills/config-navigation/references/framework-navigation-operation-override-api.md +29 -5
  550. package/dist/knowledge/skills/config-navigation/references/framework-navigation-vocabulary-api.md +40 -27
  551. package/dist/knowledge/skills/config-navigation/references/framework-navigation-zone-declaration-api.md +22 -20
  552. package/dist/knowledge/skills/config-navigation/references/how-navigation-resolves.md +112 -5
  553. package/dist/knowledge/skills/config-navigation/references/navigation-configuration-map.md +10 -10
  554. package/dist/knowledge/skills/config-navigation/references/navigation-zones.md +1 -1
  555. package/dist/knowledge/skills/config-saas/SKILL.md +3 -1
  556. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +7 -0
  557. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +21 -11
  558. package/dist/knowledge/skills/config-saas/references/framework-capability-resolution-api.md +5 -1
  559. package/dist/knowledge/skills/config-saas/references/framework-connection-target-credentials.md +59 -9
  560. package/dist/knowledge/skills/config-saas/references/framework-provider-capabilities-api.md +46 -0
  561. package/dist/knowledge/skills/config-saas/references/framework-systems-of-record-api.md +251 -12
  562. package/dist/knowledge/skills/config-saas-backend/SKILL.md +8 -0
  563. package/dist/knowledge/skills/config-saas-backend/references/framework-organization-types-api.md +81 -0
  564. package/dist/knowledge/skills/config-saas-backend/references/framework-tenant-teardown-api.md +37 -15
  565. package/dist/knowledge/skills/configure-billing/SKILL.md +64 -24
  566. package/dist/knowledge/skills/configure-billing/references/config-chain-and-failure-map.md +35 -2
  567. package/dist/knowledge/skills/configure-billing/references/example-backend-billing-enable-block.md +14 -0
  568. package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +3 -0
  569. package/dist/knowledge/skills/configure-billing/references/framework-billing-frontend-api.md +25 -2
  570. package/dist/knowledge/skills/configure-billing/references/framework-product-catalog-api.md +73 -1
  571. package/dist/knowledge/skills/configure-billing/references/framework-referral-program.md +110 -0
  572. package/dist/knowledge/skills/configure-billing/references/framework-subscription-behavior-policy.md +27 -12
  573. package/dist/knowledge/skills/configure-coding-agent/SKILL.md +11 -2
  574. package/dist/knowledge/skills/configure-coding-agent/references/agent-selection.md +26 -2
  575. package/dist/knowledge/skills/email-add-template/SKILL.md +61 -24
  576. package/dist/knowledge/skills/email-add-template/references/framework-email-attachments-and-limits.md +5 -2
  577. package/dist/knowledge/skills/email-definition-wiring/SKILL.md +1 -0
  578. package/dist/knowledge/skills/email-labels-authoring/SKILL.md +2 -1
  579. package/dist/knowledge/skills/email-template-authoring/SKILL.md +1 -0
  580. package/dist/knowledge/skills/engine-component-registration/SKILL.md +1 -0
  581. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +6 -0
  582. package/dist/knowledge/skills/flows-actors-a2a-exposure/SKILL.md +27 -3
  583. package/dist/knowledge/skills/flows-actors-autonomous-agents/SKILL.md +180 -0
  584. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/binding-and-review.md +56 -0
  585. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-autonomous-agent-api.md +208 -0
  586. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/framework-inbound-agents-api.md +51 -0
  587. package/dist/knowledge/skills/flows-actors-autonomous-agents/references/tool-posture.md +27 -0
  588. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +31 -4
  589. package/dist/knowledge/skills/flows-actors-chat-assistant/examples/todo-assistant.example.md +26 -3
  590. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-audit-agent-attribution-api.md +148 -0
  591. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-decision-deadlines-api.md +287 -0
  592. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-tool-api.md +202 -0
  593. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-flows-actors-view-api.md +93 -15
  594. package/dist/knowledge/skills/flows-actors-chat-assistant/references/framework-tool-dispatch-obligations-api.md +96 -11
  595. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +2 -1
  596. package/dist/knowledge/skills/frontend-cdn-publish/SKILL.md +1 -0
  597. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +1 -0
  598. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -2
  599. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +14 -9
  600. package/dist/knowledge/skills/guidance-onboarding-authoring/SKILL.md +1 -0
  601. package/dist/knowledge/skills/i18n-label-generation/SKILL.md +1 -0
  602. package/dist/knowledge/skills/i18n-label-generation/references/framework-labelling-sections-api.md +5 -0
  603. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +11 -9
  604. package/dist/knowledge/skills/i18n-rerun-pipeline/references/framework-labelling-sections-api.md +5 -0
  605. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +8 -1
  606. package/dist/knowledge/skills/i18n-translation-rerun/references/framework-labelling-sections-api.md +5 -0
  607. package/dist/knowledge/skills/i18n-translation-rerun/references/translation-workflow.md +5 -0
  608. package/dist/knowledge/skills/inbound-channels/SKILL.md +301 -0
  609. package/dist/knowledge/skills/inbound-channels/references/email-channel.md +133 -0
  610. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-channel-api.md +800 -0
  611. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-email-api.md +222 -0
  612. package/dist/knowledge/skills/inbound-channels/references/framework-inbound-handler-api.md +231 -0
  613. package/dist/knowledge/skills/inbound-channels/references/inbound-delivery-lifecycle.md +135 -0
  614. package/dist/knowledge/skills/inbound-channels/references/receiving-email.md +297 -0
  615. package/dist/knowledge/skills/infra-environment-config/SKILL.md +150 -44
  616. package/dist/knowledge/skills/infra-environment-config/references/framework-backing-services-api.md +83 -74
  617. package/dist/knowledge/skills/layout-3d-adoption/SKILL.md +180 -0
  618. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-focal-plane-settings-api.md +53 -0
  619. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-frame-style-overrides-api.md +141 -0
  620. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-contract-api.md +245 -0
  621. package/dist/knowledge/skills/layout-3d-adoption/references/framework-3d-layout-registration-api.md +108 -0
  622. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-building-blocks-api.md +259 -0
  623. package/dist/knowledge/skills/layout-3d-adoption/references/framework-shell-region-marker-api.md +52 -0
  624. package/dist/knowledge/skills/layout-3d-adoption/references/layouts-and-transitions.md +43 -0
  625. package/dist/knowledge/skills/layout-3d-adoption/references/manual-adoption-and-removal.md +25 -0
  626. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +32 -1
  627. package/dist/knowledge/skills/local-environment-bootstrap/references/local-environment-troubleshooting.md +2 -1
  628. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +36 -4
  629. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +2 -1
  630. package/dist/knowledge/skills/market-add-feature-benefit/references/framework-feature-benefit-api.md +1 -1
  631. package/dist/knowledge/skills/market-alternatives/SKILL.md +3 -2
  632. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +1 -0
  633. package/dist/knowledge/skills/market-authoring-overview/references/framework-market-references-api.md +7 -0
  634. package/dist/knowledge/skills/market-category/SKILL.md +2 -1
  635. package/dist/knowledge/skills/market-channels/SKILL.md +2 -1
  636. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +7 -4
  637. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +6 -4
  638. package/dist/knowledge/skills/market-generation-cli/SKILL.md +28 -13
  639. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +18 -3
  640. package/dist/knowledge/skills/market-icp/SKILL.md +2 -1
  641. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +4 -3
  642. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +2 -1
  643. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  644. package/dist/knowledge/skills/market-persona/SKILL.md +2 -1
  645. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +2 -1
  646. package/dist/knowledge/skills/market-positioning-authoring/references/framework-positioning-api.md +1 -1
  647. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +3 -2
  648. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +1 -0
  649. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -0
  650. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +2 -1
  651. package/dist/knowledge/skills/market-triggers-and-journey/SKILL.md +3 -2
  652. package/dist/knowledge/skills/milestones-and-celebrations/SKILL.md +1 -0
  653. package/dist/knowledge/skills/minion-authoring/SKILL.md +5 -1
  654. package/dist/knowledge/skills/model-cost-attribution/SKILL.md +143 -0
  655. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-pricing-api.md +211 -0
  656. package/dist/knowledge/skills/model-cost-attribution/references/framework-model-cost-summary-api.md +95 -0
  657. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-attribution-api.md +117 -0
  658. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +677 -0
  659. package/dist/knowledge/skills/module-companion-exports/SKILL.md +17 -16
  660. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +6 -4
  661. package/dist/knowledge/skills/module-registration/SKILL.md +2 -1
  662. package/dist/knowledge/skills/module-registration/references/framework-domain-modules-api.md +93 -15
  663. package/dist/knowledge/skills/module-registration/references/framework-notification-badges-api.md +86 -1
  664. package/dist/knowledge/skills/module-relationships/SKILL.md +3 -2
  665. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +34 -2
  666. package/dist/knowledge/skills/pdf-template-authoring/references/framework-pdf-collection-template-api.md +447 -0
  667. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +207 -0
  668. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-field-lookup-slot-api.md +82 -0
  669. package/dist/knowledge/skills/provider-address-lookup/references/framework-address-lookup-contract-api.md +214 -0
  670. package/dist/knowledge/skills/provider-address-lookup/references/framework-browser-operation-policy-api.md +143 -0
  671. package/dist/knowledge/skills/provider-address-lookup/references/google-places-setup.md +73 -0
  672. package/dist/knowledge/skills/provider-backend-package/SKILL.md +272 -33
  673. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-augmentation-api.md +227 -0
  674. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-credential-identity-api.md +101 -0
  675. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-file-storage-adapter-api.md +245 -0
  676. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-incremental-consent-api.md +88 -0
  677. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-package-allow-list-api.md +111 -0
  678. package/dist/knowledge/skills/provider-backend-package/references/framework-provider-shared-connection-api.md +309 -0
  679. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +132 -23
  680. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-consent-api.md +399 -0
  681. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-provider-module-api.md +29 -0
  682. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-frontend-public-config-api.md +115 -0
  683. package/dist/knowledge/skills/provider-frontend-file-picker/references/framework-provider-component-registry-api.md +386 -0
  684. package/dist/knowledge/skills/provider-frontend-module/SKILL.md +258 -0
  685. package/dist/knowledge/skills/provider-frontend-module/references/framework-frontend-facet-contracts-api.md +463 -0
  686. package/dist/knowledge/skills/provider-frontend-module/references/package-frontend-facets.md +61 -0
  687. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +75 -24
  688. package/dist/knowledge/skills/provider-operation-calls/references/browser-door-answers.md +3 -3
  689. package/dist/knowledge/skills/provider-operation-calls/references/framework-browser-operation-policy-api.md +61 -0
  690. package/dist/knowledge/skills/provider-operation-calls/references/framework-connection-rate-budgets-api.md +176 -0
  691. package/dist/knowledge/skills/provider-operation-calls/references/framework-frontend-execute-operation-api.md +17 -2
  692. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-operation-executor-api.md +15 -0
  693. package/dist/knowledge/skills/provider-operation-calls/references/framework-provider-scope-reauthorization-api.md +127 -0
  694. package/dist/knowledge/skills/provider-operation-calls/references/framework-rest-operation-contract-api.md +25 -0
  695. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +6 -0
  696. package/dist/knowledge/skills/resource-add-field/SKILL.md +1 -0
  697. package/dist/knowledge/skills/resource-add-field/examples/add-priority-field-to-todos.example.md +1 -2
  698. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +105 -6
  699. package/dist/knowledge/skills/resource-add-module/SKILL.md +1 -0
  700. package/dist/knowledge/skills/resource-add-module/references/framework-composition-scenarios-api.md +2 -1
  701. package/dist/knowledge/skills/resource-add-resource/SKILL.md +3 -0
  702. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +124 -30
  703. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +1 -0
  704. package/dist/knowledge/skills/resource-config-wiring/references/framework-administrative-continuity-codes-api.md +8 -0
  705. package/dist/knowledge/skills/resource-config-wiring/references/framework-authority-audit-interpretation.md +9 -0
  706. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +17 -1
  707. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +124 -30
  708. package/dist/knowledge/skills/resource-config-wiring/references/framework-role-ceiling-api.md +7 -6
  709. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +142 -34
  710. package/dist/knowledge/skills/resource-config-wiring/references/framework-system-access-reads-api.md +98 -0
  711. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +86 -52
  712. package/dist/knowledge/skills/resource-custom-view/SKILL.md +1 -0
  713. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +100 -5
  714. package/dist/knowledge/skills/resource-external-data/SKILL.md +1026 -28
  715. package/dist/knowledge/skills/resource-external-data/references/declared-expressions.md +144 -0
  716. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +68 -0
  717. package/dist/knowledge/skills/resource-external-data/references/facet-augmentations.md +154 -0
  718. package/dist/knowledge/skills/resource-external-data/references/framework-external-data-pipeline-api.md +686 -11
  719. package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +904 -31
  720. package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +166 -6
  721. package/dist/knowledge/skills/resource-external-data/references/incremental-extraction.md +152 -0
  722. package/dist/knowledge/skills/resource-external-data/references/odata-v2-sources.md +60 -0
  723. package/dist/knowledge/skills/resource-external-data/references/outbound-pipelines.md +179 -0
  724. package/dist/knowledge/skills/resource-external-data/references/pipeline-destination-schema.md +1 -1
  725. package/dist/knowledge/skills/resource-external-data/references/provenance-cue.md +63 -0
  726. package/dist/knowledge/skills/resource-external-data/references/rate-budgets-and-pacing.md +122 -0
  727. package/dist/knowledge/skills/resource-external-data/references/read-through-writes.md +745 -0
  728. package/dist/knowledge/skills/resource-external-data/references/remote-references.md +85 -0
  729. package/dist/knowledge/skills/resource-external-data/references/rest-keyset-sources.md +85 -0
  730. package/dist/knowledge/skills/resource-external-data/references/system-of-record-actions.md +442 -0
  731. package/dist/knowledge/skills/resource-mcp-tool-exposure/SKILL.md +1 -0
  732. package/dist/knowledge/skills/resource-rag-source-fields/SKILL.md +1 -0
  733. package/dist/knowledge/skills/resource-rag-source-fields/references/framework-embeddings-capability-api.md +12 -0
  734. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +186 -0
  735. package/dist/knowledge/skills/resource-retention-binding/references/framework-legal-holds-api.md +200 -0
  736. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-binding-api.md +111 -0
  737. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-enforcement-records-api.md +173 -0
  738. package/dist/knowledge/skills/resource-retention-binding/references/framework-retention-schedule-api.md +155 -0
  739. package/dist/knowledge/skills/resource-retention-binding/references/framework-statutory-retention-api.md +139 -0
  740. package/dist/knowledge/skills/resource-retention-binding/references/start-point-decisions.md +55 -0
  741. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +2 -2
  742. package/dist/knowledge/skills/resource-schema-authoring/examples/add-enum-field-with-ui.example.md +1 -2
  743. package/dist/knowledge/skills/resource-schema-authoring/references/field-type-selection.md +3 -1
  744. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +2 -1
  745. package/dist/knowledge/skills/resource-schema-authoring/references/framework-erasure-scrub-treatments-api.md +28 -0
  746. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-structural-params-api.md +5 -1
  747. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +34 -30
  748. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +5 -1
  749. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +101 -42
  750. package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +21 -0
  751. package/dist/knowledge/skills/resource-ui-behavior/references/framework-enum-frontend-handling-api.md +1 -2
  752. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +125 -6
  753. package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +8 -2
  754. package/dist/knowledge/skills/resource-ui-behavior/references/framework-related-resource-embeds-api.md +57 -1
  755. package/dist/knowledge/skills/resource-ui-behavior/references/framework-resource-layout-templates-api.md +61 -1
  756. package/dist/knowledge/skills/resource-ui-behavior/references/surface-decisions.md +110 -9
  757. package/dist/knowledge/skills/seeding-authoring/SKILL.md +1 -0
  758. package/dist/knowledge/skills/seeding-operations/SKILL.md +1 -0
  759. package/dist/knowledge/skills/service-provider-relationships/SKILL.md +455 -0
  760. package/dist/knowledge/skills/service-provider-relationships/references/framework-organization-types-api.md +270 -0
  761. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-activity-feed-api.md +129 -0
  762. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-capability-grants-api.md +161 -0
  763. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-client-authentication-api.md +224 -0
  764. package/dist/knowledge/skills/service-provider-relationships/references/framework-service-provider-relationships-api.md +576 -0
  765. package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +1 -0
  766. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +61 -0
  767. package/dist/knowledge/skills/spec-catalog-authoring/SKILL.md +43 -37
  768. package/dist/knowledge/skills/spec-catalog-authoring/references/catalog-spec-pattern-overview.md +15 -14
  769. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +14 -16
  770. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +6 -4
  771. package/dist/knowledge/skills/spec-component-update/SKILL.md +1 -0
  772. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +20 -21
  773. package/dist/knowledge/skills/spec-family-update/SKILL.md +1 -0
  774. package/dist/knowledge/skills/spec-feature-update/SKILL.md +1 -0
  775. package/dist/knowledge/skills/spec-resource-update/SKILL.md +13 -0
  776. package/dist/knowledge/skills/spec-resource-update/references/framework-spec-resource-contracts-api.md +158 -46
  777. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +1 -0
  778. package/dist/knowledge/skills/spec-update-after-change/references/framework-spec-factory-api.md +17 -0
  779. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +5 -1
  780. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +1 -0
  781. package/dist/knowledge/skills/views-app-level/SKILL.md +2 -1
  782. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +43 -1
  783. package/dist/knowledge/skills/views-chart-authoring/references/framework-resource-chart-data-api.md +102 -0
  784. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +5 -1
  785. package/dist/knowledge/skills/views-composite-authoring/references/composite-embedding-checklist.md +3 -2
  786. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -0
  787. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +29 -6
  788. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +3 -2
  789. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +17 -4
  790. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +23 -28
  791. package/dist/knowledge/skills/website-bundle-discipline/references/website-bundle-rules.md +7 -22
  792. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +167 -20
  793. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -3
  794. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +63 -6
  795. package/dist/knowledge/skills/website-inbound-contact-forms/references/framework-submission-challenge-api.md +275 -0
  796. package/dist/knowledge/skills/website-label-pack/SKILL.md +13 -5
  797. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -2
  798. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +11 -2
  799. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +2 -1
  800. package/dist/knowledge/skills/website-page-authoring/SKILL.md +117 -33
  801. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +164 -0
  802. package/dist/knowledge/skills/website-page-variants/SKILL.md +1 -0
  803. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +1 -0
  804. package/dist/knowledge/skills/website-section-contact/SKILL.md +65 -36
  805. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +19 -11
  806. package/dist/knowledge/skills/website-section-cta/SKILL.md +32 -22
  807. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +19 -11
  808. package/dist/knowledge/skills/website-section-faq/SKILL.md +99 -63
  809. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +19 -11
  810. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +27 -18
  811. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +19 -11
  812. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +33 -22
  813. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +19 -11
  814. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +31 -20
  815. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +19 -11
  816. package/dist/knowledge/skills/website-section-hero/SKILL.md +65 -44
  817. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +19 -11
  818. package/dist/knowledge/skills/website-section-pricing/SKILL.md +217 -200
  819. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +19 -11
  820. package/dist/knowledge/skills/website-section-pricing/references/framework-pricing-catalog-api.md +248 -0
  821. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +45 -34
  822. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +19 -11
  823. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +8 -3
  824. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +64 -34
  825. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +30 -25
  826. package/dist/knowledge/skills/worker-authoring/SKILL.md +1 -0
  827. package/dist/knowledge/topic-index.json +5957 -1729
  828. package/dist/tsconfig.build.tsbuildinfo +1 -1
  829. package/dist/tsconfig.tsbuildinfo +1 -1
  830. package/package.json +4 -4
  831. package/dist/knowledge/skills/journey-approve/SKILL.md +0 -63
  832. package/dist/knowledge/skills/journey-bootstrap-scope/SKILL.md +0 -77
  833. package/dist/knowledge/skills/journey-next/SKILL.md +0 -82
  834. package/dist/knowledge/skills/journey-report/SKILL.md +0 -56
  835. package/dist/knowledge/skills/journey-run/SKILL.md +0 -140
  836. package/dist/knowledge/skills/journey-status/SKILL.md +0 -60
  837. /package/dist/{knowledge/skills/journey-approve → claude-marketplace/plugins/wildo}/references/specification-family-map.md +0 -0
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "artifactVersion": "3",
3
- "frameworkVersion": "1.1.5",
4
- "generatorVersion": "1.1.5",
5
- "generatedAt": "2026-09-24T16:03:55.168Z",
3
+ "frameworkVersion": "1.1.7",
4
+ "generatorVersion": "1.1.7",
5
+ "generatedAt": "2026-09-30T15:35:32.423Z",
6
6
  "packageName": "@wildo-ai/framework-knowledge",
7
- "topicCount": 653,
8
- "referenceFileCount": 538,
7
+ "topicCount": 769,
8
+ "referenceFileCount": 651,
9
9
  "payload": {
10
10
  "topicIndexPath": "topic-index.json",
11
11
  "registriesDirectory": "registries",
@@ -21,19 +21,19 @@
21
21
  "registryName": "source-tags",
22
22
  "filePath": "registries/source-tags.json",
23
23
  "description": "Source-derived tag registry for extracted framework references.",
24
- "entryCount": 538
24
+ "entryCount": 651
25
25
  },
26
26
  {
27
27
  "registryName": "framework-topics",
28
28
  "filePath": "registries/framework-topics.json",
29
29
  "description": "Topic registry derived from extracted framework-knowledge tags.",
30
- "entryCount": 653
30
+ "entryCount": 769
31
31
  },
32
32
  {
33
33
  "registryName": "playbooks",
34
34
  "filePath": "registries/playbooks.json",
35
35
  "description": "Compiled meta-workflow playbooks (app-creation methodology definitions).",
36
- "entryCount": 40
36
+ "entryCount": 44
37
37
  },
38
38
  {
39
39
  "registryName": "assurance-authority-bases",
@@ -21,9 +21,6 @@
21
21
  "method": {
22
22
  "guidance": "# Assemble & verify — does the built application hold together?\n\nThis is the last bottom-up step. Everything before it AUTHORED the application; this one asks\nwhether what was authored is one working program.\n\n## What this playbook does\n\nIt runs a fixed set of deterministic checks against the application's workspace packages, outside\nany coding agent, and reports one outcome per check. It changes nothing.\n\nThe check set is host-owned, not authored here. A playbook names semantic check references; turning\none into an executable command is reviewed host work, which is why a new check cannot be introduced\nby editing this file.\n\n## What it verifies today, and what it does not\n\n**It verifies** that the application typechecks as a whole — `specifications`, `shared-lib`,\n`backend-api` and `frontend`. That is the question no earlier step answers: the dispatch lane\ntypechecks the one package a task mutated, so a build can consist entirely of green tasks and still\nnot compile as a program. Cross-package breakage is the characteristic failure of a build assembled\nfrom independent tasks, and this is where it surfaces.\n\n**It also verifies that the database schema plan is in sync** — that every resource the application\nmodels has a migration behind it. This is a different question from compilation, and no typecheck\ncan answer it: on a PostgreSQL-backed application a table is built by a MIGRATION and by nothing\nelse, so a resource whose migration was never generated compiles perfectly in all four packages and\nthen refuses to boot with `postgresql_table_schema_mismatch`. There is no type in the program that\nknows whether a table exists.\n\nThe check is safe on every application because it resolves three outcomes rather than two:\n\n- **no committed schema-plan lockfile** — read against the application's DECLARED store, because the\n absence means opposite things (#1144). A MongoDB application is permanently in this state and the\n check passes saying it verified nothing: a collection exists on first write. A PostgreSQL one has\n had no migration create its tables and cannot boot, so the check FAILS and names the initial\n `wildo db generate`. A store the check cannot read is \"we could not ask\", like the case below.\n- **no compiled `backend-api/dist`** — the plan is computed by importing the compiled registry, and\n a build that only ran `tsc --noEmit` never emitted one. Reported as an INFRASTRUCTURE error, never\n as drift: \"we could not ask\" is not \"the application has drifted\".\n- **both present** — `wildo db diff --check` decides, and its own message names the drifted tables\n and the command that fixes them.\n\nA failure here means a migration is owed. Generate it with `wildo db generate --name <what-changed>`,\nwhich writes the migration **and** advances the lockfile in one invocation; the\n`application-database-migrations` skill carries the full procedure and every refusal.\n\n**It does not** boot the application, run its test suite, validate its configuration, or regenerate\nOpenAPI and documentation. Each needs a running stack or a companion affordance that does not exist\nyet. They are absent rather than declared-and-skipped on purpose: the previous version of this\nplaybook declared all of them, ran none, and carried a long disclaimer saying so — a check that is\nannounced and not executed is worse than one that is missing, because a reader counts it.\n\n## Reading the result\n\nThree outcomes, and they mean different things:\n\n- **every check passed** — the application assembles. This is the signal the phase gate wants.\n- **a check failed** — the application does not assemble. The failure names the package; remediation\n is a refinement re-dispatch, not this playbook.\n- **an infrastructure error** — the check could not be RUN. This is reported separately and must not\n be read as a failure: \"the application does not typecheck\" and \"we could not run the typecheck\"\n lead you to entirely different places, and only the first is the application's fault.\n\nA dry run resolves the check set and executes nothing, so it tells you what would be verified\nwithout paying for it.\n\n## Quality gate\n\nThe gate is the check set itself, run by the host. There is no declared gate restating it — a second\ndescription of a live check is exactly what the retired `qualityGates` field was.\n\n## Acceptance\n\nThe creator reviews the reported outcomes. As everywhere in this lane, the run accepts nothing:\nacceptance is a later commit, and who makes it is the host's autonomy posture.\n",
23
23
  "skillRefs": [
24
- "journey-status",
25
- "journey-report",
26
- "journey-approve",
27
24
  "application-database-migrations"
28
25
  ],
29
26
  "skillBodyRefs": [],
@@ -47,8 +47,10 @@ between rounds unblocks its dependents without re-planning.
47
47
  ## Selecting the next child
48
48
 
49
49
  - **Decompose once.** Re-decompose only when the decomposer's gate says an input has
50
- moved since the plan landed, or when dispatch reports a task that cannot land — then
51
- in refine mode, keeping the refs of what has landed.
50
+ moved since the plan landed, when dispatch reports a task that cannot land, or when the
51
+ decomposer is offered again after its own judge found the plan does not cover the domain
52
+ plan (marked RE-OPENED in the round history) — then in refine mode, keeping the refs of
53
+ what has landed, and aimed at the criterion that faulted.
52
54
  - **Dispatch while tasks remain.** Each round's objective names the task the previous
53
55
  round dispatched and what it reported — the dispatch child returns that outcome, so
54
56
  read it rather than assuming. Once every task has landed, dispatch is no longer
@@ -32,13 +32,15 @@
32
32
  }
33
33
  ],
34
34
  "outputs": [],
35
- "stepOutputs": [],
35
+ "stepOutputs": [
36
+ {
37
+ "ref": "judge:bottom_up.build-decompose",
38
+ "condensation": "The decomposer verdict on the build plan: overall and per criterion, including conception-buildable."
39
+ }
40
+ ],
36
41
  "method": {
37
- "guidance": "# The Build Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that BUILD the application\nfrom its accepted conception — the build plan, the dispatch of its tasks, the assembly\ncheck — and it will end on the maturity reading: a stage against the requirements,\nnever a \"done\".\n\n## The children, and why the order is not written here\n\n- **`bottom_up.build-decompose`** — the build plan: an ordered task graph over the\n domain plan, the placement plan, the roadmap and the requirements, each task bound to\n an application skill and to what it produces. Its own gate makes it ineligible once\n the plan is fully landed and nothing upstream has moved.\n- **`bottom_up.build-dispatch`** — ONE ready task per run, routed by the task's target:\n a coding run in the workspace, or a companion-owned generation step (labels, logo,\n emails, seeds). Waits for the run, judges it, reports. Lands no family, so it is\n offered again every round — that is the loop.\n- **`bottom_up.build-scale`** — the same act as dispatch today: one ready task per run.\n It is meant to dispatch a WAVE of independent ready tasks at once, and that capability\n is not built yet. Prefer `bottom_up.build-dispatch`; choosing scale gains nothing until\n the wave exists, and its report lists the ready tasks it left behind rather than\n running them.\n- **`bottom_up.assemble-verify`** — does the built application assemble? The\n deterministic verification set over the application's packages and the migration\n drift probe.\n- **`bottom_up.maturity-reading`** — what the built application is WORTH against the\n requirements it was asked to satisfy: which are addressed, by what evidence, and the\n stage that puts it at. This is what the lane ends on. Assembly says the code compiles;\n the reading says what the application has become.\n\nNothing above is a sequence. The plan needs the conception; dispatch needs the plan;\nassembly needs the plan. Readiness is re-derived from git each round, so a task accepted\nbetween rounds unblocks its dependents without re-planning.\n\n## Selecting the next child\n\n- **Decompose once.** Re-decompose only when the decomposer's gate says an input has\n moved since the plan landed, or when dispatch reports a task that cannot land — then\n in refine mode, keeping the refs of what has landed.\n- **Dispatch while tasks remain.** Each round's objective names the task the previous\n round dispatched and what it reported — the dispatch child returns that outcome, so\n read it rather than assuming. Once every task has landed, dispatch is no longer\n offered at all and the remaining child is assemble-verify.\n- **One child per round.** Dispatch is single-flight — a coding run holds the workspace\n lock — and a second task in the same round is refused at admission.\n- **A parked question waits for the creator.** A coding run that parked on a question\n is answered on the creation surface; the task is re-dispatched when it is.\n\n## Composing an objective for a child\n\nFor dispatch: the task ref the previous round dispatched, its outcome, and what the\nnext ready task is expected to produce. For a refine decomposition: the task that could\nnot land and why. For assembly: nothing to compose — it runs the declared checks.\n\n## When to stop\n\nStop on the maturity reading. It is the decision this lane ends on, and it names a\nSTAGE rather than a completion — there is no \"done\" for an application, only a\nmeasurement against its requirements that moves every time a later run lands something. Stop when dispatch has reported a task\nthat cannot land twice, or a parked question waits on the creator, and say which. A\nfull build takes several runs of this lane; each resumes where readiness now stands.\n\n## What the creator reviews\n\nEach dispatched task's work in the application workspace, through `git status`, and\nthe assembly verdict. A task lands only when its product is committed — acceptance is\nthe commit, here as everywhere in the lane.\n",
38
- "skillRefs": [
39
- "journey-status",
40
- "journey-report"
41
- ],
42
+ "guidance": "# The Build Lane — the umbrella\n\n### Target Application Framing\n\nThis knowledge is for configuring behavior in the target application.\nWildo is the framework surface being used, not the product being built.\n\nRead and apply these patterns from the application-developer point of view:\n\n- how the application should configure the relevant app-level file\n- how the application should use framework-provided factories, enums, and helpers\n- how the application should avoid mixing frontend, backend, and infrastructure concerns\n\n\nThis playbook produces nothing itself. It drives the steps that BUILD the application\nfrom its accepted conception — the build plan, the dispatch of its tasks, the assembly\ncheck — and it will end on the maturity reading: a stage against the requirements,\nnever a \"done\".\n\n## The children, and why the order is not written here\n\n- **`bottom_up.build-decompose`** — the build plan: an ordered task graph over the\n domain plan, the placement plan, the roadmap and the requirements, each task bound to\n an application skill and to what it produces. Its own gate makes it ineligible once\n the plan is fully landed and nothing upstream has moved.\n- **`bottom_up.build-dispatch`** — ONE ready task per run, routed by the task's target:\n a coding run in the workspace, or a companion-owned generation step (labels, logo,\n emails, seeds). Waits for the run, judges it, reports. Lands no family, so it is\n offered again every round — that is the loop.\n- **`bottom_up.build-scale`** — the same act as dispatch today: one ready task per run.\n It is meant to dispatch a WAVE of independent ready tasks at once, and that capability\n is not built yet. Prefer `bottom_up.build-dispatch`; choosing scale gains nothing until\n the wave exists, and its report lists the ready tasks it left behind rather than\n running them.\n- **`bottom_up.assemble-verify`** — does the built application assemble? The\n deterministic verification set over the application's packages and the migration\n drift probe.\n- **`bottom_up.maturity-reading`** — what the built application is WORTH against the\n requirements it was asked to satisfy: which are addressed, by what evidence, and the\n stage that puts it at. This is what the lane ends on. Assembly says the code compiles;\n the reading says what the application has become.\n\nNothing above is a sequence. The plan needs the conception; dispatch needs the plan;\nassembly needs the plan. Readiness is re-derived from git each round, so a task accepted\nbetween rounds unblocks its dependents without re-planning.\n\n## Selecting the next child\n\n- **Decompose once.** Re-decompose only when the decomposer's gate says an input has\n moved since the plan landed, when dispatch reports a task that cannot land, or when the\n decomposer is offered again after its own judge found the plan does not cover the domain\n plan (marked RE-OPENED in the round history) — then in refine mode, keeping the refs of\n what has landed, and aimed at the criterion that faulted.\n- **Dispatch while tasks remain.** Each round's objective names the task the previous\n round dispatched and what it reported — the dispatch child returns that outcome, so\n read it rather than assuming. Once every task has landed, dispatch is no longer\n offered at all and the remaining child is assemble-verify.\n- **One child per round.** Dispatch is single-flight — a coding run holds the workspace\n lock — and a second task in the same round is refused at admission.\n- **A parked question waits for the creator.** A coding run that parked on a question\n is answered on the creation surface; the task is re-dispatched when it is.\n\n## Composing an objective for a child\n\nFor dispatch: the task ref the previous round dispatched, its outcome, and what the\nnext ready task is expected to produce. For a refine decomposition: the task that could\nnot land and why. For assembly: nothing to compose — it runs the declared checks.\n\n## When to stop\n\nStop on the maturity reading. It is the decision this lane ends on, and it names a\nSTAGE rather than a completion — there is no \"done\" for an application, only a\nmeasurement against its requirements that moves every time a later run lands something. Stop when dispatch has reported a task\nthat cannot land twice, or a parked question waits on the creator, and say which. A\nfull build takes several runs of this lane; each resumes where readiness now stands.\n\n## What the creator reviews\n\nEach dispatched task's work in the application workspace, through `git status`, and\nthe assembly verdict. A task lands only when its product is committed — acceptance is\nthe commit, here as everywhere in the lane.\n",
43
+ "skillRefs": [],
42
44
  "skillBodyRefs": [],
43
45
  "contextSources": [],
44
46
  "draftableDocumentDefinitionRefs": [],
@@ -53,7 +55,29 @@
53
55
  "maximumIterations": 20,
54
56
  "maximumLanesPerIteration": 1,
55
57
  "maximumDepth": 1,
56
- "maximumDurationMs": 21600000
58
+ "maximumDurationMs": 21600000,
59
+ "reopenOnVerdict": [
60
+ {
61
+ "whenVerdictOf": "bottom_up.build-decompose",
62
+ "criterionRef": "application-creation:criterion/build-plan-module-and-resource-coverage",
63
+ "verdicts": [
64
+ "GAP"
65
+ ],
66
+ "reopen": [
67
+ "bottom_up.build-decompose"
68
+ ]
69
+ },
70
+ {
71
+ "whenVerdictOf": "bottom_up.build-decompose",
72
+ "criterionRef": "application-creation:criterion/build-plan-relationship-coverage",
73
+ "verdicts": [
74
+ "GAP"
75
+ ],
76
+ "reopen": [
77
+ "bottom_up.build-decompose"
78
+ ]
79
+ }
80
+ ]
57
81
  },
58
82
  "suspendsForClarification": false,
59
83
  "briefAdequacyGate": false,
@@ -1 +1 @@
1
- {"aggregationPolicyRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1}],"instruction":"Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. Do NOT flag the absence of a seeds step: seed generation has no companion pipeline and must not be authored.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.","GAP":"A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or seeds), or a generation step declares products.","INDETERMINATE":"Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.","PASS":"Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1}],"instruction":"Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (single-flight locking, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.","GAP":"A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.","INDETERMINATE":"Task briefs are not in evidence.","PASS":"Every task describes WHAT it builds and none describes how it executes."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource"],"criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1}],"instruction":"Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), or a supporting resource's coverage is thin.","GAP":"A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).","INDETERMINATE":"The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.","PASS":"Every domain-plan resource has build tasks and every moduleRef resolves to a declared module."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1}],"instruction":"For each resource, determine whether its tasks respect the inner order schema -> config -> ui-behavior -> spec through their declared prerequisiteTaskRefs. A supporting resource may legitimately omit stages it does not need (a junction with schema and config and no ui-behavior is fine); only an out-of-order stage, or a main resource missing schema or config, is a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Stages are ordered but a prerequisite edge is carried by prose rather than by prerequisiteTaskRefs, or an omitted stage on a supporting resource is unexplained.","GAP":"A config task ordered before its resource's schema task, a spec task before its ui-behavior task, or a main resource with no schema or config stage.","INDETERMINATE":"Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.","PASS":"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config."}},{"assessesAspects":["build-plan.task","domain-plan.relationship"],"criterionRef":"application-creation:criterion/build-plan-relationship-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1}],"instruction":"Determine whether every relationship draft in the domain plan has a wiring task bound to the module-relationships skill, ordered after BOTH endpoint resources' schema tasks, and whether the wiring task is the single home of the relationship's foreign-key product.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every relationship is wired, but a wiring task's ordering relies on prose rather than declared prerequisites, or its cardinality intent is restated loosely.","GAP":"A relationship draft with no wiring task, a wiring task ordered before an endpoint's schema task, or a relationship whose foreign key is also claimed by a schema task.","INDETERMINATE":"The domain plan's relationship drafts are not in evidence.","PASS":"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1}],"instruction":"Determine whether every task names exactly one real functional topic and at least one skill from the app-knowledge skill catalog, and whether every task except a COMPANION_GENERATION_STEP declares at least one product that names something composition does not already write (the fields a schema gains, the verbs a config gains, both endpoints of a relationship, the declarations a config file gains, the jobs a worker gains — not a scaffolded file or a composed package). Every product must be of the kind that names its surface: a view is a RESOURCE_COMPOSITE_VIEW / RESOURCE_CUSTOM_VIEW / RESOURCE_CHART_VIEW / APPLICATION_VIEW, a page a WEBSITE_PAGE, a worker an APPLICATION_WORKER, a provider a PROVIDER_BINDING — a non-resource surface declared under a MODULE target with a resource-shaped product, or with no product at all, is a gap. No two tasks may claim the same artifact; two tasks enriching one resource with DIFFERENT fields is correct. A cross-resource foreign key declared on a schema task's products is a gap: the relationship task is its single home.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.","GAP":"An invented topic or dangling skill; a coding task with empty products; a product naming only a scaffolded artifact or a composed package; a non-resource surface (a view, a page, a worker, a provider, a config file) declared under a resource-shaped kind; two tasks claiming one artifact; or a foreign key attributed to a schema task.","INDETERMINATE":"The skill catalog or the task list is not in evidence, so bindings cannot be checked.","PASS":"Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"instruction":"Determine whether tasks respect the topic dependency edges: model_domain_graph before define_interaction_semantics; an app-level shape_user_experience task (views or navigation composing several 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; and a resource's spec task after the stages it documents. A resource's OWN ui-behavior depends only on its own schema and config and MAY precede cross-resource operations — that is not a violation.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The order is right but relies on band position rather than a declared prerequisite, or an MVP-first tie-break contradicts the roadmap's phasing.","GAP":"An app-level view composing resources or operations placed before they exist, an integration task before the resources it connects, a user-experience task before that resource's schema task, or a spec task before its ui-behavior stage.","INDETERMINATE":"Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.","PASS":"Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/build-plan-coherent","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.build-decompose"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
1
+ {"aggregationPolicyRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1}],"instruction":"Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. Do NOT flag the absence of a seeds step: seed generation has no companion pipeline and must not be authored.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.","GAP":"A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or seeds), or a generation step declares products.","INDETERMINATE":"Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.","PASS":"Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1}],"instruction":"Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (single-flight locking, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.","GAP":"A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.","INDETERMINATE":"Task briefs are not in evidence.","PASS":"Every task describes WHAT it builds and none describes how it executes."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource"],"criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1}],"instruction":"Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price).","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), or a supporting resource's coverage is thin.","GAP":"A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).","INDETERMINATE":"The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.","PASS":"Every domain-plan resource has build tasks and every moduleRef resolves to a declared module."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1}],"instruction":"For each resource, determine whether its tasks respect the inner order schema -> config -> ui-behavior -> spec through their declared prerequisiteTaskRefs. A supporting resource may legitimately omit stages it does not need (a junction with schema and config and no ui-behavior is fine); only an out-of-order stage, or a main resource missing schema or config, is a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Stages are ordered but a prerequisite edge is carried by prose rather than by prerequisiteTaskRefs, or an omitted stage on a supporting resource is unexplained.","GAP":"A config task ordered before its resource's schema task, a spec task before its ui-behavior task, or a main resource with no schema or config stage.","INDETERMINATE":"Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.","PASS":"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config."}},{"assessesAspects":["build-plan.task","domain-plan.relationship"],"criterionRef":"application-creation:criterion/build-plan-relationship-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1}],"instruction":"Determine whether every relationship draft in the domain plan has a wiring task bound to the module-relationships skill, ordered after BOTH endpoint resources' schema tasks, and whether the wiring task is the single home of the relationship's foreign-key product. A relationship whose source or target resource is declared by no module of the domain plan is NOT this criterion's finding: no task can wire it, so it is the conception's fault and `conception-buildable` judges it. Judge the relationships whose endpoints both exist.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every relationship is wired, but a wiring task's ordering relies on prose rather than declared prerequisites, or its cardinality intent is restated loosely.","GAP":"A relationship draft whose endpoints both exist with no wiring task, a wiring task ordered before an endpoint's schema task, or a relationship whose foreign key is also claimed by a schema task.","INDETERMINATE":"The domain plan's relationship drafts are not in evidence.","PASS":"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1}],"instruction":"Determine whether every task names exactly one real functional topic and at least one skill from the app-knowledge skill catalog, and whether every task except a COMPANION_GENERATION_STEP declares at least one product that names something composition does not already write (the fields a schema gains, the verbs a config gains, both endpoints of a relationship, the declarations a config file gains, the jobs a worker gains — not a scaffolded file or a composed package). Every product must be of the kind that names its surface: a view is a RESOURCE_COMPOSITE_VIEW / RESOURCE_CUSTOM_VIEW / RESOURCE_CHART_VIEW / APPLICATION_VIEW, a page a WEBSITE_PAGE, a worker an APPLICATION_WORKER, a provider a PROVIDER_BINDING — a non-resource surface declared under a MODULE target with a resource-shaped product, or with no product at all, is a gap. No two tasks may claim the same artifact; two tasks enriching one resource with DIFFERENT fields is correct. A cross-resource foreign key declared on a schema task's products is a gap: the relationship task is its single home.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.","GAP":"An invented topic or dangling skill; a coding task with empty products; a product naming only a scaffolded artifact or a composed package; a non-resource surface (a view, a page, a worker, a provider, a config file) declared under a resource-shaped kind; two tasks claiming one artifact; or a foreign key attributed to a schema task.","INDETERMINATE":"The skill catalog or the task list is not in evidence, so bindings cannot be checked.","PASS":"Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"instruction":"Determine whether tasks respect the topic dependency edges: model_domain_graph before define_interaction_semantics; an app-level shape_user_experience task (views or navigation composing several 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; and a resource's spec task after the stages it documents. A resource's OWN ui-behavior depends only on its own schema and config and MAY precede cross-resource operations — that is not a violation.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The order is right but relies on band position rather than a declared prerequisite, or an MVP-first tie-break contradicts the roadmap's phasing.","GAP":"An app-level view composing resources or operations placed before they exist, an integration task before the resources it connects, a user-experience task before that resource's schema task, or a spec task before its ui-behavior stage.","INDETERMINATE":"Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.","PASS":"Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource","domain-plan.relationship"],"criterionRef":"application-creation:criterion/conception-buildable","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"instruction":"Determine whether the CONCEPTION this plan rests on can be built as declared. This criterion faults the domain plan, the capability composition or the surface plans — never the build plan. It is a GAP when (a) the domain plan declares a module, resource or relationship that no build task target can express, however it is decomposed, or (b) the computed coherence report shows a dangling reference or an 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. A domain-plan element declared in an expressible shape that the build plan simply omits is NOT this criterion: that is module-and-resource coverage, the decomposer's own fault. Name the conception element in the rationale.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.","GAP":"The domain plan declares something no build target can express, or the coherence report shows a dangling reference or unrealised decision in the conception that the build cannot proceed past without inventing it.","INDETERMINATE":"The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.","PASS":"Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/build-plan-coherent","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.build-decompose"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]}
@@ -1 +1 @@
1
- {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-build-plan-task-graph","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/build-plan-module-and-resource-coverage"],"requirementRef":"application-creation:authority-requirement/build-plan-coherent-result","requirementVersion":1,"riskClassRef":"application-creation:risk/build-plan-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/build-plan-coherent","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/build-plan-coherent-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/build-plan-coherent","policyVersion":1},"decisionPointRef":"application-creation:decision-point/build-plan-coherent-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/build-plan-coherent-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/build-plan-coherent","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/build-plan-task-graph-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/build-plan-change","triggerRefs":["application-creation:trigger/build-plan-task-graph-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/build-plan-task-well-formedness-and-products"],"hardFloorRef":"application-creation:hard-floor/build-plan-task-graph-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/build-plan-coherent-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/build-plan-coherent","definitionVersion":1,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1}],"instruction":"Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. Do NOT flag the absence of a seeds step: seed generation has no companion pipeline and must not be authored.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.","GAP":"A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or seeds), or a generation step declares products.","INDETERMINATE":"Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.","PASS":"Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1}],"instruction":"Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (single-flight locking, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.","GAP":"A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.","INDETERMINATE":"Task briefs are not in evidence.","PASS":"Every task describes WHAT it builds and none describes how it executes."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource"],"criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1}],"instruction":"Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), or a supporting resource's coverage is thin.","GAP":"A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).","INDETERMINATE":"The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.","PASS":"Every domain-plan resource has build tasks and every moduleRef resolves to a declared module."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1}],"instruction":"For each resource, determine whether its tasks respect the inner order schema -> config -> ui-behavior -> spec through their declared prerequisiteTaskRefs. A supporting resource may legitimately omit stages it does not need (a junction with schema and config and no ui-behavior is fine); only an out-of-order stage, or a main resource missing schema or config, is a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Stages are ordered but a prerequisite edge is carried by prose rather than by prerequisiteTaskRefs, or an omitted stage on a supporting resource is unexplained.","GAP":"A config task ordered before its resource's schema task, a spec task before its ui-behavior task, or a main resource with no schema or config stage.","INDETERMINATE":"Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.","PASS":"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config."}},{"assessesAspects":["build-plan.task","domain-plan.relationship"],"criterionRef":"application-creation:criterion/build-plan-relationship-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1}],"instruction":"Determine whether every relationship draft in the domain plan has a wiring task bound to the module-relationships skill, ordered after BOTH endpoint resources' schema tasks, and whether the wiring task is the single home of the relationship's foreign-key product.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every relationship is wired, but a wiring task's ordering relies on prose rather than declared prerequisites, or its cardinality intent is restated loosely.","GAP":"A relationship draft with no wiring task, a wiring task ordered before an endpoint's schema task, or a relationship whose foreign key is also claimed by a schema task.","INDETERMINATE":"The domain plan's relationship drafts are not in evidence.","PASS":"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1}],"instruction":"Determine whether every task names exactly one real functional topic and at least one skill from the app-knowledge skill catalog, and whether every task except a COMPANION_GENERATION_STEP declares at least one product that names something composition does not already write (the fields a schema gains, the verbs a config gains, both endpoints of a relationship, the declarations a config file gains, the jobs a worker gains — not a scaffolded file or a composed package). Every product must be of the kind that names its surface: a view is a RESOURCE_COMPOSITE_VIEW / RESOURCE_CUSTOM_VIEW / RESOURCE_CHART_VIEW / APPLICATION_VIEW, a page a WEBSITE_PAGE, a worker an APPLICATION_WORKER, a provider a PROVIDER_BINDING — a non-resource surface declared under a MODULE target with a resource-shaped product, or with no product at all, is a gap. No two tasks may claim the same artifact; two tasks enriching one resource with DIFFERENT fields is correct. A cross-resource foreign key declared on a schema task's products is a gap: the relationship task is its single home.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.","GAP":"An invented topic or dangling skill; a coding task with empty products; a product naming only a scaffolded artifact or a composed package; a non-resource surface (a view, a page, a worker, a provider, a config file) declared under a resource-shaped kind; two tasks claiming one artifact; or a foreign key attributed to a schema task.","INDETERMINATE":"The skill catalog or the task list is not in evidence, so bindings cannot be checked.","PASS":"Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"instruction":"Determine whether tasks respect the topic dependency edges: model_domain_graph before define_interaction_semantics; an app-level shape_user_experience task (views or navigation composing several 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; and a resource's spec task after the stages it documents. A resource's OWN ui-behavior depends only on its own schema and config and MAY precede cross-resource operations — that is not a violation.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The order is right but relies on band position rather than a declared prerequisite, or an MVP-first tie-break contradicts the roadmap's phasing.","GAP":"An app-level view composing resources or operations placed before they exist, an integration task before the resources it connects, a user-experience task before that resource's schema task, or a spec task before its ui-behavior stage.","INDETERMINATE":"Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.","PASS":"Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/build-plan-coherent","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.build-decompose"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/build-plan-coherent","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-relationship-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"}],"schemaVersion":1}
1
+ {"authorityRequirement":{"admittedChannels":["INTERFACE_RELAY"],"assurancePolicyRef":"application-creation:authority-policy/local-single-operator","channelPolicyRef":"application-creation:authority-policy/interface-relay","consequenceClassRef":"application-creation:authority-consequence/accept-build-plan-task-graph","decisionModePolicyRef":"application-creation:authority-policy/explicit-operator-confirmation","expiryPolicyRef":"application-creation:authority-expiry/current-interface-session","hardFloorOverrideAllowed":false,"hardFloorPosture":"NON_WAIVABLE","minimumAssurance":"LOCAL_OS_SESSION","noncePolicyRef":"application-creation:authority-nonce/random-per-request","principalPolicyRef":null,"requiredDecisionMode":"EXPLICIT_OPERATOR_CONFIRMATION","requiredEvidenceRequirementRefs":["application-creation:evidence-requirement/build-plan-module-and-resource-coverage"],"requirementRef":"application-creation:authority-requirement/build-plan-coherent-result","requirementVersion":1,"riskClassRef":"application-creation:risk/build-plan-accepted-family-mutation","schemaVersion":1},"continuationPolicy":{"fallbackAction":"BLOCK","mappings":[{"action":"CONTINUE","decisionConsequence":"CONTINUE"},{"action":"REVISE","decisionConsequence":"REVISE"},{"action":"REQUEST_EVIDENCE","decisionConsequence":"REQUEST_EVIDENCE"},{"action":"REQUEST_AUTHORITY","decisionConsequence":"REQUEST_AUTHORITY"},{"action":"BLOCK","decisionConsequence":"BLOCK"}],"maximumAuthorityReviews":1,"maximumEvidenceRequests":2,"maximumRevisionAttempts":3,"policyRef":"application-creation:continuation-policy/build-plan-coherent","policyVersion":1,"schemaVersion":1},"decisionPointDefinition":{"authorityRequirement":{"requirementRef":"application-creation:authority-requirement/build-plan-coherent-result","requirementVersion":1},"continuationPolicy":{"policyRef":"application-creation:continuation-policy/build-plan-coherent","policyVersion":1},"decisionPointRef":"application-creation:decision-point/build-plan-coherent-result","decisionPointVersion":1,"decisionRule":{"ruleRef":"application-creation:decision-rule/build-plan-coherent-result","ruleVersion":1},"evaluatorBindingPolicy":{"policyRef":"application-creation:evaluator-binding-policy/build-plan-coherent","policyVersion":1},"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1},{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"hardFloorRefs":["application-creation:hard-floor/build-plan-task-graph-valid"],"riskPolicyRef":"application-creation:risk-policy/scoped-application-and-execution-context","schemaVersion":1,"significancePolicyRef":"application-creation:significance-policy/build-plan-change","triggerRefs":["application-creation:trigger/build-plan-task-graph-staged-and-valid"]},"decisionRule":{"boundaryClass":"QUALITY_INTERPRETATION","evaluatorFailureConsequence":"BLOCK","evidenceAggregationRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","hardFloorBindings":[{"evidenceRequirementRefs":["application-creation:evidence-requirement/build-plan-task-well-formedness-and-products"],"hardFloorRef":"application-creation:hard-floor/build-plan-task-graph-valid"}],"hardFloorFailureConsequence":"BLOCK","hardFloorShortcutAllowed":false,"resultMappings":[{"consequence":"REQUEST_AUTHORITY","verdict":"PASS"},{"consequence":"REVISE","verdict":"CONCERN"},{"consequence":"REVISE","verdict":"GAP"},{"consequence":"REQUEST_EVIDENCE","verdict":"INDETERMINATE"}],"ruleRef":"application-creation:decision-rule/build-plan-coherent-result","ruleVersion":1,"schemaVersion":1,"unresolvedConsequence":"REQUEST_EVIDENCE"},"definitionRef":"application-creation:evaluation-treatment/build-plan-coherent","definitionVersion":3,"evaluationProtocol":{"aggregationPolicyRef":"application-creation:aggregation/worst-build-plan-coherent-verdict","aggregationStrategy":"WORST_VERDICT_PRECEDENCE_V1","criteria":[{"criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1}],"instruction":"Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. Do NOT flag the absence of a seeds step: seed generation has no companion pipeline and must not be authored.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.","GAP":"A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or seeds), or a generation step declares products.","INDETERMINATE":"Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.","PASS":"Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1}],"instruction":"Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (single-flight locking, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.","GAP":"A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.","INDETERMINATE":"Task briefs are not in evidence.","PASS":"Every task describes WHAT it builds and none describes how it executes."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource"],"criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1}],"instruction":"Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price).","schemaVersion":1,"verdictGuidance":{"CONCERN":"Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), or a supporting resource's coverage is thin.","GAP":"A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).","INDETERMINATE":"The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.","PASS":"Every domain-plan resource has build tasks and every moduleRef resolves to a declared module."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1}],"instruction":"For each resource, determine whether its tasks respect the inner order schema -> config -> ui-behavior -> spec through their declared prerequisiteTaskRefs. A supporting resource may legitimately omit stages it does not need (a junction with schema and config and no ui-behavior is fine); only an out-of-order stage, or a main resource missing schema or config, is a finding.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Stages are ordered but a prerequisite edge is carried by prose rather than by prerequisiteTaskRefs, or an omitted stage on a supporting resource is unexplained.","GAP":"A config task ordered before its resource's schema task, a spec task before its ui-behavior task, or a main resource with no schema or config stage.","INDETERMINATE":"Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.","PASS":"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config."}},{"assessesAspects":["build-plan.task","domain-plan.relationship"],"criterionRef":"application-creation:criterion/build-plan-relationship-coverage","criterionVersion":2,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1}],"instruction":"Determine whether every relationship draft in the domain plan has a wiring task bound to the module-relationships skill, ordered after BOTH endpoint resources' schema tasks, and whether the wiring task is the single home of the relationship's foreign-key product. A relationship whose source or target resource is declared by no module of the domain plan is NOT this criterion's finding: no task can wire it, so it is the conception's fault and `conception-buildable` judges it. Judge the relationships whose endpoints both exist.","schemaVersion":1,"verdictGuidance":{"CONCERN":"Every relationship is wired, but a wiring task's ordering relies on prose rather than declared prerequisites, or its cardinality intent is restated loosely.","GAP":"A relationship draft whose endpoints both exist with no wiring task, a wiring task ordered before an endpoint's schema task, or a relationship whose foreign key is also claimed by a schema task.","INDETERMINATE":"The domain plan's relationship drafts are not in evidence.","PASS":"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1}],"instruction":"Determine whether every task names exactly one real functional topic and at least one skill from the app-knowledge skill catalog, and whether every task except a COMPANION_GENERATION_STEP declares at least one product that names something composition does not already write (the fields a schema gains, the verbs a config gains, both endpoints of a relationship, the declarations a config file gains, the jobs a worker gains — not a scaffolded file or a composed package). Every product must be of the kind that names its surface: a view is a RESOURCE_COMPOSITE_VIEW / RESOURCE_CUSTOM_VIEW / RESOURCE_CHART_VIEW / APPLICATION_VIEW, a page a WEBSITE_PAGE, a worker an APPLICATION_WORKER, a provider a PROVIDER_BINDING — a non-resource surface declared under a MODULE target with a resource-shaped product, or with no product at all, is a gap. No two tasks may claim the same artifact; two tasks enriching one resource with DIFFERENT fields is correct. A cross-resource foreign key declared on a schema task's products is a gap: the relationship task is its single home.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.","GAP":"An invented topic or dangling skill; a coding task with empty products; a product naming only a scaffolded artifact or a composed package; a non-resource surface (a view, a page, a worker, a provider, a config file) declared under a resource-shaped kind; two tasks claiming one artifact; or a foreign key attributed to a schema task.","INDETERMINATE":"The skill catalog or the task list is not in evidence, so bindings cannot be checked.","PASS":"Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice."}},{"assessesAspects":["build-plan.task"],"criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1}],"instruction":"Determine whether tasks respect the topic dependency edges: model_domain_graph before define_interaction_semantics; an app-level shape_user_experience task (views or navigation composing several 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; and a resource's spec task after the stages it documents. A resource's OWN ui-behavior depends only on its own schema and config and MAY precede cross-resource operations — that is not a violation.","schemaVersion":1,"verdictGuidance":{"CONCERN":"The order is right but relies on band position rather than a declared prerequisite, or an MVP-first tie-break contradicts the roadmap's phasing.","GAP":"An app-level view composing resources or operations placed before they exist, an integration task before the resources it connects, a user-experience task before that resource's schema task, or a spec task before its ui-behavior stage.","INDETERMINATE":"Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.","PASS":"Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly."}},{"assessesAspects":["build-plan.task","domain-plan.module","domain-plan.resource","domain-plan.relationship"],"criterionRef":"application-creation:criterion/conception-buildable","criterionVersion":1,"evidenceRequirements":[{"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1}],"instruction":"Determine whether the CONCEPTION this plan rests on can be built as declared. This criterion faults the domain plan, the capability composition or the surface plans — never the build plan. It is a GAP when (a) the domain plan declares a module, resource or relationship that no build task target can express, however it is decomposed, or (b) the computed coherence report shows a dangling reference or an 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. A domain-plan element declared in an expressible shape that the build plan simply omits is NOT this criterion: that is module-and-resource coverage, the decomposer's own fault. Name the conception element in the rationale.","schemaVersion":1,"verdictGuidance":{"CONCERN":"A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.","GAP":"The domain plan declares something no build target can express, or the coherence report shows a dangling reference or unrealised decision in the conception that the build cannot proceed past without inventing it.","INDETERMINATE":"The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.","PASS":"Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent."}}],"promptAssemblyStrategy":"CANONICAL_PROTOCOL_EVIDENCE_V1","protocolRef":"application-creation:evaluation-protocol/build-plan-coherent","protocolVersion":1,"provenance":{"compilerRef":"meta-workflow:compiler/evaluation-treatment","compilerVersion":1,"sourcePlaybookRef":"playbook:bottom_up.build-decompose"},"schemaVersion":1,"verdictPrecedence":["GAP","INDETERMINATE","CONCERN","PASS"]},"evaluatorBindingPolicy":{"admissibleEvaluatorDescriptors":[{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1}],"budgetPolicyRef":"application-creation:evaluator-policy/current-work-cycle-budget","defaultEvaluatorDescriptor":{"descriptorRef":"meta-workflow:evaluator/structured-semantic-coherence","descriptorVersion":1},"escalationPolicyRef":"application-creation:evaluator-policy/request-explicit-review","fallbackPolicyRef":"application-creation:evaluator-policy/fail-closed","maximumAttempts":2,"outputSchemaRef":"meta-workflow:schema/structured-semantic-evaluation-candidate","policyRef":"application-creation:evaluator-binding-policy/build-plan-coherent","policyVersion":1,"schemaVersion":1,"selectionPolicyRef":"application-creation:evaluator-policy/scoped-risk-and-evidence","timeoutPolicyRef":"application-creation:evaluator-policy/bounded-semantic-evaluation"},"evidenceRequirements":[{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-companion-generation-interleave","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-companion-generation-interleave","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-decomposition-boundary","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-decomposition-boundary","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-module-and-resource-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-module-and-resource-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-per-resource-stage-order","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-per-resource-stage-order","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-relationship-coverage","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-relationship-coverage","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-task-well-formedness-and-products","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-task-well-formedness-and-products","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/build-plan-topic-dependency-order","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/build-plan-topic-dependency-order","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"},{"aggregationPolicyRef":null,"conditionRef":null,"coveragePolicyRef":"application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate","criterionRef":"application-creation:criterion/conception-buildable","diversityPolicyRef":null,"freshnessPolicyRef":"application-creation:evidence-policy/current-action-binding","independencePolicyRef":null,"kind":"MANDATORY","maxCount":8,"minCount":2,"requirementRef":"application-creation:evidence-requirement/conception-buildable","requirementVersion":1,"schemaVersion":1,"subjectRef":"application-creation:definition-set/domain-plan-and-build-plan-candidate"}],"schemaVersion":1}