@wildo-ai/framework-knowledge 1.1.8 → 1.1.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (480) hide show
  1. package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
  2. package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
  3. package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
  4. package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
  5. package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
  6. package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
  7. package/dist/claude-marketplace/plugins/wildo/references/expert-personas-and-deliberations.md +26 -7
  8. package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
  9. package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
  10. package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
  11. package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
  12. package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
  13. package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
  14. package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
  15. package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
  16. package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +20 -4
  17. package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
  18. package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
  19. package/dist/esm/framework-knowledge.definitions.js +95 -5
  20. package/dist/esm/framework-knowledge.definitions.js.map +1 -1
  21. package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
  22. package/dist/esm/index.d.ts.map +1 -1
  23. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
  24. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -1
  25. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
  26. package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
  27. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
  28. package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
  29. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
  30. package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
  31. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +41 -3
  32. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
  33. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +175 -14
  34. package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
  35. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
  36. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
  37. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
  38. package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
  39. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
  40. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
  41. package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
  42. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts +8 -4
  43. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
  44. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
  45. package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
  46. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +4 -2
  47. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
  48. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +90 -13
  49. package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
  50. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
  51. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
  52. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
  53. package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js.map +1 -1
  54. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
  55. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
  56. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
  57. package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
  58. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
  59. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
  60. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
  61. package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
  62. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
  63. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
  64. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
  65. package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
  66. package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
  67. package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
  68. package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
  69. package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
  70. package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
  71. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
  72. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
  73. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
  74. package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
  75. package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
  76. package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.map +1 -1
  77. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
  78. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
  79. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +91 -43
  80. package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
  81. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +41 -0
  82. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
  83. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +43 -0
  84. package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
  85. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +200 -0
  86. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
  87. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +203 -0
  88. package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
  89. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +81 -0
  90. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
  91. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +93 -0
  92. package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
  93. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
  94. package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
  95. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
  96. package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
  97. package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
  98. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
  99. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
  100. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
  101. package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
  102. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
  103. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
  104. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
  105. package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
  106. package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  107. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
  108. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
  109. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
  110. package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
  111. package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -1
  112. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
  113. package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
  114. package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
  115. package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
  116. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts +27 -6
  117. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
  118. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
  119. package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
  120. package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
  121. package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
  122. package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
  123. package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
  124. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
  125. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
  126. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
  127. package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
  128. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
  129. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
  130. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +71 -2
  131. package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
  132. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
  133. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
  134. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
  135. package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
  136. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
  137. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
  138. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
  139. package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
  140. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
  141. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
  142. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
  143. package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
  144. package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
  145. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
  146. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
  147. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +41 -17
  148. package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
  149. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
  150. package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
  151. package/dist/knowledge/manifest.json +8 -8
  152. package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
  153. package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
  154. package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
  155. package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
  156. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
  157. package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
  158. package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +261 -34
  159. package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
  160. package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -59
  161. package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
  162. package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
  163. package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
  164. package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
  165. package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
  166. package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
  167. package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +11 -3
  168. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
  169. package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
  170. package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +129 -17
  171. package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
  172. package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
  173. package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
  174. package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
  175. package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
  176. package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
  177. package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
  178. package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
  179. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
  180. package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
  181. package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
  182. package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
  183. package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
  184. package/dist/knowledge/playbooks/refinement.feature-contribution/playbook.json +1 -1
  185. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
  186. package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
  187. package/dist/knowledge/playbooks/top_down.brand-identity/method.md +75 -37
  188. package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
  189. package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
  190. package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -0
  191. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
  192. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
  193. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +99 -0
  194. package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
  195. package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
  196. package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -0
  197. package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
  198. package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
  199. package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
  200. package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
  201. package/dist/knowledge/playbooks/top_down.capability-map/method.md +10 -9
  202. package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
  203. package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
  204. package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
  205. package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
  206. package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
  207. package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
  208. package/dist/knowledge/playbooks/top_down.expert-personas/playbook.json +16 -2
  209. package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
  210. package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
  211. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
  212. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
  213. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
  214. package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
  215. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
  216. package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
  217. package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
  218. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-protocol.json +1 -1
  219. package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
  220. package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
  221. package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
  222. package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
  223. package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
  224. package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
  225. package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +29 -0
  226. package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
  227. package/dist/knowledge/references/brand.name-choice.config.md +144 -0
  228. package/dist/knowledge/references/brand.name-screening.config.md +308 -0
  229. package/dist/knowledge/references/build-plan.task-graph.config.md +119 -11
  230. package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
  231. package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
  232. package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
  233. package/dist/knowledge/references/capability-composition.config.md +67 -4
  234. package/dist/knowledge/references/companion.market.prompt-renderer.md +11 -6
  235. package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
  236. package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
  237. package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
  238. package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
  239. package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
  240. package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
  241. package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
  242. package/dist/knowledge/references/example.email.template.minimal.md +1 -1
  243. package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
  244. package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
  245. package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
  246. package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
  247. package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
  248. package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
  249. package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
  250. package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
  251. package/dist/knowledge/references/experience-plan.config.md +60 -7
  252. package/dist/knowledge/references/market.context-block.builder.md +1 -1
  253. package/dist/knowledge/references/market.snapshot.validation.md +1 -1
  254. package/dist/knowledge/references/placement-plan.config.md +43 -0
  255. package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
  256. package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
  257. package/dist/knowledge/references/requirements.references.conventions.md +1 -1
  258. package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
  259. package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
  260. package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
  261. package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
  262. package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
  263. package/dist/knowledge/references/saas.backend.email.send.md +77 -0
  264. package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
  265. package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
  266. package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
  267. package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
  268. package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
  269. package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
  270. package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
  271. package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
  272. package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
  273. package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
  274. package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
  275. package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
  276. package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
  277. package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
  278. package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
  279. package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
  280. package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
  281. package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
  282. package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
  283. package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
  284. package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
  285. package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
  286. package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
  287. package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
  288. package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
  289. package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
  290. package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
  291. package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
  292. package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
  293. package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -0
  294. package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
  295. package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
  296. package/dist/knowledge/references/saas.website.root-config.seo.md +2 -1
  297. package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
  298. package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
  299. package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
  300. package/dist/knowledge/references/website-plan.config.md +26 -0
  301. package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
  302. package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
  303. package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
  304. package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
  305. package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
  306. package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
  307. package/dist/knowledge/references/zod.factories.code.md +1 -0
  308. package/dist/knowledge/references/zod.factories.duration.md +1 -0
  309. package/dist/knowledge/references/zod.factories.money.md +1 -0
  310. package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
  311. package/dist/knowledge/registries/framework-topics.json +374 -1
  312. package/dist/knowledge/registries/playbooks.json +76 -28
  313. package/dist/knowledge/registries/source-tags.json +1513 -898
  314. package/dist/knowledge/rules/live-context-door.md +5 -2
  315. package/dist/knowledge/skills/INDEX.md +5 -2
  316. package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
  317. package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
  318. package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
  319. package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
  320. package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
  321. package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
  322. package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
  323. package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
  324. package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
  325. package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
  326. package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
  327. package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
  328. package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
  329. package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
  330. package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
  331. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
  332. package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
  333. package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
  334. package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
  335. package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
  336. package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
  337. package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
  338. package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
  339. package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
  340. package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
  341. package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
  342. package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
  343. package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
  344. package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
  345. package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
  346. package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
  347. package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
  348. package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
  349. package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
  350. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
  351. package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
  352. package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
  353. package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
  354. package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
  355. package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
  356. package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
  357. package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
  358. package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
  359. package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
  360. package/dist/knowledge/skills/market-add-feature-benefit/SKILL.md +10 -2
  361. package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
  362. package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
  363. package/dist/knowledge/skills/market-category/SKILL.md +21 -7
  364. package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
  365. package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
  366. package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
  367. package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
  368. package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
  369. package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
  370. package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
  371. package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
  372. package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
  373. package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
  374. package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
  375. package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
  376. package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
  377. package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
  378. package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
  379. package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
  380. package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
  381. package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
  382. package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
  383. package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
  384. package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
  385. package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
  386. package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
  387. package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
  388. package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
  389. package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
  390. package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
  391. package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
  392. package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
  393. package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
  394. package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
  395. package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
  396. package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
  397. package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
  398. package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
  399. package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
  400. package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
  401. package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
  402. package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
  403. package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
  404. package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
  405. package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
  406. package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
  407. package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
  408. package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
  409. package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
  410. package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
  411. package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
  412. package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
  413. package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
  414. package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
  415. package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
  416. package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
  417. package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
  418. package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
  419. package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
  420. package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
  421. package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
  422. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
  423. package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
  424. package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
  425. package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
  426. package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
  427. package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
  428. package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
  429. package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
  430. package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
  431. package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
  432. package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
  433. package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
  434. package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
  435. package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
  436. package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
  437. package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
  438. package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
  439. package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
  440. package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
  441. package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
  442. package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
  443. package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
  444. package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
  445. package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
  446. package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
  447. package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
  448. package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
  449. package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
  450. package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
  451. package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
  452. package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
  453. package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
  454. package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
  455. package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
  456. package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
  457. package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
  458. package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
  459. package/dist/knowledge/skills/website-section-faq/SKILL.md +21 -1
  460. package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
  461. package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +21 -1
  462. package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
  463. package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +25 -2
  464. package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
  465. package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
  466. package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
  467. package/dist/knowledge/skills/website-section-hero/SKILL.md +33 -10
  468. package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
  469. package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
  470. package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
  471. package/dist/knowledge/skills/website-section-social-proof/SKILL.md +27 -2
  472. package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
  473. package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +16 -4
  474. package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
  475. package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
  476. package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
  477. package/dist/knowledge/topic-index.json +1590 -292
  478. package/dist/tsconfig.build.tsbuildinfo +1 -1
  479. package/dist/tsconfig.tsbuildinfo +1 -1
  480. package/package.json +4 -4
