@wildo-ai/framework-knowledge 1.1.9 → 1.1.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (376) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  5. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +4 -2
  6. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  7. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +9 -3
  8. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  9. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  10. package/dist/esm/framework-knowledge.definitions.js +84 -4
  11. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  12. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  13. package/dist/esm/index.d.ts.map +1 -1
  14. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +1 -1
  15. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  16. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +1 -1
  17. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  18. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  19. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +39 -1
  20. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  21. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +132 -20
  22. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  24. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
  25. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  26. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
  27. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  28. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
  29. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  30. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +85 -8
  31. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  32. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
  33. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  34. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
  35. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  36. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  37. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  38. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  39. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  40. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
  41. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
  43. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  44. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  45. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  46. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  47. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  49. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  50. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  51. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
  52. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  53. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  54. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  55. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +2 -2
  56. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  57. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +10 -4
  58. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  59. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +2 -1
  60. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -1
  61. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +5 -3
  62. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -1
  63. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +2 -1
  64. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -1
  65. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +11 -9
  66. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -1
  67. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +17 -3
  68. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -1
  69. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +19 -2
  70. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -1
  71. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  72. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  74. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  75. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  78. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
  80. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  81. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
  82. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  83. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  84. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  85. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  86. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  87. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  88. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  89. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
  90. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  91. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  92. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +38 -3
  93. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  94. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  95. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  96. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  97. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  98. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  99. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  101. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  102. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +11 -0
  103. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  104. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  105. package/dist/knowledge/manifest.json +7 -7
  106. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +1 -1
  107. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  108. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  109. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +149 -11
  110. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +40 -2
  111. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +55 -0
  112. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +1 -1
  113. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +10 -2
  114. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  115. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  116. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +107 -11
  117. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -2
  118. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
  119. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
  120. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
  121. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  122. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
  123. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
  124. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +2 -1
  125. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  126. package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
  127. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
  128. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  129. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  130. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  131. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  132. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +7 -3
  133. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +3 -3
  134. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +56 -16
  135. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +6 -4
  136. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -1
  137. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -1
  138. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +30 -9
  139. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +5 -3
  140. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +12 -1
  141. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  142. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  143. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
  144. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  145. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  146. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  147. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  148. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  149. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
  150. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  151. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  152. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +1 -1
  153. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  154. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  155. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  156. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  157. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +19 -0
  158. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +19 -1
  159. package/dist/knowledge/references/brand.name-choice.config.md +20 -3
  160. package/dist/knowledge/references/brand.name-screening.config.md +58 -3
  161. package/dist/knowledge/references/build-plan.task-graph.config.md +55 -0
  162. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  163. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  164. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  165. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
  166. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  167. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
  168. package/dist/knowledge/references/example.data-seeding.minimal.md +10 -9
  169. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  170. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  171. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  172. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  173. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  174. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  175. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  176. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
  177. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  178. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  179. package/dist/knowledge/references/experience-plan.config.md +60 -7
  180. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  181. package/dist/knowledge/references/placement-plan.config.md +43 -0
  182. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  183. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  184. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  185. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  186. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  187. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  188. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  189. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  190. package/dist/knowledge/references/saas.backend.email.send.md +77 -0
  191. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  192. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  193. package/dist/knowledge/references/saas.data-seeding.definition-input.md +8 -2
  194. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  195. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
  196. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
  197. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
  198. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
  199. package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
  200. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
  201. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
  202. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  203. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
  204. package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
  205. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
  206. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
  207. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  208. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  209. package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
  210. package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
  211. package/dist/knowledge/references/saas.website.astro.label-loader.md +3 -0
  212. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  213. package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
  214. package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
  215. package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
  216. package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
  217. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  218. package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
  219. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  220. package/dist/knowledge/references/website-plan.config.md +26 -0
  221. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
  222. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
  223. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  224. package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
  225. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
  226. package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
  227. package/dist/knowledge/references/zod.factories.code.md +1 -0
  228. package/dist/knowledge/references/zod.factories.duration.md +1 -0
  229. package/dist/knowledge/references/zod.factories.money.md +1 -0
  230. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  231. package/dist/knowledge/registries/framework-topics.json +337 -1
  232. package/dist/knowledge/registries/playbooks.json +18 -18
  233. package/dist/knowledge/registries/source-tags.json +1435 -873
  234. package/dist/knowledge/rules/live-context-door.md +1 -1
  235. package/dist/knowledge/skills/INDEX.md +3 -1
  236. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  237. package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
  238. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  239. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  240. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  241. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
  242. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
  243. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  244. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
  245. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
  246. package/dist/knowledge/skills/brand-name-screening/SKILL.md +33 -9
  247. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +78 -6
  248. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +30 -8
  249. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +2 -1
  250. package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
  251. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
  252. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
  253. package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
  254. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  255. package/dist/knowledge/skills/config-saas/SKILL.md +25 -11
  256. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +51 -1
  257. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
  258. package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
  259. package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
  260. package/dist/knowledge/skills/email-add-template/SKILL.md +27 -5
  261. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  262. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
  263. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  264. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  265. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  266. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
  267. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
  268. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
  269. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
  270. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
  271. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +18 -4
  272. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
  273. package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
  274. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +6 -1
  275. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  276. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  277. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  278. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  279. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  280. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -3
  281. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +1 -1
  282. package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
  283. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
  284. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  285. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  286. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  287. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  288. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  289. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  290. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  291. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +14 -3
  292. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  293. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
  294. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  295. package/dist/knowledge/skills/module-relationships/SKILL.md +31 -4
  296. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  297. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
  298. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
  299. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
  300. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
  301. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  302. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
  303. package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
  304. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
  305. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
  306. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
  307. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
  308. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
  309. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  310. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
  311. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
  312. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  313. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
  314. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
  315. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
  316. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
  317. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
  318. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  319. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
  320. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
  321. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
  322. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
  323. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  324. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  325. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  326. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
  327. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
  328. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
  329. package/dist/knowledge/skills/seeding-authoring/SKILL.md +155 -40
  330. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  331. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +148 -4
  332. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  333. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
  334. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
  335. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  336. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  337. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
  338. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  339. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  340. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  341. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  342. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  343. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  344. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
  345. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  346. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  347. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
  348. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
  349. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
  350. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
  351. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
  352. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
  353. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
  354. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
  355. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +10 -2
  356. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
  357. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
  358. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
  359. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
  360. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
  361. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
  362. package/dist/knowledge/skills/website-page-authoring/SKILL.md +16 -5
  363. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
  364. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
  365. package/dist/knowledge/skills/website-section-faq/SKILL.md +6 -1
  366. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +6 -1
  367. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +10 -2
  368. package/dist/knowledge/skills/website-section-hero/SKILL.md +6 -1
  369. package/dist/knowledge/skills/website-section-pricing/SKILL.md +6 -1
  370. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +12 -2
  371. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +15 -3
  372. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
  373. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
  374. package/dist/knowledge/topic-index.json +1441 -269
  375. package/dist/tsconfig.build.tsbuildinfo +1 -1
  376. package/package.json +4 -4
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build-decompose/playbook.definition.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,6BAA6B,GAC9B,MAAM,sCAAsC,CAAC;AAE9C;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,2BAA2B;IAClC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,+6DAA+6D;IACz7D,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;QACtE;YACE,MAAM,EAAE,mBAAmB;YAC3B,UAAU,EAAE,EAAE,QAAQ,EAAE,gBAAgB,EAAE;YAC1C,IAAI,EAAE,g1BAAg1B;SACv1B;KACF;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,SAAS,EAAE;QACvB,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,8SAA8S,EAAE;QAClV,EAAE,QAAQ,EAAE,aAAa,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,2PAA2P,EAAE;QAC/S,EAAE,QAAQ,EAAE,iBAAiB,EAAE,IAAI,EAAE,gYAAgY,EAAE;QACva,EAAE,QAAQ,EAAE,oBAAoB,EAAE,IAAI,EAAE,gPAAgP,EAAE;QAC1R,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,yfAAyf,EAAE;QACjiB,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,qfAAqf,EAAE;QAC3hB,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,qVAAqV,EAAE;QACzX,EAAE,QAAQ,EAAE,YAAY,EAAE,IAAI,EAAE,kMAAkM,EAAE;KACrO;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,YAAY;YACtB,WAAW,EAAE,wCAAwC;YACrD,aAAa,EAAE,8nJAA8nJ;SAC9oJ;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,ywBAAywB;QAC7xB,gBAAgB,EAAE,CAAC,iBAAiB,EAAE,eAAe,EAAE,kBAAkB,CAAC;QAC1E,WAAW,EAAE;YACX,qBAAqB;YACrB,uBAAuB;YACvB,2BAA2B;YAC3B,wBAAwB;YACxB,sBAAsB;YACtB,4BAA4B;YAC5B,sBAAsB;YACtB,sBAAsB;YACtB,qBAAqB;YACrB,iCAAiC;SAClC;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC;AAEX,MAAM,CAAC,MAAM,yBAAyB,GAAG;IACvC,aAAa,EAAE,CAAC;IAChB,aAAa,EAAE,+DAA+D;IAC9E,6GAA6G;IAC7G,sGAAsG;IACtG,iHAAiH;IACjH,wHAAwH;IACxH,gIAAgI;IAChI,iBAAiB,EAAE,CAAC;IACpB,kBAAkB,EAAE;QAClB,aAAa,EAAE,CAAC;QAChB,WAAW,EAAE,8DAA8D;QAC3E,eAAe,EAAE,CAAC;QAClB,sBAAsB,EAAE,6CAA6C,CAAC,8BAA8B;QACpG,mBAAmB,EAAE,0CAA0C,CAAC,2BAA2B;QAC3F,iBAAiB,EAAE,CAAC,8BAA8B,CAAC,GAAG,EAAE,8BAA8B,CAAC,aAAa,EAAE,8BAA8B,CAAC,OAAO,EAAE,8BAA8B,CAAC,IAAI,CAAC;QAClL,oBAAoB,EAAE,oEAAoE;QAC1F;;;;;;;WAOG;QACH,QAAQ,EAAE;YACV;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,wEAAwE;gBACtF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,0/BAA0/B;gBAC5/B,eAAe,EAAE,CAAC,iBAAiB,EAAE,oBAAoB,EAAE,sBAAsB,CAAC;gBAClF,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,mFAAmF;wBACnG,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,+FAA+F;oBACtI,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,qQAAqQ;oBAC/S,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,wJAAwJ;oBAC9L,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,0GAA0G;iBAC3J;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,6EAA6E;gBAC3F,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,6iCAA6iC;gBAC/iC,eAAe,EAAE,CAAC,iBAAiB,CAAC;gBACpC,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,wFAAwF;wBACxG,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,wIAAwI;oBAC/K,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,mHAAmH;oBAC7J,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,+UAA+U;oBACrX,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,uFAAuF;iBACxI;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,oEAAoE;gBAClF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,wXAAwX;gBAC1X,eAAe,EAAE,CAAC,iBAAiB,CAAC;gBACpC,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,+EAA+E;wBAC/F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,4JAA4J;oBACnM,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,kKAAkK;oBAC5M,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,sJAAsJ;oBAC5L,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,6FAA6F;iBAC9I;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,kEAAkE;gBAChF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,qlBAAqlB;gBACvlB,eAAe,EAAE,CAAC,iBAAiB,CAAC;gBACpC,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,6EAA6E;wBAC7F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,sIAAsI;oBAC7K,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,kJAAkJ;oBAC5L,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,6OAA6O;oBACnR,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,6FAA6F;iBAC9I;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,iEAAiE;gBAC/E;;;;;;mBAMG;gBACH,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,ohBAAohB;gBACthB,eAAe,EAAE,CAAC,iBAAiB,EAAE,0BAA0B,CAAC;gBAChE,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,4EAA4E;wBAC5F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,2FAA2F;oBAClI,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,8JAA8J;oBACxM,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,oMAAoM;oBAC1O,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,4DAA4D;iBAC7G;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,2EAA2E;gBACzF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,kvBAAkvB;gBACpvB,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,sFAAsF;wBACtG,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,mJAAmJ;oBAC1L,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,sMAAsM;oBAChP,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,+JAA+J;oBACrM,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,kIAAkI;iBACnL;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,kEAAkE;gBAChF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,0cAA0c;gBAC5c,eAAe,EAAE,CAAC,iBAAiB,CAAC;gBACpC,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,6EAA6E;wBAC7F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,yEAAyE;oBAChH,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,2HAA2H;oBACrK,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,sGAAsG;oBAC5I,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,kCAAkC;iBACnF;aACF;YACD;;;;;;;;;;;;;;;;;eAiBG;YACH;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,+DAA+D;gBAC7E,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,6tCAA6tC;gBAC/tC,eAAe,EAAE,CAAC,iBAAiB,EAAE,sBAAsB,EAAE,+BAA+B,EAAE,2BAA2B,EAAE,0BAA0B,CAAC;gBACtJ,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,0EAA0E;wBAC1F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,8NAA8N;oBACrQ,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,0MAA0M;oBACpP,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,0JAA0J;oBAChM,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,mNAAmN;iBACpQ;aACF;YACD;;;;;;;eAOG;YACH;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,qDAAqD;gBACnE,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,qzBAAqzB;gBACvzB,eAAe,EAAE,CAAC,iBAAiB,EAAE,oBAAoB,EAAE,sBAAsB,EAAE,0BAA0B,CAAC;gBAC9G,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,gEAAgE;wBAChF,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,qIAAqI;oBAC5K,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,2IAA2I;oBACrL,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,sNAAsN;oBAC5P,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,gHAAgH;iBACjK;aACF;SACA;KACF;IACD,sBAAsB,EAAE;QACtB,aAAa,EAAE,CAAC;QAChB,SAAS,EAAE,mEAAmE;QAC9E,aAAa,EAAE,CAAC;QAChB,4BAA4B,EAAE,CAAC,EAAE,YAAY,EAAE,uDAAuD,EAAE,gBAAgB,EAAE,CAAC,EAAE,CAAC;QAC9H,wBAAwB,EAAE,EAAE,YAAY,EAAE,uDAAuD,EAAE,gBAAgB,EAAE,CAAC,EAAE;QACxH,sBAAsB,EAAE,EAAE,iBAAiB,EAAE,wEAAwE,EAAE,qBAAqB,EAAE,CAAC,EAAE;QACjJ,iBAAiB,EAAE,mDAAmD;QACtE,mBAAmB,EAAE,+DAA+D;QACpF,eAAe,EAAE,CAAC;QAClB,gBAAgB,EAAE,mEAAmE;QACrF,eAAe,EAAE,iEAAiE;QAClF,kBAAkB,EAAE,gEAAgE;KACrF;IACD,uBAAuB,EAAE;QACvB,aAAa,EAAE,CAAC;QAChB,gBAAgB,EAAE,gEAAgE;QAClF,oBAAoB,EAAE,CAAC;QACvB,WAAW,EAAE,CAAC,qEAAqE,CAAC;QACpF,aAAa,EAAE,CAAC,6DAA6D,CAAC;QAC9E,aAAa,EAAE,2EAA2E;QAC1F,qBAAqB,EAAE,4DAA4D;KACpF;IACD,YAAY,EAAE;QACZ,aAAa,EAAE,CAAC;QAChB,OAAO,EAAE,+DAA+D;QACxE,WAAW,EAAE,CAAC;QACd,aAAa,EAAE,sCAAsC,CAAC,sBAAsB;QAC5E,sBAAsB,EAAE,oEAAoE;QAC5F,cAAc,EAAE;YACd,EAAE,OAAO,EAAE,8BAA8B,CAAC,IAAI,EAAE,WAAW,EAAE,gCAAgC,CAAC,iBAAiB,EAAE;YACjH,EAAE,OAAO,EAAE,8BAA8B,CAAC,OAAO,EAAE,WAAW,EAAE,gCAAgC,CAAC,MAAM,EAAE;YACzG,EAAE,OAAO,EAAE,8BAA8B,CAAC,GAAG,EAAE,WAAW,EAAE,gCAAgC,CAAC,MAAM,EAAE;YACrG,EAAE,OAAO,EAAE,8BAA8B,CAAC,aAAa,EAAE,WAAW,EAAE,gCAAgC,CAAC,gBAAgB,EAAE;SAC1H;QACD,iBAAiB,EAAE,CAAC;gBAClB,YAAY,EAAE,6DAA6D;gBAC3E,uBAAuB,EAAE,CAAC,wFAAwF,CAAC;aACpH,CAAC;QACF,2BAA2B,EAAE,gCAAgC,CAAC,KAAK;QACnE,wBAAwB,EAAE,KAAK;QAC/B,qBAAqB,EAAE,gCAAgC,CAAC,gBAAgB;QACxE,2BAA2B,EAAE,gCAAgC,CAAC,KAAK;KACpE;IACD,oBAAoB,EAAE;QACpB,aAAa,EAAE,CAAC;QAChB,cAAc,EAAE,uEAAuE;QACvF,kBAAkB,EAAE,CAAC;QACrB,mBAAmB,EAAE,yEAAyE;QAC9F,YAAY,EAAE,+DAA+D;QAC7E,qBAAqB,EAAE,sEAAsE;QAC7F,kBAAkB,EAAE,6DAA6D;QACjF,gBAAgB,EAAE,uDAAuD;QACzE,kBAAkB,EAAE,IAAI;QACxB,oBAAoB,EAAE,kCAAkC,CAAC,8BAA8B;QACvF,gBAAgB,EAAE,oCAAoC,CAAC,gBAAgB;QACvE,gBAAgB,EAAE,CAAC,wCAAwC,CAAC,eAAe,CAAC;QAC5E,+BAA+B,EAAE,CAAC,mFAAmF,CAAC;QACtH,eAAe,EAAE,iEAAiE;QAClF,cAAc,EAAE,yDAAyD;QACzE,gBAAgB,EAAE,6BAA6B,CAAC,YAAY;QAC5D,wBAAwB,EAAE,KAAK;KAChC;IACD,kBAAkB,EAAE;QAClB,aAAa,EAAE,CAAC;QAChB,SAAS,EAAE,8DAA8D;QACzE,aAAa,EAAE,CAAC;QAChB,QAAQ,EAAE;YACR,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,QAAQ,EAAE,MAAM,EAAE,+BAA+B,CAAC,QAAQ,EAAE;YACpH,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,MAAM,EAAE,MAAM,EAAE,+BAA+B,CAAC,MAAM,EAAE;YAChH,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,gBAAgB,EAAE,MAAM,EAAE,+BAA+B,CAAC,gBAAgB,EAAE;YACpI,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,iBAAiB,EAAE,MAAM,EAAE,+BAA+B,CAAC,iBAAiB,EAAE;YACtI,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,KAAK,EAAE,MAAM,EAAE,+BAA+B,CAAC,KAAK,EAAE;SAC/G;QACD,uBAAuB,EAAE,CAAC;QAC1B,uBAAuB,EAAE,CAAC;QAC1B,uBAAuB,EAAE,CAAC;QAC1B,cAAc,EAAE,+BAA+B,CAAC,KAAK;KACtD;CAC8C,CAAC","sourcesContent":["import type { MetaWorkflowEvaluationTreatmentSource } from '@wildo-ai/saas-backend-lib/meta-workflow-runtime';\nimport {\n MetaWorkflow_AuthorityAssuranceClass,\n MetaWorkflow_AuthorityDecisionMode,\n MetaWorkflow_AuthorityInteractionChannel,\n MetaWorkflow_ContinuationAction,\n MetaWorkflow_DecisionConsequence,\n MetaWorkflow_DecisionRuleBoundaryClass,\n MetaWorkflow_EvaluationAggregationStrategy,\n MetaWorkflow_EvaluationPromptAssemblyStrategy,\n MetaWorkflow_EvaluationVerdict,\n MetaWorkflow_EvidenceRequirementKind,\n MetaWorkflow_HardFloorPosture,\n} from '@wildo-ai/saas-models/meta-workflows';\n\n/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes.\n *\n * The `evaluationTreatmentSource` below is the `build-plan-coherent` reviewer checklist the\n * method carried as prose from the flexible-intelligence hard cut until 2026-09-22 (#1487) —\n * eight invariants that its own closing sentence said \"nothing executes\". Compiled here, the\n * ADVISORY judge reads them against the landed build plan and the domain plan it decomposes,\n * so a resource with no task, a relationship wired before its endpoints, or a product naming\n * only a scaffolded file is reported BEFORE a coding dispatch pays for it. Advisory as\n * everywhere in this lane: the plan is landed when the judge speaks, and a verdict is a note\n * for the creator's `approve_result` review, never a refusal.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.build-decompose\",\n \"version\": \"0.4.1\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / lock or schedule runs / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } },\n {\n \"kind\": \"artifact_expected\",\n \"selector\": { \"family\": \"placement-plan\" },\n \"//\": \"SEQUENCING, not readiness — and the distinction is the whole point. `bottom_up.placement-plan` gates on the SAME `domain-plan` this does, so both become eligible at the same instant and decomposing first is legal. This method then says, at its placement section, 'No placement plan? Emit nothing here and say so' — which is honest per task and catastrophic per plan: the build proceeds with ZERO SHELL_PLACEMENT tasks and nothing refuses, so the finished application has no navigation and the cause is three playbooks upstream. `artifact_expected` is the kind written for exactly this (its own doc: use it whenever running early DEGRADES the output rather than invalidating it): the board reports `blocked only by sequencing`, a human may still run it deliberately, and `unmet` finally explains WHY the order matters instead of losing the signal.\"\n }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"roadmap\" },\n { \"family\": \"requirements\" },\n { \"family\": \"feature-drafts\" },\n { \"family\": \"placement-plan\" },\n { \"family\": \"vision-brief\", \"//\": \"Carries the landed COMPLIANCE POSTURE and constraints. Measured 2026-09-04 (#309): without this input the decomposer, given a landed GDPR/ePrivacy posture, produced ZERO posture-derived tasks — the obligations lived in a family the brief never carried. No intent slice: the posture must arrive whole.\" },\n { \"family\": \"brand-brief\", \"render\": \"map\", \"//\": \"Whether the application HAS a brand decides whether the `logo` generation step is authored (method: companion generation steps; checklist invariant 6). The method only needs to know it exists, so it reads the brand as a map, not its content (#1424).\" },\n { \"family\": \"experience-plan\", \"//\": \"The application's own surfaces and its shell composition (#1493). Each view becomes a task over the product kind its KIND names, each configuration an APPLICATION_FRONTEND_CONFIG task, each planned milestone an APPLICATION_MILESTONE task and each planned piece of guidance an APPLICATION_GUIDANCE task — with the skill taken from the experience plan's total maps, never chosen here.\" },\n { \"family\": \"documentation-plan\", \"//\": \"Which chapters the documentation portal carries (#1494). Each becomes a DOCUMENTATION_CHAPTER task under the TECHNICAL_DOCUMENTATION target, whose scope prohibits the portal's generated tree. A NOT_APPLICABLE plan, or none, emits nothing.\" },\n { \"family\": \"integration-plan\", \"//\": \"What runs beside the backend and what the application reaches out to (#1495). Each worker, minion and provider binding becomes a task over its own target kind, with the skill taken from the three total maps rather than chosen here — which is what makes the worker, minion and provider skills reachable. Each declared inbound channel becomes an INBOUND_CHANNEL_HANDLER task in the module its messages concern (#1832), routed to `inbound-channels` by the dispatch. No plan, or an empty one, emits nothing.\" },\n { \"family\": \"business-model\", \"//\": \"The pricing plans the application sells (#1835). Each becomes a product of the billing catalogue — one BILLING_CATALOG task producing an APPLICATION_BILLING_PRODUCT per plan — so the backend has something to sell and the website's pricing page reads the catalogue instead of re-typing the plans' prices. Measured on the first journey-built application: with no such task its catalogue stayed EMPTY and the website agent hand-copied the prices. No business model, or one with no plans, emits nothing.\" },\n { \"family\": \"website-plan\", \"//\": \"What the marketing site says, page by page (#1492). The decomposer turns each page into a WEBSITE_PAGE task and each section into a WEBSITE_SECTION task bound to the skill its KIND names — so the website skills are reached by construction rather than by a model recalling folder names. A NOT_APPLICABLE plan, or none at all, emits nothing.\" },\n { \"family\": \"build-plan\", \"//\": \"Its own family: its method refines its own prior output and keeps its refs, so it must be GIVEN that output (#1430). Input, not precondition: a first run, with no prior output, stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"build-plan\",\n \"schemaRef\": \"saas-specifications:BuildPlanTaskGraph\",\n \"description\": \"The build decomposition — an ORDERED set of coding-agent build tasks (a task graph) that turns the approved domain plan into a sequence of buildable units. Each task carries: a stable task ref, the target it builds (a module, a resource + one of its build stages, a relationship, a companion-generation step, a shell-surface placement config), WHAT IT PRODUCES (`produces` — the artifacts whose presence in the finished application proves the task landed; distinct from the target, which is a write scope several tasks may share), the ONE functional topic it belongs to (a real MetaWorkflow_FunctionalTopic value), the skill(s) that carry its technical HOW (real folders from the app-knowledge skill catalog, resolved via the skills router), and its ordering intent (which tasks must precede it — expressed as typed prerequisiteTaskRefs, which the host resolves for readiness). Author prerequisiteTaskRefs to express the actual dependencies, using these planning considerations: (a) the cross-app topic dependency edges (model_domain_graph before define_interaction_semantics before app-level shape_user_experience before extend_application before connect_runtime_and_external_capabilities; foundation and assemble/verify are owned by sibling playbooks) and (b) the per-resource stage sequence schema -> config -> ui-behavior -> spec — which deliberately CROSSES topics (ui-behavior is shape_user_experience; the spec is a model_domain_graph documentation capstone ordered last) and so is not monotonic on axis (a); a roadmap-driven MVP-first preference breaks ties within a band. TYPED since the flexible-intelligence Block 3: the `_core` build-task-graph contract (`BuildPlanTaskGraph` — `tasks[]` with a stable `taskRef`, a closed `BuildPlanTaskTargetKind` target (MODULE / RESOURCE_STAGE / RELATIONSHIP / COMPANION_GENERATION_STEP / SHELL_PLACEMENT / MODULE_FRONTEND / MODULE_BACKEND / APPLICATION_FRONTEND_CONFIG / WEBSITE / TECHNICAL_DOCUMENTATION / WORKER / MINION / PROVIDER_BINDING / BILLING_CATALOG), a `produces` list over the closed `BuildPlanTaskProductKind` vocabulary (the resource products — schema fields, registration, ui-behavior, specification, relationship, operation, composite / custom / chart view, PDF template; the application products — view, document, module, frontend configuration, custom component, milestone, guidance; and the runtime products — worker jobs, minion behaviours, provider binding, website page and section, documentation chapter, inbound channel handler; and the billing product the catalogue sells), exactly one `functionalTopic`, `skillRefs`, DECLARED `prerequisiteTaskRefs` the host resolves for readiness, and traceability `servesRefs`) is the family schema; the provider answers the strict `BuildPlanTaskGraphGeneration` shape and the trusted runtime stamps refs and version. The task never carries paths, commands, prompts or runtime controls — the dispatch host derives mutation scope and verification from the target kind. `validateBuildPlanTaskGraph` is the deterministic validator. A task's products must name something COMPOSITION DOES NOT ALREADY WRITE (the fields a schema gains, not its scaffolded file) and no two tasks may claim the same artifact — that is what makes landing decidable; a coding task declaring none is reported as `TASK_DECLARES_NO_PRODUCT`. If such a task has a COMPLETED durable run, the host advances past it but reports its ref in `unverifiableLandedTaskRefs`: it ran, but its output is not proven. Without that completed run it remains unlanded. Companion-generation tasks use their own landed conditions; migrations require the schema plan to be in sync. Product probes inspect committed files and named declarations, not runtime correctness. Two things are HARD FLOORS: a prerequisite cycle, and a resource stage that declares its predecessor stage in the SAME graph without depending on it — dispatch order comes solely from `prerequisiteTaskRefs`, so an undeclared stage edge lets the host author a resources-config for a schema that has not landed. A predecessor stage that is ABSENT from the plan is an authoring WARNING instead, because a plan may legitimately author one stage of a resource the tree already carries; the coherence reviewer checklist (`build-plan-coherent`, in the method) remains the semantic check and the creator's approve_result review the trust floor. Consumed by the bottom-up DISPATCH-ORCHESTRATION playbook (which dispatches the tasks through the coding-agent contract in parallel waves, up to the application's build parallelism at once) and the SCALE playbook (which describes how those waves are scheduled, interleaved with the companion generation steps, and reconciled) — both downstream of this decomposition.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"WORKSPACE_TRUTH — this playbook plans against CODE, not against definition artifacts: it needs real module ids and per-resource present schema fields, or it invents ids that do not resolve and every task it emits fails at dispatch. SKILL_CATALOG — its method routes THROUGH the skills router and binds every emitted task to a skill folder, so it must choose from the real set; measured 2026-08-27 it was choosing from recall, and a dangling skill ref is a task the dispatch playbook cannot run. COHERENCE_REPORT — the computed cross-family findings over the conception it builds on (dangling edges into the domain plan, a composition surface no plan realises), so its judge can tell a conception fault from its own (#1638): the build lane routes the first back to conception.\",\n \"contextSources\": [\"workspace_truth\", \"skill_catalog\", \"coherence_report\"],\n \"skillRefs\": [\n \"resource-add-module\",\n \"resource-add-resource\",\n \"resource-schema-authoring\",\n \"resource-config-wiring\",\n \"resource-ui-behavior\",\n \"frontend-component-catalog\",\n \"spec-resource-update\",\n \"module-relationships\",\n \"module-registration\",\n \"application-database-migrations\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n\nexport const evaluationTreatmentSource = {\n schemaVersion: 1,\n definitionRef: 'application-creation:evaluation-treatment/build-plan-coherent',\n // 2 since #1638: `conception-buildable` faults the CONCEPTION, not the plan, which changes what a GAP means.\n // 3: relationship coverage leaves a relationship to an undeclared resource to `conception-buildable`.\n // 4: experience coverage (#2235) — the experience plan's surfaces each have a task, and its absence is recorded.\n // 5: module-and-resource coverage also asks for demonstration data (#2234), so a built application does not open empty.\n // 6: experience coverage keys its absence case on the accepted-truth statement, not on a heading it did not see (#2235 review).\n definitionVersion: 6,\n evaluationProtocol: {\n schemaVersion: 1,\n protocolRef: 'application-creation:evaluation-protocol/build-plan-coherent',\n protocolVersion: 1,\n promptAssemblyStrategy: MetaWorkflow_EvaluationPromptAssemblyStrategy.CANONICAL_PROTOCOL_EVIDENCE_V1,\n aggregationStrategy: MetaWorkflow_EvaluationAggregationStrategy.WORST_VERDICT_PRECEDENCE_V1,\n verdictPrecedence: [MetaWorkflow_EvaluationVerdict.GAP, MetaWorkflow_EvaluationVerdict.INDETERMINATE, MetaWorkflow_EvaluationVerdict.CONCERN, MetaWorkflow_EvaluationVerdict.PASS],\n aggregationPolicyRef: 'application-creation:aggregation/worst-build-plan-coherent-verdict',\n /*\n * One criterion per invariant of the method's `build-plan-coherent` checklist (its invariants 2 and 2b\n * share one criterion, because well-formedness and product declaration are read off the same task).\n * `assessesAspects` scopes a criterion to the families it actually reads (#1423): coverage reads the\n * domain plan's modules and resources beside the tasks; relationship coverage reads its relationship\n * drafts; the interleave criterion names no aspects because it needs the brand MAP and the store\n * selection, which are not aspects of a family, and so reads the whole evidence.\n */\n criteria: [\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-module-and-resource-coverage',\n criterionVersion: 2,\n instruction:\n \"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). Seeding is covered the same way: a plan whose domain has main resources and no APPLICATION_DATA_SEED task of content DEMONSTRATION is a concern — the application would open empty, with nothing a creator can judge or show (#2234).\",\n assessesAspects: ['build-plan.task', 'domain-plan.module', 'domain-plan.resource'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-module-and-resource-coverage',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every domain-plan resource has build tasks and every moduleRef resolves to a declared module.',\n [MetaWorkflow_EvaluationVerdict.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), a supporting resource's coverage is thin, or no DEMONSTRATION data seed gives the main resources sample rows.\",\n [MetaWorkflow_EvaluationVerdict.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).',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-task-well-formedness-and-products',\n criterionVersion: 1,\n instruction:\n \"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.\",\n assessesAspects: ['build-plan.task'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-task-well-formedness-and-products',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice.',\n [MetaWorkflow_EvaluationVerdict.CONCERN]: \"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.\",\n [MetaWorkflow_EvaluationVerdict.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.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The skill catalog or the task list is not in evidence, so bindings cannot be checked.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-per-resource-stage-order',\n criterionVersion: 1,\n instruction:\n '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.',\n assessesAspects: ['build-plan.task'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-per-resource-stage-order',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: \"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config.\",\n [MetaWorkflow_EvaluationVerdict.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.',\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-topic-dependency-order',\n criterionVersion: 1,\n instruction:\n \"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.\",\n assessesAspects: ['build-plan.task'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-topic-dependency-order',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly.',\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-relationship-coverage',\n /*\n * Version 2 (2026-09-25): a relationship whose endpoint no module declares is excluded. Measured on\n * scratch-journey with a planted relationship to an undeclared resource: `conception-buildable` gave\n * GAP and version 1 of this criterion ALSO gave GAP (\"no wiring task\"). This one's GAP re-opens the\n * decomposer inside the build lane, so the lane re-ran decomposition on a relationship no task can\n * wire, up to its iteration cap, before the conception verdict reached the root.\n */\n criterionVersion: 2,\n instruction:\n \"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.\",\n assessesAspects: ['build-plan.task', 'domain-plan.relationship'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-relationship-coverage',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: \"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks.\",\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: \"The domain plan's relationship drafts are not in evidence.\",\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-companion-generation-interleave',\n criterionVersion: 1,\n instruction:\n '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 an i18n-translations step: the dispatch host derives it after i18n-labels. Do NOT flag the absence of a seeds GENERATION step: none exists, and seeding is an APPLICATION_DATA_SEED coding task judged under module-and-resource coverage.',\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-companion-generation-interleave',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists.',\n [MetaWorkflow_EvaluationVerdict.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.',\n [MetaWorkflow_EvaluationVerdict.GAP]: 'A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or a seeds generation step), or a generation step declares products.',\n [MetaWorkflow_EvaluationVerdict.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.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-decomposition-boundary',\n criterionVersion: 1,\n instruction:\n '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 (dispatch locking and concurrency, 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.',\n assessesAspects: ['build-plan.task'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-decomposition-boundary',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every task describes WHAT it builds and none describes how it executes.',\n [MetaWorkflow_EvaluationVerdict.CONCERN]: 'A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.',\n [MetaWorkflow_EvaluationVerdict.GAP]: 'A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'Task briefs are not in evidence.',\n },\n },\n /*\n * The experience plan's surfaces each have a task, and an ABSENT experience plan is recorded rather than\n * silent (#2235).\n *\n * Measured on app-creation-test-004 (2026-10-01): `bottom_up.experience-plan` was refused twice, the build\n * plan was decomposed anyway, and the application shipped with no app-level views, no onboarding and no\n * milestones. The method is right to emit no such task without a plan (\"an improvised surface is the state\n * this family replaced\"), and the plan read as complete — no criterion here looked at the experience plan.\n *\n * Why an absent plan is PASS with a marked rationale, and not a weaker verdict: every non-PASS verdict of\n * this treatment routes back to the decomposer (CONCERN and GAP → REVISE, INDETERMINATE → REQUEST_EVIDENCE,\n * which ends in BLOCK). The decomposer cannot produce an upstream family by revising, so either would spend\n * revisions on something it cannot fix, and the second would stop the build on an unfinished upstream —\n * the refusal `.claude/rules/application-creation-directive.md` forbids (\"mark, never block\"). Rejected too:\n * an `artifact_expected` precondition on the family, the `placement-plan` shape. Inside a lane every child\n * is admitted past SEQUENCING (`playbook-run.companion.service.ts`, `proceedPastSequencing: true`), so it\n * would have marked nothing in the run that motivated this.\n */\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-experience-coverage',\n criterionVersion: 2,\n instruction:\n \"Determine whether every surface the experience plan decides has its build task: one task per VIEW (target MODULE_FRONTEND on the view's module, a product of the view's kind carrying the plan's viewRef verbatim), one APPLICATION_FRONTEND_CONFIG task per CONFIGURATION, one APPLICATION_MILESTONE task per planned MILESTONE, and one APPLICATION_GUIDANCE task per planned piece of GUIDANCE (an onboarding document's objective naming the hostViewRef that embeds it). A view, configuration, milestone or guidance entry with no task is a gap: the application would ship without it while the plan reads complete. Never conclude the plan is absent because this criterion's own slice does not show it: the accepted application truth either renders the experience plan or says it has none. When the accepted application truth STATES that `experience-plan` has no accepted content, the decomposer has rightly emitted none of these tasks and cannot repair the absence by revising: record PASS, and begin the rationale with the words 'NO EXPERIENCE PLAN:' followed by what the application will therefore lack (its app-level views, its shell and navigation configuration, its milestones and its onboarding), so the absence is on the record instead of silent.\",\n assessesAspects: ['build-plan.task', 'experience-plan.view', 'experience-plan.configuration', 'experience-plan.milestone', 'experience-plan.guidance'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-experience-coverage',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 1,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: \"Every view, configuration, milestone and guidance entry of the experience plan has its task — or no experience plan is in evidence, and the rationale begins 'NO EXPERIENCE PLAN:' and names what the application will lack.\",\n [MetaWorkflow_EvaluationVerdict.CONCERN]: \"Every entry has a task, but a task's objective drops what the plan decided for it: a view's reusesComponentRefs, a milestone's moment, a guidance entry's gate, or an onboarding document's hostViewRef.\",\n [MetaWorkflow_EvaluationVerdict.GAP]: 'A view, configuration, milestone or guidance entry the experience plan declares has no task, or a view task carries a viewRef the plan does not declare.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan is not in evidence, or the accepted application truth neither renders the experience plan nor states that it has none. (A STATED absence is not indeterminate: it is the PASS case above, marked.)',\n },\n },\n /*\n * The one criterion that faults the CONCEPTION rather than the plan (#1638). Every other criterion\n * here is the decomposer's own, and its GAP re-opens the decomposer. This one says the plan could not\n * be right however it was decomposed, because what it rests on is wrong — and the root routes that\n * GAP back to the conception lane through the build lane's exported verdict. Keeping it separate from\n * module-and-resource coverage is the point: a resource the plan merely FORGOT is not a conception\n * fault, and re-running the conception for it would be the most expensive way to fix an omission.\n */\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/conception-buildable',\n criterionVersion: 1,\n instruction:\n \"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.\",\n assessesAspects: ['build-plan.task', 'domain-plan.module', 'domain-plan.resource', 'domain-plan.relationship'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/conception-buildable',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent.',\n [MetaWorkflow_EvaluationVerdict.CONCERN]: 'A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.',\n [MetaWorkflow_EvaluationVerdict.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.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.',\n },\n },\n ],\n },\n evaluatorBindingPolicy: {\n schemaVersion: 1,\n policyRef: 'application-creation:evaluator-binding-policy/build-plan-coherent',\n policyVersion: 1,\n admissibleEvaluatorSelectors: [{ evaluatorRef: 'meta-workflow:evaluator/structured-semantic-coherence', evaluatorVersion: 1 }],\n defaultEvaluatorSelector: { evaluatorRef: 'meta-workflow:evaluator/structured-semantic-coherence', evaluatorVersion: 1 },\n outputContractSelector: { outputContractRef: 'meta-workflow:output-contract/structured-semantic-evaluation-candidate', outputContractVersion: 1 },\n fallbackPolicyRef: 'application-creation:evaluator-policy/fail-closed',\n escalationPolicyRef: 'application-creation:evaluator-policy/request-explicit-review',\n maximumAttempts: 2,\n timeoutPolicyRef: 'application-creation:evaluator-policy/bounded-semantic-evaluation',\n budgetPolicyRef: 'application-creation:evaluator-policy/current-work-cycle-budget',\n selectionPolicyRef: 'application-creation:evaluator-policy/scoped-risk-and-evidence',\n },\n decisionPointDefinition: {\n schemaVersion: 1,\n decisionPointRef: 'application-creation:decision-point/build-plan-coherent-result',\n decisionPointVersion: 1,\n triggerRefs: ['application-creation:trigger/build-plan-task-graph-staged-and-valid'],\n hardFloorRefs: ['application-creation:hard-floor/build-plan-task-graph-valid'],\n riskPolicyRef: 'application-creation:risk-policy/scoped-application-and-execution-context',\n significancePolicyRef: 'application-creation:significance-policy/build-plan-change',\n },\n decisionRule: {\n schemaVersion: 1,\n ruleRef: 'application-creation:decision-rule/build-plan-coherent-result',\n ruleVersion: 1,\n boundaryClass: MetaWorkflow_DecisionRuleBoundaryClass.QUALITY_INTERPRETATION,\n evidenceAggregationRef: 'application-creation:aggregation/worst-build-plan-coherent-verdict',\n resultMappings: [\n { verdict: MetaWorkflow_EvaluationVerdict.PASS, consequence: MetaWorkflow_DecisionConsequence.REQUEST_AUTHORITY },\n { verdict: MetaWorkflow_EvaluationVerdict.CONCERN, consequence: MetaWorkflow_DecisionConsequence.REVISE },\n { verdict: MetaWorkflow_EvaluationVerdict.GAP, consequence: MetaWorkflow_DecisionConsequence.REVISE },\n { verdict: MetaWorkflow_EvaluationVerdict.INDETERMINATE, consequence: MetaWorkflow_DecisionConsequence.REQUEST_EVIDENCE },\n ],\n hardFloorBindings: [{\n hardFloorRef: 'application-creation:hard-floor/build-plan-task-graph-valid',\n evidenceRequirementRefs: ['application-creation:evidence-requirement/build-plan-task-well-formedness-and-products'],\n }],\n hardFloorFailureConsequence: MetaWorkflow_DecisionConsequence.BLOCK,\n hardFloorShortcutAllowed: false,\n unresolvedConsequence: MetaWorkflow_DecisionConsequence.REQUEST_EVIDENCE,\n evaluatorFailureConsequence: MetaWorkflow_DecisionConsequence.BLOCK,\n },\n authorityRequirement: {\n schemaVersion: 1,\n requirementRef: 'application-creation:authority-requirement/build-plan-coherent-result',\n requirementVersion: 1,\n consequenceClassRef: 'application-creation:authority-consequence/accept-build-plan-task-graph',\n riskClassRef: 'application-creation:risk/build-plan-accepted-family-mutation',\n decisionModePolicyRef: 'application-creation:authority-policy/explicit-operator-confirmation',\n assurancePolicyRef: 'application-creation:authority-policy/local-single-operator',\n channelPolicyRef: 'application-creation:authority-policy/interface-relay',\n principalPolicyRef: null,\n requiredDecisionMode: MetaWorkflow_AuthorityDecisionMode.EXPLICIT_OPERATOR_CONFIRMATION,\n minimumAssurance: MetaWorkflow_AuthorityAssuranceClass.LOCAL_OS_SESSION,\n admittedChannels: [MetaWorkflow_AuthorityInteractionChannel.INTERFACE_RELAY],\n requiredEvidenceRequirementRefs: ['application-creation:evidence-requirement/build-plan-module-and-resource-coverage'],\n expiryPolicyRef: 'application-creation:authority-expiry/current-interface-session',\n noncePolicyRef: 'application-creation:authority-nonce/random-per-request',\n hardFloorPosture: MetaWorkflow_HardFloorPosture.NON_WAIVABLE,\n hardFloorOverrideAllowed: false,\n },\n continuationPolicy: {\n schemaVersion: 1,\n policyRef: 'application-creation:continuation-policy/build-plan-coherent',\n policyVersion: 1,\n mappings: [\n { decisionConsequence: MetaWorkflow_DecisionConsequence.CONTINUE, action: MetaWorkflow_ContinuationAction.CONTINUE },\n { decisionConsequence: MetaWorkflow_DecisionConsequence.REVISE, action: MetaWorkflow_ContinuationAction.REVISE },\n { decisionConsequence: MetaWorkflow_DecisionConsequence.REQUEST_EVIDENCE, action: MetaWorkflow_ContinuationAction.REQUEST_EVIDENCE },\n { decisionConsequence: MetaWorkflow_DecisionConsequence.REQUEST_AUTHORITY, action: MetaWorkflow_ContinuationAction.REQUEST_AUTHORITY },\n { decisionConsequence: MetaWorkflow_DecisionConsequence.BLOCK, action: MetaWorkflow_ContinuationAction.BLOCK },\n ],\n maximumRevisionAttempts: 3,\n maximumEvidenceRequests: 2,\n maximumAuthorityReviews: 1,\n fallbackAction: MetaWorkflow_ContinuationAction.BLOCK,\n },\n} satisfies MetaWorkflowEvaluationTreatmentSource;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.build-decompose/playbook.definition.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,6BAA6B,GAC9B,MAAM,sCAAsC,CAAC;AAE9C;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,2BAA2B;IAClC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,+6DAA+6D;IACz7D,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,aAAa,EAAE,EAAE;QACtE;YACE,MAAM,EAAE,mBAAmB;YAC3B,UAAU,EAAE,EAAE,QAAQ,EAAE,gBAAgB,EAAE;YAC1C,IAAI,EAAE,g1BAAg1B;SACv1B;QACD;YACE,MAAM,EAAE,mBAAmB;YAC3B,UAAU,EAAE,EAAE,QAAQ,EAAE,iBAAiB,EAAE;YAC3C,IAAI,EAAE,2gBAA2gB;SAClhB;QACD;YACE,MAAM,EAAE,mBAAmB;YAC3B,UAAU,EAAE,EAAE,QAAQ,EAAE,kBAAkB,EAAE;YAC5C,IAAI,EAAE,iMAAiM;SACxM;QACD;YACE,MAAM,EAAE,mBAAmB;YAC3B,UAAU,EAAE,EAAE,QAAQ,EAAE,cAAc,EAAE;YACxC,MAAM,EAAE,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE,UAAU,EAAE,aAAa,EAAE,QAAQ,EAAE,QAAQ,EAAE;YAC7G,IAAI,EAAE,0LAA0L;SACjM;QACD;YACE,MAAM,EAAE,mBAAmB;YAC3B,UAAU,EAAE,EAAE,QAAQ,EAAE,oBAAoB,EAAE;YAC9C,MAAM,EAAE,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,wBAAwB,EAAE,EAAE,UAAU,EAAE,mBAAmB,EAAE,QAAQ,EAAE,QAAQ,EAAE;YACnH,IAAI,EAAE,yFAAyF;SAChG;KACF;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,aAAa,EAAE;QAC3B,EAAE,QAAQ,EAAE,SAAS,EAAE;QACvB,EAAE,QAAQ,EAAE,cAAc,EAAE;QAC5B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B,EAAE,QAAQ,EAAE,gBAAgB,EAAE;QAC9B,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,8SAA8S,EAAE;QAClV,EAAE,QAAQ,EAAE,aAAa,EAAE,QAAQ,EAAE,KAAK,EAAE,IAAI,EAAE,2PAA2P,EAAE;QAC/S,EAAE,QAAQ,EAAE,iBAAiB,EAAE,IAAI,EAAE,gYAAgY,EAAE;QACva,EAAE,QAAQ,EAAE,oBAAoB,EAAE,IAAI,EAAE,gPAAgP,EAAE;QAC1R,EAAE,QAAQ,EAAE,kBAAkB,EAAE,IAAI,EAAE,yfAAyf,EAAE;QACjiB,EAAE,QAAQ,EAAE,gBAAgB,EAAE,IAAI,EAAE,qfAAqf,EAAE;QAC3hB,EAAE,QAAQ,EAAE,cAAc,EAAE,IAAI,EAAE,qVAAqV,EAAE;QACzX,EAAE,QAAQ,EAAE,YAAY,EAAE,IAAI,EAAE,kMAAkM,EAAE;KACrO;IACD,SAAS,EAAE;QACT;YACE,QAAQ,EAAE,YAAY;YACtB,WAAW,EAAE,wCAAwC;YACrD,aAAa,EAAE,8nJAA8nJ;SAC9oJ;KACF;IACD,QAAQ,EAAE;QACR,kBAAkB,EAAE,ywBAAywB;QAC7xB,gBAAgB,EAAE,CAAC,iBAAiB,EAAE,eAAe,EAAE,kBAAkB,CAAC;QAC1E,WAAW,EAAE;YACX,qBAAqB;YACrB,uBAAuB;YACvB,2BAA2B;YAC3B,wBAAwB;YACxB,sBAAsB;YACtB,4BAA4B;YAC5B,sBAAsB;YACtB,sBAAsB;YACtB,qBAAqB;YACrB,iCAAiC;SAClC;KACF;IACD,UAAU,EAAE,iBAAiB;IAC7B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,CAAC;KACb;IACD,WAAW,EAAE,eAAe;CACpB,CAAC;AAEX,MAAM,CAAC,MAAM,yBAAyB,GAAG;IACvC,aAAa,EAAE,CAAC;IAChB,aAAa,EAAE,+DAA+D;IAC9E,6GAA6G;IAC7G,sGAAsG;IACtG,iHAAiH;IACjH,wHAAwH;IACxH,gIAAgI;IAChI,kGAAkG;IAClG,sGAAsG;IACtG,kHAAkH;IAClH,2GAA2G;IAC3G,+GAA+G;IAC/G,4HAA4H;IAC5H,qEAAqE;IACrE,0FAA0F;IAC1F,iBAAiB,EAAE,EAAE;IACrB,kBAAkB,EAAE;QAClB,aAAa,EAAE,CAAC;QAChB,WAAW,EAAE,8DAA8D;QAC3E,eAAe,EAAE,CAAC;QAClB,sBAAsB,EAAE,6CAA6C,CAAC,8BAA8B;QACpG,mBAAmB,EAAE,0CAA0C,CAAC,2BAA2B;QAC3F,iBAAiB,EAAE,CAAC,8BAA8B,CAAC,GAAG,EAAE,8BAA8B,CAAC,aAAa,EAAE,8BAA8B,CAAC,OAAO,EAAE,8BAA8B,CAAC,IAAI,CAAC;QAClL,oBAAoB,EAAE,oEAAoE;QAC1F;;;;;;;WAOG;QACH,QAAQ,EAAE;YACV;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,wEAAwE;gBACtF,mFAAmF;gBACnF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,6wCAA6wC;gBAC/wC,eAAe,EAAE,CAAC,iBAAiB,EAAE,oBAAoB,EAAE,sBAAsB,CAAC;gBAClF,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,mFAAmF;wBACnG,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,+FAA+F;oBACtI,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,qQAAqQ;oBAC/S,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,wJAAwJ;oBAC9L,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,0GAA0G;iBAC3J;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,6EAA6E;gBAC3F,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,6iCAA6iC;gBAC/iC,eAAe,EAAE,CAAC,iBAAiB,CAAC;gBACpC,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,wFAAwF;wBACxG,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,wIAAwI;oBAC/K,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,mHAAmH;oBAC7J,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,+UAA+U;oBACrX,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,uFAAuF;iBACxI;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,oEAAoE;gBAClF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,wXAAwX;gBAC1X,eAAe,EAAE,CAAC,iBAAiB,CAAC;gBACpC,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,+EAA+E;wBAC/F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,4JAA4J;oBACnM,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,kKAAkK;oBAC5M,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,sJAAsJ;oBAC5L,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,6FAA6F;iBAC9I;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,kEAAkE;gBAChF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,qlBAAqlB;gBACvlB,eAAe,EAAE,CAAC,iBAAiB,CAAC;gBACpC,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,6EAA6E;wBAC7F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,sIAAsI;oBAC7K,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,kJAAkJ;oBAC5L,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,6OAA6O;oBACnR,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,6FAA6F;iBAC9I;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,iEAAiE;gBAC/E;;;;;;mBAMG;gBACH,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,ohBAAohB;gBACthB,eAAe,EAAE,CAAC,iBAAiB,EAAE,0BAA0B,CAAC;gBAChE,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,4EAA4E;wBAC5F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,2FAA2F;oBAClI,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,8JAA8J;oBACxM,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,oMAAoM;oBAC1O,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,4DAA4D;iBAC7G;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,2EAA2E;gBACzF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,kvBAAkvB;gBACpvB,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,sFAAsF;wBACtG,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,mJAAmJ;oBAC1L,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,sMAAsM;oBAChP,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,+JAA+J;oBACrM,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,kIAAkI;iBACnL;aACF;YACD;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,kEAAkE;gBAChF,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,0cAA0c;gBAC5c,eAAe,EAAE,CAAC,iBAAiB,CAAC;gBACpC,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,6EAA6E;wBAC7F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,yEAAyE;oBAChH,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,2HAA2H;oBACrK,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,sGAAsG;oBAC5I,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,kCAAkC;iBACnF;aACF;YACD;;;;;;;;;;;;;;;;;;;;;;;;eAwBG;YACH;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,+DAA+D;gBAC7E,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,69CAA69C;gBAC/9C,eAAe,EAAE,CAAC,iBAAiB,EAAE,sBAAsB,EAAE,+BAA+B,EAAE,2BAA2B,EAAE,0BAA0B,EAAE,sBAAsB,CAAC;gBAC9K,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,0EAA0E;wBAC1F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,8NAA8N;oBACrQ,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,0MAA0M;oBACpP,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,yMAAyM;oBAC/O,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,mNAAmN;iBACpQ;aACF;YACD;;;;eAIG;YACH;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,yDAAyD;gBACvE,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,8yBAA8yB;gBAChzB,eAAe,EAAE,CAAC,iBAAiB,EAAE,yBAAyB,EAAE,6BAA6B,CAAC;gBAC9F,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,oEAAoE;wBACpF,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,yPAAyP;oBAChS,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,sLAAsL;oBAChO,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,yMAAyM;oBAC/O,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,yDAAyD;iBAC1G;aACF;YACD;;;;eAIG;YACH;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,gEAAgE;gBAC9E,yFAAyF;gBACzF,yGAAyG;gBACzG,0HAA0H;gBAC1H,6GAA6G;gBAC7G,mEAAmE;gBACnE,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,m+CAAm+C;gBACr+C,eAAe,EAAE,CAAC,iBAAiB,EAAE,yBAAyB,EAAE,oBAAoB,EAAE,sBAAsB,EAAE,uBAAuB,CAAC;gBACtI,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,2EAA2E;wBAC3F,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,oLAAoL;oBAC3N,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,4KAA4K;oBACtN,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,2bAA2b;oBACje,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,yDAAyD;iBAC1G;aACF;YACD;;;;;;;eAOG;YACH;gBACE,aAAa,EAAE,CAAC;gBAChB,YAAY,EAAE,qDAAqD;gBACnE,gGAAgG;gBAChG,gBAAgB,EAAE,CAAC;gBACnB,WAAW,EACT,81CAA81C;gBACh2C,wHAAwH;gBACxH,+GAA+G;gBAC/G,eAAe,EAAE,CAAC,iBAAiB,EAAE,oBAAoB,EAAE,sBAAsB,EAAE,0BAA0B,EAAE,sBAAsB,EAAE,yBAAyB,CAAC;gBACjK,oBAAoB,EAAE,CAAC;wBACrB,aAAa,EAAE,CAAC;wBAChB,cAAc,EAAE,gEAAgE;wBAChF,kBAAkB,EAAE,CAAC;wBACrB,IAAI,EAAE,oCAAoC,CAAC,SAAS;wBACpD,UAAU,EAAE,0EAA0E;wBACtF,QAAQ,EAAE,CAAC;wBACX,QAAQ,EAAE,CAAC;wBACX,iBAAiB,EAAE,iFAAiF;wBACpG,kBAAkB,EAAE,6DAA6D;wBACjF,YAAY,EAAE,IAAI;wBAClB,qBAAqB,EAAE,IAAI;wBAC3B,kBAAkB,EAAE,IAAI;wBACxB,oBAAoB,EAAE,IAAI;qBAC3B,CAAC;gBACF,eAAe,EAAE;oBACf,CAAC,8BAA8B,CAAC,IAAI,CAAC,EAAE,qIAAqI;oBAC5K,CAAC,8BAA8B,CAAC,OAAO,CAAC,EAAE,2IAA2I;oBACrL,CAAC,8BAA8B,CAAC,GAAG,CAAC,EAAE,uSAAuS;oBAC7U,CAAC,8BAA8B,CAAC,aAAa,CAAC,EAAE,gHAAgH;iBACjK;aACF;SACA;KACF;IACD,sBAAsB,EAAE;QACtB,aAAa,EAAE,CAAC;QAChB,SAAS,EAAE,mEAAmE;QAC9E,aAAa,EAAE,CAAC;QAChB,4BAA4B,EAAE,CAAC,EAAE,YAAY,EAAE,uDAAuD,EAAE,gBAAgB,EAAE,CAAC,EAAE,CAAC;QAC9H,wBAAwB,EAAE,EAAE,YAAY,EAAE,uDAAuD,EAAE,gBAAgB,EAAE,CAAC,EAAE;QACxH,sBAAsB,EAAE,EAAE,iBAAiB,EAAE,wEAAwE,EAAE,qBAAqB,EAAE,CAAC,EAAE;QACjJ,iBAAiB,EAAE,mDAAmD;QACtE,mBAAmB,EAAE,+DAA+D;QACpF,eAAe,EAAE,CAAC;QAClB,gBAAgB,EAAE,mEAAmE;QACrF,eAAe,EAAE,iEAAiE;QAClF,kBAAkB,EAAE,gEAAgE;KACrF;IACD,uBAAuB,EAAE;QACvB,aAAa,EAAE,CAAC;QAChB,gBAAgB,EAAE,gEAAgE;QAClF,oBAAoB,EAAE,CAAC;QACvB,WAAW,EAAE,CAAC,qEAAqE,CAAC;QACpF,aAAa,EAAE,CAAC,6DAA6D,CAAC;QAC9E,aAAa,EAAE,2EAA2E;QAC1F,qBAAqB,EAAE,4DAA4D;KACpF;IACD,YAAY,EAAE;QACZ,aAAa,EAAE,CAAC;QAChB,OAAO,EAAE,+DAA+D;QACxE,WAAW,EAAE,CAAC;QACd,aAAa,EAAE,sCAAsC,CAAC,sBAAsB;QAC5E,sBAAsB,EAAE,oEAAoE;QAC5F,cAAc,EAAE;YACd,EAAE,OAAO,EAAE,8BAA8B,CAAC,IAAI,EAAE,WAAW,EAAE,gCAAgC,CAAC,iBAAiB,EAAE;YACjH,EAAE,OAAO,EAAE,8BAA8B,CAAC,OAAO,EAAE,WAAW,EAAE,gCAAgC,CAAC,MAAM,EAAE;YACzG,EAAE,OAAO,EAAE,8BAA8B,CAAC,GAAG,EAAE,WAAW,EAAE,gCAAgC,CAAC,MAAM,EAAE;YACrG,EAAE,OAAO,EAAE,8BAA8B,CAAC,aAAa,EAAE,WAAW,EAAE,gCAAgC,CAAC,gBAAgB,EAAE;SAC1H;QACD,iBAAiB,EAAE,CAAC;gBAClB,YAAY,EAAE,6DAA6D;gBAC3E,uBAAuB,EAAE,CAAC,wFAAwF,CAAC;aACpH,CAAC;QACF,2BAA2B,EAAE,gCAAgC,CAAC,KAAK;QACnE,wBAAwB,EAAE,KAAK;QAC/B,qBAAqB,EAAE,gCAAgC,CAAC,gBAAgB;QACxE,2BAA2B,EAAE,gCAAgC,CAAC,KAAK;KACpE;IACD,oBAAoB,EAAE;QACpB,aAAa,EAAE,CAAC;QAChB,cAAc,EAAE,uEAAuE;QACvF,kBAAkB,EAAE,CAAC;QACrB,mBAAmB,EAAE,yEAAyE;QAC9F,YAAY,EAAE,+DAA+D;QAC7E,qBAAqB,EAAE,sEAAsE;QAC7F,kBAAkB,EAAE,6DAA6D;QACjF,gBAAgB,EAAE,uDAAuD;QACzE,kBAAkB,EAAE,IAAI;QACxB,oBAAoB,EAAE,kCAAkC,CAAC,8BAA8B;QACvF,gBAAgB,EAAE,oCAAoC,CAAC,gBAAgB;QACvE,gBAAgB,EAAE,CAAC,wCAAwC,CAAC,eAAe,CAAC;QAC5E,+BAA+B,EAAE,CAAC,mFAAmF,CAAC;QACtH,eAAe,EAAE,iEAAiE;QAClF,cAAc,EAAE,yDAAyD;QACzE,gBAAgB,EAAE,6BAA6B,CAAC,YAAY;QAC5D,wBAAwB,EAAE,KAAK;KAChC;IACD,kBAAkB,EAAE;QAClB,aAAa,EAAE,CAAC;QAChB,SAAS,EAAE,8DAA8D;QACzE,aAAa,EAAE,CAAC;QAChB,QAAQ,EAAE;YACR,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,QAAQ,EAAE,MAAM,EAAE,+BAA+B,CAAC,QAAQ,EAAE;YACpH,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,MAAM,EAAE,MAAM,EAAE,+BAA+B,CAAC,MAAM,EAAE;YAChH,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,gBAAgB,EAAE,MAAM,EAAE,+BAA+B,CAAC,gBAAgB,EAAE;YACpI,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,iBAAiB,EAAE,MAAM,EAAE,+BAA+B,CAAC,iBAAiB,EAAE;YACtI,EAAE,mBAAmB,EAAE,gCAAgC,CAAC,KAAK,EAAE,MAAM,EAAE,+BAA+B,CAAC,KAAK,EAAE;SAC/G;QACD,uBAAuB,EAAE,CAAC;QAC1B,uBAAuB,EAAE,CAAC;QAC1B,uBAAuB,EAAE,CAAC;QAC1B,cAAc,EAAE,+BAA+B,CAAC,KAAK;KACtD;CAC8C,CAAC","sourcesContent":["import type { MetaWorkflowEvaluationTreatmentSource } from '@wildo-ai/saas-backend-lib/meta-workflow-runtime';\nimport {\n MetaWorkflow_AuthorityAssuranceClass,\n MetaWorkflow_AuthorityDecisionMode,\n MetaWorkflow_AuthorityInteractionChannel,\n MetaWorkflow_ContinuationAction,\n MetaWorkflow_DecisionConsequence,\n MetaWorkflow_DecisionRuleBoundaryClass,\n MetaWorkflow_EvaluationAggregationStrategy,\n MetaWorkflow_EvaluationPromptAssemblyStrategy,\n MetaWorkflow_EvaluationVerdict,\n MetaWorkflow_EvidenceRequirementKind,\n MetaWorkflow_HardFloorPosture,\n} from '@wildo-ai/saas-models/meta-workflows';\n\n/**\n * Canonical native declaration for this reusable application-creation method.\n *\n * The structured method remains intentionally rich: its intent, inputs, output\n * contracts, elicitation, deterministic verification and skill routing are the\n * application knowledge a later generic assessment loop composes.\n *\n * The `evaluationTreatmentSource` below is the `build-plan-coherent` reviewer checklist the\n * method carried as prose from the flexible-intelligence hard cut until 2026-09-22 (#1487) —\n * eight invariants that its own closing sentence said \"nothing executes\". Compiled here, the\n * ADVISORY judge reads them against the landed build plan and the domain plan it decomposes,\n * so a resource with no task, a relationship wired before its endpoints, or a product naming\n * only a scaffolded file is reported BEFORE a coding dispatch pays for it. Advisory as\n * everywhere in this lane: the plan is landed when the judge speaks, and a verdict is a note\n * for the creator's `approve_result` review, never a refusal.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.build-decompose\",\n \"version\": \"0.4.6\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / lock or schedule runs / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"domain-plan\" } },\n {\n \"kind\": \"artifact_expected\",\n \"selector\": { \"family\": \"placement-plan\" },\n \"//\": \"SEQUENCING, not readiness — and the distinction is the whole point. `bottom_up.placement-plan` gates on the SAME `domain-plan` this does, so both become eligible at the same instant and decomposing first is legal. This method then says, at its placement section, 'No placement plan? Emit nothing here and say so' — which is honest per task and catastrophic per plan: the build proceeds with ZERO SHELL_PLACEMENT tasks and nothing refuses, so the finished application has no navigation and the cause is three playbooks upstream. `artifact_expected` is the kind written for exactly this (its own doc: use it whenever running early DEGRADES the output rather than invalidating it): the board reports `blocked only by sequencing`, a human may still run it deliberately, and `unmet` finally explains WHY the order matters instead of losing the signal.\"\n },\n {\n \"kind\": \"artifact_expected\",\n \"selector\": { \"family\": \"experience-plan\" },\n \"//\": \"The same shape for the experience plan (#2494): decomposing without it emits no view, no shell or design-system configuration, no milestone and no guidance, so the application ships with no home, the scaffold's colours and the default navigation. Inside the conception and build lanes every child is admitted past SEQUENCING, so this marks the board and a standalone run; what makes the LANE wait is the conception's stop condition, and what routes a plan decomposed without it back is the conception-buildable criterion.\"\n },\n {\n \"kind\": \"artifact_expected\",\n \"selector\": { \"family\": \"integration-plan\" },\n \"//\": \"Same reasoning: without it no worker, minion, provider binding or inbound-channel task is emitted. Its producer gates on the domain plan alone, so it is always producible and always expected.\"\n },\n {\n \"kind\": \"artifact_expected\",\n \"selector\": { \"family\": \"website-plan\" },\n \"when\": { \"selector\": { \"family\": \"capability-composition\" }, \"decision\": \"add-website\", \"equals\": \"NEEDED\" },\n \"//\": \"Expected only when the composition decided a website: an application without one has no website plan, and an unconditional expectation would wait for something its producer never runs.\"\n },\n {\n \"kind\": \"artifact_expected\",\n \"selector\": { \"family\": \"documentation-plan\" },\n \"when\": { \"selector\": { \"family\": \"capability-composition\" }, \"decision\": \"add-technical-doc\", \"equals\": \"NEEDED\" },\n \"//\": \"Expected only when the composition decided a documentation portal, for the same reason.\"\n }\n ],\n \"inputs\": [\n { \"family\": \"domain-plan\" },\n { \"family\": \"roadmap\" },\n { \"family\": \"requirements\" },\n { \"family\": \"feature-drafts\" },\n { \"family\": \"placement-plan\" },\n { \"family\": \"vision-brief\", \"//\": \"Carries the landed COMPLIANCE POSTURE and constraints. Measured 2026-09-04 (#309): without this input the decomposer, given a landed GDPR/ePrivacy posture, produced ZERO posture-derived tasks — the obligations lived in a family the brief never carried. No intent slice: the posture must arrive whole.\" },\n { \"family\": \"brand-brief\", \"render\": \"map\", \"//\": \"Whether the application HAS a brand decides whether the `logo` generation step is authored (method: companion generation steps; checklist invariant 6). The method only needs to know it exists, so it reads the brand as a map, not its content (#1424).\" },\n { \"family\": \"experience-plan\", \"//\": \"The application's own surfaces and its shell composition (#1493). Each view becomes a task over the product kind its KIND names, each configuration an APPLICATION_FRONTEND_CONFIG task, each planned milestone an APPLICATION_MILESTONE task and each planned piece of guidance an APPLICATION_GUIDANCE task — with the skill taken from the experience plan's total maps, never chosen here.\" },\n { \"family\": \"documentation-plan\", \"//\": \"Which chapters the documentation portal carries (#1494). Each becomes a DOCUMENTATION_CHAPTER task under the TECHNICAL_DOCUMENTATION target, whose scope prohibits the portal's generated tree. A NOT_APPLICABLE plan, or none, emits nothing.\" },\n { \"family\": \"integration-plan\", \"//\": \"What runs beside the backend and what the application reaches out to (#1495). Each worker, minion and provider binding becomes a task over its own target kind, with the skill taken from the three total maps rather than chosen here — which is what makes the worker, minion and provider skills reachable. Each declared inbound channel becomes an INBOUND_CHANNEL_HANDLER task in the module its messages concern (#1832), routed to `inbound-channels` by the dispatch. No plan, or an empty one, emits nothing.\" },\n { \"family\": \"business-model\", \"//\": \"The pricing plans the application sells (#1835). Each becomes a product of the billing catalogue — one BILLING_CATALOG task producing an APPLICATION_BILLING_PRODUCT per plan — so the backend has something to sell and the website's pricing page reads the catalogue instead of re-typing the plans' prices. Measured on the first journey-built application: with no such task its catalogue stayed EMPTY and the website agent hand-copied the prices. No business model, or one with no plans, emits nothing.\" },\n { \"family\": \"website-plan\", \"//\": \"What the marketing site says, page by page (#1492). The decomposer turns each page into a WEBSITE_PAGE task and each section into a WEBSITE_SECTION task bound to the skill its KIND names — so the website skills are reached by construction rather than by a model recalling folder names. A NOT_APPLICABLE plan, or none at all, emits nothing.\" },\n { \"family\": \"build-plan\", \"//\": \"Its own family: its method refines its own prior output and keeps its refs, so it must be GIVEN that output (#1430). Input, not precondition: a first run, with no prior output, stays eligible.\" }\n ],\n \"outputs\": [\n {\n \"family\": \"build-plan\",\n \"schemaRef\": \"saas-specifications:BuildPlanTaskGraph\",\n \"description\": \"The build decomposition — an ORDERED set of coding-agent build tasks (a task graph) that turns the approved domain plan into a sequence of buildable units. Each task carries: a stable task ref, the target it builds (a module, a resource + one of its build stages, a relationship, a companion-generation step, a shell-surface placement config), WHAT IT PRODUCES (`produces` — the artifacts whose presence in the finished application proves the task landed; distinct from the target, which is a write scope several tasks may share), the ONE functional topic it belongs to (a real MetaWorkflow_FunctionalTopic value), the skill(s) that carry its technical HOW (real folders from the app-knowledge skill catalog, resolved via the skills router), and its ordering intent (which tasks must precede it — expressed as typed prerequisiteTaskRefs, which the host resolves for readiness). Author prerequisiteTaskRefs to express the actual dependencies, using these planning considerations: (a) the cross-app topic dependency edges (model_domain_graph before define_interaction_semantics before app-level shape_user_experience before extend_application before connect_runtime_and_external_capabilities; foundation and assemble/verify are owned by sibling playbooks) and (b) the per-resource stage sequence schema -> config -> ui-behavior -> spec — which deliberately CROSSES topics (ui-behavior is shape_user_experience; the spec is a model_domain_graph documentation capstone ordered last) and so is not monotonic on axis (a); a roadmap-driven MVP-first preference breaks ties within a band. TYPED since the flexible-intelligence Block 3: the `_core` build-task-graph contract (`BuildPlanTaskGraph` — `tasks[]` with a stable `taskRef`, a closed `BuildPlanTaskTargetKind` target (MODULE / RESOURCE_STAGE / RELATIONSHIP / COMPANION_GENERATION_STEP / SHELL_PLACEMENT / MODULE_FRONTEND / MODULE_BACKEND / APPLICATION_FRONTEND_CONFIG / WEBSITE / TECHNICAL_DOCUMENTATION / WORKER / MINION / PROVIDER_BINDING / BILLING_CATALOG), a `produces` list over the closed `BuildPlanTaskProductKind` vocabulary (the resource products — schema fields, registration, ui-behavior, specification, relationship, operation, composite / custom / chart view, PDF template; the application products — view, document, module, frontend configuration, custom component, milestone, guidance; and the runtime products — worker jobs, minion behaviours, provider binding, website page and section, documentation chapter, inbound channel handler; and the billing product the catalogue sells), exactly one `functionalTopic`, `skillRefs`, DECLARED `prerequisiteTaskRefs` the host resolves for readiness, and traceability `servesRefs`) is the family schema; the provider answers the strict `BuildPlanTaskGraphGeneration` shape and the trusted runtime stamps refs and version. The task never carries paths, commands, prompts or runtime controls — the dispatch host derives mutation scope and verification from the target kind. `validateBuildPlanTaskGraph` is the deterministic validator. A task's products must name something COMPOSITION DOES NOT ALREADY WRITE (the fields a schema gains, not its scaffolded file) and no two tasks may claim the same artifact — that is what makes landing decidable; a coding task declaring none is reported as `TASK_DECLARES_NO_PRODUCT`. If such a task has a COMPLETED durable run, the host advances past it but reports its ref in `unverifiableLandedTaskRefs`: it ran, but its output is not proven. Without that completed run it remains unlanded. Companion-generation tasks use their own landed conditions; migrations require the schema plan to be in sync. Product probes inspect committed files and named declarations, not runtime correctness. Two things are HARD FLOORS: a prerequisite cycle, and a resource stage that declares its predecessor stage in the SAME graph without depending on it — dispatch order comes solely from `prerequisiteTaskRefs`, so an undeclared stage edge lets the host author a resources-config for a schema that has not landed. A predecessor stage that is ABSENT from the plan is an authoring WARNING instead, because a plan may legitimately author one stage of a resource the tree already carries; the coherence reviewer checklist (`build-plan-coherent`, in the method) remains the semantic check and the creator's approve_result review the trust floor. Consumed by the bottom-up DISPATCH-ORCHESTRATION playbook (which dispatches the tasks through the coding-agent contract in parallel waves, up to the application's build parallelism at once) and the SCALE playbook (which describes how those waves are scheduled, interleaved with the companion generation steps, and reconciled) — both downstream of this decomposition.\"\n }\n ],\n \"method\": {\n \"//contextSources\": \"WORKSPACE_TRUTH — this playbook plans against CODE, not against definition artifacts: it needs real module ids and per-resource present schema fields, or it invents ids that do not resolve and every task it emits fails at dispatch. SKILL_CATALOG — its method routes THROUGH the skills router and binds every emitted task to a skill folder, so it must choose from the real set; measured 2026-08-27 it was choosing from recall, and a dangling skill ref is a task the dispatch playbook cannot run. COHERENCE_REPORT — the computed cross-family findings over the conception it builds on (dangling edges into the domain plan, a composition surface no plan realises), so its judge can tell a conception fault from its own (#1638): the build lane routes the first back to conception.\",\n \"contextSources\": [\"workspace_truth\", \"skill_catalog\", \"coherence_report\"],\n \"skillRefs\": [\n \"resource-add-module\",\n \"resource-add-resource\",\n \"resource-schema-authoring\",\n \"resource-config-wiring\",\n \"resource-ui-behavior\",\n \"frontend-component-catalog\",\n \"spec-resource-update\",\n \"module-relationships\",\n \"module-registration\",\n \"application-database-migrations\"\n ]\n },\n \"executor\": \"companion_agent\",\n \"approval\": \"approve_result\",\n \"budget\": {\n \"maxRuns\": 3\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n\nexport const evaluationTreatmentSource = {\n schemaVersion: 1,\n definitionRef: 'application-creation:evaluation-treatment/build-plan-coherent',\n // 2 since #1638: `conception-buildable` faults the CONCEPTION, not the plan, which changes what a GAP means.\n // 3: relationship coverage leaves a relationship to an undeclared resource to `conception-buildable`.\n // 4: experience coverage (#2235) — the experience plan's surfaces each have a task, and its absence is recorded.\n // 5: module-and-resource coverage also asks for demonstration data (#2234), so a built application does not open empty.\n // 6: experience coverage keys its absence case on the accepted-truth statement, not on a heading it did not see (#2235 review).\n // 7: module-and-resource coverage orders a linked demo seed after the seed it references (#2392).\n // 8: role coverage (#2490) — a requirement naming user groups is served by an APPLICATION_ROLES task.\n // 9: interaction coverage (#2493) — a requirement verb beyond the default verbs is served by an interaction task.\n // 10: interaction coverage also requires a task per lifecycle transition the domain plan declares (#2491).\n // 11: interaction coverage also requires the UPDATE freeze of a lifecycle with final states (#2491 review F4).\n // 12: that freeze lives in the objective of the transition into a final state, never in an `update` task (#2491 re-review).\n // 13: locked states are frozen like final ones (#2491 re-review M1).\n // 14: conception-buildable reports an absent experience plan as a conception gap (#2494).\n definitionVersion: 14,\n evaluationProtocol: {\n schemaVersion: 1,\n protocolRef: 'application-creation:evaluation-protocol/build-plan-coherent',\n protocolVersion: 1,\n promptAssemblyStrategy: MetaWorkflow_EvaluationPromptAssemblyStrategy.CANONICAL_PROTOCOL_EVIDENCE_V1,\n aggregationStrategy: MetaWorkflow_EvaluationAggregationStrategy.WORST_VERDICT_PRECEDENCE_V1,\n verdictPrecedence: [MetaWorkflow_EvaluationVerdict.GAP, MetaWorkflow_EvaluationVerdict.INDETERMINATE, MetaWorkflow_EvaluationVerdict.CONCERN, MetaWorkflow_EvaluationVerdict.PASS],\n aggregationPolicyRef: 'application-creation:aggregation/worst-build-plan-coherent-verdict',\n /*\n * One criterion per invariant of the method's `build-plan-coherent` checklist (its invariants 2 and 2b\n * share one criterion, because well-formedness and product declaration are read off the same task).\n * `assessesAspects` scopes a criterion to the families it actually reads (#1423): coverage reads the\n * domain plan's modules and resources beside the tasks; relationship coverage reads its relationship\n * drafts; the interleave criterion names no aspects because it needs the brand MAP and the store\n * selection, which are not aspects of a family, and so reads the whole evidence.\n */\n criteria: [\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-module-and-resource-coverage',\n // 3: a linked demo seed not ordered after the seed it references is a gap (#2392).\n criterionVersion: 3,\n instruction:\n \"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). Seeding is covered the same way: a plan whose domain has main resources and no APPLICATION_DATA_SEED task of content DEMONSTRATION is a concern — the application would open empty, with nothing a creator can judge or show (#2234). A seed task whose rows point at rows another seed writes (a contact's customer, a quote's customer) and that is not ordered after that seed's task is a gap: the seed links them with referenceDataSeedRow and dependsOn, which resolve only against rows already written (#2392).\",\n assessesAspects: ['build-plan.task', 'domain-plan.module', 'domain-plan.resource'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-module-and-resource-coverage',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every domain-plan resource has build tasks and every moduleRef resolves to a declared module.',\n [MetaWorkflow_EvaluationVerdict.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), a supporting resource's coverage is thin, or no DEMONSTRATION data seed gives the main resources sample rows.\",\n [MetaWorkflow_EvaluationVerdict.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).',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-task-well-formedness-and-products',\n criterionVersion: 1,\n instruction:\n \"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.\",\n assessesAspects: ['build-plan.task'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-task-well-formedness-and-products',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every task is bound to a real topic and skill, declares products composition does not already write, and no artifact is claimed twice.',\n [MetaWorkflow_EvaluationVerdict.CONCERN]: \"A task's products are meaningful but thinly described, or a generation step's landed condition is stated loosely.\",\n [MetaWorkflow_EvaluationVerdict.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.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The skill catalog or the task list is not in evidence, so bindings cannot be checked.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-per-resource-stage-order',\n criterionVersion: 1,\n instruction:\n '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.',\n assessesAspects: ['build-plan.task'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-per-resource-stage-order',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: \"Every resource's stages are ordered schema -> config -> ui-behavior -> spec through declared prerequisites, and every main resource has schema and config.\",\n [MetaWorkflow_EvaluationVerdict.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.',\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'Tasks do not carry enough target and prerequisite detail to reconstruct per-resource order.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-topic-dependency-order',\n criterionVersion: 1,\n instruction:\n \"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.\",\n assessesAspects: ['build-plan.task'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-topic-dependency-order',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every cross-topic dependency is honoured by declared prerequisites, and the per-resource ui-behavior exception is applied correctly.',\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'Topics or prerequisites are missing from the evidence, so ordering cannot be reconstructed.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-relationship-coverage',\n /*\n * Version 2 (2026-09-25): a relationship whose endpoint no module declares is excluded. Measured on\n * scratch-journey with a planted relationship to an undeclared resource: `conception-buildable` gave\n * GAP and version 1 of this criterion ALSO gave GAP (\"no wiring task\"). This one's GAP re-opens the\n * decomposer inside the build lane, so the lane re-ran decomposition on a relationship no task can\n * wire, up to its iteration cap, before the conception verdict reached the root.\n */\n criterionVersion: 2,\n instruction:\n \"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.\",\n assessesAspects: ['build-plan.task', 'domain-plan.relationship'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-relationship-coverage',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: \"Every relationship draft has one wiring task, ordered after both endpoints' schema tasks.\",\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.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.\",\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: \"The domain plan's relationship drafts are not in evidence.\",\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-companion-generation-interleave',\n criterionVersion: 1,\n instruction:\n '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 an i18n-translations step: the dispatch host derives it after i18n-labels. Do NOT flag the absence of a seeds GENERATION step: none exists, and seeding is an APPLICATION_DATA_SEED coding task judged under module-and-resource coverage.',\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-companion-generation-interleave',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists.',\n [MetaWorkflow_EvaluationVerdict.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.',\n [MetaWorkflow_EvaluationVerdict.GAP]: 'A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or a seeds generation step), or a generation step declares products.',\n [MetaWorkflow_EvaluationVerdict.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.',\n },\n },\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-decomposition-boundary',\n criterionVersion: 1,\n instruction:\n '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 (dispatch locking and concurrency, 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.',\n assessesAspects: ['build-plan.task'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-decomposition-boundary',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Every task describes WHAT it builds and none describes how it executes.',\n [MetaWorkflow_EvaluationVerdict.CONCERN]: 'A task brief drifts toward execution detail or names a concrete field type or foreign key the coding agent should decide.',\n [MetaWorkflow_EvaluationVerdict.GAP]: 'A task that specifies dispatch mechanics, concurrency, or authors schema or code in the plan itself.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'Task briefs are not in evidence.',\n },\n },\n /*\n * The experience plan's surfaces each have a task, and an ABSENT experience plan is recorded rather than\n * silent (#2235).\n *\n * Measured on app-creation-test-004 (2026-10-01): `bottom_up.experience-plan` was refused twice, the build\n * plan was decomposed anyway, and the application shipped with no app-level views, no onboarding and no\n * milestones. The method is right to emit no such task without a plan (\"an improvised surface is the state\n * this family replaced\"), and the plan read as complete — no criterion here looked at the experience plan.\n *\n * Why an absent plan is PASS with a marked rationale, and not a weaker verdict: this treatment DECLARES every\n * non-PASS verdict as routing back to the decomposer (CONCERN and GAP → REVISE, INDETERMINATE →\n * REQUEST_EVIDENCE, which ends in BLOCK), and the decomposer cannot produce an upstream family by revising.\n * Corrected 2026-10-05 (#2494 review G4): those consequences are declarations only — the treatment compiler\n * copies the continuation policy and nothing acts on it, and the judge is advisory. What a verdict DOES today\n * is what a composite's `reopenOnVerdict` table says, keyed on the criterion and the verdict; the build lane's\n * table re-opens this decomposer for module and relationship coverage only. So the PASS rule keeps this\n * criterion's verdict truthful against the declared treatment, not against a live routing.\n *\n * The absence is still not left at a marked PASS (#2494): it is a CONCEPTION fault, and `conception-buildable`\n * reports it as a GAP. The root's `reopenOnVerdict` re-opens the conception and build lanes on exactly that GAP\n * (exported by the build lane as `judge:bottom_up.build-decompose`), which is the routing that exists. The\n * `artifact_expected` precondition on the family, rejected here before because every lane child is admitted\n * past SEQUENCING, was added anyway for the board and standalone runs; what makes the lane wait is the\n * conception's stop condition, which now names the experience plan.\n */\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-experience-coverage',\n criterionVersion: 3,\n instruction:\n \"Determine whether every surface the experience plan decides has its build task: one task per VIEW (target MODULE_FRONTEND on the view's module, a product of the view's kind carrying the plan's viewRef verbatim), one APPLICATION_FRONTEND_CONFIG task per CONFIGURATION, one APPLICATION_MILESTONE task per planned MILESTONE, and one APPLICATION_GUIDANCE task per planned piece of GUIDANCE (an onboarding document's objective naming the hostViewRef that embeds it). When the plan decides a HOME, the GLOBAL_VIEWS configuration task's objective must set it: name `homeDefinitionFactory` and the home's view or resource operation. A view, configuration, milestone or guidance entry with no task, or a decided home no objective sets, is a gap: the application would ship without it (a missing home opens on the framework's welcome page) while the plan reads complete. Never conclude the plan is absent because this criterion's own slice does not show it: the accepted application truth either renders the experience plan or says it has none. When the accepted application truth STATES that `experience-plan` has no accepted content, the decomposer has rightly emitted none of these tasks and cannot repair the absence by revising: record PASS, and begin the rationale with the words 'NO EXPERIENCE PLAN:' followed by what the application will therefore lack (its app-level views, its shell and navigation configuration, its milestones and its onboarding), so the absence is on the record instead of silent.\",\n assessesAspects: ['build-plan.task', 'experience-plan.view', 'experience-plan.configuration', 'experience-plan.milestone', 'experience-plan.guidance', 'experience-plan.home'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-experience-coverage',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 1,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: \"Every view, configuration, milestone and guidance entry of the experience plan has its task — or no experience plan is in evidence, and the rationale begins 'NO EXPERIENCE PLAN:' and names what the application will lack.\",\n [MetaWorkflow_EvaluationVerdict.CONCERN]: \"Every entry has a task, but a task's objective drops what the plan decided for it: a view's reusesComponentRefs, a milestone's moment, a guidance entry's gate, or an onboarding document's hostViewRef.\",\n [MetaWorkflow_EvaluationVerdict.GAP]: 'A view, configuration, milestone or guidance entry the experience plan declares has no task, a decided home is set by no task\\'s objective, or a view task carries a viewRef the plan does not declare.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan is not in evidence, or the accepted application truth neither renders the experience plan nor states that it has none. (A STATED absence is not indeterminate: it is the PASS case above, marked.)',\n },\n },\n /*\n * #2490: app-creation-test-005's requirement \"office and field users see different areas\" was served by\n * per-resource config tasks that all left every verb on ORG_MEMBER, plus an access-role RESOURCE nothing\n * reads. No criterion asked whether the plan could enforce a role at all.\n */\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-role-coverage',\n criterionVersion: 1,\n instruction:\n \"Determine whether every requirement that names groups of users with different access (office and field staff, technicians, accountants, read-only reviewers, 'only administrators may …') is served by an APPLICATION_ROLES task producing one APPLICATION_ROLE per group that no core role already covers (ORG_OWNER, ORG_ADMIN, ORG_MANAGER, ORG_MEMBER, ORG_GUEST), ordered after the config tasks of the resources whose operations it narrows. A requirement satisfied by the core roles alone (only administrators may delete) needs no APPLICATION_ROLES task, but the config tasks of the resources it covers must say which operations are restricted. A task, product or resource that models roles, permissions or role assignments as DATA (an access-role or permission resource) is never a way to satisfy such a requirement.\",\n assessesAspects: ['build-plan.task', 'requirements.functional', 'requirements.non-functional'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-role-coverage',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 1,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'No requirement names user groups with different access, or every such group has an APPLICATION_ROLE product of an APPLICATION_ROLES task ordered after the config tasks it narrows, or is covered by a core role the relevant config tasks restrict to.',\n [MetaWorkflow_EvaluationVerdict.CONCERN]: 'Each group has its role, but the APPLICATION_ROLES task is ordered before a config task of a resource it narrows, or its objective does not say which operations each role may call.',\n [MetaWorkflow_EvaluationVerdict.GAP]: 'A requirement names a user group no core role covers and no APPLICATION_ROLE product declares, or the plan answers a role requirement with a task or resource that stores roles or permissions as data.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan or the requirements are not in evidence.',\n },\n },\n /*\n * #2493: app-creation-test-004 (92 tasks) and -005 (86) planned no operation, document or email at all,\n * and every lifecycle step shipped as a status users edit by hand. Each requirement was \"served\" by CRUD\n * tasks citing it in servesRefs, and no criterion weighed whether those tasks could realise its verbs.\n */\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/build-plan-interaction-coverage',\n // 2: every lifecycle transition the domain plan declares has its operation task (#2491).\n // 3: every lifecycle with final states has its UPDATE freeze, as the method places it (#2491 review F4).\n // 4: the freeze lives in the objective of the transition into a final state, never in an `update` task (#2491 re-review).\n // 5: locked states (no edits, may still move on) are frozen the same way as final ones (#2491 re-review M1),\n // in both its lifecycle clause and its requirement-verb clause.\n criterionVersion: 5,\n instruction:\n \"Determine whether every transition the domain plan's lifecycles declare has a RESOURCE_OPERATION task on its resource (plus a MODULE_BACKEND task when the transition creates another resource), whether, for every lifecycle with locked or final states, the objective of a transition task moving into each of them restricts that resource's UPDATE to the states that are neither locked nor final (a separate RESOURCE_OPERATION named update is not a realisation: the scaffold already writes update, so it reads as built before it runs), and whether every functional acceptance criterion whose verb goes beyond the default resource verbs (create, read, update, list, delete) is served by a task able to realise it: a state change ('an accepted quote', 'issue the invoice', 'mark it paid') by a RESOURCE_OPERATION on the resource whose state changes; one record creating or filling another ('an accepted quote creates a job') by a RESOURCE_OPERATION on the source resource with a MODULE_BACKEND implementation; a record that must stop changing by the objective of the transition task into the locked or final state; a produced document by a PDF_TEMPLATE task; a sent message by the email generation step plus the triggering operation's task. A task citing the requirement in servesRefs does not realise a verb its kind cannot carry: a config or schema task leaves a status freely editable. A value derived from other records (a next action, an overdue flag) planned as a stored field is not a realisation either.\",\n assessesAspects: ['build-plan.task', 'requirements.functional', 'domain-plan.module', 'domain-plan.resource', 'domain-plan.lifecycle'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/build-plan-interaction-coverage',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 1,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'No functional criterion names a verb beyond the default resource verbs, or each such verb is served by a task of a kind that can realise it, naming the requirement in servesRefs.',\n [MetaWorkflow_EvaluationVerdict.CONCERN]: 'Every verb has a task, but a derived value (a next action, an overdue flag) is planned as a stored field, or an operation task does not say which states it moves between.',\n [MetaWorkflow_EvaluationVerdict.GAP]: 'A declared lifecycle transition has no operation task, or no transition task into a locked or final state carries the UPDATE freeze (or it is planned as a separate update task); or a state change, a record creating another, a record that must stop changing, a produced document or a sent message named by a functional criterion has no task of a kind that can realise it — including a workflow-describing plan with no interaction task at all.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan or the requirements are not in evidence.',\n },\n },\n /*\n * The one criterion that faults the CONCEPTION rather than the plan (#1638). Every other criterion\n * here is the decomposer's own, and its GAP re-opens the decomposer. This one says the plan could not\n * be right however it was decomposed, because what it rests on is wrong — and the root routes that\n * GAP back to the conception lane through the build lane's exported verdict. Keeping it separate from\n * module-and-resource coverage is the point: a resource the plan merely FORGOT is not a conception\n * fault, and re-running the conception for it would be the most expensive way to fix an omission.\n */\n {\n schemaVersion: 1,\n criterionRef: 'application-creation:criterion/conception-buildable',\n // 2: an absent experience plan is a conception gap, routed back to the conception lane (#2494).\n criterionVersion: 2,\n instruction:\n \"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, or (c) the accepted application truth STATES that `experience-plan` has no accepted content: every application with a frontend has an experience, and without its plan the build has no home, no design system from the brand, no navigation decision and no application views, which no revision of this plan can supply; the same when it STATES that `integration-plan` has none, since then nothing decided whether the application runs workers, minions, provider bindings or inbound channels (an integration plan that decides none is content, not an absence). 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.\",\n // An aspect of each family clause (c) reads, so the slice states an ABSENT experience or integration plan and points at\n // the accepted truth (#2494 review G1, G6); a criterion naming no aspect of a family is told nothing about it.\n assessesAspects: ['build-plan.task', 'domain-plan.module', 'domain-plan.resource', 'domain-plan.relationship', 'experience-plan.view', 'integration-plan.worker'],\n evidenceRequirements: [{\n schemaVersion: 1,\n requirementRef: 'application-creation:evidence-requirement/conception-buildable',\n requirementVersion: 1,\n kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,\n subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',\n minCount: 2,\n maxCount: 8,\n coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',\n freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',\n conditionRef: null,\n independencePolicyRef: null,\n diversityPolicyRef: null,\n aggregationPolicyRef: null,\n }],\n verdictGuidance: {\n [MetaWorkflow_EvaluationVerdict.PASS]: 'Everything the conception declares has a build target, and the coherence report shows nothing in it the build would have to invent.',\n [MetaWorkflow_EvaluationVerdict.CONCERN]: 'A conception element is expressible only awkwardly, or the coherence report shows an unrealised item that reads as a deliberate deferral.',\n [MetaWorkflow_EvaluationVerdict.GAP]: 'The domain plan declares something no build target can express, the coherence report shows a dangling reference or unrealised decision in the conception that the build cannot proceed past without inventing it, or the accepted truth states the experience plan or the integration plan is absent.',\n [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The domain plan or the coherence report is not in evidence, so the conception cannot be read against the plan.',\n },\n },\n ],\n },\n evaluatorBindingPolicy: {\n schemaVersion: 1,\n policyRef: 'application-creation:evaluator-binding-policy/build-plan-coherent',\n policyVersion: 1,\n admissibleEvaluatorSelectors: [{ evaluatorRef: 'meta-workflow:evaluator/structured-semantic-coherence', evaluatorVersion: 1 }],\n defaultEvaluatorSelector: { evaluatorRef: 'meta-workflow:evaluator/structured-semantic-coherence', evaluatorVersion: 1 },\n outputContractSelector: { outputContractRef: 'meta-workflow:output-contract/structured-semantic-evaluation-candidate', outputContractVersion: 1 },\n fallbackPolicyRef: 'application-creation:evaluator-policy/fail-closed',\n escalationPolicyRef: 'application-creation:evaluator-policy/request-explicit-review',\n maximumAttempts: 2,\n timeoutPolicyRef: 'application-creation:evaluator-policy/bounded-semantic-evaluation',\n budgetPolicyRef: 'application-creation:evaluator-policy/current-work-cycle-budget',\n selectionPolicyRef: 'application-creation:evaluator-policy/scoped-risk-and-evidence',\n },\n decisionPointDefinition: {\n schemaVersion: 1,\n decisionPointRef: 'application-creation:decision-point/build-plan-coherent-result',\n decisionPointVersion: 1,\n triggerRefs: ['application-creation:trigger/build-plan-task-graph-staged-and-valid'],\n hardFloorRefs: ['application-creation:hard-floor/build-plan-task-graph-valid'],\n riskPolicyRef: 'application-creation:risk-policy/scoped-application-and-execution-context',\n significancePolicyRef: 'application-creation:significance-policy/build-plan-change',\n },\n decisionRule: {\n schemaVersion: 1,\n ruleRef: 'application-creation:decision-rule/build-plan-coherent-result',\n ruleVersion: 1,\n boundaryClass: MetaWorkflow_DecisionRuleBoundaryClass.QUALITY_INTERPRETATION,\n evidenceAggregationRef: 'application-creation:aggregation/worst-build-plan-coherent-verdict',\n resultMappings: [\n { verdict: MetaWorkflow_EvaluationVerdict.PASS, consequence: MetaWorkflow_DecisionConsequence.REQUEST_AUTHORITY },\n { verdict: MetaWorkflow_EvaluationVerdict.CONCERN, consequence: MetaWorkflow_DecisionConsequence.REVISE },\n { verdict: MetaWorkflow_EvaluationVerdict.GAP, consequence: MetaWorkflow_DecisionConsequence.REVISE },\n { verdict: MetaWorkflow_EvaluationVerdict.INDETERMINATE, consequence: MetaWorkflow_DecisionConsequence.REQUEST_EVIDENCE },\n ],\n hardFloorBindings: [{\n hardFloorRef: 'application-creation:hard-floor/build-plan-task-graph-valid',\n evidenceRequirementRefs: ['application-creation:evidence-requirement/build-plan-task-well-formedness-and-products'],\n }],\n hardFloorFailureConsequence: MetaWorkflow_DecisionConsequence.BLOCK,\n hardFloorShortcutAllowed: false,\n unresolvedConsequence: MetaWorkflow_DecisionConsequence.REQUEST_EVIDENCE,\n evaluatorFailureConsequence: MetaWorkflow_DecisionConsequence.BLOCK,\n },\n authorityRequirement: {\n schemaVersion: 1,\n requirementRef: 'application-creation:authority-requirement/build-plan-coherent-result',\n requirementVersion: 1,\n consequenceClassRef: 'application-creation:authority-consequence/accept-build-plan-task-graph',\n riskClassRef: 'application-creation:risk/build-plan-accepted-family-mutation',\n decisionModePolicyRef: 'application-creation:authority-policy/explicit-operator-confirmation',\n assurancePolicyRef: 'application-creation:authority-policy/local-single-operator',\n channelPolicyRef: 'application-creation:authority-policy/interface-relay',\n principalPolicyRef: null,\n requiredDecisionMode: MetaWorkflow_AuthorityDecisionMode.EXPLICIT_OPERATOR_CONFIRMATION,\n minimumAssurance: MetaWorkflow_AuthorityAssuranceClass.LOCAL_OS_SESSION,\n admittedChannels: [MetaWorkflow_AuthorityInteractionChannel.INTERFACE_RELAY],\n requiredEvidenceRequirementRefs: ['application-creation:evidence-requirement/build-plan-module-and-resource-coverage'],\n expiryPolicyRef: 'application-creation:authority-expiry/current-interface-session',\n noncePolicyRef: 'application-creation:authority-nonce/random-per-request',\n hardFloorPosture: MetaWorkflow_HardFloorPosture.NON_WAIVABLE,\n hardFloorOverrideAllowed: false,\n },\n continuationPolicy: {\n schemaVersion: 1,\n policyRef: 'application-creation:continuation-policy/build-plan-coherent',\n policyVersion: 1,\n mappings: [\n { decisionConsequence: MetaWorkflow_DecisionConsequence.CONTINUE, action: MetaWorkflow_ContinuationAction.CONTINUE },\n { decisionConsequence: MetaWorkflow_DecisionConsequence.REVISE, action: MetaWorkflow_ContinuationAction.REVISE },\n { decisionConsequence: MetaWorkflow_DecisionConsequence.REQUEST_EVIDENCE, action: MetaWorkflow_ContinuationAction.REQUEST_EVIDENCE },\n { decisionConsequence: MetaWorkflow_DecisionConsequence.REQUEST_AUTHORITY, action: MetaWorkflow_ContinuationAction.REQUEST_AUTHORITY },\n { decisionConsequence: MetaWorkflow_DecisionConsequence.BLOCK, action: MetaWorkflow_ContinuationAction.BLOCK },\n ],\n maximumRevisionAttempts: 3,\n maximumEvidenceRequests: 2,\n maximumAuthorityReviews: 1,\n fallbackAction: MetaWorkflow_ContinuationAction.BLOCK,\n },\n} satisfies MetaWorkflowEvaluationTreatmentSource;\n"]}
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build-dispatch/playbook.definition.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,6BAA6B,EAC9B,MAAM,sCAAsC,CAAC;AAE9C;;;;;;;;;;GAUG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwCrB,CAAC;AAEX;;;;;;;;;;GAUG;AACH,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsKW,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.build-dispatch/playbook.definition.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,6BAA6B,EAC9B,MAAM,sCAAsC,CAAC;AAE9C;;;;;;;;;;GAUG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwCrB,CAAC;AAEX;;;;;;;;;;GAUG;AACH,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsKW,CAAC"}
@@ -75,10 +75,14 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase } from '@wildo-ai/saas-spe
75
75
  * as INPUTS, so they are read when the build plan is authored. A surface planned after decomposition
