@wildo-ai/framework-knowledge 1.1.7 → 1.1.9
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.
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/composites-and-the-loop.md +9 -2
- package/dist/claude-marketplace/plugins/wildo/references/creation-state.md +21 -0
- package/dist/claude-marketplace/plugins/wildo/references/derived-artifacts.md +121 -0
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +29 -5
- package/dist/claude-marketplace/plugins/wildo/skills/answer/SKILL.md +29 -2
- package/dist/claude-marketplace/plugins/wildo/skills/build/SKILL.md +69 -24
- package/dist/claude-marketplace/plugins/wildo/skills/doctor/SKILL.md +10 -0
- package/dist/claude-marketplace/plugins/wildo/skills/run/SKILL.md +21 -5
- package/dist/claude-marketplace/plugins/wildo/skills/start/SKILL.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/status/SKILL.md +2 -0
- package/dist/claude-marketplace/plugins/wildo/skills/why/SKILL.md +11 -1
- package/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +11 -1
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +2 -2
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts +11 -11
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js +29 -22
- package/dist/esm/playbooks/bottom_up.build/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +3 -3
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +59 -10
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +3 -3
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +5 -5
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +8 -0
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +12 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +25 -27
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +85 -43
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts +40 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js +41 -0
- package/dist/esm/playbooks/top_down.brand-name-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts +199 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js +201 -0
- package/dist/esm/playbooks/top_down.brand-name-screening-produce/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts +67 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js +76 -0
- package/dist/esm/playbooks/top_down.brand-naming/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +3 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +27 -18
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +11 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +11 -11
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +2 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +3 -1
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +2 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +3 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts +5 -2
- package/dist/esm/playbooks/top_down.definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js +16 -4
- package/dist/esm/playbooks/top_down.definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +7 -3
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +36 -2
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts +7 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js +4 -2
- package/dist/esm/playbooks/top_down.risk-register/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +9 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +3 -3
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +35 -2
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +30 -17
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/authority-basis.json +1 -1
- package/dist/knowledge/assurance-authority-bases/wildo-safe-baseline-v1/external-framework-mapping.json +1 -1
- package/dist/knowledge/manifest.json +8 -8
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/method.md +22 -7
- package/dist/knowledge/playbooks/bottom_up.assemble-verify/playbook.json +3 -3
- package/dist/knowledge/playbooks/bottom_up.build/method.md +17 -15
- package/dist/knowledge/playbooks/bottom_up.build/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +117 -28
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +4 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +133 -59
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.build-scale/method.md +169 -276
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.capability-composition/method.md +8 -1
- package/dist/knowledge/playbooks/bottom_up.capability-composition/playbook.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.conception/method.md +3 -2
- package/dist/knowledge/playbooks/bottom_up.conception/playbook.json +2 -2
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/bottom_up.domain-plan/method.md +22 -6
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +4 -3
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.brand-identity/method.md +71 -37
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +105 -0
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +55 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-protocol.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/evaluation-treatment.json +1 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/method.md +78 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +63 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +65 -0
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.business-model/method.md +60 -6
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +15 -10
- package/dist/knowledge/playbooks/top_down.compliance-analysis/playbook.json +30 -10
- package/dist/knowledge/playbooks/top_down.compliance-conception/playbook.json +3 -1
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +4 -1
- package/dist/knowledge/playbooks/top_down.definition/method.md +8 -3
- package/dist/knowledge/playbooks/top_down.definition/playbook.json +6 -4
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +11 -1
- package/dist/knowledge/playbooks/top_down.risk-register/method.md +21 -0
- package/dist/knowledge/playbooks/top_down.risk-register/playbook.json +8 -2
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +4 -2
- package/dist/knowledge/playbooks/top_down.vision-elicitation/method.md +10 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +40 -17
- package/dist/knowledge/references/brand.name-choice.config.md +127 -0
- package/dist/knowledge/references/brand.name-screening.config.md +253 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +64 -11
- package/dist/knowledge/references/business-model.pricing-plan.config.md +16 -0
- package/dist/knowledge/references/business-model.snapshot.config.md +64 -0
- package/dist/knowledge/references/business-model.snapshot.validation.md +68 -4
- package/dist/knowledge/references/capability-composition.config.md +67 -4
- package/dist/knowledge/references/example.data-seeding.minimal.md +29 -1
- package/dist/knowledge/references/market.snapshot.validation.md +1 -1
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +6 -0
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +9 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
- package/dist/knowledge/references/saas.website.page-manifest.schema.md +12 -3
- package/dist/knowledge/references/saas.website.page-sections.component.md +72 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +38 -1
- package/dist/knowledge/registries/playbooks.json +68 -20
- package/dist/knowledge/registries/source-tags.json +748 -695
- package/dist/knowledge/rules/live-context-door.md +5 -2
- package/dist/knowledge/skills/INDEX.md +2 -1
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +1 -1
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +154 -0
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +394 -0
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +65 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +5 -2
- package/dist/knowledge/skills/config-saas/SKILL.md +31 -4
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +14 -1
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
- package/dist/knowledge/skills/email-add-template/SKILL.md +1 -1
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +1 -1
- package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +11 -1
- package/dist/knowledge/skills/local-environment-bootstrap/references/derived-artifact-currency.md +122 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/framework-upgrade-and-dependency-alignment.md +11 -0
- package/dist/knowledge/skills/local-environment-bootstrap/references/wildo-cli-bootstrap-commands.md +9 -2
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +11 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +11 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +1 -1
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +6 -4
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +51 -3
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +6 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +4 -0
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +84 -3
- package/dist/knowledge/skills/website-section-contact/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-contact/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-faq/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-faq/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-feature-benefit-summary/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-feature-detail/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-footer-cta/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-hero/SKILL.md +27 -9
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/SKILL.md +15 -0
- package/dist/knowledge/skills/website-section-social-proof/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/SKILL.md +1 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
- package/dist/knowledge/topic-index.json +169 -43
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -18,9 +18,9 @@
|
|
|
18
18
|
*/
|
|
19
19
|
export declare const playbookDefinition: {
|
|
20
20
|
readonly ref: "bottom_up.assemble-verify";
|
|
21
|
-
readonly version: "0.
|
|
21
|
+
readonly version: "0.4.0";
|
|
22
22
|
readonly phase: "bottom_up";
|
|
23
|
-
readonly intent: "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over the application
|
|
23
|
+
readonly intent: "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'). A boot probe, the whole test suite and OpenAPI/docs regeneration are NOT in this set: each needs a running stack or a companion affordance that does not exist, and declaring them here without running them is exactly what made the deleted version of this playbook inert.";
|
|
24
24
|
readonly preconditions: readonly [{
|
|
25
25
|
readonly kind: "artifact_exists";
|
|
26
26
|
readonly selector: {
|
|
@@ -18,9 +18,9 @@
|
|
|
18
18
|
*/
|
|
19
19
|
export const playbookDefinition = {
|
|
20
20
|
"ref": "bottom_up.assemble-verify",
|
|
21
|
-
"version": "0.
|
|
21
|
+
"version": "0.4.0",
|
|
22
22
|
"phase": "bottom_up",
|
|
23
|
-
"intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over the application
|
|
23
|
+
"intent": "Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'). A boot probe, the whole test suite and OpenAPI/docs regeneration are NOT in this set: each needs a running stack or a companion affordance that does not exist, and declaring them here without running them is exactly what made the deleted version of this playbook inert.",
|
|
24
24
|
"preconditions": [
|
|
25
25
|
{ "kind": "artifact_exists", "selector": { "family": "build-plan" } }
|
|
26
26
|
],
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.assemble-verify/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,2BAA2B;IAClC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,
|
|
1
|
+
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.assemble-verify/playbook.definition.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC/B;IACE,KAAK,EAAE,2BAA2B;IAClC,SAAS,EAAE,OAAO;IAClB,OAAO,EAAE,WAAW;IACpB,QAAQ,EAAE,sjFAAsjF;IAChkF,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;YACX,iCAAiC;SAClC;KACF;IACD,UAAU,EAAE,mBAAmB;IAC/B,UAAU,EAAE,gBAAgB;IAC5B;;;;;;;OAOG;IACH,QAAQ,EAAE;QACR,SAAS,EAAE,EAAE;QACb,eAAe,EAAE,OAAO;KACzB;IACD,WAAW,EAAE,eAAe;CACpB,CAAC","sourcesContent":["/**\n * Canonical native declaration for topic 7 — the app-wide assemble/verify step.\n *\n * REBUILT rather than restored (issue #147). A playbook of this ref existed from\n * 2026-07-10 and was deleted on 2026-08-25 with the app-creation digest\n * demolition; the question it asked went with it, even though answering \"does\n * the built application assemble?\" needs no digests. Restoring it verbatim was\n * rejected: it declared the retired `COMPOSITE` executor, depended on two\n * families the demolition removed (`foundation-manifest`, `build-verification`),\n * and its method was explicit that NONE of its checks were actually run by the\n * runner — `// TODO CLI COMMAND:` placeholders and \"companion affordances that\n * do not exist yet\".\n *\n * What is different now is that the checks RUN. `DETERMINISTIC_CLI` is honoured\n * by the runtime as of #147, and the check refs below resolve through the same\n * closed `APPLICATION_CODING_TASK_VERIFICATION_CATALOG` a coding task uses, so\n * an unknown ref is refused rather than silently skipped.\n */\nexport const playbookDefinition =\n{\n \"ref\": \"bottom_up.assemble-verify\",\n \"version\": \"0.4.0\",\n \"phase\": \"bottom_up\",\n \"intent\": \"Bottom-up assemble & verify — the FINAL bottom-up step and the capstone of the build: the pivot from having BUILT the application (the decompose / dispatch / scale loop authored its modules, resources, config and integrations) to answering ONE mechanical question — does the built application ASSEMBLE? It runs the deterministic verification set over EVERY workspace package the application has (specifications, shared-lib, backend-api, frontend, and the website, technical documentation site, workers and minions it composed), derived from those packages rather than listed, OUTSIDE any coding agent, and reports a per-check outcome. It fixes NOTHING: a failure is surfaced for a refinement re-dispatch, which is a different playbook's job, and it authors no schemas and writes no code. Deliberately DISTINCT from the refinement phase's coverage audit, which also binds topic 7 but asks a SEMANTIC question (does the built app match the intent — specs diffed against introspected reality). This playbook never diffs intent against reality; if you are judging coverage you are in the refinement lane. Scope honesty: the check set is the whole-application TYPECHECK across every package — the question 'does it compile as one program', which no per-task check can answer because the dispatch lane typechecks only the package a task mutated — PLUS the schema-plan drift gate (`check:schema-plan-in-sync`), which asks whether the modelled resources have migrations behind them. The second is not a variant of the first: on a PostgreSQL-backed application a table exists only because a migration built it, so a resource whose migration was never generated compiles green in every package and then refuses to boot on `postgresql_table_schema_mismatch` — invisible to a typecheck, because no type in the program knows whether a table exists. It is safe on MongoDB applications and on unbuilt trees because it resolves three outcomes (not adopted / could-not-ask / decided) rather than reading an exit code. Since #2228 it also asks the two questions a typecheck cannot: does each optional site BUILD (the website's `astro build`, the documentation portal's `docusaurus build`; an absent package answers 'nothing to build'), and does the configuration pass `wildo config validate` (errors fail, warnings do not, a missing CLI is 'we could not ask'). A boot probe, the whole test suite and OpenAPI/docs regeneration are NOT in this set: each needs a running stack or a companion affordance that does not exist, and declaring them here without running them is exactly what made the deleted version of this playbook inert.\",\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 \"application-database-migrations\"\n ]\n },\n \"executor\": \"deterministic_cli\",\n \"approval\": \"approve_result\",\n /*\n * Token and model-call ceilings are OMITTED, not zeroed.\n *\n * Every field here is optional, and this tier makes no model calls at all — it runs typechecks in\n * a subprocess. Declaring `maxModelCalls: 0` is rejected by the schema (positive only), and\n * declaring `1` to satisfy it would state a ceiling nobody chose for a resource that is never\n * consumed. What IS bounded is wall-clock and how many times the step may run.\n */\n \"budget\": {\n \"maxRuns\": 40,\n \"maxDurationMs\": 3600000\n },\n \"onFailure\": \"keep_and_flag\",\n} as const;\n"]}
|
|
@@ -23,9 +23,10 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase } from '@wildo-ai/saas-spe
|
|
|
23
23
|
*
|
|
24
24
|
* ## The dispatch LOOP is the child being re-offered, on purpose
|
|
25
25
|
*
|
|
26
|
-
* `build-dispatch` is a `CODING_AGENT` step: one run dispatches
|
|
27
|
-
*
|
|
28
|
-
*
|
|
26
|
+
* `build-dispatch` is a `CODING_AGENT` step: one run dispatches a WAVE of ready tasks — up to the
|
|
27
|
+
* application's build parallelism at once, 5 by default, one when it is set to 1 (#1528) — each a coding
|
|
28
|
+
* run or a companion-owned generation step (labels, logo, emails, seeds) routed by the task's own target
|
|
29
|
+
* kind, waits for them, and reports. It lands no family, so the runtime never marks it delivered and
|
|
29
30
|
* offers it again every round: that IS the loop. The plan's readiness is re-derived from git each
|
|
30
31
|
* time, so a task accepted between two rounds unblocks its dependents without anyone re-planning.
|
|
31
32
|
*
|
|
@@ -53,15 +54,13 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase } from '@wildo-ai/saas-spe
|
|
|
53
54
|
* refused) re-opens `bottom_up.build-decompose` in refine mode only once a verdict routes (#1498),
|
|
54
55
|
* and that declaration belongs on a revise child rather than on this lane.
|
|
55
56
|
*
|
|
56
|
-
* ## `build-scale` is admitted, and
|
|
57
|
+
* ## `build-scale` is admitted, and it runs the same wave as dispatch
|
|
57
58
|
*
|
|
58
|
-
* Admitted in c6a1a235 (#1273) because nothing else could ever reach it.
|
|
59
|
-
*
|
|
60
|
-
*
|
|
61
|
-
*
|
|
62
|
-
*
|
|
63
|
-
* scale run from reading as a wave it never ran). #1528 owns building it. Until then the method
|
|
64
|
-
* tells the selector to prefer `build-dispatch`, so the two names do not compete for one act.
|
|
59
|
+
* Admitted in c6a1a235 (#1273) because nothing else could ever reach it. `build-scale` declares the
|
|
60
|
+
* same executor as `build-dispatch`, so it runs through the same CODING_AGENT branch: with a build
|
|
61
|
+
* parallelism above one, both start the same rolling wave (#1528); at one, both dispatch one task.
|
|
62
|
+
* Its method describes that wave from the scheduling side. The lane's method tells the selector to
|
|
63
|
+
* prefer `build-dispatch`, so the two names do not compete for one act (#2207).
|
|
65
64
|
*
|
|
66
65
|
* ## The lane ENDS on the maturity reading (#1496, admitted 2026-09-22 when its leaf landed)
|
|
67
66
|
*
|
|
@@ -117,6 +116,7 @@ export declare const playbookDefinition: {
|
|
|
117
116
|
skillRefs: any[];
|
|
118
117
|
choreography: {
|
|
119
118
|
admits: string[];
|
|
119
|
+
closingMove: string;
|
|
120
120
|
maximumIterations: number;
|
|
121
121
|
maximumLanesPerIteration: number;
|
|
122
122
|
maximumDurationMs: number;
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,8BAA8B,EAC9B,0BAA0B,EAC1B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,8BAA8B,EAC9B,0BAA0B,EAC1B,0BAA0B,EAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,EAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2FG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0H9B,CAAC"}
|
|
@@ -23,9 +23,10 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-sp
|
|
|
23
23
|
*
|
|
24
24
|
* ## The dispatch LOOP is the child being re-offered, on purpose
|
|
25
25
|
*
|
|
26
|
-
* `build-dispatch` is a `CODING_AGENT` step: one run dispatches
|
|
27
|
-
*
|
|
28
|
-
*
|
|
26
|
+
* `build-dispatch` is a `CODING_AGENT` step: one run dispatches a WAVE of ready tasks — up to the
|
|
27
|
+
* application's build parallelism at once, 5 by default, one when it is set to 1 (#1528) — each a coding
|
|
28
|
+
* run or a companion-owned generation step (labels, logo, emails, seeds) routed by the task's own target
|
|
29
|
+
* kind, waits for them, and reports. It lands no family, so the runtime never marks it delivered and
|
|
29
30
|
* offers it again every round: that IS the loop. The plan's readiness is re-derived from git each
|
|
30
31
|
* time, so a task accepted between two rounds unblocks its dependents without anyone re-planning.
|
|
31
32
|
*
|
|
@@ -53,15 +54,13 @@ import { MetaWorkflow_InputRender, MetaWorkflow_Phase, } from '@wildo-ai/saas-sp
|
|
|
53
54
|
* refused) re-opens `bottom_up.build-decompose` in refine mode only once a verdict routes (#1498),
|
|
54
55
|
* and that declaration belongs on a revise child rather than on this lane.
|
|
55
56
|
*
|
|
56
|
-
* ## `build-scale` is admitted, and
|
|
57
|
+
* ## `build-scale` is admitted, and it runs the same wave as dispatch
|
|
57
58
|
*
|
|
58
|
-
* Admitted in c6a1a235 (#1273) because nothing else could ever reach it.
|
|
59
|
-
*
|
|
60
|
-
*
|
|
61
|
-
*
|
|
62
|
-
*
|
|
63
|
-
* scale run from reading as a wave it never ran). #1528 owns building it. Until then the method
|
|
64
|
-
* tells the selector to prefer `build-dispatch`, so the two names do not compete for one act.
|
|
59
|
+
* Admitted in c6a1a235 (#1273) because nothing else could ever reach it. `build-scale` declares the
|
|
60
|
+
* same executor as `build-dispatch`, so it runs through the same CODING_AGENT branch: with a build
|
|
61
|
+
* parallelism above one, both start the same rolling wave (#1528); at one, both dispatch one task.
|
|
62
|
+
* Its method describes that wave from the scheduling side. The lane's method tells the selector to
|
|
63
|
+
* prefer `build-dispatch`, so the two names do not compete for one act (#2207).
|
|
65
64
|
*
|
|
66
65
|
* ## The lane ENDS on the maturity reading (#1496, admitted 2026-09-22 when its leaf landed)
|
|
67
66
|
*
|
|
@@ -97,7 +96,7 @@ export const playbookDefinition = {
|
|
|
97
96
|
ref: 'bottom_up.build',
|
|
98
97
|
version: '0.1.0',
|
|
99
98
|
phase: MetaWorkflow_Phase.BOTTOM_UP,
|
|
100
|
-
intent: 'Drive the BUILD of the application as one lane: decompose the accepted conception into a build plan, dispatch the plan\'s ready tasks one at a time
|
|
99
|
+
intent: 'Drive the BUILD of the application as one lane: decompose the accepted conception into a build plan, dispatch the plan\'s ready tasks in parallel waves — up to the application\'s build parallelism at once (5 by default; 1 means one at a time), coding runs and the companion\'s own generation steps alike — until every task has landed, then assemble and verify the built application, and read its maturity against the requirements it was asked to satisfy. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. The build plan is decomposed ONCE unless its inputs have moved since it landed (the decomposer\'s own gate says so). Dispatch is one wave per run (the parallelism is inside it, so select ONE child per round) and lands no family, so it is offered every round: keep selecting it while the plan has tasks left, with each round\'s objective naming what the previous round\'s wave dispatched and how each run came out. Prefer build-dispatch to build-scale: both start the same wave. When dispatch reports the plan exhausted, select assemble-verify, and then the maturity reading. STOP on the reading: it is what this lane ends on, and it names a STAGE rather than a completion. Stop early only when dispatch reports a task that cannot land twice, or a parked question waits on the creator — say which. A parked coding question waits for the creator; run everything else.',
|
|
101
100
|
preconditions: [
|
|
102
101
|
{ kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'domain-plan' } },
|
|
103
102
|
{ kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'placement-plan' } },
|
|
@@ -144,26 +143,34 @@ export const playbookDefinition = {
|
|
|
144
143
|
* the eligibility board answers about the playbook, never about whether anyone can dispatch
|
|
145
144
|
* it. Measured on the first end-to-end run, where it cost the build lane its parallelism.
|
|
146
145
|
*
|
|
147
|
-
* It does not replace `build-dispatch
|
|
148
|
-
*
|
|
149
|
-
*
|
|
150
|
-
* run's change-set attributable, and the wave reconciliation. Both stay admitted so the lane
|
|
151
|
-
* can still take one task at a time when that is what the frontier holds.
|
|
146
|
+
* It does not replace `build-dispatch`: both start the same wave, and the method prefers
|
|
147
|
+
* dispatch. Scale stays admitted because its method is where the wave's scheduling — the
|
|
148
|
+
* ready-set, the width, the shared-worktree repair — is described for a selector that asks.
|
|
152
149
|
*/
|
|
153
150
|
'bottom_up.build-scale',
|
|
154
151
|
'bottom_up.build-dispatch',
|
|
155
152
|
'bottom_up.build-decompose',
|
|
156
153
|
],
|
|
157
154
|
/*
|
|
158
|
-
* The schema's ceiling, and for this lane it is the BINDING bound: one round per
|
|
159
|
-
*
|
|
160
|
-
* run. So a full build is SEVERAL runs of this lane, each resuming where readiness now stands —
|
|
155
|
+
* The schema's ceiling, and for this lane it is the BINDING bound: one round per wave (per task
|
|
156
|
+
* at a build parallelism of 1), and a 42-task plan (Wonder CRM's, measured) can need more rounds
|
|
157
|
+
* than any composite may run. So a full build is SEVERAL runs of this lane, each resuming where readiness now stands —
|
|
161
158
|
* which is correct by construction (the plan's state is git, not the run) and is the reason the
|
|
162
159
|
* lane is re-runnable at all. A breaker, not a budget.
|
|
163
160
|
*/
|
|
161
|
+
/*
|
|
162
|
+
* No run of this lane ends without asking whether the application ASSEMBLES (#2228). On app-creation-test-004 the
|
|
163
|
+
* lane reached 91 of 93 tasks and stopped, assemble-verify was never selected, and the website that did not build
|
|
164
|
+
* went unreported. When the selector stops first — the plan exhausted, a task that cannot land, a question waiting
|
|
165
|
+
* on the creator — the runtime runs assemble-verify; a run that cannot reach it (no build plan yet) ends recorded
|
|
166
|
+
* as not concluded. The cost is deliberate: a paused build also pays one assembly pass, because a pause is where a
|
|
167
|
+
* person reads the state, and the state without this answer is the misleading one.
|
|
168
|
+
*/
|
|
169
|
+
closingMove: 'bottom_up.assemble-verify',
|
|
164
170
|
maximumIterations: 20,
|
|
165
|
-
//
|
|
166
|
-
//
|
|
171
|
+
// One lane per round because the parallelism is INSIDE the dispatch child: its wave already runs
|
|
172
|
+
// up to the build parallelism of tasks at once (#1528). A second lane would start a second wave
|
|
173
|
+
// beside it and double the width the person set (#2207).
|
|
167
174
|
maximumLanesPerIteration: 1,
|
|
168
175
|
/*
|
|
169
176
|
* Six hours. A coding run measured ~15 minutes and ~$26 (#1454); twenty rounds of dispatch at
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.js","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,8BAA8B,EAC9B,0BAA0B,EAC1B,0BAA0B,GAC3B,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EACL,wBAAwB,EACxB,kBAAkB,GAEnB,MAAM,oDAAoD,CAAC;AAE5D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4FG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,GAAG,EAAE,iBAAiB;IACtB,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,SAAS;IACnC,MAAM,EACJ,irCAAirC;IACnrC,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,aAAa,EAAE,EAAE;QACxF,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,gBAAgB,EAAE,EAAE;KAC5F;IACD,kGAAkG;IAClG,6DAA6D;IAC7D,MAAM,EAAE;QACN,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,EAAE,MAAM,EAAE,YAAY,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;KAC/D;IACD,kGAAkG;IAClG,iFAAiF;IACjF,OAAO,EAAE,EAAE;IACX;;;;OAIG;IACH,WAAW,EAAE;QACX;YACE,GAAG,EAAE,iCAAiC;YACtC,YAAY,EAAE,sGAAsG;SACrH;KACF;IACD,MAAM,EAAE;QACN,SAAS,EAAE,EAAE;QACb,YAAY,EAAE;YACZ;;;eAGG;YACH,MAAM,EAAE;gBACN,gGAAgG;gBAChG,gFAAgF;gBAChF,4BAA4B;gBAC5B,2BAA2B;gBAC3B;;;;;;;;;;;;;;mBAcG;gBACH,uBAAuB;gBACvB,0BAA0B;gBAC1B,2BAA2B;aAC5B;YACD;;;;;;eAMG;YACH,iBAAiB,EAAE,EAAE;YACrB,+FAA+F;YAC/F,gFAAgF;YAChF,wBAAwB,EAAE,CAAC;YAC3B;;;;;eAKG;YACH,iBAAiB,EAAE,UAAU;YAC7B;;;;;eAKG;YACH,eAAe,EAAE;gBACf;oBACE,aAAa,EAAE,2BAA2B;oBAC1C,YAAY,EAAE,wEAAwE;oBACtF,QAAQ,EAAE,CAAC,8BAA8B,CAAC,GAAG,CAAC;oBAC9C,MAAM,EAAE,CAAC,2BAA2B,CAAC;iBACtC;gBACD;oBACE,aAAa,EAAE,2BAA2B;oBAC1C,YAAY,EAAE,iEAAiE;oBAC/E,QAAQ,EAAE,CAAC,8BAA8B,CAAC,GAAG,CAAC;oBAC9C,MAAM,EAAE,CAAC,2BAA2B,CAAC;iBACtC;aACF;SACF;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_EvaluationVerdict,\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 BUILD LANE — from an accepted conception to a built, verified application and its maturity\n * reading (#1501, epic #1506).\n *\n * Until this existed `build-decompose`, `build-dispatch` and `assemble-verify` were driven by hand or\n * by `dispatch_next`: a task that could not land was re-offered until the loop guard stopped it, a\n * coherence GAP found after the build had no way back to conception, and the lane ended on four\n * typechecks with no reading of what was built against what was required. This lane runs the three\n * as one choreography — decompose, then dispatch until the plan is exhausted, then assemble — and it\n * will end on the maturity reading (#1496): a stage against the requirements, never a \"done\".\n *\n * ## The lane's OWN gate is the conception lane's output\n *\n * READINESS on the placement plan, which is the last family the conception lane lands and the one\n * the decomposer only EXPECTS on its own (`artifact_expected`, so a standalone decompose may run\n * without it — which is how an application came to have no navigation, #1265 R-6). Gating the lane\n * at READINESS is what makes \"the decomposer cannot start before placement has landed\" true for a\n * build driven through the lane: the leaf keeps its own sequencing gate and its own explicit-run\n * door, and the lane will not open until placement is on record. The domain plan is declared for the\n * same reason, and both are declared as inputs (audit rule 24).\n *\n * ## The dispatch LOOP is the child being re-offered, on purpose\n *\n * `build-dispatch` is a `CODING_AGENT` step: one run dispatches ONE ready task (a coding run, or a\n * companion-owned generation step — labels, logo, emails, seeds — routed by the task's own target\n * kind), waits for it, and reports. It lands no family, so the runtime never marks it delivered and\n * offers it again every round: that IS the loop. The plan's readiness is re-derived from git each\n * time, so a task accepted between two rounds unblocks its dependents without anyone re-planning.\n *\n * ## How the lane SEES its own work, and where it ends\n *\n * Both halves were measured missing on this lane's first live run and both are now built (#1501):\n *\n * - **A dispatch child reports what it did**, as a step value under `dispatch:<ref>` — the task, its\n * kind, how its coding run settled, and how much of the plan is left. Before that a child which\n * lands no family returned nothing into the run's scope, so the round history carried the objective\n * and no outcome: over twenty live rounds the selector narrated task names it could not have seen\n * and finally instructed the child to \"inspect the recorded D4 outcome for the immediately preceding\n * dispatch\" — the composite asking to be told what it should have been handed.\n * - **An exhausted plan withholds dispatch** rather than failing it. `BUILD_PLAN_EXHAUSTED` is the\n * twin of `NOTHING_TO_DECOMPOSE` one step down the same plan, and READINESS where that one is\n * SEQUENCING: re-decomposing a finished plan succeeds, dispatching one cannot, and only READINESS\n * ends the loop inside an explicitly-run lane, where sequencing is bypassed. So the round that\n * used to re-offer a dispatch that threw now offers `assemble-verify`, and the lane ends there.\n * - **A plan whose every ready task is stuck withholds dispatch too.** `BUILD_PLAN_BLOCKED_ON_STUCK_TASKS`\n * is exhaustion's twin for \"tasks remain, and none that is ready can run\": the dispatcher refuses\n * before starting one, so the lane stops offering it and says which tasks hold it, instead of\n * failing a dispatch every round (#1547).\n *\n * What is still a report rather than a route: a task that cannot land (parked on a question, or\n * refused) re-opens `bottom_up.build-decompose` in refine mode only once a verdict routes (#1498),\n * and that declaration belongs on a revise child rather than on this lane.\n *\n * ## `build-scale` is admitted, and today it runs as a dispatch\n *\n * Admitted in c6a1a235 (#1273) because nothing else could ever reach it. This section used to argue\n * the opposite, and it was left standing beside that admission — a lane saying two things at once.\n * What is true now: `build-scale` declares the same executor as `build-dispatch` and runs through\n * the same single-flight branch, one ready task per run. The wave its method describes does not\n * exist yet (the runtime says so where it reports a dispatch, and `remainingReadyTaskRefs` keeps a\n * scale run from reading as a wave it never ran). #1528 owns building it. Until then the method\n * tells the selector to prefer `build-dispatch`, so the two names do not compete for one act.\n *\n * ## The lane ENDS on the maturity reading (#1496, admitted 2026-09-22 when its leaf landed)\n *\n * `bottom_up.assemble-verify` answers whether what was built ASSEMBLES — four typechecks and a\n * migration probe, its own method saying it \"does not boot the application, run its test suite\".\n * `bottom_up.maturity-reading` answers the question that makes the lane worth running: which of the\n * application's own requirements are addressed, by what evidence, and what STAGE that puts it at.\n *\n * Paul, 2026-09-22: *\"there are no 'Done' for an app, there are a measurement face to requirements,\n * with some stage … this measurement should be evolutive.\"* So the lane's closing decision is read\n * against the reading, and a run that stops short of it has not finished — which is why it is listed\n * FIRST in `admits`, where the trap check puts the closing move.\n *\n * **Only this lane admits it, deliberately.** Its own gate is `artifact_exists: requirements`, so it\n * could be offered far earlier — and a reading of an application nobody has conceived says \"nothing is\n * addressed\", which is true and worth nothing. A second admitter would also let one root run land the\n * same reading twice from the same inputs, because a nested lane's delivered set is its own. The root's\n * ending is the boundary decision READ AGAINST whatever reading is on record, not a second reading.\n *\n * The surface lanes' work (UX #1493, website #1492, documentation #1494, integration #1495) feeds the\n * same task graph through DECOMPOSITION rather than through new children here — their plans are the\n * conception lane's, and the decomposer declares all of them as inputs.\n *\n * ## Loop-back — declared when the mechanism exists\n *\n * | signal | re-opens | how, once it can |\n * |---|---|---|\n * | a task that cannot land (parked, refused, failed twice) | `bottom_up.build-decompose` in refine mode | verdict routing (#1498) on the dispatch report |\n * | a coherence GAP naming a module or relationship | `bottom_up.domain-plan`, through the root | the root routes it to the conception lane (#1503, after #1497) |\n * | a domain plan or placement newer than the landed build plan | `bottom_up.build-decompose` | ALREADY WORKS — the decompose completion gate re-opens on any newer upstream commit |\n */\nexport const playbookDefinition = {\n ref: 'bottom_up.build',\n version: '0.1.0',\n phase: MetaWorkflow_Phase.BOTTOM_UP,\n intent:\n 'Drive the BUILD of the application as one lane: decompose the accepted conception into a build plan, dispatch the plan\\'s ready tasks one at a time — coding runs and the companion\\'s own generation steps alike — until every task has landed, then assemble and verify the built application, and read its maturity against the requirements it was asked to satisfy. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. The build plan is decomposed ONCE unless its inputs have moved since it landed (the decomposer\\'s own gate says so). Dispatch is one task per run and lands no family, so it is offered every round: keep selecting it while the plan has tasks left, with each round\\'s objective naming what the previous round dispatched. When dispatch reports the plan exhausted, select assemble-verify, and then the maturity reading. STOP on the reading: it is what this lane ends on, and it names a STAGE rather than a completion. Stop early only when dispatch reports a task that cannot land twice, or a parked question waits on the creator — say which. A parked coding question waits for the creator; run everything else.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'domain-plan' } },\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'placement-plan' } },\n ],\n // For the SELECTOR: the plans as maps of what exists; the build plan's tasks by ref, so a round's\n // objective can name the task the previous round dispatched.\n inputs: [\n { family: 'domain-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'placement-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'build-plan', render: MetaWorkflow_InputRender.MAP },\n ],\n // Nothing — the lane's write scope is resolved transitively through `admits`: the build plan, and\n // the application WORKSPACE, which a dispatch writes and a human commit accepts.\n outputs: [],\n /*\n * The one value this lane hands up (#1638): the decomposer's verdict, so the root can send the run back\n * to CONCEPTION when the plan cannot be right because what it rests on is wrong (the decomposer's\n * `conception-buildable` criterion). Its own coverage GAPs stay in the lane and re-open the decomposer.\n */\n stepOutputs: [\n {\n ref: 'judge:bottom_up.build-decompose',\n condensation: 'The decomposer verdict on the build plan: overall and per criterion, including conception-buildable.',\n },\n ],\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 verify an application nobody had built, and fail loudly.\n */\n admits: [\n // The lane's ENDING, and the reason it is not `assemble-verify`: assembly asks whether what was\n // built compiles, the reading asks what it is worth against what was asked for.\n 'bottom_up.maturity-reading',\n 'bottom_up.assemble-verify',\n /*\n * SCALE, and the reason it is listed beside dispatch rather than instead of it.\n *\n * It was admitted by NOTHING until 2026-09-23 (#1273) — authored, compiled, shipped in the\n * catalog and reported `eligible: true` by the board, while no lane could ever reach it. A\n * playbook no composite admits is unreachable from any journey, and nothing reports that:\n * the eligibility board answers about the playbook, never about whether anyone can dispatch\n * it. Measured on the first end-to-end run, where it cost the build lane its parallelism.\n *\n * It does not replace `build-dispatch` and must not: each of its parallel slots INVOKES the\n * single-flight dispatch contract, and it adds only what dispatch deliberately left open —\n * the ready-SET, the parallelism degree, the worktree isolation that keeps each concurrent\n * run's change-set attributable, and the wave reconciliation. Both stay admitted so the lane\n * can still take one task at a time when that is what the frontier holds.\n */\n 'bottom_up.build-scale',\n 'bottom_up.build-dispatch',\n 'bottom_up.build-decompose',\n ],\n /*\n * The schema's ceiling, and for this lane it is the BINDING bound: one round per dispatched\n * task, and a 42-task plan (Wonder CRM's, measured) needs more rounds than any composite may\n * run. So a full build is SEVERAL runs of this lane, each resuming where readiness now stands —\n * which is correct by construction (the plan's state is git, not the run) and is the reason the\n * lane is re-runnable at all. A breaker, not a budget.\n */\n maximumIterations: 20,\n // Single-flight dispatch: one coding run at a time holds the workspace lock, and a second task\n // selected in the same round would be refused at admission. One lane per round.\n maximumLanesPerIteration: 1,\n /*\n * Six hours. A coding run measured ~15 minutes and ~$26 (#1454); twenty rounds of dispatch at\n * that figure is five hours, and a decomposition or an assembly is minutes beside it. Far longer\n * than the companion's HTTP ceiling (30 min): submit with `async: true` and read the outcome\n * from `/playbooks/runs`. Literal: the evaluator computes no expressions.\n */\n maximumDurationMs: 21_600_000,\n /*\n * The loop back to DECOMPOSITION (#1501): a plan its own judge finds does not cover the domain\n * plan's modules, resources or relationships is re-decomposed before anything is built on it.\n * The decomposer re-opens itself, in refine mode per the method, keeping the refs of what landed.\n * The loop back to CONCEPTION is the ROOT's, from this lane's exported verdict (#1638).\n */\n reopenOnVerdict: [\n {\n whenVerdictOf: 'bottom_up.build-decompose',\n criterionRef: 'application-creation:criterion/build-plan-module-and-resource-coverage',\n verdicts: [MetaWorkflow_EvaluationVerdict.GAP],\n reopen: ['bottom_up.build-decompose'],\n },\n {\n whenVerdictOf: 'bottom_up.build-decompose',\n criterionRef: 'application-creation:criterion/build-plan-relationship-coverage',\n verdicts: [MetaWorkflow_EvaluationVerdict.GAP],\n reopen: ['bottom_up.build-decompose'],\n },\n ],\n },\n },\n /*\n * The lane's closing decision — read the maturity, accept the stage or send the build back.\n * LIVE since #111 landed: the runtime derives this lane's boundary from the field and the companion\n * projects one `approve_result` decision over the paths the lane kept — which for this lane is the\n * application WORKSPACE its dispatches wrote, not a specifications family. The maturity reading the\n * decision should be read against is still #1496.\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.build/playbook.definition.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,8BAA8B,EAC9B,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,iBAAiB;IACtB,OAAO,EAAE,OAAO;IAChB,KAAK,EAAE,kBAAkB,CAAC,SAAS;IACnC,MAAM,EACJ,+6CAA+6C;IACj7C,aAAa,EAAE;QACb,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,aAAa,EAAE,EAAE;QACxF,EAAE,IAAI,EAAE,0BAA0B,CAAC,cAAc,EAAE,QAAQ,EAAE,EAAE,MAAM,EAAE,gBAAgB,EAAE,EAAE;KAC5F;IACD,kGAAkG;IAClG,6DAA6D;IAC7D,MAAM,EAAE;QACN,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,EAAE,MAAM,EAAE,YAAY,EAAE,MAAM,EAAE,wBAAwB,CAAC,GAAG,EAAE;KAC/D;IACD,kGAAkG;IAClG,iFAAiF;IACjF,OAAO,EAAE,EAAE;IACX;;;;OAIG;IACH,WAAW,EAAE;QACX;YACE,GAAG,EAAE,iCAAiC;YACtC,YAAY,EAAE,sGAAsG;SACrH;KACF;IACD,MAAM,EAAE;QACN,SAAS,EAAE,EAAE;QACb,YAAY,EAAE;YACZ;;;eAGG;YACH,MAAM,EAAE;gBACN,gGAAgG;gBAChG,gFAAgF;gBAChF,4BAA4B;gBAC5B,2BAA2B;gBAC3B;;;;;;;;;;;;mBAYG;gBACH,uBAAuB;gBACvB,0BAA0B;gBAC1B,2BAA2B;aAC5B;YACD;;;;;;eAMG;YACH;;;;;;;eAOG;YACH,WAAW,EAAE,2BAA2B;YACxC,iBAAiB,EAAE,EAAE;YACrB,iGAAiG;YACjG,gGAAgG;YAChG,yDAAyD;YACzD,wBAAwB,EAAE,CAAC;YAC3B;;;;;eAKG;YACH,iBAAiB,EAAE,UAAU;YAC7B;;;;;eAKG;YACH,eAAe,EAAE;gBACf;oBACE,aAAa,EAAE,2BAA2B;oBAC1C,YAAY,EAAE,wEAAwE;oBACtF,QAAQ,EAAE,CAAC,8BAA8B,CAAC,GAAG,CAAC;oBAC9C,MAAM,EAAE,CAAC,2BAA2B,CAAC;iBACtC;gBACD;oBACE,aAAa,EAAE,2BAA2B;oBAC1C,YAAY,EAAE,iEAAiE;oBAC/E,QAAQ,EAAE,CAAC,8BAA8B,CAAC,GAAG,CAAC;oBAC9C,MAAM,EAAE,CAAC,2BAA2B,CAAC;iBACtC;aACF;SACF;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_EvaluationVerdict,\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 BUILD LANE — from an accepted conception to a built, verified application and its maturity\n * reading (#1501, epic #1506).\n *\n * Until this existed `build-decompose`, `build-dispatch` and `assemble-verify` were driven by hand or\n * by `dispatch_next`: a task that could not land was re-offered until the loop guard stopped it, a\n * coherence GAP found after the build had no way back to conception, and the lane ended on four\n * typechecks with no reading of what was built against what was required. This lane runs the three\n * as one choreography — decompose, then dispatch until the plan is exhausted, then assemble — and it\n * will end on the maturity reading (#1496): a stage against the requirements, never a \"done\".\n *\n * ## The lane's OWN gate is the conception lane's output\n *\n * READINESS on the placement plan, which is the last family the conception lane lands and the one\n * the decomposer only EXPECTS on its own (`artifact_expected`, so a standalone decompose may run\n * without it — which is how an application came to have no navigation, #1265 R-6). Gating the lane\n * at READINESS is what makes \"the decomposer cannot start before placement has landed\" true for a\n * build driven through the lane: the leaf keeps its own sequencing gate and its own explicit-run\n * door, and the lane will not open until placement is on record. The domain plan is declared for the\n * same reason, and both are declared as inputs (audit rule 24).\n *\n * ## The dispatch LOOP is the child being re-offered, on purpose\n *\n * `build-dispatch` is a `CODING_AGENT` step: one run dispatches a WAVE of ready tasks — up to the\n * application's build parallelism at once, 5 by default, one when it is set to 1 (#1528) — each a coding\n * run or a companion-owned generation step (labels, logo, emails, seeds) routed by the task's own target\n * kind, waits for them, and reports. It lands no family, so the runtime never marks it delivered and\n * offers it again every round: that IS the loop. The plan's readiness is re-derived from git each\n * time, so a task accepted between two rounds unblocks its dependents without anyone re-planning.\n *\n * ## How the lane SEES its own work, and where it ends\n *\n * Both halves were measured missing on this lane's first live run and both are now built (#1501):\n *\n * - **A dispatch child reports what it did**, as a step value under `dispatch:<ref>` — the task, its\n * kind, how its coding run settled, and how much of the plan is left. Before that a child which\n * lands no family returned nothing into the run's scope, so the round history carried the objective\n * and no outcome: over twenty live rounds the selector narrated task names it could not have seen\n * and finally instructed the child to \"inspect the recorded D4 outcome for the immediately preceding\n * dispatch\" — the composite asking to be told what it should have been handed.\n * - **An exhausted plan withholds dispatch** rather than failing it. `BUILD_PLAN_EXHAUSTED` is the\n * twin of `NOTHING_TO_DECOMPOSE` one step down the same plan, and READINESS where that one is\n * SEQUENCING: re-decomposing a finished plan succeeds, dispatching one cannot, and only READINESS\n * ends the loop inside an explicitly-run lane, where sequencing is bypassed. So the round that\n * used to re-offer a dispatch that threw now offers `assemble-verify`, and the lane ends there.\n * - **A plan whose every ready task is stuck withholds dispatch too.** `BUILD_PLAN_BLOCKED_ON_STUCK_TASKS`\n * is exhaustion's twin for \"tasks remain, and none that is ready can run\": the dispatcher refuses\n * before starting one, so the lane stops offering it and says which tasks hold it, instead of\n * failing a dispatch every round (#1547).\n *\n * What is still a report rather than a route: a task that cannot land (parked on a question, or\n * refused) re-opens `bottom_up.build-decompose` in refine mode only once a verdict routes (#1498),\n * and that declaration belongs on a revise child rather than on this lane.\n *\n * ## `build-scale` is admitted, and it runs the same wave as dispatch\n *\n * Admitted in c6a1a235 (#1273) because nothing else could ever reach it. `build-scale` declares the\n * same executor as `build-dispatch`, so it runs through the same CODING_AGENT branch: with a build\n * parallelism above one, both start the same rolling wave (#1528); at one, both dispatch one task.\n * Its method describes that wave from the scheduling side. The lane's method tells the selector to\n * prefer `build-dispatch`, so the two names do not compete for one act (#2207).\n *\n * ## The lane ENDS on the maturity reading (#1496, admitted 2026-09-22 when its leaf landed)\n *\n * `bottom_up.assemble-verify` answers whether what was built ASSEMBLES — four typechecks and a\n * migration probe, its own method saying it \"does not boot the application, run its test suite\".\n * `bottom_up.maturity-reading` answers the question that makes the lane worth running: which of the\n * application's own requirements are addressed, by what evidence, and what STAGE that puts it at.\n *\n * Paul, 2026-09-22: *\"there are no 'Done' for an app, there are a measurement face to requirements,\n * with some stage … this measurement should be evolutive.\"* So the lane's closing decision is read\n * against the reading, and a run that stops short of it has not finished — which is why it is listed\n * FIRST in `admits`, where the trap check puts the closing move.\n *\n * **Only this lane admits it, deliberately.** Its own gate is `artifact_exists: requirements`, so it\n * could be offered far earlier — and a reading of an application nobody has conceived says \"nothing is\n * addressed\", which is true and worth nothing. A second admitter would also let one root run land the\n * same reading twice from the same inputs, because a nested lane's delivered set is its own. The root's\n * ending is the boundary decision READ AGAINST whatever reading is on record, not a second reading.\n *\n * The surface lanes' work (UX #1493, website #1492, documentation #1494, integration #1495) feeds the\n * same task graph through DECOMPOSITION rather than through new children here — their plans are the\n * conception lane's, and the decomposer declares all of them as inputs.\n *\n * ## Loop-back — declared when the mechanism exists\n *\n * | signal | re-opens | how, once it can |\n * |---|---|---|\n * | a task that cannot land (parked, refused, failed twice) | `bottom_up.build-decompose` in refine mode | verdict routing (#1498) on the dispatch report |\n * | a coherence GAP naming a module or relationship | `bottom_up.domain-plan`, through the root | the root routes it to the conception lane (#1503, after #1497) |\n * | a domain plan or placement newer than the landed build plan | `bottom_up.build-decompose` | ALREADY WORKS — the decompose completion gate re-opens on any newer upstream commit |\n */\nexport const playbookDefinition = {\n ref: 'bottom_up.build',\n version: '0.1.0',\n phase: MetaWorkflow_Phase.BOTTOM_UP,\n intent:\n 'Drive the BUILD of the application as one lane: decompose the accepted conception into a build plan, dispatch the plan\\'s ready tasks in parallel waves — up to the application\\'s build parallelism at once (5 by default; 1 means one at a time), coding runs and the companion\\'s own generation steps alike — until every task has landed, then assemble and verify the built application, and read its maturity against the requirements it was asked to satisfy. An umbrella: it authors nothing itself; every child declares what it needs and the runtime recomputes what may run after each round. The build plan is decomposed ONCE unless its inputs have moved since it landed (the decomposer\\'s own gate says so). Dispatch is one wave per run (the parallelism is inside it, so select ONE child per round) and lands no family, so it is offered every round: keep selecting it while the plan has tasks left, with each round\\'s objective naming what the previous round\\'s wave dispatched and how each run came out. Prefer build-dispatch to build-scale: both start the same wave. When dispatch reports the plan exhausted, select assemble-verify, and then the maturity reading. STOP on the reading: it is what this lane ends on, and it names a STAGE rather than a completion. Stop early only when dispatch reports a task that cannot land twice, or a parked question waits on the creator — say which. A parked coding question waits for the creator; run everything else.',\n preconditions: [\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'domain-plan' } },\n { kind: MetaWorkflow_PredicateKind.ARTIFACT_VALID, selector: { family: 'placement-plan' } },\n ],\n // For the SELECTOR: the plans as maps of what exists; the build plan's tasks by ref, so a round's\n // objective can name the task the previous round dispatched.\n inputs: [\n { family: 'domain-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'placement-plan', render: MetaWorkflow_InputRender.MAP },\n { family: 'build-plan', render: MetaWorkflow_InputRender.MAP },\n ],\n // Nothing — the lane's write scope is resolved transitively through `admits`: the build plan, and\n // the application WORKSPACE, which a dispatch writes and a human commit accepts.\n outputs: [],\n /*\n * The one value this lane hands up (#1638): the decomposer's verdict, so the root can send the run back\n * to CONCEPTION when the plan cannot be right because what it rests on is wrong (the decomposer's\n * `conception-buildable` criterion). Its own coverage GAPs stay in the lane and re-open the decomposer.\n */\n stepOutputs: [\n {\n ref: 'judge:bottom_up.build-decompose',\n condensation: 'The decomposer verdict on the build plan: overall and per criterion, including conception-buildable.',\n },\n ],\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 verify an application nobody had built, and fail loudly.\n */\n admits: [\n // The lane's ENDING, and the reason it is not `assemble-verify`: assembly asks whether what was\n // built compiles, the reading asks what it is worth against what was asked for.\n 'bottom_up.maturity-reading',\n 'bottom_up.assemble-verify',\n /*\n * SCALE, and the reason it is listed beside dispatch rather than instead of it.\n *\n * It was admitted by NOTHING until 2026-09-23 (#1273) — authored, compiled, shipped in the\n * catalog and reported `eligible: true` by the board, while no lane could ever reach it. A\n * playbook no composite admits is unreachable from any journey, and nothing reports that:\n * the eligibility board answers about the playbook, never about whether anyone can dispatch\n * it. Measured on the first end-to-end run, where it cost the build lane its parallelism.\n *\n * It does not replace `build-dispatch`: both start the same wave, and the method prefers\n * dispatch. Scale stays admitted because its method is where the wave's scheduling — the\n * ready-set, the width, the shared-worktree repair — is described for a selector that asks.\n */\n 'bottom_up.build-scale',\n 'bottom_up.build-dispatch',\n 'bottom_up.build-decompose',\n ],\n /*\n * The schema's ceiling, and for this lane it is the BINDING bound: one round per wave (per task\n * at a build parallelism of 1), and a 42-task plan (Wonder CRM's, measured) can need more rounds\n * than any composite may run. So a full build is SEVERAL runs of this lane, each resuming where readiness now stands —\n * which is correct by construction (the plan's state is git, not the run) and is the reason the\n * lane is re-runnable at all. A breaker, not a budget.\n */\n /*\n * No run of this lane ends without asking whether the application ASSEMBLES (#2228). On app-creation-test-004 the\n * lane reached 91 of 93 tasks and stopped, assemble-verify was never selected, and the website that did not build\n * went unreported. When the selector stops first — the plan exhausted, a task that cannot land, a question waiting\n * on the creator — the runtime runs assemble-verify; a run that cannot reach it (no build plan yet) ends recorded\n * as not concluded. The cost is deliberate: a paused build also pays one assembly pass, because a pause is where a\n * person reads the state, and the state without this answer is the misleading one.\n */\n closingMove: 'bottom_up.assemble-verify',\n maximumIterations: 20,\n // One lane per round because the parallelism is INSIDE the dispatch child: its wave already runs\n // up to the build parallelism of tasks at once (#1528). A second lane would start a second wave\n // beside it and double the width the person set (#2207).\n maximumLanesPerIteration: 1,\n /*\n * Six hours. A coding run measured ~15 minutes and ~$26 (#1454); twenty rounds of dispatch at\n * that figure is five hours, and a decomposition or an assembly is minutes beside it. Far longer\n * than the companion's HTTP ceiling (30 min): submit with `async: true` and read the outcome\n * from `/playbooks/runs`. Literal: the evaluator computes no expressions.\n */\n maximumDurationMs: 21_600_000,\n /*\n * The loop back to DECOMPOSITION (#1501): a plan its own judge finds does not cover the domain\n * plan's modules, resources or relationships is re-decomposed before anything is built on it.\n * The decomposer re-opens itself, in refine mode per the method, keeping the refs of what landed.\n * The loop back to CONCEPTION is the ROOT's, from this lane's exported verdict (#1638).\n */\n reopenOnVerdict: [\n {\n whenVerdictOf: 'bottom_up.build-decompose',\n criterionRef: 'application-creation:criterion/build-plan-module-and-resource-coverage',\n verdicts: [MetaWorkflow_EvaluationVerdict.GAP],\n reopen: ['bottom_up.build-decompose'],\n },\n {\n whenVerdictOf: 'bottom_up.build-decompose',\n criterionRef: 'application-creation:criterion/build-plan-relationship-coverage',\n verdicts: [MetaWorkflow_EvaluationVerdict.GAP],\n reopen: ['bottom_up.build-decompose'],\n },\n ],\n },\n },\n /*\n * The lane's closing decision — read the maturity, accept the stage or send the build back.\n * LIVE since #111 landed: the runtime derives this lane's boundary from the field and the companion\n * projects one `approve_result` decision over the paths the lane kept — which for this lane is the\n * application WORKSPACE its dispatches wrote, not a specifications family. The maturity reading the\n * decision should be read against is still #1496.\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"]}
|
|
@@ -17,9 +17,9 @@ import { MetaWorkflow_AuthorityAssuranceClass, MetaWorkflow_AuthorityDecisionMod
|
|
|
17
17
|
*/
|
|
18
18
|
export declare const playbookDefinition: {
|
|
19
19
|
readonly ref: "bottom_up.build-decompose";
|
|
20
|
-
readonly version: "0.4.
|
|
20
|
+
readonly version: "0.4.1";
|
|
21
21
|
readonly phase: "bottom_up";
|
|
22
|
-
readonly intent: "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets /
|
|
22
|
+
readonly intent: "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / lock or schedule runs / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.";
|
|
23
23
|
readonly preconditions: readonly [{
|
|
24
24
|
readonly kind: "artifact_exists";
|
|
25
25
|
readonly selector: {
|
|
@@ -71,7 +71,7 @@ export declare const playbookDefinition: {
|
|
|
71
71
|
readonly outputs: readonly [{
|
|
72
72
|
readonly family: "build-plan";
|
|
73
73
|
readonly schemaRef: "saas-specifications:BuildPlanTaskGraph";
|
|
74
|
-
readonly description: "The build decomposition — an ORDERED set of coding-agent build tasks (a task graph) that turns the approved domain plan into a sequence of buildable units. Each task carries: a stable task ref, the target it builds (a module, a resource + one of its build stages, a relationship, a companion-generation step, a shell-surface placement config), WHAT IT PRODUCES (`produces` — the artifacts whose presence in the finished application proves the task landed; distinct from the target, which is a write scope several tasks may share), the ONE functional topic it belongs to (a real MetaWorkflow_FunctionalTopic value), the skill(s) that carry its technical HOW (real folders from the app-knowledge skill catalog, resolved via the skills router), and its ordering intent (which tasks must precede it — expressed as typed prerequisiteTaskRefs, which the host resolves for readiness). Author prerequisiteTaskRefs to express the actual dependencies, using these planning considerations: (a) the cross-app topic dependency edges (model_domain_graph before define_interaction_semantics before app-level shape_user_experience before extend_application before connect_runtime_and_external_capabilities; foundation and assemble/verify are owned by sibling playbooks) and (b) the per-resource stage sequence schema -> config -> ui-behavior -> spec — which deliberately CROSSES topics (ui-behavior is shape_user_experience; the spec is a model_domain_graph documentation capstone ordered last) and so is not monotonic on axis (a); a roadmap-driven MVP-first preference breaks ties within a band. TYPED since the flexible-intelligence Block 3: the `_core` build-task-graph contract (`BuildPlanTaskGraph` — `tasks[]` with a stable `taskRef`, a closed `BuildPlanTaskTargetKind` target (MODULE / RESOURCE_STAGE / RELATIONSHIP / COMPANION_GENERATION_STEP / SHELL_PLACEMENT / MODULE_FRONTEND / MODULE_BACKEND / APPLICATION_FRONTEND_CONFIG / WEBSITE / TECHNICAL_DOCUMENTATION / WORKER / MINION / PROVIDER_BINDING / BILLING_CATALOG), a `produces` list over the closed `BuildPlanTaskProductKind` vocabulary (the resource products — schema fields, registration, ui-behavior, specification, relationship, operation, composite / custom / chart view, PDF template; the application products — view, document, module, frontend configuration, custom component, milestone, guidance; and the runtime products — worker jobs, minion behaviours, provider binding, website page and section, documentation chapter, inbound channel handler; and the billing product the catalogue sells), exactly one `functionalTopic`, `skillRefs`, DECLARED `prerequisiteTaskRefs` the host resolves for readiness, and traceability `servesRefs`) is the family schema; the provider answers the strict `BuildPlanTaskGraphGeneration` shape and the trusted runtime stamps refs and version. The task never carries paths, commands, prompts or runtime controls — the dispatch host derives mutation scope and verification from the target kind. `validateBuildPlanTaskGraph` is the deterministic validator. A task's products must name something COMPOSITION DOES NOT ALREADY WRITE (the fields a schema gains, not its scaffolded file) and no two tasks may claim the same artifact — that is what makes landing decidable; a coding task declaring none is reported as `TASK_DECLARES_NO_PRODUCT`. If such a task has a COMPLETED durable run, the host advances past it but reports its ref in `unverifiableLandedTaskRefs`: it ran, but its output is not proven. Without that completed run it remains unlanded. Companion-generation tasks use their own landed conditions; migrations require the schema plan to be in sync. Product probes inspect committed files and named declarations, not runtime correctness. Two things are HARD FLOORS: a prerequisite cycle, and a resource stage that declares its predecessor stage in the SAME graph without depending on it — dispatch order comes solely from `prerequisiteTaskRefs`, so an undeclared stage edge lets the host author a resources-config for a schema that has not landed. A predecessor stage that is ABSENT from the plan is an authoring WARNING instead, because a plan may legitimately author one stage of a resource the tree already carries; the coherence reviewer checklist (`build-plan-coherent`, in the method) remains the semantic check and the creator's approve_result review the trust floor. Consumed by the bottom-up DISPATCH-ORCHESTRATION playbook (which
|
|
74
|
+
readonly description: "The build decomposition — an ORDERED set of coding-agent build tasks (a task graph) that turns the approved domain plan into a sequence of buildable units. Each task carries: a stable task ref, the target it builds (a module, a resource + one of its build stages, a relationship, a companion-generation step, a shell-surface placement config), WHAT IT PRODUCES (`produces` — the artifacts whose presence in the finished application proves the task landed; distinct from the target, which is a write scope several tasks may share), the ONE functional topic it belongs to (a real MetaWorkflow_FunctionalTopic value), the skill(s) that carry its technical HOW (real folders from the app-knowledge skill catalog, resolved via the skills router), and its ordering intent (which tasks must precede it — expressed as typed prerequisiteTaskRefs, which the host resolves for readiness). Author prerequisiteTaskRefs to express the actual dependencies, using these planning considerations: (a) the cross-app topic dependency edges (model_domain_graph before define_interaction_semantics before app-level shape_user_experience before extend_application before connect_runtime_and_external_capabilities; foundation and assemble/verify are owned by sibling playbooks) and (b) the per-resource stage sequence schema -> config -> ui-behavior -> spec — which deliberately CROSSES topics (ui-behavior is shape_user_experience; the spec is a model_domain_graph documentation capstone ordered last) and so is not monotonic on axis (a); a roadmap-driven MVP-first preference breaks ties within a band. TYPED since the flexible-intelligence Block 3: the `_core` build-task-graph contract (`BuildPlanTaskGraph` — `tasks[]` with a stable `taskRef`, a closed `BuildPlanTaskTargetKind` target (MODULE / RESOURCE_STAGE / RELATIONSHIP / COMPANION_GENERATION_STEP / SHELL_PLACEMENT / MODULE_FRONTEND / MODULE_BACKEND / APPLICATION_FRONTEND_CONFIG / WEBSITE / TECHNICAL_DOCUMENTATION / WORKER / MINION / PROVIDER_BINDING / BILLING_CATALOG), a `produces` list over the closed `BuildPlanTaskProductKind` vocabulary (the resource products — schema fields, registration, ui-behavior, specification, relationship, operation, composite / custom / chart view, PDF template; the application products — view, document, module, frontend configuration, custom component, milestone, guidance; and the runtime products — worker jobs, minion behaviours, provider binding, website page and section, documentation chapter, inbound channel handler; and the billing product the catalogue sells), exactly one `functionalTopic`, `skillRefs`, DECLARED `prerequisiteTaskRefs` the host resolves for readiness, and traceability `servesRefs`) is the family schema; the provider answers the strict `BuildPlanTaskGraphGeneration` shape and the trusted runtime stamps refs and version. The task never carries paths, commands, prompts or runtime controls — the dispatch host derives mutation scope and verification from the target kind. `validateBuildPlanTaskGraph` is the deterministic validator. A task's products must name something COMPOSITION DOES NOT ALREADY WRITE (the fields a schema gains, not its scaffolded file) and no two tasks may claim the same artifact — that is what makes landing decidable; a coding task declaring none is reported as `TASK_DECLARES_NO_PRODUCT`. If such a task has a COMPLETED durable run, the host advances past it but reports its ref in `unverifiableLandedTaskRefs`: it ran, but its output is not proven. Without that completed run it remains unlanded. Companion-generation tasks use their own landed conditions; migrations require the schema plan to be in sync. Product probes inspect committed files and named declarations, not runtime correctness. Two things are HARD FLOORS: a prerequisite cycle, and a resource stage that declares its predecessor stage in the SAME graph without depending on it — dispatch order comes solely from `prerequisiteTaskRefs`, so an undeclared stage edge lets the host author a resources-config for a schema that has not landed. A predecessor stage that is ABSENT from the plan is an authoring WARNING instead, because a plan may legitimately author one stage of a resource the tree already carries; the coherence reviewer checklist (`build-plan-coherent`, in the method) remains the semantic check and the creator's approve_result review the trust floor. Consumed by the bottom-up DISPATCH-ORCHESTRATION playbook (which dispatches the tasks through the coding-agent contract in parallel waves, up to the application's build parallelism at once) and the SCALE playbook (which describes how those waves are scheduled, interleaved with the companion generation steps, and reconciled) — both downstream of this decomposition.";
|
|
75
75
|
}];
|
|
76
76
|
readonly method: {
|
|
77
77
|
readonly "//contextSources": "WORKSPACE_TRUTH — this playbook plans against CODE, not against definition artifacts: it needs real module ids and per-resource present schema fields, or it invents ids that do not resolve and every task it emits fails at dispatch. SKILL_CATALOG — its method routes THROUGH the skills router and binds every emitted task to a skill folder, so it must choose from the real set; measured 2026-08-27 it was choosing from recall, and a dangling skill ref is a task the dispatch playbook cannot run. COHERENCE_REPORT — the computed cross-family findings over the conception it builds on (dangling edges into the domain plan, a composition surface no plan realises), so its judge can tell a conception fault from its own (#1638): the build lane routes the first back to conception.";
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build-decompose/playbook.definition.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,6BAA6B,EAC9B,MAAM,sCAAsC,CAAC;AAE9C;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0DrB,CAAC;AAEX,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
|
1
|
+
{"version":3,"file":"playbook.definition.d.ts","sourceRoot":"","sources":["../../../../../src/playbooks/bottom_up.build-decompose/playbook.definition.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oCAAoC,EACpC,kCAAkC,EAClC,wCAAwC,EACxC,+BAA+B,EAC/B,gCAAgC,EAChC,sCAAsC,EACtC,0CAA0C,EAC1C,6CAA6C,EAC7C,8BAA8B,EAC9B,oCAAoC,EACpC,6BAA6B,EAC9B,MAAM,sCAAsC,CAAC;AAE9C;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,kBAAkB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0DrB,CAAC;AAEX,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgZW,CAAC"}
|
|
@@ -17,9 +17,9 @@ import { MetaWorkflow_AuthorityAssuranceClass, MetaWorkflow_AuthorityDecisionMod
|
|
|
17
17
|
*/
|
|
18
18
|
export const playbookDefinition = {
|
|
19
19
|
"ref": "bottom_up.build-decompose",
|
|
20
|
-
"version": "0.4.
|
|
20
|
+
"version": "0.4.1",
|
|
21
21
|
"phase": "bottom_up",
|
|
22
|
-
"intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets /
|
|
22
|
+
"intent": "Bottom-up build decomposition — the FIRST build-execution playbook, the pivot from planning the domain (the domain-plan) to decomposing the BUILD. Reads the approved domain-plan (the ModuleBusinessSemantics module drafts + per-module resource inventory), the relationship drafts inside it (the inter-resource relationship intents), and the definition set (roadmap for phasing, requirements + feature-drafts for task-brief context), and the PLACEMENT PLAN (where each settings destination, resource operation and view sits in the shell, decided upstream), and DECOMPOSES the build work into an ordered set of coding-agent tasks. Each task is bound onto (a) the 7-topic functional taxonomy (configure_application_foundation -> model_domain_graph -> define_interaction_semantics -> shape_user_experience -> extend_application -> connect_runtime_and_external_capabilities -> assemble_verify_and_iterate) and (b) the app-knowledge skill catalog (each task names the skill(s) that carry its technical HOW). The tasks follow the per-resource inner order (schema -> config -> ui-behavior -> spec, then operations / interaction semantics, then UX, then extensions, then integrations), with companion-owned generation steps (i18n-labels, email-templates, logo, and database-migrations for applications with an accepted PostgreSQL schema plan) interleaved at the points their inputs exist. This playbook PRODUCES the ordered task graph (a build-plan artifact); it does NOT dispatch tasks to coding agents (that is the dispatch-orchestration playbook downstream), does NOT capture change-sets / lock or schedule runs / verify, and does NOT solve multi-agent scale or interleaving. It authors no schemas and generates no code. The typed BuildPlanTaskGraph contract and deterministic validator already exist. Declare prerequisiteTaskRefs explicitly: the host derives readiness from those edges; functionalTopic provides context and skill routing, not an implicit execution order.",
|
|
23
23
|
"preconditions": [
|
|
24
24
|
{ "kind": "artifact_exists", "selector": { "family": "domain-plan" } },
|
|
25
25
|
{
|
|
@@ -47,7 +47,7 @@ export const playbookDefinition = {
|
|
|
47
47
|
{
|
|
48
48
|
"family": "build-plan",
|
|
49
49
|
"schemaRef": "saas-specifications:BuildPlanTaskGraph",
|
|
50
|
-
"description": "The build decomposition — an ORDERED set of coding-agent build tasks (a task graph) that turns the approved domain plan into a sequence of buildable units. Each task carries: a stable task ref, the target it builds (a module, a resource + one of its build stages, a relationship, a companion-generation step, a shell-surface placement config), WHAT IT PRODUCES (`produces` — the artifacts whose presence in the finished application proves the task landed; distinct from the target, which is a write scope several tasks may share), the ONE functional topic it belongs to (a real MetaWorkflow_FunctionalTopic value), the skill(s) that carry its technical HOW (real folders from the app-knowledge skill catalog, resolved via the skills router), and its ordering intent (which tasks must precede it — expressed as typed prerequisiteTaskRefs, which the host resolves for readiness). Author prerequisiteTaskRefs to express the actual dependencies, using these planning considerations: (a) the cross-app topic dependency edges (model_domain_graph before define_interaction_semantics before app-level shape_user_experience before extend_application before connect_runtime_and_external_capabilities; foundation and assemble/verify are owned by sibling playbooks) and (b) the per-resource stage sequence schema -> config -> ui-behavior -> spec — which deliberately CROSSES topics (ui-behavior is shape_user_experience; the spec is a model_domain_graph documentation capstone ordered last) and so is not monotonic on axis (a); a roadmap-driven MVP-first preference breaks ties within a band. TYPED since the flexible-intelligence Block 3: the `_core` build-task-graph contract (`BuildPlanTaskGraph` — `tasks[]` with a stable `taskRef`, a closed `BuildPlanTaskTargetKind` target (MODULE / RESOURCE_STAGE / RELATIONSHIP / COMPANION_GENERATION_STEP / SHELL_PLACEMENT / MODULE_FRONTEND / MODULE_BACKEND / APPLICATION_FRONTEND_CONFIG / WEBSITE / TECHNICAL_DOCUMENTATION / WORKER / MINION / PROVIDER_BINDING / BILLING_CATALOG), a `produces` list over the closed `BuildPlanTaskProductKind` vocabulary (the resource products — schema fields, registration, ui-behavior, specification, relationship, operation, composite / custom / chart view, PDF template; the application products — view, document, module, frontend configuration, custom component, milestone, guidance; and the runtime products — worker jobs, minion behaviours, provider binding, website page and section, documentation chapter, inbound channel handler; and the billing product the catalogue sells), exactly one `functionalTopic`, `skillRefs`, DECLARED `prerequisiteTaskRefs` the host resolves for readiness, and traceability `servesRefs`) is the family schema; the provider answers the strict `BuildPlanTaskGraphGeneration` shape and the trusted runtime stamps refs and version. The task never carries paths, commands, prompts or runtime controls — the dispatch host derives mutation scope and verification from the target kind. `validateBuildPlanTaskGraph` is the deterministic validator. A task's products must name something COMPOSITION DOES NOT ALREADY WRITE (the fields a schema gains, not its scaffolded file) and no two tasks may claim the same artifact — that is what makes landing decidable; a coding task declaring none is reported as `TASK_DECLARES_NO_PRODUCT`. If such a task has a COMPLETED durable run, the host advances past it but reports its ref in `unverifiableLandedTaskRefs`: it ran, but its output is not proven. Without that completed run it remains unlanded. Companion-generation tasks use their own landed conditions; migrations require the schema plan to be in sync. Product probes inspect committed files and named declarations, not runtime correctness. Two things are HARD FLOORS: a prerequisite cycle, and a resource stage that declares its predecessor stage in the SAME graph without depending on it — dispatch order comes solely from `prerequisiteTaskRefs`, so an undeclared stage edge lets the host author a resources-config for a schema that has not landed. A predecessor stage that is ABSENT from the plan is an authoring WARNING instead, because a plan may legitimately author one stage of a resource the tree already carries; the coherence reviewer checklist (`build-plan-coherent`, in the method) remains the semantic check and the creator's approve_result review the trust floor. Consumed by the bottom-up DISPATCH-ORCHESTRATION playbook (which
|
|
50
|
+
"description": "The build decomposition — an ORDERED set of coding-agent build tasks (a task graph) that turns the approved domain plan into a sequence of buildable units. Each task carries: a stable task ref, the target it builds (a module, a resource + one of its build stages, a relationship, a companion-generation step, a shell-surface placement config), WHAT IT PRODUCES (`produces` — the artifacts whose presence in the finished application proves the task landed; distinct from the target, which is a write scope several tasks may share), the ONE functional topic it belongs to (a real MetaWorkflow_FunctionalTopic value), the skill(s) that carry its technical HOW (real folders from the app-knowledge skill catalog, resolved via the skills router), and its ordering intent (which tasks must precede it — expressed as typed prerequisiteTaskRefs, which the host resolves for readiness). Author prerequisiteTaskRefs to express the actual dependencies, using these planning considerations: (a) the cross-app topic dependency edges (model_domain_graph before define_interaction_semantics before app-level shape_user_experience before extend_application before connect_runtime_and_external_capabilities; foundation and assemble/verify are owned by sibling playbooks) and (b) the per-resource stage sequence schema -> config -> ui-behavior -> spec — which deliberately CROSSES topics (ui-behavior is shape_user_experience; the spec is a model_domain_graph documentation capstone ordered last) and so is not monotonic on axis (a); a roadmap-driven MVP-first preference breaks ties within a band. TYPED since the flexible-intelligence Block 3: the `_core` build-task-graph contract (`BuildPlanTaskGraph` — `tasks[]` with a stable `taskRef`, a closed `BuildPlanTaskTargetKind` target (MODULE / RESOURCE_STAGE / RELATIONSHIP / COMPANION_GENERATION_STEP / SHELL_PLACEMENT / MODULE_FRONTEND / MODULE_BACKEND / APPLICATION_FRONTEND_CONFIG / WEBSITE / TECHNICAL_DOCUMENTATION / WORKER / MINION / PROVIDER_BINDING / BILLING_CATALOG), a `produces` list over the closed `BuildPlanTaskProductKind` vocabulary (the resource products — schema fields, registration, ui-behavior, specification, relationship, operation, composite / custom / chart view, PDF template; the application products — view, document, module, frontend configuration, custom component, milestone, guidance; and the runtime products — worker jobs, minion behaviours, provider binding, website page and section, documentation chapter, inbound channel handler; and the billing product the catalogue sells), exactly one `functionalTopic`, `skillRefs`, DECLARED `prerequisiteTaskRefs` the host resolves for readiness, and traceability `servesRefs`) is the family schema; the provider answers the strict `BuildPlanTaskGraphGeneration` shape and the trusted runtime stamps refs and version. The task never carries paths, commands, prompts or runtime controls — the dispatch host derives mutation scope and verification from the target kind. `validateBuildPlanTaskGraph` is the deterministic validator. A task's products must name something COMPOSITION DOES NOT ALREADY WRITE (the fields a schema gains, not its scaffolded file) and no two tasks may claim the same artifact — that is what makes landing decidable; a coding task declaring none is reported as `TASK_DECLARES_NO_PRODUCT`. If such a task has a COMPLETED durable run, the host advances past it but reports its ref in `unverifiableLandedTaskRefs`: it ran, but its output is not proven. Without that completed run it remains unlanded. Companion-generation tasks use their own landed conditions; migrations require the schema plan to be in sync. Product probes inspect committed files and named declarations, not runtime correctness. Two things are HARD FLOORS: a prerequisite cycle, and a resource stage that declares its predecessor stage in the SAME graph without depending on it — dispatch order comes solely from `prerequisiteTaskRefs`, so an undeclared stage edge lets the host author a resources-config for a schema that has not landed. A predecessor stage that is ABSENT from the plan is an authoring WARNING instead, because a plan may legitimately author one stage of a resource the tree already carries; the coherence reviewer checklist (`build-plan-coherent`, in the method) remains the semantic check and the creator's approve_result review the trust floor. Consumed by the bottom-up DISPATCH-ORCHESTRATION playbook (which dispatches the tasks through the coding-agent contract in parallel waves, up to the application's build parallelism at once) and the SCALE playbook (which describes how those waves are scheduled, interleaved with the companion generation steps, and reconciled) — both downstream of this decomposition."
|
|
51
51
|
}
|
|
52
52
|
],
|
|
53
53
|
"method": {
|
|
@@ -78,7 +78,10 @@ export const evaluationTreatmentSource = {
|
|
|
78
78
|
definitionRef: 'application-creation:evaluation-treatment/build-plan-coherent',
|
|
79
79
|
// 2 since #1638: `conception-buildable` faults the CONCEPTION, not the plan, which changes what a GAP means.
|
|
80
80
|
// 3: relationship coverage leaves a relationship to an undeclared resource to `conception-buildable`.
|
|
81
|
-
|
|
81
|
+
// 4: experience coverage (#2235) — the experience plan's surfaces each have a task, and its absence is recorded.
|
|
82
|
+
// 5: module-and-resource coverage also asks for demonstration data (#2234), so a built application does not open empty.
|
|
83
|
+
// 6: experience coverage keys its absence case on the accepted-truth statement, not on a heading it did not see (#2235 review).
|
|
84
|
+
definitionVersion: 6,
|
|
82
85
|
evaluationProtocol: {
|
|
83
86
|
schemaVersion: 1,
|
|
84
87
|
protocolRef: 'application-creation:evaluation-protocol/build-plan-coherent',
|
|
@@ -99,8 +102,8 @@ export const evaluationTreatmentSource = {
|
|
|
99
102
|
{
|
|
100
103
|
schemaVersion: 1,
|
|
101
104
|
criterionRef: 'application-creation:criterion/build-plan-module-and-resource-coverage',
|
|
102
|
-
criterionVersion:
|
|
103
|
-
instruction: "Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price).",
|
|
105
|
+
criterionVersion: 2,
|
|
106
|
+
instruction: "Determine whether every resource in every module's inventory (mainResources and supportingResources) of the domain plan has build tasks, and whether every task's moduleRef names a module the domain plan declares. A module whose resources have tasks but which carries no redundant scaffold task is NOT a finding: module slices are scaffolded by the foundation step. A module added after foundation with neither a foundation slice nor an ensure-module task IS a gap. The billing catalogue is covered the same way: every pricing plan the business model declares must be an APPLICATION_BILLING_PRODUCT of a BILLING_CATALOG task whose servesRefs name the plan; a declared plan with no billing product is a gap (the backend would have nothing to sell and the website would re-type its price). Seeding is covered the same way: a plan whose domain has main resources and no APPLICATION_DATA_SEED task of content DEMONSTRATION is a concern — the application would open empty, with nothing a creator can judge or show (#2234).",
|
|
104
107
|
assessesAspects: ['build-plan.task', 'domain-plan.module', 'domain-plan.resource'],
|
|
105
108
|
evidenceRequirements: [{
|
|
106
109
|
schemaVersion: 1,
|
|
@@ -119,7 +122,7 @@ export const evaluationTreatmentSource = {
|
|
|
119
122
|
}],
|
|
120
123
|
verdictGuidance: {
|
|
121
124
|
[MetaWorkflow_EvaluationVerdict.PASS]: 'Every domain-plan resource has build tasks and every moduleRef resolves to a declared module.',
|
|
122
|
-
[MetaWorkflow_EvaluationVerdict.CONCERN]: "Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch),
|
|
125
|
+
[MetaWorkflow_EvaluationVerdict.CONCERN]: "Coverage is complete, but a task's objective CREATES a resource the domain plan shows as already existing instead of enriching it (a no-op dispatch), a supporting resource's coverage is thin, or no DEMONSTRATION data seed gives the main resources sample rows.",
|
|
123
126
|
[MetaWorkflow_EvaluationVerdict.GAP]: 'A resource with no task (the build would not produce it), or a task naming a module the domain plan does not declare (the dispatcher cannot route it).',
|
|
124
127
|
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The domain plan or the build plan is absent, truncated or unreadable, so coverage cannot be established.',
|
|
125
128
|
},
|
|
@@ -247,7 +250,7 @@ export const evaluationTreatmentSource = {
|
|
|
247
250
|
schemaVersion: 1,
|
|
248
251
|
criterionRef: 'application-creation:criterion/build-plan-companion-generation-interleave',
|
|
249
252
|
criterionVersion: 1,
|
|
250
|
-
instruction: 'Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. Do NOT flag the absence of a seeds step:
|
|
253
|
+
instruction: 'Determine whether the executable companion-owned generation steps are present and placed after the surfaces whose output they consume: i18n-labels after the resources it labels; email-templates after the surfaces it serves; database-migrations after the schema stages whose drift it migrates, and only for a PostgreSQL-backed application; logo present whenever the application has a brand brief, and unordered with respect to resource work because it consumes the brand and no code surface. Do NOT flag the absence of an i18n-translations step: the dispatch host derives it after i18n-labels. Do NOT flag the absence of a seeds GENERATION step: none exists, and seeding is an APPLICATION_DATA_SEED coding task judged under module-and-resource coverage.',
|
|
251
254
|
evidenceRequirements: [{
|
|
252
255
|
schemaVersion: 1,
|
|
253
256
|
requirementRef: 'application-creation:evidence-requirement/build-plan-companion-generation-interleave',
|
|
@@ -266,7 +269,7 @@ export const evaluationTreatmentSource = {
|
|
|
266
269
|
verdictGuidance: {
|
|
267
270
|
[MetaWorkflow_EvaluationVerdict.PASS]: 'Every executable generation step the application needs is present and placed after the surfaces it consumes; logo is present when a brand exists.',
|
|
268
271
|
[MetaWorkflow_EvaluationVerdict.CONCERN]: 'A labels or email step is ordered before some surface it consumes, a migration step is missing on a PostgreSQL-backed application, or the logo step is missing on an application with a brand brief.',
|
|
269
|
-
[MetaWorkflow_EvaluationVerdict.GAP]: 'A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or seeds), or a generation step declares products.',
|
|
272
|
+
[MetaWorkflow_EvaluationVerdict.GAP]: 'A generation step the pipeline cannot execute is authored (an unknown generationStepRef, or a seeds generation step), or a generation step declares products.',
|
|
270
273
|
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'Whether the application has a brand brief or which store it uses is not in evidence, so the required step set cannot be decided.',
|
|
271
274
|
},
|
|
272
275
|
},
|
|
@@ -274,7 +277,7 @@ export const evaluationTreatmentSource = {
|
|
|
274
277
|
schemaVersion: 1,
|
|
275
278
|
criterionRef: 'application-creation:criterion/build-plan-decomposition-boundary',
|
|
276
279
|
criterionVersion: 1,
|
|
277
|
-
instruction: 'Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (
|
|
280
|
+
instruction: 'Determine whether the plan stays at DECOMPOSITION depth: tasks name what they build, their topic, their skills, their target, their products and their ordering intent, and do not specify how a task is dispatched (dispatch locking and concurrency, change-set capture, git baseline, verify mechanics), do not solve multi-agent scale or interleaving concurrency, and do not author a schema, resolve a cardinality into a concrete foreign key, or generate code.',
|
|
278
281
|
assessesAspects: ['build-plan.task'],
|
|
279
282
|
evidenceRequirements: [{
|
|
280
283
|
schemaVersion: 1,
|
|
@@ -298,6 +301,52 @@ export const evaluationTreatmentSource = {
|
|
|
298
301
|
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'Task briefs are not in evidence.',
|
|
299
302
|
},
|
|
300
303
|
},
|
|
304
|
+
/*
|
|
305
|
+
* The experience plan's surfaces each have a task, and an ABSENT experience plan is recorded rather than
|
|
306
|
+
* silent (#2235).
|
|
307
|
+
*
|
|
308
|
+
* Measured on app-creation-test-004 (2026-10-01): `bottom_up.experience-plan` was refused twice, the build
|
|
309
|
+
* plan was decomposed anyway, and the application shipped with no app-level views, no onboarding and no
|
|
310
|
+
* milestones. The method is right to emit no such task without a plan ("an improvised surface is the state
|
|
311
|
+
* this family replaced"), and the plan read as complete — no criterion here looked at the experience plan.
|
|
312
|
+
*
|
|
313
|
+
* Why an absent plan is PASS with a marked rationale, and not a weaker verdict: every non-PASS verdict of
|
|
314
|
+
* this treatment routes back to the decomposer (CONCERN and GAP → REVISE, INDETERMINATE → REQUEST_EVIDENCE,
|
|
315
|
+
* which ends in BLOCK). The decomposer cannot produce an upstream family by revising, so either would spend
|
|
316
|
+
* revisions on something it cannot fix, and the second would stop the build on an unfinished upstream —
|
|
317
|
+
* the refusal `.claude/rules/application-creation-directive.md` forbids ("mark, never block"). Rejected too:
|
|
318
|
+
* an `artifact_expected` precondition on the family, the `placement-plan` shape. Inside a lane every child
|
|
319
|
+
* is admitted past SEQUENCING (`playbook-run.companion.service.ts`, `proceedPastSequencing: true`), so it
|
|
320
|
+
* would have marked nothing in the run that motivated this.
|
|
321
|
+
*/
|
|
322
|
+
{
|
|
323
|
+
schemaVersion: 1,
|
|
324
|
+
criterionRef: 'application-creation:criterion/build-plan-experience-coverage',
|
|
325
|
+
criterionVersion: 2,
|
|
326
|
+
instruction: "Determine whether every surface the experience plan decides has its build task: one task per VIEW (target MODULE_FRONTEND on the view's module, a product of the view's kind carrying the plan's viewRef verbatim), one APPLICATION_FRONTEND_CONFIG task per CONFIGURATION, one APPLICATION_MILESTONE task per planned MILESTONE, and one APPLICATION_GUIDANCE task per planned piece of GUIDANCE (an onboarding document's objective naming the hostViewRef that embeds it). A view, configuration, milestone or guidance entry with no task is a gap: the application would ship without it while the plan reads complete. Never conclude the plan is absent because this criterion's own slice does not show it: the accepted application truth either renders the experience plan or says it has none. When the accepted application truth STATES that `experience-plan` has no accepted content, the decomposer has rightly emitted none of these tasks and cannot repair the absence by revising: record PASS, and begin the rationale with the words 'NO EXPERIENCE PLAN:' followed by what the application will therefore lack (its app-level views, its shell and navigation configuration, its milestones and its onboarding), so the absence is on the record instead of silent.",
|
|
327
|
+
assessesAspects: ['build-plan.task', 'experience-plan.view', 'experience-plan.configuration', 'experience-plan.milestone', 'experience-plan.guidance'],
|
|
328
|
+
evidenceRequirements: [{
|
|
329
|
+
schemaVersion: 1,
|
|
330
|
+
requirementRef: 'application-creation:evidence-requirement/build-plan-experience-coverage',
|
|
331
|
+
requirementVersion: 1,
|
|
332
|
+
kind: MetaWorkflow_EvidenceRequirementKind.MANDATORY,
|
|
333
|
+
subjectRef: 'application-creation:definition-set/domain-plan-and-build-plan-candidate',
|
|
334
|
+
minCount: 1,
|
|
335
|
+
maxCount: 8,
|
|
336
|
+
coveragePolicyRef: 'application-creation:evidence-policy/exact-build-decompose-inputs-and-candidate',
|
|
337
|
+
freshnessPolicyRef: 'application-creation:evidence-policy/current-action-binding',
|
|
338
|
+
conditionRef: null,
|
|
339
|
+
independencePolicyRef: null,
|
|
340
|
+
diversityPolicyRef: null,
|
|
341
|
+
aggregationPolicyRef: null,
|
|
342
|
+
}],
|
|
343
|
+
verdictGuidance: {
|
|
344
|
+
[MetaWorkflow_EvaluationVerdict.PASS]: "Every view, configuration, milestone and guidance entry of the experience plan has its task — or no experience plan is in evidence, and the rationale begins 'NO EXPERIENCE PLAN:' and names what the application will lack.",
|
|
345
|
+
[MetaWorkflow_EvaluationVerdict.CONCERN]: "Every entry has a task, but a task's objective drops what the plan decided for it: a view's reusesComponentRefs, a milestone's moment, a guidance entry's gate, or an onboarding document's hostViewRef.",
|
|
346
|
+
[MetaWorkflow_EvaluationVerdict.GAP]: 'A view, configuration, milestone or guidance entry the experience plan declares has no task, or a view task carries a viewRef the plan does not declare.',
|
|
347
|
+
[MetaWorkflow_EvaluationVerdict.INDETERMINATE]: 'The build plan is not in evidence, or the accepted application truth neither renders the experience plan nor states that it has none. (A STATED absence is not indeterminate: it is the PASS case above, marked.)',
|
|
348
|
+
},
|
|
349
|
+
},
|
|
301
350
|
/*
|
|
302
351
|
* The one criterion that faults the CONCEPTION rather than the plan (#1638). Every other criterion
|
|
303
352
|
* here is the decomposer's own, and its GAP re-opens the decomposer. This one says the plan could not
|