@@ -1 +1 @@
1
- {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build-scale/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,uBAAuB;IAC9B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,uvGAAuvG;IACjwG,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,YAAY,EAAE,EAAE;KACtE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,YAAY,EAAE;KAC3B;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE,EACZ;KACF;IACD,UAAU,EAAE,cAAc;IAC1B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,EAAE;KACd;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\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. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.build-scale\",\n \"version\": \"0.1.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up build scale — the THIRD and final build-execution playbook, the pivot from dispatching ONE task safely (the single-flight dispatch contract) to running the build at SCALE: parallelism across several coding agents, the concurrency schedule, and interleaving the companion-owned generation steps concurrently with coding runs. Reads the approved build-plan (the ordered coding-agent task graph, each task carrying a target, ONE MetaWorkflow_FunctionalTopic, its skill(s), and prose prerequisite ordering) and the current journey state, and answers the SCALE questions the single-flight dispatch playbook deliberately left open: (1) derive the ready-SET (a wave / frontier of tasks whose prose prerequisites have ALL SUCCEEDED — not merely been attempted); (2) decide the parallelism degree (how many coding agents run at once) and the worktree-isolation model that keeps each concurrent run's change-set cleanly attributable; (3) schedule the waves respecting the DEPENDS_ON ordering the build-plan encodes; (4) interleave the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) concurrently with coding runs at the points their inputs exist — those steps run through their deterministic companion endpoints, NOT the coding-agent single-flight lock, so they genuinely overlap coding runs; (5) reconcile wave completion across the concurrent runs (all tasks in the frontier SUCCEEDED before the next wave opens) and apply onFailure across siblings + downstream. Then advance to the next wave and loop. Each parallel slot INVOKES the single-flight dispatch contract (the build-dispatch playbook, upstream — select-next / context-pack / one ACP prompt turn / change-set capture / verify-outside / record + onFailure); this playbook does NOT re-specify those per-task mechanics and does NOT re-decompose the plan (the build-decompose playbook owns the task graph) and authors no schemas / no code. IMPORTANT HONESTY: the companion runner HARD-ENFORCES single-flight today (a run plan carries at most ONE coding-agent task; a concurrent dispatch is refused; the workspace-mutation lock + the lock-free cursor + the missing run-outcome observation loop all assume one dispatch at a time). So this v1 scale METHOD is the DECLARATIVE TARGET a runner-serializer slice will realize — on the current runner the waves DEGRADE to sequential single-flight dispatch. And even the deterministic companion-generation steps, though they do not take the coding single-flight lock, cannot SAFELY overlap an active coding run today: the coding run's change-set is captured as a whole-worktree time-window diff, so a generation step writing files inside that window is misattributed to the coding run (the same whole-worktree pollution that forbids two concurrent coding agents) — so the generation steps also serialize outside an active coding-capture window today, and genuine concurrency (coding-parallel OR generation-overlap) both arrive only with the git worktree-per-agent isolation runner task. v1 scaffold: a multi-CODING_AGENT run-completion serializer, git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock are companion-runner mechanism filed as runner tasks, NOT built here; a priority/work-stealing scheduler and cost-optimal packing are a later depth phase.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"build-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"build-plan\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n ]\n },\n \"executor\": \"coding_agent\",\n \"approval\": \"approve_before\",\n \"budget\": {\n \"maxRuns\": 30\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
1
+ {"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build-scale/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,uBAAuB;IAC9B,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,47DAA47D;IACt8D,eAAe,EAAE;QACf,EAAE,MAAM,EAAE,iBAAiB,EAAE,UAAU,EAAE,EAAE,QAAQ,EAAE,YAAY,EAAE,EAAE;KACtE;IACD,QAAQ,EAAE;QACR,EAAE,QAAQ,EAAE,YAAY,EAAE;KAC3B;IACD,SAAS,EAAE,EAAE;IACb,QAAQ,EAAE;QACR,WAAW,EAAE,EACZ;KACF;IACD,UAAU,EAAE,cAAc;IAC1B,UAAU,EAAE,gBAAgB;IAC5B,QAAQ,EAAE;QACR,SAAS,EAAE,EAAE;KACd;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\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. This source\n * intentionally omits the superseded per-playbook evaluation-treatment object;\n * generation records that absence rather than fabricating legacy judge behavior.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.build-scale\",\n \"version\": \"0.1.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up build scale — the THIRD build-execution playbook: how the build runs at SCALE, as shipped. A run of a build-execution playbook starts a WAVE: up to the application's build parallelism of build-plan tasks at once (`wildo workbench parallelism`, 5 by default; 1 = one task at a time, the single-flight mode), in ONE shared worktree, as a rolling pool that refills each slot with whatever is ready when a run settles. This playbook declares the same CODING_AGENT executor as the build-dispatch playbook and runs through the same runtime branch, so both start the SAME wave; prefer build-dispatch to start a build, and read this one for the scale questions: (1) the ready-SET — tasks whose declared prerequisites have ALL SUCCEEDED, not merely been attempted, resolved by the host from the declared refs and git; (2) the width — the build parallelism, the person's setting, never chosen by the method; (3) the isolation model — none by decision: the runs share the worktree, only a task being built twice at once is prevented, and overlap is RECORDED on each run (`concurrency`, `interferenceSuspected`); (4) the deterministic companion-owned generation steps (labels / i18n, email templates, seeds) — run through their companion endpoints at their input-ready point, inline while live coding runs continue, at most once per wave; (5) the wave's end — bounded at four dispatches per slot per call, it drains its live runs, commits what their own accepts left as ONE change naming every run it carries, re-runs ALONE each completed task whose product a sibling overwrote, and applies keep_and_flag across siblings + dependents. Each slot runs the per-task dispatch contract of the build-dispatch playbook; this playbook does NOT re-specify it, does NOT re-decompose the plan (the build-decompose playbook owns the task graph), and authors no schemas / no code. A priority / work-stealing scheduler, cost-optimal packing and a revert_changeset failure path are later phases.\",\n \"preconditions\": [\n { \"kind\": \"artifact_exists\", \"selector\": { \"family\": \"build-plan\" } }\n ],\n \"inputs\": [\n { \"family\": \"build-plan\" }\n ],\n \"outputs\": [],\n \"method\": {\n \"skillRefs\": [\n ]\n },\n \"executor\": \"coding_agent\",\n \"approval\": \"approve_before\",\n \"budget\": {\n \"maxRuns\": 30\n },\n \"onFailure\": \"keep_and_flag\"\n} as const;\n"]}
@@ -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 family already on record is not re-derived unless the plan it was derived from has been re-derived in this run. 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,2mDAA2mD;IAC7mD,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 family already on record is not re-derived unless the plan it was derived from has been re-derived in this run. 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
- 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 } from '@wildo-ai/saas-models/meta-workflows';
3
- import { MetaWorkflow_Phase, DomainPlanEvaluationCriterionRef, DomainPlanEvaluationEvidenceCoveragePolicyRef, DomainPlanEvaluationEvidenceFreshnessPolicyRef, DomainPlanEvaluationEvidenceRequirementRef, DomainPlanEvaluationEvidenceSubjectRef } from '@wildo-ai/saas-specifications/application-creation';
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_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: {
@@ -33,6 +34,7 @@ export declare const playbookDefinition: {
33
34
  question: string;
34
35
  kind: HumanDecision_FieldKind.CHOICE;
35
36
  options: string[];
37
+ depth: MetaWorkflow_ElicitationQuestionDepth.ESSENTIAL;
36
38
  }[];
37
39
  };