76
76
  * is a surface the build plan has no task for.
77
77
  *
78
- * **Declared as inputs and NOT as preconditions, on the decomposer's side and on this lane's.** An
79
- * application with no website has no website plan, and a build that refused to decompose without one
80
- * would refuse every application that does not want a site. The capability composition is what says
81
- * whether each surface exists — which is why two of the three gate on it and the lane runs it first.
78
+ * **Never a READINESS precondition, on the decomposer's side or on this lane's.** An application with no
79
+ * website has no website plan, and a build that refused to decompose without one would refuse every
80
+ * application that does not want a site. The capability composition is what says whether each surface
81
+ * exists — which is why two of the three gate on it and the lane runs it first. Since #2494 the decomposer
82
+ * EXPECTS each plan (`artifact_expected`, a SEQUENCING predicate): the experience and integration plans
83
+ * unconditionally, the website and documentation plans only when the composition decided `add-website` /
84
+ * `add-technical-doc` NEEDED (its `when` clause). Inside a lane every child is admitted past sequencing, so
85
+ * that marks the board and a standalone run; what holds THIS lane is its stop condition.
82
86
  *
83
87
  * ## `capability-composition` joined the lane the day it landed (#1491, 2026-09-22)
84
88
  *
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.conception/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2FG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+F9B,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.conception/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+FG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkG9B,CAAC"}
@@ -75,10 +75,14 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-sp
75
75
  * as INPUTS, so they are read when the build plan is authored. A surface planned after decomposition
