@wildo-ai/framework-knowledge 1.1.8 → 1.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/claude-marketplace/.claude-plugin/marketplace.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/.claude-plugin/plugin.json +1 -1
- package/dist/claude-marketplace/plugins/wildo/references/acceptance.md +11 -0
- 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/expert-personas-and-deliberations.md +26 -7
- package/dist/claude-marketplace/plugins/wildo/references/runs-judges-and-questions.md +31 -5
- package/dist/claude-marketplace/plugins/wildo/skills/accept/SKILL.md +4 -2
- 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 +20 -4
- 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 +95 -5
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/index.d.ts.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.d.ts.map +1 -1
- 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 +41 -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 +175 -14
- 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.d.ts.map +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.d.ts +8 -4
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.conception/playbook.definition.js +13 -6
- 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 +4 -2
- 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 +90 -13
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts +4 -3
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.experience-plan/playbook.definition.js +4 -3
- package/dist/esm/playbooks/bottom_up.experience-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/bottom_up.placement-plan/playbook.definition.d.ts +12 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +8 -4
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts +4 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js +2 -1
- package/dist/esm/playbooks/bottom_up.website-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/cross_cutting.application-creation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.compliance/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.feature-development/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/cross_cutting.refinement/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.feature-contribution/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.governance-document-candidate/playbook.definition.d.ts.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 +91 -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 +41 -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 +43 -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 +200 -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 +203 -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 +81 -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 +93 -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.capability-map/playbook.definition.d.ts.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-evidence-adequacy/playbook.definition.d.ts.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.compliance-research/playbook.definition.d.ts.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.expert-personas/playbook.definition.d.ts +27 -6
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js +32 -12
- package/dist/esm/playbooks/top_down.expert-personas/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.feature-drafts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +13 -5
- package/dist/esm/playbooks/top_down.market-snapshot-produce/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 +71 -2
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +23 -8
- package/dist/esm/playbooks/top_down.requirements-definition/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.value-proposition/playbook.definition.d.ts.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 +41 -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 +261 -34
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +42 -4
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +188 -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 +11 -3
- 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 +129 -17
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +7 -4
- package/dist/knowledge/playbooks/bottom_up.experience-plan/method.md +28 -6
- package/dist/knowledge/playbooks/bottom_up.experience-plan/playbook.json +5 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +13 -5
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +50 -0
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +16 -4
- package/dist/knowledge/playbooks/bottom_up.website-plan/method.md +19 -0
- package/dist/knowledge/playbooks/bottom_up.website-plan/playbook.json +5 -2
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +7 -3
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +1 -1
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +8 -0
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +3 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/method.md +5 -2
- package/dist/knowledge/playbooks/refinement.feature-contribution/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 +75 -37
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +35 -38
- package/dist/knowledge/playbooks/top_down.brand-name-research/method.md +145 -0
- package/dist/knowledge/playbooks/top_down.brand-name-research/playbook.json +57 -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 +99 -0
- package/dist/knowledge/playbooks/top_down.brand-name-screening-produce/playbook.json +65 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/method.md +56 -0
- package/dist/knowledge/playbooks/top_down.brand-naming/playbook.json +76 -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.capability-map/method.md +10 -9
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +1 -1
- 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.expert-personas/playbook.json +16 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/method.md +5 -2
- package/dist/knowledge/playbooks/top_down.feature-drafts/playbook.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +26 -0
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +4 -2
- 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.requirements-definition/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.requirements-definition/method.md +84 -9
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +6 -3
- 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 +29 -0
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +58 -17
- package/dist/knowledge/references/brand.name-choice.config.md +144 -0
- package/dist/knowledge/references/brand.name-screening.config.md +308 -0
- package/dist/knowledge/references/build-plan.task-graph.config.md +119 -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/companion.market.prompt-renderer.md +11 -6
- package/dist/knowledge/references/example.authorization.application-roles.office-and-field.md +44 -0
- package/dist/knowledge/references/example.backend.custom-operation.audit-event.md +81 -0
- package/dist/knowledge/references/example.backend.custom-operation.child-line-total.md +258 -0
- package/dist/knowledge/references/example.backend.custom-operation.computed-total.md +153 -0
- package/dist/knowledge/references/example.backend.custom-operation.create-related-resource.md +107 -0
- package/dist/knowledge/references/example.data-seeding.minimal.md +39 -10
- package/dist/knowledge/references/example.data-seeding.row-reference.md +80 -0
- package/dist/knowledge/references/example.email.template.minimal.md +1 -1
- package/dist/knowledge/references/example.resource.config-wiring.retention-policy-operations.md +74 -0
- package/dist/knowledge/references/example.resource.personal-data.free-text-field.md +19 -0
- package/dist/knowledge/references/example.resource.personal-data.person-without-account.md +27 -0
- package/dist/knowledge/references/example.resource.status-lifecycle.quote.md +152 -0
- package/dist/knowledge/references/example.resource.ui-behavior.filter-presets.md +15 -0
- package/dist/knowledge/references/example.resource.ui-behavior.operation-icon.md +8 -0
- package/dist/knowledge/references/example.views.app-level.home-definition.md +13 -0
- package/dist/knowledge/references/example.views.chart-definition.shared.md +83 -0
- package/dist/knowledge/references/experience-plan.config.md +60 -7
- package/dist/knowledge/references/market.context-block.builder.md +1 -1
- package/dist/knowledge/references/market.snapshot.validation.md +1 -1
- package/dist/knowledge/references/placement-plan.config.md +43 -0
- package/dist/knowledge/references/requirements.functional-requirement.config.md +8 -2
- package/dist/knowledge/references/requirements.non-functional-requirement.config.md +2 -0
- package/dist/knowledge/references/requirements.references.conventions.md +1 -1
- package/dist/knowledge/references/requirements.snapshot.config.md +57 -1
- package/dist/knowledge/references/requirements.snapshot.validation.md +35 -1
- package/dist/knowledge/references/saas.backend.audit-logs.log-event.md +63 -0
- package/dist/knowledge/references/saas.backend.document-sequence.issue-in-operation.md +60 -0
- package/dist/knowledge/references/saas.backend.document-sequence.raise-floor.md +156 -0
- package/dist/knowledge/references/saas.backend.email.send.md +77 -0
- package/dist/knowledge/references/saas.backend.notifications.operation-email-template-ref.md +60 -0
- package/dist/knowledge/references/saas.data-seeding.bootstrap-wiring.md +7 -1
- package/dist/knowledge/references/saas.data-seeding.computed-entry.md +43 -0
- package/dist/knowledge/references/saas.data-seeding.definition-input.md +14 -2
- package/dist/knowledge/references/saas.data-seeding.row-reference.md +93 -0
- package/dist/knowledge/references/saas.frontend.collection-filter-presets.md +124 -0
- package/dist/knowledge/references/saas.frontend.launcher.item-refs.md +316 -0
- package/dist/knowledge/references/saas.frontend.launcher.merge-rules.md +106 -0
- package/dist/knowledge/references/saas.frontend.launcher.runtime-availability.md +60 -0
- package/dist/knowledge/references/saas.frontend.resource-label-params.md +52 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +47 -18
- package/dist/knowledge/references/saas.frontend.resource-ui-behavior-config.md +4 -1
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destination-roles.md +25 -0
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +2 -2
- package/dist/knowledge/references/saas.models.audit.trail-config.md +45 -0
- package/dist/knowledge/references/saas.models.notifications.user-notification-definition.md +5 -3
- package/dist/knowledge/references/saas.models.queue.scheduled-recovery.md +81 -2
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +26 -0
- package/dist/knowledge/references/saas.models.roles.definition.md +61 -0
- package/dist/knowledge/references/saas.models.roles.organization-defaults.md +97 -0
- package/dist/knowledge/references/saas.public-runtime.contract.md +26 -0
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +10 -0
- package/dist/knowledge/references/saas.website.astro.bridge.md +10 -0
- package/dist/knowledge/references/saas.website.astro.label-loader.md +12 -0
- package/dist/knowledge/references/saas.website.astro.llms-txt-server.md +14 -1
- package/dist/knowledge/references/saas.website.astro.site-context.md +13 -0
- package/dist/knowledge/references/saas.website.blog.bridge.md +4 -0
- package/dist/knowledge/references/saas.website.config.site-context-loader.md +3 -0
- package/dist/knowledge/references/saas.website.factories.define-section.md +4 -0
- package/dist/knowledge/references/saas.website.legal.public-document-links.md +76 -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.root-config.seo.md +2 -1
- package/dist/knowledge/references/saas.website.runtime.context.md +7 -0
- package/dist/knowledge/references/saas.website.sections.definition-schema.md +11 -0
- package/dist/knowledge/references/saas.website.seo.llms-txt-config.md +2 -0
- package/dist/knowledge/references/website-plan.config.md +26 -0
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +13 -0
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +7 -0
- package/dist/knowledge/references/zod.decorators.document-sequence.md +65 -0
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +1 -0
- package/dist/knowledge/references/zod.decorators.shared-structural-methods.md +21 -0
- package/dist/knowledge/references/zod.factories.bigdecimal.md +1 -0
- package/dist/knowledge/references/zod.factories.code.md +1 -0
- package/dist/knowledge/references/zod.factories.duration.md +1 -0
- package/dist/knowledge/references/zod.factories.money.md +1 -0
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +374 -1
- package/dist/knowledge/registries/playbooks.json +76 -28
- package/dist/knowledge/registries/source-tags.json +1513 -898
- package/dist/knowledge/rules/live-context-door.md +5 -2
- package/dist/knowledge/skills/INDEX.md +5 -2
- package/dist/knowledge/skills/application-consumer-documentation-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/application-database-migrations/SKILL.md +14 -3
- package/dist/knowledge/skills/application-roles-authoring/SKILL.md +158 -0
- package/dist/knowledge/skills/application-roles-authoring/references/framework-application-roles-api.md +169 -0
- package/dist/knowledge/skills/application-roles-authoring/references/office-and-field-worked-example.md +63 -0
- package/dist/knowledge/skills/authorization-unit-narrowing/SKILL.md +6 -1
- package/dist/knowledge/skills/backend-custom-operation/SKILL.md +256 -9
- package/dist/knowledge/skills/backend-custom-operation/references/after-the-operation.md +42 -0
- package/dist/knowledge/skills/backend-custom-operation/references/framework-audit-log-event-api.md +220 -0
- package/dist/knowledge/skills/brand-logo-authoring/SKILL.md +5 -0
- package/dist/knowledge/skills/brand-name-screening/SKILL.md +178 -0
- package/dist/knowledge/skills/brand-name-screening/references/framework-brand-name-screening-api.md +466 -0
- package/dist/knowledge/skills/brand-name-screening/references/screening-procedure.md +87 -0
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +7 -3
- package/dist/knowledge/skills/config-app-shell/SKILL.md +58 -5
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-items-api.md +461 -0
- package/dist/knowledge/skills/config-app-shell/references/framework-launcher-visibility-api.md +80 -0
- package/dist/knowledge/skills/config-design-system/SKILL.md +28 -6
- package/dist/knowledge/skills/config-navigation/SKILL.md +14 -3
- package/dist/knowledge/skills/config-saas/SKILL.md +56 -15
- package/dist/knowledge/skills/config-saas/references/compliance-declarations.md +65 -2
- package/dist/knowledge/skills/config-saas/references/framework-audit-trail-config-api.md +62 -2
- package/dist/knowledge/skills/config-saas/references/framework-background-work-api.md +81 -2
- package/dist/knowledge/skills/config-saas-backend/SKILL.md +6 -1
- package/dist/knowledge/skills/configure-billing/SKILL.md +18 -4
- package/dist/knowledge/skills/email-add-template/SKILL.md +28 -6
- package/dist/knowledge/skills/email-add-template/references/email-artifact-paths.md +1 -1
- package/dist/knowledge/skills/email-add-template/references/framework-email-send-api.md +128 -0
- package/dist/knowledge/skills/email-add-template/references/framework-operation-email-template-ref-api.md +99 -0
- package/dist/knowledge/skills/engine-component-registration/SKILL.md +6 -1
- package/dist/knowledge/skills/engine-product-definitions/SKILL.md +21 -8
- package/dist/knowledge/skills/flows-actors-chat-assistant/SKILL.md +10 -2
- package/dist/knowledge/skills/flows-actors-llm-agent-invocation/SKILL.md +18 -4
- package/dist/knowledge/skills/frontend-component-catalog/SKILL.md +11 -3
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-catalog.md +2 -1
- package/dist/knowledge/skills/frontend-component-catalog/references/framework-component-usage.md +8 -0
- package/dist/knowledge/skills/i18n-rerun-pipeline/SKILL.md +19 -5
- package/dist/knowledge/skills/i18n-translation-rerun/SKILL.md +10 -2
- package/dist/knowledge/skills/inbound-channels/SKILL.md +2 -2
- package/dist/knowledge/skills/infra-environment-config/SKILL.md +6 -1
- package/dist/knowledge/skills/local-environment-bootstrap/SKILL.md +17 -2
- 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-add-feature-benefit/SKILL.md +10 -2
- package/dist/knowledge/skills/market-alternatives/SKILL.md +10 -2
- package/dist/knowledge/skills/market-authoring-overview/SKILL.md +10 -2
- package/dist/knowledge/skills/market-category/SKILL.md +21 -7
- package/dist/knowledge/skills/market-channels/SKILL.md +6 -1
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +22 -4
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +12 -2
- package/dist/knowledge/skills/market-generation-cli/SKILL.md +21 -11
- package/dist/knowledge/skills/market-generation-cli/references/framework-market-generation-cli.md +11 -6
- package/dist/knowledge/skills/market-icp/SKILL.md +10 -2
- package/dist/knowledge/skills/market-jobs-pains-gains/SKILL.md +6 -1
- package/dist/knowledge/skills/market-message-templates-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-message-templates-authoring/references/framework-message-template-api.md +1 -1
- package/dist/knowledge/skills/market-persona/SKILL.md +14 -3
- package/dist/knowledge/skills/market-positioning-authoring/SKILL.md +6 -1
- package/dist/knowledge/skills/market-proof-and-objection/SKILL.md +10 -2
- package/dist/knowledge/skills/market-scoring-interpretation/SKILL.md +6 -1
- package/dist/knowledge/skills/market-snapshot-validation/SKILL.md +15 -4
- package/dist/knowledge/skills/market-snapshot-validation/references/framework-snapshot-validation-api.md +1 -1
- package/dist/knowledge/skills/market-tone-of-voice/SKILL.md +6 -1
- package/dist/knowledge/skills/model-cost-attribution/references/framework-work-unit-api.md +26 -0
- package/dist/knowledge/skills/module-companion-exports/SKILL.md +7 -1
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +10 -0
- package/dist/knowledge/skills/module-relationships/SKILL.md +37 -8
- package/dist/knowledge/skills/pdf-template-authoring/SKILL.md +4 -2
- package/dist/knowledge/skills/provider-address-lookup/SKILL.md +14 -3
- package/dist/knowledge/skills/provider-frontend-file-picker/SKILL.md +6 -1
- package/dist/knowledge/skills/provider-operation-calls/SKILL.md +14 -3
- package/dist/knowledge/skills/rate-limit-authoring/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +46 -17
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +14 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +29 -3
- package/dist/knowledge/skills/resource-config-wiring/references/framework-collection-operation-declarations.md +19 -4
- package/dist/knowledge/skills/resource-config-wiring/references/framework-operation-audit-api.md +5 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +103 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-retention-policy-operations.md +135 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +26 -0
- package/dist/knowledge/skills/resource-config-wiring/references/framework-user-notifications-api.md +26 -7
- package/dist/knowledge/skills/resource-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +46 -17
- package/dist/knowledge/skills/resource-external-data/references/erasure-suppression.md +2 -2
- package/dist/knowledge/skills/resource-retention-binding/SKILL.md +5 -1
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +15 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/computed-totals.md +569 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/document-numbers.md +358 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +8 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-shared-decorator-methods-api.md +21 -0
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-special-factories-api.md +7 -2
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +13 -0
- package/dist/knowledge/skills/resource-status-lifecycle/SKILL.md +153 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/commercial-documents.md +46 -0
- package/dist/knowledge/skills/resource-status-lifecycle/references/quote-lifecycle-worked-example.md +198 -0
- package/dist/knowledge/skills/resource-ui-behavior/SKILL.md +30 -4
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-collection-filter-presets-api.md +157 -0
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +101 -19
- package/dist/knowledge/skills/seeding-authoring/SKILL.md +202 -39
- package/dist/knowledge/skills/seeding-authoring/references/cross-seed-row-references.md +67 -0
- package/dist/knowledge/skills/seeding-authoring/references/framework-data-seeding-api.md +154 -4
- package/dist/knowledge/skills/seeding-authoring/references/seed-row-overlay.md +22 -0
- package/dist/knowledge/skills/seeding-operations/references/framework-data-seeding-operations-api.md +7 -1
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +43 -0
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +2 -2
- package/dist/knowledge/skills/spec-companion-exports/SKILL.md +6 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +10 -0
- package/dist/knowledge/skills/spec-component-update/SKILL.md +10 -2
- package/dist/knowledge/skills/spec-composite-view-update/SKILL.md +2 -2
- package/dist/knowledge/skills/spec-family-update/SKILL.md +71 -66
- package/dist/knowledge/skills/spec-family-update/references/family-spec-routing.md +1 -1
- package/dist/knowledge/skills/spec-resource-update/SKILL.md +30 -10
- package/dist/knowledge/skills/spec-resource-update/references/resource-spec-field-routing.md +28 -0
- package/dist/knowledge/skills/spec-update-after-change/SKILL.md +22 -5
- package/dist/knowledge/skills/views-add-composite-view/SKILL.md +6 -1
- package/dist/knowledge/skills/views-add-custom-view/SKILL.md +10 -2
- package/dist/knowledge/skills/views-app-level/SKILL.md +13 -3
- package/dist/knowledge/skills/views-app-level/references/application-home.md +56 -0
- package/dist/knowledge/skills/views-chart-authoring/SKILL.md +221 -37
- package/dist/knowledge/skills/views-composite-authoring/SKILL.md +22 -5
- package/dist/knowledge/skills/views-execution-authoring/SKILL.md +1 -1
- package/dist/knowledge/skills/website-anonymous-session/SKILL.md +32 -2
- package/dist/knowledge/skills/website-blog-authoring/SKILL.md +16 -3
- package/dist/knowledge/skills/website-blog-authoring/references/blog-adapter-api.md +4 -0
- package/dist/knowledge/skills/website-bundle-discipline/SKILL.md +7 -1
- package/dist/knowledge/skills/website-consent-gate-overrides/SKILL.md +13 -1
- package/dist/knowledge/skills/website-factory-advanced/SKILL.md +14 -2
- package/dist/knowledge/skills/website-inbound-contact-forms/SKILL.md +13 -1
- package/dist/knowledge/skills/website-layout-overrides/SKILL.md +6 -1
- package/dist/knowledge/skills/website-marketing-metadata-extension/SKILL.md +19 -1
- package/dist/knowledge/skills/website-navigation-authoring/SKILL.md +55 -18
- package/dist/knowledge/skills/website-navigation-authoring/references/framework-public-document-links-api.md +98 -0
- package/dist/knowledge/skills/website-navigation-authoring/references/worked-examples-header-footer.md +8 -11
- package/dist/knowledge/skills/website-page-authoring/SKILL.md +100 -8
- package/dist/knowledge/skills/website-page-authoring/references/framework-site-context-loader-api.md +3 -0
- package/dist/knowledge/skills/website-primitive-overrides/SKILL.md +6 -1
- 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 +21 -1
- 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 +21 -1
- 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 +25 -2
- 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 +33 -10
- package/dist/knowledge/skills/website-section-hero/references/define-website-section-api.md +15 -0
- package/dist/knowledge/skills/website-section-pricing/SKILL.md +21 -1
- 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 +27 -2
- 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 +16 -4
- package/dist/knowledge/skills/website-seo-aeo-geo/references/aeo-api.md +11 -0
- package/dist/knowledge/skills/website-seo-aeo-geo/references/geo-api.md +16 -1
- package/dist/knowledge/skills/website-seo-aeo-geo/references/seo-api.md +2 -1
- package/dist/knowledge/topic-index.json +1590 -292
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation
|
|
1
|
+
# Build Scale — Run the Build at Scale: Waves, Parallelism, Interleaved Generation
|
|
2
2
|
|
|
3
3
|
### Target Application Framing
|
|
4
4
|
|
|
@@ -12,310 +12,203 @@ Read and apply these patterns from the application-developer point of view:
|
|
|
12
12
|
- how the application should avoid mixing frontend, backend, and infrastructure concerns
|
|
13
13
|
|
|
14
14
|
|
|
15
|
-
> **
|
|
16
|
-
>
|
|
17
|
-
>
|
|
18
|
-
>
|
|
19
|
-
>
|
|
20
|
-
>
|
|
21
|
-
>
|
|
22
|
-
>
|
|
23
|
-
>
|
|
24
|
-
> degrade to sequential single-flight dispatch** — read the "What the runner
|
|
25
|
-
> actually does today" section before you assume anything ran in parallel. Do
|
|
26
|
-
> not overclaim concurrency the runner cannot do.
|
|
15
|
+
> **The build already runs at scale, and this playbook describes how.** A run of
|
|
16
|
+
> a build-execution playbook starts a **wave**: up to N build-plan tasks at once
|
|
17
|
+
> in the application's one worktree, N being the application's **build
|
|
18
|
+
> parallelism** (`wildo workbench parallelism`, 5 unless the person set it). This
|
|
19
|
+
> playbook and the build-dispatch playbook declare the same executor and run
|
|
20
|
+
> through the same runtime branch, so they start the SAME wave. Prefer the
|
|
21
|
+
> build-dispatch playbook to start a build; read this one for how a wave is
|
|
22
|
+
> scheduled, how wide it is, and how it is reconciled. With a build parallelism
|
|
23
|
+
> of `1` the lane dispatches one task at a time (the single-flight mode).
|
|
27
24
|
|
|
28
25
|
## Where you are in the journey
|
|
29
26
|
|
|
30
|
-
This is the **third
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
**safely**, in **what order**, with the companion-generation steps interleaved.
|
|
27
|
+
This is the **third build-execution playbook**. It runs in the **bottom-up
|
|
28
|
+
phase**, after the build plan exists (`artifact_exists build-plan`) and the
|
|
29
|
+
foundation step has authored the app's config and skeleton. You are not
|
|
30
|
+
re-opening the decomposition here, and you are not re-specifying how one task
|
|
31
|
+
dispatches — you are reading **how many** tasks run **concurrently**, in **what
|
|
32
|
+
order**, with the companion-generation steps interleaved, and how the wave
|
|
33
|
+
**ends**.
|
|
38
34
|
|
|
39
|
-
Upstream: the **build-decompose** playbook produced the ordered task graph
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
35
|
+
Upstream: the **build-decompose** playbook produced the ordered task graph the
|
|
36
|
+
wave schedules; the **build-dispatch** playbook defines the per-task contract
|
|
37
|
+
every slot runs (context pack, one ACP prompt turn, change-set capture, verify
|
|
38
|
+
outside the agent, record + `onFailure`). **You author neither of those
|
|
39
|
+
concerns** — see the boundary section.
|
|
43
40
|
|
|
44
41
|
## What this playbook does
|
|
45
42
|
|
|
46
|
-
You are the **scale
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
schedule artifact authored here (see "What you emit"). You do **not** decompose
|
|
54
|
-
the plan, re-specify the per-task dispatch mechanics, author any schema, or
|
|
55
|
-
write any code.
|
|
56
|
-
|
|
57
|
-
## The scale contract — you sequence waves, the dispatch playbook runs each slot
|
|
58
|
-
|
|
59
|
-
Most of the *per-task* mechanism is **not yours**: selecting one task,
|
|
60
|
-
composing its context pack, running one prompt turn against the coding agent over
|
|
61
|
-
the Agent Client Protocol (answering its permission requests within the declared
|
|
62
|
-
ceiling), capturing the change-set, running the verify hook, holding the
|
|
63
|
-
single-flight lock, applying the host's actual execution limits — all of that is the **build-dispatch** contract, which each
|
|
64
|
-
parallel slot invokes. Your method here is the **declarative concurrency
|
|
65
|
-
recipe** the runner (or a future runner-serializer) interprets: *which set* of
|
|
66
|
-
tasks is ready, *how many* run at once, *how* they are isolated, *when* the
|
|
67
|
-
deterministic generation steps interleave, and *when* a wave is done. Do not
|
|
68
|
-
hand-drive git, do not compose a dispatch prompt, do not re-implement the
|
|
69
|
-
single-flight capture — invoke the dispatch contract per slot and let it own
|
|
70
|
-
those.
|
|
43
|
+
You are the **scale reader**. Across the *whole* build you answer: *"which tasks
|
|
44
|
+
are ready now, how many run at once, when do the deterministic generation steps
|
|
45
|
+
run, and when has a wave actually finished?"* You do **not** produce a journey
|
|
46
|
+
artifact — the observable result of the build is the per-task change-sets and
|
|
47
|
+
task statuses the runner records on the task rows (see "What you emit"). You do
|
|
48
|
+
**not** decompose the plan, re-specify the per-task dispatch mechanics, author
|
|
49
|
+
any schema, or write any code.
|
|
71
50
|
|
|
72
51
|
## Read state first — no artifact to write
|
|
73
52
|
|
|
74
|
-
This playbook is **idempotent** and, on a re-run, *advances the
|
|
75
|
-
wave
|
|
76
|
-
Before scheduling anything:
|
|
53
|
+
This playbook is **idempotent** and, on a re-run, *advances the build by one
|
|
54
|
+
wave*. Before reasoning about a wave:
|
|
77
55
|
|
|
78
|
-
1. Read the current journey state and scope from what this run is given — the
|
|
79
|
-
specifications and the workspace sections of your brief — and do not
|
|
80
|
-
|
|
81
|
-
|
|
56
|
+
1. Read the current journey state and scope from what this run is given — the
|
|
57
|
+
loaded specifications and the workspace sections of your brief — and do not
|
|
58
|
+
re-derive it. Confirm the **build plan** is present and approved and the
|
|
59
|
+
**foundation** ran. For each build-plan task, read its dispatch state from
|
|
60
|
+
its task row (`wildo build tasks`) — **not yet dispatched**,
|
|
82
61
|
**dispatched-and-succeeded** (a captured change-set + a passed verify),
|
|
83
62
|
**dispatched-and-failed** (a captured change-set but a failed/timed-out run
|
|
84
|
-
or a failed verify), or **in-flight**.
|
|
85
|
-
change-set
|
|
86
|
-
|
|
87
|
-
alone never means "done").
|
|
63
|
+
or a failed verify), or **in-flight**. Under `keep_and_flag` a *failed* task
|
|
64
|
+
also has a captured change-set, so the presence of a change-set alone never
|
|
65
|
+
means "done".
|
|
88
66
|
2. Read the approved **build plan** (`build-plan` — the ordered task graph, with
|
|
89
|
-
each task's
|
|
67
|
+
each task's declared prerequisite references). It is the work list.
|
|
90
68
|
|
|
91
69
|
That there is an application to dispatch into is answered by the committed
|
|
92
|
-
`./wildo.saas.config.ts` and skeleton, not by a journey artifact.
|
|
93
|
-
`foundation-manifest` played that role until 2026-08-25 and was retired with the
|
|
94
|
-
app-creation verification/digest aspect.) The honest limitation the foundation step
|
|
95
|
-
carries still applies: on-disk skeleton materialization depends on greenfield
|
|
96
|
-
bring-up tooling (deferred); the dogfood app already has a skeleton, so the scale
|
|
97
|
-
contract runs against an existing workspace.
|
|
70
|
+
`./wildo.saas.config.ts` and skeleton, not by a journey artifact.
|
|
98
71
|
|
|
99
72
|
// Operator status: `wildo context journey` (eligibility board + runs in flight); per-task landed
|
|
100
73
|
// state is read from git by the runner.
|
|
101
74
|
|
|
102
|
-
You **read** `build-plan`; you **write** no journey
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
reconciled/merged after the wave. This is the general answer.
|
|
147
|
-
- **module / resource partitioning** — schedule concurrent agents only onto
|
|
148
|
-
tasks whose targets touch **disjoint file sets** (different modules /
|
|
149
|
-
resources), so even on one shared worktree no two runs collide. This is the
|
|
150
|
-
cheaper answer when the frontier naturally partitions by module.
|
|
151
|
-
- **or keep coding single-flight** and only parallelise the deterministic
|
|
152
|
-
companion-generation steps (Step 3), which are not coding-locked.
|
|
153
|
-
- **Pick the degree deliberately, not maximally.** At scaffold depth prefer a
|
|
154
|
-
small degree (or a module partition) over max fan-out — cost-optimal packing,
|
|
155
|
-
a priority / work-stealing scheduler, and backoff are a later depth phase, not
|
|
156
|
-
this scaffold. State the isolation model you chose; a wave with degree > 1 and
|
|
157
|
-
**no** isolation answer is unsafe (the reviewer rubric flags it as a GAP).
|
|
158
|
-
|
|
159
|
-
## Step 3 — Interleave the deterministic companion-generation steps
|
|
75
|
+
You **read** `build-plan`; you **write** no journey artifact.
|
|
76
|
+
|
|
77
|
+
## Step 1 — The ready-set (the frontier)
|
|
78
|
+
|
|
79
|
+
A task is **ready** when it is not yet dispatched (or a previously-**failed**
|
|
80
|
+
task cleared for retry), it is not already running, and every prerequisite it
|
|
81
|
+
declares has **SUCCEEDED** — not merely been attempted. A prerequisite that is
|
|
82
|
+
dispatched-and-failed, in-flight, or un-run does **not** satisfy the dependency.
|
|
83
|
+
The runner resolves this from the declared prerequisite refs and from git; it is
|
|
84
|
+
never inferred from prose, and you do not re-order the edges the build-decompose
|
|
85
|
+
playbook encoded.
|
|
86
|
+
|
|
87
|
+
The wave is a **rolling pool**, not a fixed batch: when a run settles, its slot
|
|
88
|
+
is refilled with whatever is ready THEN, so a task that just landed unlocks its
|
|
89
|
+
dependents within the same wave. An empty frontier with no run live ends the
|
|
90
|
+
wave; if every task has landed the build is done (and the wave reports whether
|
|
91
|
+
the application assembles), and if the only remaining tasks are stuck the wave
|
|
92
|
+
names them and why.
|
|
93
|
+
|
|
94
|
+
## Step 2 — The width and the isolation model, as shipped
|
|
95
|
+
|
|
96
|
+
- **The width is the build parallelism.** `wildo workbench parallelism` shows it
|
|
97
|
+
and sets it, from `1` to a safety ceiling; the default is 5. The runner reads it
|
|
98
|
+
at the start of every wave, so a change needs no restart. Each slot is a live
|
|
99
|
+
coding agent spending on its own, so the width is the person's decision, not
|
|
100
|
+
the method's: do not propose a different degree as part of a run.
|
|
101
|
+
- **The runs share ONE worktree, by decision.** Concurrent agents editing the same
|
|
102
|
+
tree reconcile fine in practice, so the lane does not isolate them (no
|
|
103
|
+
worktree per agent, no partition by module). It prevents only a task being
|
|
104
|
+
built twice at once. Everything else is DETECTED and REPAIRED (Step 4).
|
|
105
|
+
- **Attribution is recorded, not guaranteed.** Each run still captures its
|
|
106
|
+
change-set and attributes every file (`RUN_EXCLUSIVE`, `APPEARED_DURING_RUN`,
|
|
107
|
+
`BASELINE_DIRTY_AMBIGUOUS`). In a wave, files a sibling also touched are
|
|
108
|
+
expected to come out ambiguous; the run's `concurrency` entry names the runs
|
|
109
|
+
that overlapped it and the paths both touched, which is what a reviewer reads
|
|
110
|
+
to settle authorship.
|
|
111
|
+
- **One wave is bounded.** A call takes at most four tasks per slot and then
|
|
112
|
+
stops taking new ones, waits for its live runs, and returns. The next run of a
|
|
113
|
+
build-execution playbook continues from where the build stands.
|
|
114
|
+
- **One wave at a time.** The companion refuses a second wave while one runs —
|
|
115
|
+
submitted, running, or in its end-of-wave commit and repair — because a second
|
|
116
|
+
wave would double the width and write while the first one repairs.
|
|
117
|
+
|
|
118
|
+
## Step 3 — The deterministic companion-generation steps
|
|
160
119
|
|
|
161
120
|
The build plan carries **companion-owned generation steps** — labels / i18n,
|
|
162
|
-
email templates, seeds — as tasks.
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
- **
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
|
|
197
|
-
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
221
|
-
-
|
|
222
|
-
|
|
223
|
-
|
|
224
|
-
|
|
225
|
-
|
|
226
|
-
|
|
227
|
-
|
|
228
|
-
|
|
229
|
-
auto-retry a failed task (automated retry / backoff is a deferred build-loop
|
|
230
|
-
resilience concern).
|
|
231
|
-
|
|
232
|
-
> **Why keep_and_flag, not revert_changeset (a v1 boundary).** Reverting a
|
|
233
|
-
> failed run's edits is a *mutating* git op, deliberately **outside** the
|
|
234
|
-
> read-only change-set carve-out the dispatch lane observes. So `keep_and_flag`
|
|
235
|
-
> is both the correct F-5 workspace-safety posture and the behavior the runner
|
|
236
|
-
> enforces today; a `revert_changeset` path is a deliberate later boundary.
|
|
237
|
-
|
|
238
|
-
Then **loop**: on the next run, the build plan's task records reflect the just-completed
|
|
239
|
-
wave's outcomes (`wildo build tasks`), and you derive the next frontier (Step 1). Close a
|
|
240
|
-
significant stretch of the build with a progress summary — which waves ran, which
|
|
241
|
-
change-sets landed, what verify said, which generation steps interleaved, and
|
|
242
|
-
any failed task left flagged for triage.
|
|
243
|
-
|
|
244
|
-
## What the runner actually does today (do not overclaim)
|
|
245
|
-
|
|
246
|
-
Be honest with the creator about the gap between this method and the runner:
|
|
247
|
-
|
|
248
|
-
- **The runner enforces single-flight.** It refuses a run plan carrying more
|
|
249
|
-
than one coding-agent task, refuses a second dispatch while one is active, and
|
|
250
|
-
holds one workspace-mutation lock per background run. So a wave with
|
|
251
|
-
parallelism degree > 1 is **not** realizable on today's runner — the wave
|
|
252
|
-
**degrades to sequential single-flight dispatch** (repeated invocation of the
|
|
253
|
-
build-dispatch contract, one task at a time, in frontier order). The frontier
|
|
254
|
-
math, the readiness discipline, and the reconciliation are all still correct
|
|
255
|
-
and useful sequentially — you just do not get concurrency yet.
|
|
256
|
-
- **No overlap is attribution-safe today — not even a companion-generation
|
|
257
|
-
step.** The generation endpoints are not coding-locked, but the coding
|
|
258
|
-
change-set capture is a whole-worktree time-window diff, so a generation step
|
|
259
|
-
writing files while a coding dispatch is capturing is misattributed to that
|
|
260
|
-
run (Step 3's caveat). So the generation steps **also** serialize outside an
|
|
261
|
-
active coding-capture window: their input-ready *ordering* holds, only the
|
|
262
|
-
*concurrency* is deferred. Safe overlap of generation-with-coding, and
|
|
263
|
-
coding-with-coding, both require git worktree-per-agent isolation.
|
|
264
|
-
- **The concurrency this method describes is the declarative target** for a
|
|
265
|
-
runner-serializer slice (multi-coding-agent run-completion serialization,
|
|
266
|
-
git worktree-per-agent isolation, a run-outcome reconciler, and a cursor lock)
|
|
267
|
-
— filed as runner tasks, **not** built by this scaffold playbook. Until they
|
|
268
|
-
land, run the waves sequentially and do not claim a parallel run (or a
|
|
269
|
-
generation-alongside-coding overlap) happened when it did not.
|
|
270
|
-
|
|
271
|
-
## Scaffold-depth boundary (owned by a sibling, or deferred to a later phase)
|
|
272
|
-
|
|
273
|
-
Keep this playbook at **scale-orchestration depth**. Explicitly **out of scope
|
|
274
|
-
here**:
|
|
121
|
+
email templates, seeds — as tasks. They run through their **deterministic
|
|
122
|
+
companion endpoint**, never a coding agent.
|
|
123
|
+
|
|
124
|
+
- **They run at their input-ready point**, like any task: a labels step after the
|
|
125
|
+
resources it labels exist, a seed step after the resources it seeds exist. Their
|
|
126
|
+
readiness is declared in the plan the same way.
|
|
127
|
+
- **In a wave they run in their turn while the coding runs already started keep
|
|
128
|
+
going.** The runner runs a ready generation step inline as it fills the wave;
|
|
129
|
+
it does not wait for the live coding runs to settle first. A generation step's
|
|
130
|
+
files that land inside a coding run's capture window are recorded as overlap on
|
|
131
|
+
that run, and the end-of-wave repair commits them with the rest.
|
|
132
|
+
- **Each generation step runs at most once per wave.** If its landing is still unmet
|
|
133
|
+
afterwards, the wave stops taking tasks rather than re-select it forever; the
|
|
134
|
+
next wave tries again, and a step that never lands is a stuck task to report.
|
|
135
|
+
|
|
136
|
+
// The trigger is `wildo build run` from a console (or `/wildo:build` in a Claude Code session),
|
|
137
|
+
// which starts a wave through the build-dispatch playbook; `wildo creation run <playbookRef>`
|
|
138
|
+
// starts one through this playbook or that one alike.
|
|
139
|
+
|
|
140
|
+
## Step 4 — How a wave ends: reconcile, repair, advance
|
|
141
|
+
|
|
142
|
+
A wave stops taking tasks for one of four reasons — nothing ready, its per-call
|
|
143
|
+
cap, a generation step it already ran, or a refused admission — and it always
|
|
144
|
+
drains the runs already live before it ends.
|
|
145
|
+
|
|
146
|
+
- **The repair, once nothing is writing.** The runner commits what the runs' own
|
|
147
|
+
accepts left in the tree as ONE change naming every run whose writes it may
|
|
148
|
+
carry, failed runs included (a failed run's files sit in the same tree). Then
|
|
149
|
+
each run that COMPLETED but whose declared product a sibling overwrote is
|
|
150
|
+
re-armed and re-run ALONE, so nothing can overwrite the second attempt; the
|
|
151
|
+
number of such re-runs per task is bounded, after which the task waits for a
|
|
152
|
+
person. Each repair is on the wave's result and on the task's record
|
|
153
|
+
(`interference`).
|
|
154
|
+
- **Failure disposition across siblings + downstream** — `keep_and_flag`. A
|
|
155
|
+
failed or timed-out run keeps its captured change-set flagged for human triage
|
|
156
|
+
(never silently reverted). Its siblings in the same wave run to completion. Its
|
|
157
|
+
**dependents** stay out of every frontier until it is triaged and re-dispatched
|
|
158
|
+
successfully. This playbook does not auto-retry a failure that was the task's
|
|
159
|
+
own; only a suspected interference is re-run.
|
|
160
|
+
- **Advance.** On the next run, the task records reflect the wave's outcomes
|
|
161
|
+
(`wildo build tasks`), and the next wave selects from what is ready now. Close a
|
|
162
|
+
significant stretch of the build with a progress summary — which waves ran,
|
|
163
|
+
which change-sets landed, what verify said, which runs overlapped or were
|
|
164
|
+
repaired, and any task left flagged for triage.
|
|
165
|
+
|
|
166
|
+
> **Why keep_and_flag, not revert_changeset.** Reverting a failed run's edits is
|
|
167
|
+
> a *mutating* git op, deliberately **outside** the read-only change-set
|
|
168
|
+
> carve-out the dispatch lane observes; with a shared worktree it would also
|
|
169
|
+
> reach a sibling's files. A `revert_changeset` path is a deliberate later
|
|
170
|
+
> boundary.
|
|
171
|
+
|
|
172
|
+
## Step 5 — Check the actual host authorization boundary
|
|
173
|
+
|
|
174
|
+
A coding dispatch writes the application workspace. Each run is confined to its
|
|
175
|
+
own task's mutation scope by the configured coding host's authorization policy;
|
|
176
|
+
nothing confines it from its siblings, which is what Steps 2 and 4 are about.
|
|
177
|
+
|
|
178
|
+
The playbook's `approval` declaration and the journey autonomy presets express
|
|
179
|
+
policy intent. The current playbook runner does not interpret them as
|
|
180
|
+
pre-dispatch gates, automatic authorization, or a GUIDED/YOLO mapping. A declared
|
|
181
|
+
`approve_before` does not create a pending Authority Request — never invent one
|
|
182
|
+
from an enum. Do not infer enforced run ceilings from declared budget fields;
|
|
183
|
+
respect the limits actually reported by the execution host.
|
|
184
|
+
|
|
185
|
+
## Boundary (owned by a sibling, or deferred to a later phase)
|
|
186
|
+
|
|
187
|
+
Explicitly **out of scope here**:
|
|
275
188
|
|
|
276
189
|
- **Re-decomposition.** You do NOT split modules/resources into tasks, re-order
|
|
277
|
-
the graph, or add tasks — the **build-decompose** playbook owns the task
|
|
278
|
-
|
|
279
|
-
-
|
|
280
|
-
|
|
281
|
-
|
|
282
|
-
|
|
283
|
-
|
|
284
|
-
|
|
285
|
-
- **
|
|
286
|
-
worktree-per-agent provisioning, the run-outcome reconciler, and the cursor
|
|
287
|
-
lock are **companion-runner mechanism**, filed as runner tasks — this
|
|
288
|
-
declarative method does not build them.
|
|
289
|
-
- **A priority / work-stealing scheduler + cost-optimal packing.** Deciding an
|
|
290
|
-
optimal task ordering within a band, work-stealing across idle slots, backoff,
|
|
291
|
-
and cost-optimal packing are a later depth phase — the v1 scaffold picks a
|
|
292
|
-
small parallelism degree (or a module partition) and a simple frontier order.
|
|
293
|
-
- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the v1
|
|
190
|
+
the graph, or add tasks — the **build-decompose** playbook owns the task graph.
|
|
191
|
+
- **The per-task dispatch contract.** You do NOT re-specify context-pack
|
|
192
|
+
composition, change-set capture, or the verify hook — the **build-dispatch**
|
|
193
|
+
playbook owns "how one task dispatches safely", and every slot runs it.
|
|
194
|
+
- **Choosing the width or a different isolation model.** The width is the
|
|
195
|
+
application's build parallelism, set by the person; the shared worktree with
|
|
196
|
+
detection and repair is the lane's decision. A priority / work-stealing
|
|
197
|
+
scheduler and cost-optimal packing are a later depth phase.
|
|
198
|
+
- **A `revert_changeset` failure path.** Deferred; `keep_and_flag` is the
|
|
294
199
|
disposition.
|
|
295
|
-
- **Auto-executed reviewer checklist.** The scale-soundness checklist ships
|
|
296
|
-
**declarative** — the deterministic typecheck gate runs automatically; nothing
|
|
297
|
-
executes the checklist prose (rubric-only judge gates were retired at the
|
|
298
|
-
flexible-intelligence hard cut). Do not assume it auto-ran.
|
|
299
200
|
- **Schema / field authoring + code generation.** The **coding agents** author
|
|
300
201
|
fields, schemas, ui-behavior, and code at dispatch time — never the
|
|
301
202
|
orchestrator.
|
|
302
203
|
|
|
303
|
-
If you find yourself designing how ONE task dispatches safely rather than how
|
|
304
|
-
MANY tasks are scheduled + reconciled, stop — that is the build-dispatch
|
|
305
|
-
playbook.
|
|
306
|
-
|
|
307
204
|
## What you emit
|
|
308
205
|
|
|
309
|
-
**No journey artifact.**
|
|
310
|
-
|
|
311
|
-
|
|
312
|
-
|
|
313
|
-
|
|
314
|
-
|
|
315
|
-
would drift (a typed wave-schedule / run-ledger contract is a filed later-phase
|
|
316
|
-
item). Use the configured host's actual authorization boundary and review its
|
|
317
|
-
recorded changes and verification outcomes. The approval declaration alone does
|
|
318
|
-
not authorize or gate dispatch.
|
|
206
|
+
**No journey artifact.** The observable result of the build — each task's
|
|
207
|
+
**change-set** and **status**, plus each run's overlap and repair record — is
|
|
208
|
+
materialized by the runner on the task rows and on the wave's result, not
|
|
209
|
+
authored here. A separate wave-log artifact family is deliberately not added:
|
|
210
|
+
the task rows already *are* the dispatch record, and a second home for it would
|
|
211
|
+
drift.
|
|
319
212
|
|
|
320
213
|
## References
|
|
321
214
|
|
|
@@ -324,6 +217,6 @@ not authorize or gate dispatch.
|
|
|
324
217
|
|
|
325
218
|
## Reviewer checklist — `scale-schedule-sound`
|
|
326
219
|
|
|
327
|
-
|
|
220
|
+
Creator-facing review guidance (the generic rubric-only gate kind was retired at the flexible-intelligence hard cut; nothing executes this checklist):
|
|
328
221
|
|
|
329
|
-
Judge whether
|
|
222
|
+
Judge whether a WAVE ran the build soundly — how MANY tasks were scheduled, run concurrently, and reconciled, WITHOUT straying into how ONE task dispatches (the build-dispatch playbook's checklist) or how the plan was decomposed (the build-decompose playbook's). Assess six invariants and mark each PASS / CONCERN / GAP with a one-line evidence note. (1) WAVE READINESS — every task the wave dispatched had ALL its declared prerequisites already SUCCEEDED (dispatched-and-verified), not merely attempted; a task dispatched while a prerequisite was un-run, in-flight, or dispatched-and-FAILED is a GAP. (2) WIDTH — the wave ran no more coding runs at once than the application's build parallelism; more is a GAP, and a width chosen by the method rather than by the person's setting is a CONCERN. (3) OVERLAP ACCOUNTED FOR — the runs shared one worktree by design, so overlap is expected; each run that overlapped another carries a `concurrency` record naming the runs and paths, and a change-set dominated by BASELINE_DIRTY_AMBIGUOUS files is resolved against that record. An overlap the reviewer cannot account for from the records is a CONCERN; a run accepted as clean while its record says `interferenceSuspected` is a GAP. (4) REPAIR — after the runs settled, the wave's end-of-run commit names the runs whose writes it carries, and every completed run whose product a sibling overwrote was re-run alone (or is shown waiting for a person once its re-runs were spent); a lost product with no repair and no record is a GAP. (5) FAILURE DISPOSITION ACROSS SIBLINGS + DOWNSTREAM — a failed / timed-out task kept its captured change-set flagged for human triage (keep_and_flag), its siblings in the wave were left to complete, and its DEPENDENTS stayed out of later frontiers until it was triaged and re-dispatched successfully; a failed task whose dependents were dispatched anyway, or a failure silently reverted / left un-recorded, is a GAP. (6) GENERATION STEPS + BOUNDARY — the deterministic companion-generation steps ran through their companion endpoints at their input-ready point, at most once per wave, and never as a coding-agent dispatch (a CONCERN otherwise); the orchestration did not re-decompose the plan, re-specify the per-task contract, or author code itself (a CONCERN otherwise).
|