38
40
  };
@@ -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,EAC3B,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"}
@@ -1,9 +1,9 @@
1
1
  import { HumanDecision_FieldKind, } from '@wildo-ai/saas-models';
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, } from '@wildo-ai/saas-models/meta-workflows';
3
- import { MetaWorkflow_Phase, DomainPlanEvaluationCriterionRef, DomainPlanEvaluationEvidenceCoveragePolicyRef, DomainPlanEvaluationEvidenceFreshnessPolicyRef, DomainPlanEvaluationEvidenceRequirementRef, DomainPlanEvaluationEvidenceSubjectRef, } from '@wildo-ai/saas-specifications/application-creation';
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_ContextSource, MetaWorkflow_Phase, DomainPlanEvaluationCriterionRef, DomainPlanEvaluationEvidenceCoveragePolicyRef, DomainPlanEvaluationEvidenceFreshnessPolicyRef, DomainPlanEvaluationEvidenceRequirementRef, DomainPlanEvaluationEvidenceSubjectRef, } from '@wildo-ai/saas-specifications/application-creation';
4
4
  export const playbookDefinition = {
5
5
  ref: 'bottom_up.domain-plan',
6
- version: '0.2.1',
6
+ version: '0.3.0',
7
7
  phase: MetaWorkflow_Phase.BOTTOM_UP,
8
8
  intent: 'Turn the approved definition set into one atomic, planning-depth domain output set: module decomposition with per-module resource inventory plus typed inter-resource relationship intents. The output remains staged until deterministic validation, semantic evaluation and distinct result authority complete.',
9
9
  preconditions: [
@@ -29,6 +29,13 @@ export const playbookDefinition = {
29
29
  },
30
30
  ],
31
31
  method: {
32
+ /*
33
+ * What the creator stated in the other interviews (#2498, #2499): data classes, regimes, jurisdictions, the core
34
+ * workflow, user groups, the scope boundary. 005's creator named VAT identifiers, site addresses, two national
35
+ * e-invoicing regimes and four countries, and none of it reached this step. A section, never a gate: the step runs
36
+ * whether or not those interviews were answered.
37
+ */
38
+ contextSources: [MetaWorkflow_ContextSource.CREATOR_STATED_FACTS],
32
39
  /*
33
40
  * The mid-run clarification channel, opt-in.
34
41
  *
@@ -66,7 +73,7 @@ export const playbookDefinition = {
66
73
  */
67
74
  question: 'Do people use this application together, in shared workspaces or teams, or does each person only see their own data? Choose organizations if they work together, users if each person\'s data is their own.',
68
75
  kind: HumanDecision_FieldKind.CHOICE,
69
- options: ['organizations', 'users'],
76
+ options: ['organizations', 'users'], depth: MetaWorkflow_ElicitationQuestionDepth.ESSENTIAL,
70
77
  },
71
78
  ],