76
76
  * is a surface the build plan has no task for.
77
77
  *
78
- * **Declared as inputs and NOT as preconditions, on the decomposer's side and on this lane's.** An
79
- * application with no website has no website plan, and a build that refused to decompose without one
80
- * would refuse every application that does not want a site. The capability composition is what says
81
- * whether each surface exists — which is why two of the three gate on it and the lane runs it first.
78
+ * **Never a READINESS precondition, on the decomposer's side or on this lane's.** An application with no
79
+ * website has no website plan, and a build that refused to decompose without one would refuse every
80
+ * application that does not want a site. The capability composition is what says whether each surface
81
+ * exists — which is why two of the three gate on it and the lane runs it first. Since #2494 the decomposer
82
+ * EXPECTS each plan (`artifact_expected`, a SEQUENCING predicate): the experience and integration plans
83
+ * unconditionally, the website and documentation plans only when the composition decided `add-website` /
84
+ * `add-technical-doc` NEEDED (its `when` clause). Inside a lane every child is admitted past sequencing, so
85
+ * that marks the board and a standalone run; what holds THIS lane is its stop condition.
82
86
  *
83
87
  * ## `capability-composition` joined the lane the day it landed (#1491, 2026-09-22)
84
88
  *
@@ -94,9 +98,9 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-sp
94
98
  */
95
99
  export const playbookDefinition = {
96
100
  ref: 'bottom_up.conception',
97
- version: '0.1.2',
101
+ version: '0.1.3',
98
102
  phase: MetaWorkflow_Phase.BOTTOM_UP,
99
- intent: 'Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane\'s closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.',
103
+ intent: 'Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record, the EXPERIENCE plan and the INTEGRATION plan are on record (an integration plan that decides nothing runs in the background is a plan on record), AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane\'s closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. The experience plan is not a composition decision because every application with a frontend has an experience: without it the build has no home, no design system from the brand, no navigation decision and no application views (#2494, both creation runs that closed this lane without it). The integration plan is the same kind of decision: without it the build emits no worker, minion, provider binding or inbound channel, and nothing says whether that was decided. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.',
100
104
  preconditions: [
101
105
  { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'requirements' } },
102
106
  { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'market-snapshot' } },
@@ -121,6 +125,9 @@ export const playbookDefinition = {
121
125
  { family: 'capability-composition' },
122
126
  { family: 'website-plan', render: MetaWorkflow_InputRender.MAP },
123
127
  { family: 'documentation-plan', render: MetaWorkflow_InputRender.MAP },
128
+ // The experience and integration plans the stop rule also checks (#2494), as maps: enough to see that each exists.
129
+ { family: 'experience-plan', render: MetaWorkflow_InputRender.MAP },
130
+ { family: 'integration-plan', render: MetaWorkflow_InputRender.MAP },
124
131
  ],