72
79
  },
@@ -144,7 +151,10 @@ export const structuredArtifactActionSource = {
144
151
  export const evaluationTreatmentSource = {
145
152
  schemaVersion: 1,
146
153
  definitionRef: 'application-creation:evaluation-treatment/domain-plan-output-set-result',
147
- definitionVersion: 1,
154
+ // 2: requirement coverage counts an engine-realized requirement as covered, and engine-concern discipline (#2492).
155
+ // 3: lifecycle coverage, and boundary discipline admits lifecycle intents (#2491).
156
+ // 4: lifecycle coverage counts locked states beside final ones (#2491 re-review M1).
157
+ definitionVersion: 4,
148
158
  evaluationProtocol: {
149
159
  schemaVersion: 1,
150
160
  protocolRef: 'application-creation:evaluation-protocol/domain-plan-output-set-result',
@@ -162,8 +172,9 @@ export const evaluationTreatmentSource = {
162
172
  {
163
173
  schemaVersion: 1,
164
174
  criterionRef: DomainPlanEvaluationCriterionRef.REQUIREMENT_COVERAGE,
165
- criterionVersion: 1,
166
- instruction: 'Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory. Treat a requirement without a resolvable module home as a material gap.',
175
+ // 2: a requirement the plan leaves to the engine (engineRealizedRequirements) is covered (#2492).
176
+ criterionVersion: 2,
177
+ instruction: 'Determine whether every current-horizon functional requirement is served by at least one module capability and resource inventory, OR is recorded in engineRealizedRequirements because the engine already provides it (roles, membership, audit, personal data, governed documents, billing, guidance, notifications, localization). Treat a requirement with neither a resolvable module home nor an engine realization as a material gap.',
167
178
  evidenceRequirements: [{
168
179
  schemaVersion: 1,
169
180
  requirementRef: DomainPlanEvaluationEvidenceRequirementRef.REQUIREMENT_COVERAGE,
@@ -180,9 +191,9 @@ export const evaluationTreatmentSource = {
180
191
  aggregationPolicyRef: null,
181
192
  }],
182
193
  verdictGuidance: {
183
- [MetaWorkflow_EvaluationVerdict.PASS]: 'Every current-horizon functional requirement has a coherent module and resource home.',
194
+ [MetaWorkflow_EvaluationVerdict.PASS]: 'Every current-horizon functional requirement has a coherent module and resource home, or an engine realization naming the concern that meets it.',
184
195
  [MetaWorkflow_EvaluationVerdict.CONCERN]: 'Coverage is complete but one or more requirement-to-module links are weak or indirect.',
185
- [MetaWorkflow_EvaluationVerdict.GAP]: 'At least one current-horizon functional requirement has no resolvable module home.',
196
+ [MetaWorkflow_EvaluationVerdict.GAP]: 'At least one current-horizon functional requirement has neither a resolvable module home nor an engine realization.',
186
197
  [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The staged evidence cannot establish complete requirement coverage.',
187
198
  },
188
199
  },
@@ -270,8 +281,8 @@ export const evaluationTreatmentSource = {
270
281
  {
271
282
  schemaVersion: 1,
272
283
  criterionRef: DomainPlanEvaluationCriterionRef.RELATIONSHIP_INTEGRITY,
273
- criterionVersion: 1,
274
- instruction: 'Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Do not resolve them into physical foreign keys.',
284
+ criterionVersion: 2,
285
+ instruction: 'Assess whether the typed relationship intents are semantically necessary and coherent with the inventoried resources, conceptual cardinality and ownership direction. Read every cardinality from the source resource to the target resource (how many sources to how many targets): an edge from the resource holding the reference to the resource it references, where many holders share one referenced row, is many-to-one and is correct. Deterministic validation has already refused a one-sided cardinality whose "one" end holds the reference; do not re-report that. Do not resolve the intents into physical foreign keys.',
275
286
  evidenceRequirements: [{
276
287
  schemaVersion: 1,
277
288
  requirementRef: DomainPlanEvaluationEvidenceRequirementRef.RELATIONSHIP_INTEGRITY,
@@ -297,8 +308,9 @@ export const evaluationTreatmentSource = {
297
308
  {
298
309
  schemaVersion: 1,
299
310
  criterionRef: DomainPlanEvaluationCriterionRef.BOUNDARY_DISCIPLINE,
300
- criterionVersion: 1,
301
- instruction: 'Determine whether the output remains at planning depth: modules, resource inventories and relationship intents only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.',
311
+ // 2: lifecycle intents (states, transitions, conversions, final states) are planning depth (#2491).
312
+ criterionVersion: 2,
313
+ instruction: 'Determine whether the output remains at planning depth: modules, resource inventories, relationship intents and resource lifecycles (states, transitions, conversions, locked and final states) only. Treat schema fields, concrete foreign-key placement or generated implementation code as scope leakage.',
302
314
  evidenceRequirements: [{
303
315
  schemaVersion: 1,
304
316
  requirementRef: DomainPlanEvaluationEvidenceRequirementRef.BOUNDARY_DISCIPLINE,
@@ -321,6 +333,71 @@ export const evaluationTreatmentSource = {
321
333
  [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The staged evidence cannot establish the output depth boundary.',
322
334
  },
323
335
  },
336
+ /*
337
+ * #2491: app-creation-test-004 and -005 had no lifecycle at all, so the build planned no operation and every
338
+ * step (accept, convert, issue, pay) shipped as a status users edit by hand.
339
+ */
340
+ {
341
+ schemaVersion: 1,
342
+ criterionRef: DomainPlanEvaluationCriterionRef.LIFECYCLE_COVERAGE,
343
+ // 2: locked states (no edits, may still move on) beside final ones (#2491 re-review M1).
344
+ criterionVersion: 2,
345
+ instruction: 'Determine whether every resource a current-horizon requirement describes moving through states (sent, accepted, issued, paid, approved, closed) has a lifecycle whose transitions carry the requirement\'s verbs, whose conversions name the resource they create when one record creates another ("an accepted quote creates a job"), and whose locked and final states together cover what the requirements say must stop changing (locked when the record still moves on, final when nothing moves it again). A state change expressed only as a relationship, a status the requirements never move, or a lifecycle for a value derived from other records is not coverage.',
346
+ evidenceRequirements: [{
347
+ schemaVersion: 1,
348
+ requirementRef: DomainPlanEvaluationEvidenceRequirementRef.LIFECYCLE_COVERAGE,
349
+ requirementVersion: 1,
350
+ kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,
351
+ subjectRef: DomainPlanEvaluationEvidenceSubjectRef.DEFINITION_CONTEXT_AND_STAGED_OUTPUT_SET,
352
+ minCount: 2,
353
+ maxCount: 2,
354
+ coveragePolicyRef: DomainPlanEvaluationEvidenceCoveragePolicyRef.COMPLETE_DEFINITION_CONTEXT_AND_EXACT_OUTPUT_SET,
355
+ freshnessPolicyRef: DomainPlanEvaluationEvidenceFreshnessPolicyRef.CURRENT_ACCEPTED_HEADS_AND_ACTION_RESULT,
356
+ conditionRef: null,
357
+ independencePolicyRef: null,
358
+ diversityPolicyRef: null,
359
+ aggregationPolicyRef: null,
360
+ }],
361
+ verdictGuidance: {
362
+ [MetaWorkflow_EvaluationVerdict.PASS]: 'No requirement moves a record through states, or every such record has a lifecycle carrying the requirement\'s verbs, its conversions and its final states.',
363
+ [MetaWorkflow_EvaluationVerdict.CONCERN]: 'Each such record has a lifecycle, but a verb, a conversion target, or a locked or final state the requirements imply is missing from it.',
364
+ [MetaWorkflow_EvaluationVerdict.GAP]: 'A requirement moves a record through states and the plan has no lifecycle for it, or expresses the move only as a relationship.',
365
+ [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The staged evidence cannot establish which requirements move records through states.',
366
+ },
367
+ },
368
+ /*
369
+ * #2492: app-creation-test-005 planned six of thirteen resources for things the engine provides or that
370
+ * are not data at all (an access role, a role assignment, a record of processing, a country declaration,
371
+ * a sensitive-evidence register, a hand-kept workflow progress), and -004 planned country guidance as an
372
+ * empty form. No criterion asked whether a resource was the engine's concern.
373
+ */
374
+ {
375
+ schemaVersion: 1,
376
+ criterionRef: DomainPlanEvaluationCriterionRef.ENGINE_CONCERN_DISCIPLINE,
377
+ criterionVersion: 1,
378
+ instruction: 'Determine whether any module or resource stands in for a concern the engine already provides or that is not data a user maintains: roles, permissions or role assignments (the engine roles); members, invitations or teams; an audit history; processing purposes, legal bases, compliance or country declarations typed in by users (a governed document); a next action, stage or status copied from other records (derived, shown in a view). Such a requirement belongs in engineRealizedRequirements, or is derived. A product resource that merely mentions one of these words (an invoice with a status, a job with a stage the user sets as part of the work) is not a finding.',
379
+ evidenceRequirements: [{
380
+ schemaVersion: 1,
381
+ requirementRef: DomainPlanEvaluationEvidenceRequirementRef.ENGINE_CONCERN_DISCIPLINE,
382
+ requirementVersion: 1,
383
+ kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,
384
+ subjectRef: DomainPlanEvaluationEvidenceSubjectRef.DEFINITION_CONTEXT_AND_STAGED_OUTPUT_SET,
385
+ minCount: 2,
386
+ maxCount: 2,
387
+ coveragePolicyRef: DomainPlanEvaluationEvidenceCoveragePolicyRef.COMPLETE_DEFINITION_CONTEXT_AND_EXACT_OUTPUT_SET,
388
+ freshnessPolicyRef: DomainPlanEvaluationEvidenceFreshnessPolicyRef.CURRENT_ACCEPTED_HEADS_AND_ACTION_RESULT,
389
+ conditionRef: null,
390
+ independencePolicyRef: null,
391
+ diversityPolicyRef: null,
392
+ aggregationPolicyRef: null,
393
+ }],
394
+ verdictGuidance: {
395
+ [MetaWorkflow_EvaluationVerdict.PASS]: 'No module or resource models an engine-provided concern, a disclaimer, or state derived from other records.',
396
+ [MetaWorkflow_EvaluationVerdict.CONCERN]: 'A resource may duplicate an engine concern or derived state, but the definition context leaves room for a genuine product reading; name it and the reading.',
397
+ [MetaWorkflow_EvaluationVerdict.GAP]: 'A module or resource models roles or permissions, a compliance or country declaration users type in, or state copied from other records, while the requirement it serves is the engine\'s or derivable.',
398
+ [MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The staged evidence cannot establish what the resources hold.',
399
+ },
400
+ },
324
401
  ],
325
402
  },
326
403
  evaluatorBindingPolicy: {