125
132
  // Nothing — the lane's write scope is resolved transitively through `admits`: domain-plan,
126
133
  // placement-plan, and the application itself (the foundation composes it in the working tree).
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.conception/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,0BAA0B,GAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,GAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2FG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,sBAAsB;IAC3B,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,SAAS;IACnC,MAAM,EACJ,gqDAAgqD;IAClqD,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE;QACzF,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,iBAAiB,EAAE,EAAE;QAC5F,EAAE,IAAI,EAAE,0BAA0B,CAAC,iBAAiB,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,SAAS,EAAE,EAAE;KACxF;IACD,oGAAoG;IACpG,6DAA6D;IAC7D,MAAM,EAAE;QACN,EAAE,MAAM,EAAE,cAAc,EAAE;QAC1B,EAAE,MAAM,EAAE,cAAc,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAChE,EAAE,MAAM,EAAE,iBAAiB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QACnE,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAC3D,EAAE,MAAM,EAAE,gBAAgB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAClE,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAC/D,EAAE,MAAM,EAAE,gBAAgB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAClE;;;;;WAKG;QACH,EAAE,MAAM,EAAE,wBAAwB,EAAE;QACpC,EAAE,MAAM,EAAE,cAAc,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAChE,EAAE,MAAM,EAAE,oBAAoB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;KACvE;IACD,2FAA2F;IAC3F,+FAA+F;IAC/F,OAAO,EAAE,EAAE;IACX,MAAM,EAAE;QACN,SAAS,EAAE,EAAE;QACb,YAAY,EAAE;YACZ;;;eAGG;YACH,MAAM,EAAE;gBACN,0BAA0B;gBAC1B,+FAA+F;gBAC/F,gGAAgG;gBAChG,8BAA8B;gBAC9B,wBAAwB;gBACxB,2BAA2B;gBAC3B;;;;;;;;;;mBAUG;gBACH,4BAA4B;gBAC5B,sBAAsB;gBACtB,kCAAkC;gBAClC,0BAA0B;gBAC1B,uBAAuB;aACxB;YACD;;;;;eAKG;YACH,iBAAiB,EAAE,EAAE;YACrB,wBAAwB,EAAE,CAAC;YAC3B;;;;;;eAMG;YACH,iBAAiB,EAAE,SAAS;SAC7B;KACF;IACD;;;;;;OAMG;IACH,QAAQ,EAAE,2BAA2B,CAAC,cAAc;IACpD,MAAM,EAAE,EAAE;IACV,SAAS,EAAE,0BAA0B,CAAC,aAAa;CAGpD,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_PredicateKind,\n} from '@wildo-ai/saas-models/meta-workflows';\nimport {\n MetaWorkflow_InputRender,\n MetaWorkflow_Phase,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\n/**\n * The CONCEPTION LANE — from a landed definition to an accepted placement plan (#1500, epic #1506).\n *\n * Until this existed `bottom_up.domain-plan`, `bottom_up.foundation` and `bottom_up.placement-plan`\n * were run one at a time: the decomposer could run before placement (#1265 R-6, an application with\n * no navigation), placement's panel failed closed with nobody to staff it (#572), and a module the\n * plan could not route had no way back to the plan. This lane runs the four steps that CONCEIVE the\n * application's structure as one choreography and ends on one decision: the conception is accepted,\n * or returned.\n *\n * ## Order is the leaves' preconditions\n *\n * `domain-plan` needs the requirements and the market snapshot; `expert-personas` needs the vision and\n * the snapshot and staffs the panels `placement-plan` convenes; `foundation` needs the domain plan\n * and composes the application from it; `placement-plan` needs the domain plan. Nothing here says\n * \"domain plan first\" — the runtime recomputes what may run after every round, and a re-run of the\n * lane on an application whose domain plan already exists goes straight to what is missing.\n *\n * ## The lane's OWN gate is the definition lane's output\n *\n * READINESS on the two families the domain plan derives from (declared as inputs, per audit rule 24),\n * and a SEQUENCING expectation of the roadmap — the last family the definition lane lands before its\n * phase gate. A conception without a roadmap is a legitimate choice (the domain plan's own gate does\n * not need one), so it is `artifact_expected`: the board says \"you are early\", and an explicit run\n * proceeds. When the decision boundary (#111) lands, the definition lane's ACCEPTANCE becomes the\n * thing this gate reads; today the roadmap is the closest fact on record.\n *\n * ## Two children are RUNNER-OWNED and both are safe to re-offer\n *\n * `foundation` and `expert-personas` are bespoke executors, not generations: the runner short-circuits\n * them before any brief is composed. Both land nothing the runtime marks delivered, so the loop offers\n * them again each round, and both are idempotent by their own contracts — foundation plans\n * byte-identical targets as SKIPS and refuses on a collision rather than overwriting authored work;\n * expert-personas never re-derives a committed charter and reports a role whose inputs have not\n * landed as WAITING. The intent below tells the selector not to spend a round on either once it has\n * run; their idempotence is what makes a wrong selection cheap rather than harmful.\n *\n * ## `domain-plan` may SUSPEND for a clarification\n *\n * It declares `suspendsForClarification`: a run that reaches a decision only the creator can make\n * checkpoints and waits on `/playbooks/suspended`. Inside this lane that child returns nothing and the\n * round records it; the lane runs whatever else is eligible (nothing, on a fresh application — every\n * other child needs the plan) and stops on NOTHING_ELIGIBLE. Answer the clarification, re-run the lane:\n * the resumed plan lands, and the next round has three eligible children.\n *\n * ## Interviews are answered in the DOSSIER\n *\n * `domain-plan` asks one question (tenancy) and `foundation` five (primary scope, operating entity,\n * operating jurisdictions, and the billing and SMS provider choices — #1488, answer `none` to decide later). A child whose interview the dossier does not answer is not eligible in\n * this run; the lane runs the rest and the board reports the leaf as waiting for the creator — the\n * same contract as the definition lane, for the same mechanical reason (#1454, Step 5).\n *\n * ## Loop-back — the mechanism exists; what declares it is a child, and this lane has none yet\n *\n * | signal | re-opens | how, once it can |\n * |---|---|---|\n * | placement's panel or judge names a module or resource the plan cannot route | `bottom_up.domain-plan` | a `step_available` gate on placement's verdict (#1498), the same shape as the market produce gate |\n * | the build lane's coherence GAP names a module or relationship | `bottom_up.domain-plan`, through the root | the root routes the build lane's verdict here (#1503, after #1497) |\n * | requirements or market newer than the landed plan | `bottom_up.domain-plan` | the staleness gate (#57) |\n *\n * Each is one additive declaration on the CHILD that re-runs — never on this lane, which declares\n * `admits` and not a child's preconditions. Both mechanisms landed 2026-09-22; what is missing is a\n * revise child to carry them, and `application-creation-directive.md` is why one has not been\n * authored: the lane has never been driven live, so a loop-back for a gap nobody has seen would be\n * three guesses about what a real one looks like. See the definition lane for the same reasoning\n * written out.\n *\n * ## The SURFACE plans are conception, not build (#1493, #1492, #1494 — joined 2026-09-22)\n *\n * `experience-plan`, `website-plan` and `documentation-plan` each decide what a surface CONTAINS —\n * the views and their interaction, the site's sections, the documentation's shape. They belong here\n * and not in the build lane for one mechanical reason: `bottom_up.build-decompose` declares all three\n * as INPUTS, so they are read when the build plan is authored. A surface planned after decomposition\n * is a surface the build plan has no task for.\n *\n * **Declared as inputs and NOT as preconditions, on the decomposer's side and on this lane's.** An\n * application with no website has no website plan, and a build that refused to decompose without one\n * would refuse every application that does not want a site. The capability composition is what says\n * whether each surface exists — which is why two of the three gate on it and the lane runs it first.\n *\n * ## `capability-composition` joined the lane the day it landed (#1491, 2026-09-22)\n *\n * It sits between the domain plan and the foundation, which is where the lane needed it: it decides\n * which of the composition scenarios an application needs, and the foundation is what applies\n * them. Its own gate is `artifact_expected: domain-plan` — SEQUENCING, so a creator may compose\n * before a plan exists and inside this lane it is offered from round one. The lane's intent is what\n * orders it after the plan, as it does for every other pair here.\n *\n * Its record is its own family, so it is marked delivered when it lands and is not re-offered; it\n * declares that family as an INPUT too, which is what lets a later run refine the composition rather\n * than restart it.\n */\nexport const playbookDefinition = {\n ref: 'bottom_up.conception',\n version: '0.1.2',\n phase: MetaWorkflow_Phase.BOTTOM_UP,\n intent:\n 'Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane\\'s closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'requirements' } },\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'market-snapshot' } },\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_EXPECTED, selector: { family: 'roadmap' } },\n ],\n // For the SELECTOR (see the definition lane for why a composite's inputs reach exactly one reader):\n // the vision whole, everything else as a map of what exists.\n inputs: [\n { family: 'vision-brief' },\n { family: 'requirements', render: MetaWorkflow_InputRender.MAP },\n { family: 'market-snapshot', render: MetaWorkflow_InputRender.MAP },\n { family: 'roadmap', render: MetaWorkflow_InputRender.MAP },\n { family: 'business-model', render: MetaWorkflow_InputRender.MAP },\n { family: 'domain-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'placement-plan', render: MetaWorkflow_InputRender.MAP },\n /*\n * What the stop rule checks: a surface the composition decided NEEDED has its plan on record. The\n * composition is read WHOLE — one decision per scenario, and the dispositions are the point — and the two\n * surface plans as MAPS, which is enough to see that they exist and carry pages or chapters. Before\n * these, the selector was told to check something its brief did not contain.\n */\n { family: 'capability-composition' },\n { family: 'website-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'documentation-plan', render: MetaWorkflow_InputRender.MAP },\n ],\n // Nothing — the lane's write scope is resolved transitively through `admits`: domain-plan,\n // placement-plan, and the application itself (the foundation composes it in the working tree).\n outputs: [],\n method: {\n skillRefs: [],\n choreography: {\n /*\n * UNORDERED. Listed closing-move-first on purpose, the umbrellas' own trap check: read as a\n * sequence this would try to place modules before any plan named them, and fail loudly.\n */\n admits: [\n 'bottom_up.placement-plan',\n // The SURFACE plans — what the application presents, each over the composition that decided it\n // exists. They are conception, not build: the decomposer READS all three (#1493, #1492, #1494).\n 'bottom_up.documentation-plan',\n 'bottom_up.website-plan',\n 'bottom_up.experience-plan',\n /*\n * And what the application RUNS beside its backend — workers, minions, provider bindings\n * (#1495). Conception for the same reason as the three above, and it must come BEFORE the\n * foundation in practice rather than in this list: the foundation composes one package per\n * surface this plan declares, so a foundation that ran first composes none. The runtime\n * decides the order from each child's own preconditions; the ordering here is reading order.\n *\n * Its absence was measured 2026-09-22: the leaf existed, was audited, was named by no\n * composite, and a choreography's child set IS its `admits` — so the whole worker/minion\n * chain was unreachable in a journey while every test around it was green.\n */\n 'bottom_up.integration-plan',\n 'bottom_up.foundation',\n 'bottom_up.capability-composition',\n 'top_down.expert-personas',\n 'bottom_up.domain-plan',\n ],\n /*\n * One round per child on a fresh application (plan → personas + composition → foundation +\n * the three surface plans → placement = 5), plus a clarification suspension and a plan\n * re-derivation when placement sends it back. Twelve is headroom, not a plan. A breaker: it\n * stops a loop spinning, never refuses work.\n */\n maximumIterations: 12,\n maximumLanesPerIteration: 3,\n /*\n * Ninety minutes. Placement's panel runs three candidates through two reviewers, the foundation\n * composes scenarios and applies migrations, and a domain plan with a clarification round-trips\n * through the creator. Longer than the companion's HTTP ceiling (30 min): submit with\n * `async: true` and read the outcome from `/playbooks/runs`. Literal: the evaluator computes no\n * expressions.\n */\n maximumDurationMs: 5_400_000,\n },\n },\n /*\n * The lane's closing decision — the conception is accepted, or returned.\n *\n * LIVE since #111 landed: the runtime derives this lane's boundary from the field and the companion\n * projects one `approve_result` decision on the human-decision plane, which the posture then\n * resolves (YOLO notifies and proceeds). `onFailure` is read at the same boundary.\n */\n approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT,\n budget: {},\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & {\n method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'>;\n};\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.conception/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,0BAA0B,EAC1B,0BAA0B,GAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,GAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+FG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,sBAAsB;IAC3B,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,SAAS;IACnC,MAAM,EACJ,owEAAowE;IACtwE,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,cAAc,EAAE,EAAE;QACzF,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,iBAAiB,EAAE,EAAE;QAC5F,EAAE,IAAI,EAAE,0BAA0B,CAAC,iBAAiB,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,SAAS,EAAE,EAAE;KACxF;IACD,oGAAoG;IACpG,6DAA6D;IAC7D,MAAM,EAAE;QACN,EAAE,MAAM,EAAE,cAAc,EAAE;QAC1B,EAAE,MAAM,EAAE,cAAc,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAChE,EAAE,MAAM,EAAE,iBAAiB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QACnE,EAAE,MAAM,EAAE,SAAS,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAC3D,EAAE,MAAM,EAAE,gBAAgB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAClE,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAC/D,EAAE,MAAM,EAAE,gBAAgB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAClE;;;;;WAKG;QACH,EAAE,MAAM,EAAE,wBAAwB,EAAE;QACpC,EAAE,MAAM,EAAE,cAAc,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QAChE,EAAE,MAAM,EAAE,oBAAoB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QACtE,mHAAmH;QACnH,EAAE,MAAM,EAAE,iBAAiB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;QACnE,EAAE,MAAM,EAAE,kBAAkB,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;KACrE;IACD,2FAA2F;IAC3F,+FAA+F;IAC/F,OAAO,EAAE,EAAE;IACX,MAAM,EAAE;QACN,SAAS,EAAE,EAAE;QACb,YAAY,EAAE;YACZ;;;eAGG;YACH,MAAM,EAAE;gBACN,0BAA0B;gBAC1B,+FAA+F;gBAC/F,gGAAgG;gBAChG,8BAA8B;gBAC9B,wBAAwB;gBACxB,2BAA2B;gBAC3B;;;;;;;;;;mBAUG;gBACH,4BAA4B;gBAC5B,sBAAsB;gBACtB,kCAAkC;gBAClC,0BAA0B;gBAC1B,uBAAuB;aACxB;YACD;;;;;eAKG;YACH,iBAAiB,EAAE,EAAE;YACrB,wBAAwB,EAAE,CAAC;YAC3B;;;;;;eAMG;YACH,iBAAiB,EAAE,SAAS;SAC7B;KACF;IACD;;;;;;OAMG;IACH,QAAQ,EAAE,2BAA2B,CAAC,cAAc;IACpD,MAAM,EAAE,EAAE;IACV,SAAS,EAAE,0BAA0B,CAAC,aAAa;CAGpD,CAAC","sourcesContent":["import {\n MetaWorkflow_ApprovalPolicy,\n MetaWorkflow_FailurePolicy,\n MetaWorkflow_PredicateKind,\n} from '@wildo-ai/saas-models/meta-workflows';\nimport {\n MetaWorkflow_InputRender,\n MetaWorkflow_Phase,\n type MetaWorkflowPlaybookAuthoring,\n} from '@wildo-ai/saas-specifications/application-creation';\n\n/**\n * The CONCEPTION LANE — from a landed definition to an accepted placement plan (#1500, epic #1506).\n *\n * Until this existed `bottom_up.domain-plan`, `bottom_up.foundation` and `bottom_up.placement-plan`\n * were run one at a time: the decomposer could run before placement (#1265 R-6, an application with\n * no navigation), placement's panel failed closed with nobody to staff it (#572), and a module the\n * plan could not route had no way back to the plan. This lane runs the four steps that CONCEIVE the\n * application's structure as one choreography and ends on one decision: the conception is accepted,\n * or returned.\n *\n * ## Order is the leaves' preconditions\n *\n * `domain-plan` needs the requirements and the market snapshot; `expert-personas` needs the vision and\n * the snapshot and staffs the panels `placement-plan` convenes; `foundation` needs the domain plan\n * and composes the application from it; `placement-plan` needs the domain plan. Nothing here says\n * \"domain plan first\" — the runtime recomputes what may run after every round, and a re-run of the\n * lane on an application whose domain plan already exists goes straight to what is missing.\n *\n * ## The lane's OWN gate is the definition lane's output\n *\n * READINESS on the two families the domain plan derives from (declared as inputs, per audit rule 24),\n * and a SEQUENCING expectation of the roadmap — the last family the definition lane lands before its\n * phase gate. A conception without a roadmap is a legitimate choice (the domain plan's own gate does\n * not need one), so it is `artifact_expected`: the board says \"you are early\", and an explicit run\n * proceeds. When the decision boundary (#111) lands, the definition lane's ACCEPTANCE becomes the\n * thing this gate reads; today the roadmap is the closest fact on record.\n *\n * ## Two children are RUNNER-OWNED and both are safe to re-offer\n *\n * `foundation` and `expert-personas` are bespoke executors, not generations: the runner short-circuits\n * them before any brief is composed. Both land nothing the runtime marks delivered, so the loop offers\n * them again each round, and both are idempotent by their own contracts — foundation plans\n * byte-identical targets as SKIPS and refuses on a collision rather than overwriting authored work;\n * expert-personas never re-derives a committed charter and reports a role whose inputs have not\n * landed as WAITING. The intent below tells the selector not to spend a round on either once it has\n * run; their idempotence is what makes a wrong selection cheap rather than harmful.\n *\n * ## `domain-plan` may SUSPEND for a clarification\n *\n * It declares `suspendsForClarification`: a run that reaches a decision only the creator can make\n * checkpoints and waits on `/playbooks/suspended`. Inside this lane that child returns nothing and the\n * round records it; the lane runs whatever else is eligible (nothing, on a fresh application — every\n * other child needs the plan) and stops on NOTHING_ELIGIBLE. Answer the clarification, re-run the lane:\n * the resumed plan lands, and the next round has three eligible children.\n *\n * ## Interviews are answered in the DOSSIER\n *\n * `domain-plan` asks one question (tenancy) and `foundation` five (primary scope, operating entity,\n * operating jurisdictions, and the billing and SMS provider choices — #1488, answer `none` to decide later). A child whose interview the dossier does not answer is not eligible in\n * this run; the lane runs the rest and the board reports the leaf as waiting for the creator — the\n * same contract as the definition lane, for the same mechanical reason (#1454, Step 5).\n *\n * ## Loop-back — the mechanism exists; what declares it is a child, and this lane has none yet\n *\n * | signal | re-opens | how, once it can |\n * |---|---|---|\n * | placement's panel or judge names a module or resource the plan cannot route | `bottom_up.domain-plan` | a `step_available` gate on placement's verdict (#1498), the same shape as the market produce gate |\n * | the build lane's coherence GAP names a module or relationship | `bottom_up.domain-plan`, through the root | the root routes the build lane's verdict here (#1503, after #1497) |\n * | requirements or market newer than the landed plan | `bottom_up.domain-plan` | the staleness gate (#57) |\n *\n * Each is one additive declaration on the CHILD that re-runs — never on this lane, which declares\n * `admits` and not a child's preconditions. Both mechanisms landed 2026-09-22; what is missing is a\n * revise child to carry them, and `application-creation-directive.md` is why one has not been\n * authored: the lane has never been driven live, so a loop-back for a gap nobody has seen would be\n * three guesses about what a real one looks like. See the definition lane for the same reasoning\n * written out.\n *\n * ## The SURFACE plans are conception, not build (#1493, #1492, #1494 — joined 2026-09-22)\n *\n * `experience-plan`, `website-plan` and `documentation-plan` each decide what a surface CONTAINS —\n * the views and their interaction, the site's sections, the documentation's shape. They belong here\n * and not in the build lane for one mechanical reason: `bottom_up.build-decompose` declares all three\n * as INPUTS, so they are read when the build plan is authored. A surface planned after decomposition\n * is a surface the build plan has no task for.\n *\n * **Never a READINESS precondition, on the decomposer's side or on this lane's.** An application with no\n * website has no website plan, and a build that refused to decompose without one would refuse every\n * application that does not want a site. The capability composition is what says whether each surface\n * exists — which is why two of the three gate on it and the lane runs it first. Since #2494 the decomposer\n * EXPECTS each plan (`artifact_expected`, a SEQUENCING predicate): the experience and integration plans\n * unconditionally, the website and documentation plans only when the composition decided `add-website` /\n * `add-technical-doc` NEEDED (its `when` clause). Inside a lane every child is admitted past sequencing, so\n * that marks the board and a standalone run; what holds THIS lane is its stop condition.\n *\n * ## `capability-composition` joined the lane the day it landed (#1491, 2026-09-22)\n *\n * It sits between the domain plan and the foundation, which is where the lane needed it: it decides\n * which of the composition scenarios an application needs, and the foundation is what applies\n * them. Its own gate is `artifact_expected: domain-plan` — SEQUENCING, so a creator may compose\n * before a plan exists and inside this lane it is offered from round one. The lane's intent is what\n * orders it after the plan, as it does for every other pair here.\n *\n * Its record is its own family, so it is marked delivered when it lands and is not re-offered; it\n * declares that family as an INPUT too, which is what lets a later run refine the composition rather\n * than restart it.\n */\nexport const playbookDefinition = {\n ref: 'bottom_up.conception',\n version: '0.1.3',\n phase: MetaWorkflow_Phase.BOTTOM_UP,\n intent:\n 'Drive the CONCEPTION of the application as one lane: the domain plan from the requirements and the market, the expert personas that staff the panels, the capability composition the application needs, the foundation composed from the plan and that composition, the surface plans for whatever the composition says this application presents — its experience, its website, its documentation — and the placement plan the panel decides — ending on one decision: the conception is accepted, or returned to the domain plan. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. Select what is MISSING from the accepted truth shown to you. A child already on record whose inputs have not changed since it landed is not offered at all; every option is marked FIRST RUN, or REFRESH with the input that moved. The foundation and the expert personas are runner-owned steps that land no family: run each ONCE, when its inputs are on record, and do not spend a round on either again — the round history shows they ran. Run independent children in the same round. STOP when the placement plan is on record, the EXPERIENCE plan and the INTEGRATION plan are on record (an integration plan that decides nothing runs in the background is a plan on record), AND every surface the capability composition decided NEEDED (a website, a documentation portal) has its plan on record: the placement plan is this lane\\'s closing decision, but it needs only the domain plan, so it can land before a surface plan — and a surface decided and never planned is one the build decomposition emits no task for. The experience plan is not a composition decision because every application with a frontend has an experience: without it the build has no home, no design system from the brand, no navigation decision and no application views (#2494, both creation runs that closed this lane without it). The integration plan is the same kind of decision: without it the build emits no worker, minion, provider binding or inbound channel, and nothing says whether that was decided. A child whose interview the creator has not answered, or whose run suspended on a clarification, is not offered; run everything else and stop when nothing eligible advances the conception.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'requirements' } },\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'market-snapshot' } },\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_EXPECTED, selector: { family: 'roadmap' } },\n ],\n // For the SELECTOR (see the definition lane for why a composite's inputs reach exactly one reader):\n // the vision whole, everything else as a map of what exists.\n inputs: [\n { family: 'vision-brief' },\n { family: 'requirements', render: MetaWorkflow_InputRender.MAP },\n { family: 'market-snapshot', render: MetaWorkflow_InputRender.MAP },\n { family: 'roadmap', render: MetaWorkflow_InputRender.MAP },\n { family: 'business-model', render: MetaWorkflow_InputRender.MAP },\n { family: 'domain-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'placement-plan', render: MetaWorkflow_InputRender.MAP },\n /*\n * What the stop rule checks: a surface the composition decided NEEDED has its plan on record. The\n * composition is read WHOLE — one decision per scenario, and the dispositions are the point — and the two\n * surface plans as MAPS, which is enough to see that they exist and carry pages or chapters. Before\n * these, the selector was told to check something its brief did not contain.\n */\n { family: 'capability-composition' },\n { family: 'website-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'documentation-plan', render: MetaWorkflow_InputRender.MAP },\n // The experience and integration plans the stop rule also checks (#2494), as maps: enough to see that each exists.\n { family: 'experience-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'integration-plan', render: MetaWorkflow_InputRender.MAP },\n ],\n // Nothing — the lane's write scope is resolved transitively through `admits`: domain-plan,\n // placement-plan, and the application itself (the foundation composes it in the working tree).\n outputs: [],\n method: {\n skillRefs: [],\n choreography: {\n /*\n * UNORDERED. Listed closing-move-first on purpose, the umbrellas' own trap check: read as a\n * sequence this would try to place modules before any plan named them, and fail loudly.\n */\n admits: [\n 'bottom_up.placement-plan',\n // The SURFACE plans — what the application presents, each over the composition that decided it\n // exists. They are conception, not build: the decomposer READS all three (#1493, #1492, #1494).\n 'bottom_up.documentation-plan',\n 'bottom_up.website-plan',\n 'bottom_up.experience-plan',\n /*\n * And what the application RUNS beside its backend — workers, minions, provider bindings\n * (#1495). Conception for the same reason as the three above, and it must come BEFORE the\n * foundation in practice rather than in this list: the foundation composes one package per\n * surface this plan declares, so a foundation that ran first composes none. The runtime\n * decides the order from each child's own preconditions; the ordering here is reading order.\n *\n * Its absence was measured 2026-09-22: the leaf existed, was audited, was named by no\n * composite, and a choreography's child set IS its `admits` — so the whole worker/minion\n * chain was unreachable in a journey while every test around it was green.\n */\n 'bottom_up.integration-plan',\n 'bottom_up.foundation',\n 'bottom_up.capability-composition',\n 'top_down.expert-personas',\n 'bottom_up.domain-plan',\n ],\n /*\n * One round per child on a fresh application (plan → personas + composition → foundation +\n * the three surface plans → placement = 5), plus a clarification suspension and a plan\n * re-derivation when placement sends it back. Twelve is headroom, not a plan. A breaker: it\n * stops a loop spinning, never refuses work.\n */\n maximumIterations: 12,\n maximumLanesPerIteration: 3,\n /*\n * Ninety minutes. Placement's panel runs three candidates through two reviewers, the foundation\n * composes scenarios and applies migrations, and a domain plan with a clarification round-trips\n * through the creator. Longer than the companion's HTTP ceiling (30 min): submit with\n * `async: true` and read the outcome from `/playbooks/runs`. Literal: the evaluator computes no\n * expressions.\n */\n maximumDurationMs: 5_400_000,\n },\n },\n /*\n * The lane's closing decision — the conception is accepted, or returned.\n *\n * LIVE since #111 landed: the runtime derives this lane's boundary from the field and the companion\n * projects one `approve_result` decision on the human-decision plane, which the posture then\n * resolves (YOLO notifies and proceeds). `onFailure` is read at the same boundary.\n */\n approval: MetaWorkflow_ApprovalPolicy.APPROVE_RESULT,\n budget: {},\n onFailure: MetaWorkflow_FailurePolicy.KEEP_AND_FLAG,\n} satisfies Omit<MetaWorkflowPlaybookAuthoring, 'method'> & {\n method: Omit<NonNullable<MetaWorkflowPlaybookAuthoring['method']>, 'guidance'>;\n};\n"]}
@@ -1,6 +1,6 @@
1
1
  import { HumanDecision_FieldKind } from '@wildo-ai/saas-models';
2
2
  import { MetaWorkflow_AuthorityAssuranceClass, MetaWorkflow_AuthorityDecisionMode, MetaWorkflow_AuthorityInteractionChannel, MetaWorkflow_ContinuationAction, MetaWorkflow_DecisionConsequence, MetaWorkflow_DecisionRuleBoundaryClass, MetaWorkflow_EvaluationAggregationStrategy, MetaWorkflow_EvaluationPromptAssemblyStrategy, MetaWorkflow_EvaluationVerdict, MetaWorkflow_EvidenceRequirementKind, MetaWorkflow_FailureDisposition, MetaWorkflow_HardFloorPosture, MetaWorkflow_OutputContentClass, MetaWorkflow_OutputContractCardinality, MetaWorkflow_StructuredArtifactOutputSetCommitment, MetaWorkflow_ApprovalPolicy, MetaWorkflow_ArtifactIntent, MetaWorkflow_Executor, MetaWorkflow_FailurePolicy, MetaWorkflow_PredicateKind, MetaWorkflow_ElicitationQuestionDepth } from '@wildo-ai/saas-models/meta-workflows';
3
- import { MetaWorkflow_Phase, DomainPlanEvaluationCriterionRef, DomainPlanEvaluationEvidenceCoveragePolicyRef, DomainPlanEvaluationEvidenceFreshnessPolicyRef, DomainPlanEvaluationEvidenceRequirementRef, DomainPlanEvaluationEvidenceSubjectRef } from '@wildo-ai/saas-specifications/application-creation';
3
+ import { MetaWorkflow_ContextSource, MetaWorkflow_Phase, DomainPlanEvaluationCriterionRef, DomainPlanEvaluationEvidenceCoveragePolicyRef, DomainPlanEvaluationEvidenceFreshnessPolicyRef, DomainPlanEvaluationEvidenceRequirementRef, DomainPlanEvaluationEvidenceSubjectRef } from '@wildo-ai/saas-specifications/application-creation';
4
4
  export declare const playbookDefinition: {
5
5
  ref: string;
6
6
  version: string;
@@ -25,6 +25,7 @@ export declare const playbookDefinition: {
25
25
  description: string;
26
26
  }[];
27
27
  method: {
28
+ contextSources: MetaWorkflow_ContextSource.CREATOR_STATED_FACTS[];
28
29
  suspendsForClarification: true;
29
30
  skillRefs: string[];
30
31
  elicitation: {
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.domain-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,uBAAuB,EACxB,MAAM,uBAAuB,CAAC;AAK/B,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,+BAA+B,EAC/B,6BAA6B,EAC7B,+BAA+B,EAC/B,sCAAsC,EACtC,kDAAkD,EAClD,2BAA2B,EAC3B,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,0BAA0B,EAC1B,qCAAqC,EACtC,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EAEL,kBAAkB,EAClB,gCAAgC,EAChC,6CAA6C,EAC7C,8CAA8C,EAC9C,0CAA0C,EAC1C,sCAAsC,EAEvC,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+E9B,CAAC;AAEF;;;;;;GAMG;AACH,eAAO,MAAM,8BAA8B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyDW,CAAC;AAEvD,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyRW,CAAC"}
1
+ {"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../src/playbooks/bottom_up.domain-plan/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,uBAAuB,EACxB,MAAM,uBAAuB,CAAC;AAK/B,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,+BAA+B,EAC/B,6BAA6B,EAC7B,+BAA+B,EAC/B,sCAAsC,EACtC,kDAAkD,EAClD,2BAA2B,EAC3B,2BAA2B,EAC3B,qBAAqB,EACrB,0BAA0B,EAC1B,0BAA0B,EAC1B,qCAAqC,EACtC,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,0BAA0B,EAE1B,kBAAkB,EAClB,gCAAgC,EAChC,6CAA6C,EAC7C,8CAA8C,EAC9C,0CAA0C,EAC1C,sCAAsC,EAEvC,MAAM,oDAAoD,CAAC;AAE5D,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsF9B,CAAC;AAEF;;;;;;GAMG;AACH,eAAO,MAAM,8BAA8B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyDW,CAAC;AAEvD,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiWW,CAAC"}